-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IdentifiHR #3579
Comments
Hi @ashleyweir1 Thanks for submitting your package. We are taking a quick The DESCRIPTION file for this package is:
|
I have updated the DESCRIPTION file and made necessary changes. The updated version is now available on GitHub with version 0.99.1. Please consider the new version for review. Thank you! |
Please adapt to also use standard Bioconductor object for gene expression, SummarizedExperiment |
Hi, I have updated my main branch so that the package can also use SummarizedExperiment objects. However, I want to double check - do I have access to the Bioconductor git server, to push these changes to the remote branch? Thank you for your help. |
at this point you do not have git access yet. We will check your github branch shortly |
In the description your license is gpl3 + file license but I only see the gpl3 Could you also add a section in the vignette to show the use of the Bioconductor class. And update the man pages/documentation to indicate as such |
Hi, |
Your vignette uses a data.frame of "rawCounts" not a SummarizedExperiment object? Did you not push to the github repo? Your man pages mention SummarizedExperiment but again use data.frame. Please add a SummarizedExperiment example in the vignette -- there are lots of available existing SummarizedExperiments in other packages or ExperimentHub if needed. |
Hi, |
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]'
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 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:
months, for bug fixes.
(optionally via GitHub).
For questions/help about the submission process, including questions about
the output of the automatic reports generated by the SPB (Single Package
Builder), please use the #package-submission channel of our Community Slack.
Follow the link on the home page of the Bioconductor website to sign up.
The text was updated successfully, but these errors were encountered: