This question is actually pretty complicated and involves matters of
copyright and academic credit, which are two different things. In general
you cannot take code from the internet and republish it under your own name.
It sounds like you want to include something substantial (as opposed to say
a
This is the repository: https://github.com/Vivianstats/scImpute
*Ana Carolina Leote*
*MSc. Biological Engineering*
*PhD student at the Cologne Graduate School for Ageing Research*
*Cellular networks and systems biology (Beyer group), **CECAD Research
Center*
It is wise to be careful here. If we don't know the provenance of the code
in github it might actually be someone else's.
It reminds me of the Numerical Recipes events, in which folks redistributed
proprietary code without permission.
What repo are we talking about anyway?
On Wed, Feb 10, 2021
I don�t know what the legal requirement is.
As a human if I hadn�t given explicit consent I�d like to be asked. And if I
had used someone else�s code I�d like it to be transparent that my use was
legitimate, and a private exchange of email between me and the other individual
consenting to use
My motivation to include this package is that my own package includes, but
is not limited to, an ensemble of different packages that attempt to solve
the same problem, besides my own solution, since I did some work showing
they all have their pros and cons. At the moment my package does not
Have you looked at some of the scRNA packages that are already on Bioconductor
to see if there is similar functionality in an existing package already
accepted?
You can search for packages that have scRNA in the package name or title on
this page:
If the package is already widely used, then I guess it provides useful
functionality, and so your package doesn't have to provide that functionality,
so perhaps a better solution is to refer users to the unsupported package in
your vignette??
What you say about not being maintained in over a
> Il giorno 10feb2021, alle ore 14:31, Kern, Lori
> ha scritto:
>
> Have you reached out to the maintainer of the github package to see if they
> would plan on submitting to CRAN or Bioconductor?
> If they do not, you could see if they are okay with you including the code
> in your
Dear all,
Thank you so much for the great input and to Wolfgang for raising these
points.
I am afraid I gain more than I lose by including this particular package,
as it is somewhat commonly used in the scRNA-seq community. It seems not to
be maintained in over a year, however, judging by the
On Wed, Feb 10, 2021 at 8:32 AM Kern, Lori
wrote:
> Have you reached out to the maintainer of the github package to see if
> they would plan on submitting to CRAN or Bioconductor?
> If they do not, you could see if they are okay with you including the
> code in your package and then clearly
Have you reached out to the maintainer of the github package to see if they
would plan on submitting to CRAN or Bioconductor?
If they do not, you could see if they are okay with you including the code in
your package and then clearly indicate their authorship in the man pages and by
giving
Dear all,
I am a package maintainer and would like to add a functionality that
depends on another package which is not available in bioconductor, only via
GitHub. I would like to make the necessary changes in order to be able to
use their code in my package. Can anyone point me towards the best
12 matches
Mail list logo
