Skip to content
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

submit new package #12

Open
mengchen18 opened this issue Sep 8, 2021 · 1 comment
Open

submit new package #12

mengchen18 opened this issue Sep 8, 2021 · 1 comment

Comments

@mengchen18
Copy link

Dear @lgatto, @sgibb and @jorainer,

First thanks for creating and maintaining the rformassspectrometry project. I would like to ask how I can submit a new package to the project, is there a guideline like in Bioconductor?

More information: I have implemented a pipeline to process untargeted MS/MS-based metabolomics data, from raw data reading to metabolite annotation (MS1 and MS2 levels) to statistical analysis of expression matrix. The package is also focused on the interactive visualization of annotation and statistical results. The MS data processing is mainly based on the xcms package. The package works by itself at the moment. But I guess some of the functions in my package have also been implemented in other packages of the project, it would be great in the future development I can make more use of the features from them. Of course, I would also be happy to transfer some of the functions in my packages to other packages if they are more functionally related. I hope to provide users a more uniform interface by doing this (before submitting it to the Bioconductor).

Thanks for your advice in advance.

best,
Chen

@lgatto
Copy link
Member

lgatto commented Sep 8, 2021

Dear @mengchen18

Thank you for your interest. We typically don't take package submission, but rather co-develop packages as a team, including members of the core team (i.e. myself, @sgibb and @jorainer), as well as other collaborators (such as @michaelwitting). One important motivation of the project in general, is for individual packages to tackle specific problems, insure interoperability between packages, and put considerable emphasis on code testing and documentation. These are some of the ground rule to package inclusion. And as I said, packages are generally developed collaboratively, to make sure that all these points are addressed.

If you believe that your contribution addresses these, feel free to share more details and a link to the package's Github repo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants