bioc-issue-bot
commented
6 months ago Hi @LiNk-NY
Thanks for submitting your package. We are taking a quick look at it and you will hear back from us soon.
The DESCRIPTION file for this package is:
Package: AnVILBase
Title: Generic functions for interacting with the AnVIL ecosystem
Version: 0.99.22
Authors@R: c(
person("Marcel", "Ramos", , "marcel.ramos@roswellpark.org",
c("aut", "cre"), c(ORCID = "0000-0002-3242-0582")),
person("Martin", "Morgan", , , c("aut", "ctb"),
c(ORCID = "0000-0002-5874-8148")),
person("NIH NHGRI U24HG004059", role = "fnd")
)
Description: Provides generic functions for interacting with the AnVIL
ecosystem. Packages that use either GCP or Azure in AnVIL are built on top
of AnVILBase. Extension packages will provide methods for interacting with
other cloud providers.
License: Artistic-2.0
Imports:
httr,
httr2,
dplyr,
jsonlite,
methods,
tibble
Suggests:
AnVILAz,
AnVILGCP,
BiocStyle,
knitr,
rmarkdown,
testthat (>= 3.0.0),
tinytest
biocViews: Software, Infrastructure
URL: https://github.com/Bioconductor/AnVILBase
BugReports: https://github.com/Bioconductor/AnVILBase/issues
VignetteBuilder: knitr
Encoding: UTF-8
Roxygen: list(markdown = TRUE)
RoxygenNote: 7.3.1
Date: 2024-03-23
Config/testthat/edition: 3
Collate:
'AnVILBase-generics.R'
'AnVILBase-methods.R'
'AnVILBase-package.R'
'Platform-class.R'
'Response.R'
'avdata-generics.R'
'avdata-methods.R'
'avnotebooks-generics.R'
'avnotebooks-methods.R'
'avtable-generics.R'
'avtable-methods.R'
'avworkflow-generics.R'
'avworkflow-methods.R'
'avworkspace-generics.R'
'avworkspace-methods.R'
'cloud_platform.R'
'utilities.R'
LiNk-NY
lshep
Kayla-Morrell
Update the following URL to point to the GitHub repository of the package you wish to submit to 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 Package Naming Policy and acknowledge Bioconductor may retain use of package name.
[x] I understand that a minimum requirement for package acceptance is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. Passing these checks does not result in automatic acceptance. The package will then undergo a formal review and recommendations for acceptance regarding other Bioconductor standards will be addressed.
[x] My package addresses statistical or bioinformatic issues related to the analysis and comprehension of high throughput genomic data.
[x] I am committed to the long-term maintenance of my package. This includes monitoring the support site for issues that users may have, subscribing to the bioc-devel mailing list to stay aware of developments in the Bioconductor community, responding promptly to requests for updates from the Core team in response to changes in R or underlying software.
[x] I am familiar with the Bioconductor code of conduct and agree to abide by it.
I am familiar with the essential aspects of Bioconductor software management, including:
For questions/help about the submission process, including questions about the output of the automatic reports generated by the SPB (Single Package Builder), please use the #package-submission channel of our Community Slack. Follow the link on the home page of the Bioconductor website to sign up.