On Nov 15, 2019, at 9:30 AM, Julien Wollbrett <julien.wollbrett at unil.ch> wrote:
Hello Nitesh,
Thank you for your answer.
I added some functionalities to the BgeeCall package that are not compatible to a workflow approach.
It is now possible to run some steps outside of the initial workflow, to download files from different locations, to reuse data generated by the user or already processed by the Bgee team, etc.
Furthermore BgeeCall does not only reuse already existing bioconductor packages and combine them to create a workflow. It corresponds to a new approach allowing to generate present/absent gene expression calls from RNA-Seq libraries without using an arbitrary cutoff.
I would be very happy if you can help me moving it to the software section.
Best,
Julien
Le 15.11.19 ? 11:59, Turaga, Nitesh a ?crit :
Hi,
Changing the BiocViews section in the DESCRIPTION file doesn't change your package from a workflow package to a software package.
There are fundamental differences between workflow packages and software packages in the way we handle them within Bioconductor. Could you tell us why you'd like to change it from a workflow to a software package?
The Bioc team, would have to assist in moving it to the software section.
Best,
Nitesh
?On 11/15/19, 4:46 AM, "Bioc-devel on behalf of Julien Wollbrett" <bioc-devel-bounces at r-project.org on behalf of julien.wollbrett at unil.ch> wrote:
Hello,
I am the maintainer of the BgeeCall R package.
In bioconductor 3.9 my package was registered as a workflow package.
I modified my DESCRIPTION file before the release 3.10 in order to move
the package to the software section hopping for it to automatically move
after the new release. Unfortunately it did not work.
Could you please tell me how to do to move BgeeCall to the software section?
Thank you,
Julien