Martin, The lab, who developed the GUIDE-seq protocol, just published a python tool called guideseq in Nature Biotechnology, which is too similar to our Bioconductor package name GUIDEseq. I am wondering if there is an easy way to change the package name, or perhaps give it an alias to point to the same package. Thanks! Best regards, Julie
[Bioc-devel] inquiry about possibility of package name change
5 messages · Martin Morgan, Dario Strbenac, Zhu, Lihua (Julie)
On 07/01/2016 10:45 AM, Zhu, Lihua (Julie) wrote:
Martin, The lab, who developed the GUIDE-seq protocol, just published a python tool called guideseq in Nature Biotechnology, which is too similar to our Bioconductor package name GUIDEseq. I am wondering if there is an easy way to change the package name, or perhaps give it an alias to point to the same package. Thanks!
Changing package names is strongly discouraged, since the internet tends to have a strong memory. However, the recommended approach is like deprecating a function, as described at http://bioconductor.org/developers/how-to/deprecation/ In the current devel, we would clone your current code base to XXX, and add .onLoad <- function(...) { warning("Package 'GUIDEseq' is deprecated, use package 'XXX'") } in the next devel cycle, you'd change that to .onLoad <- function(...) { stop("Package 'GUIDEseq' is defunct, use package 'XXX'") } and remove all code other code / documentation from GUIDEseq. In the devel cycle after that, we'd remove GUIDEseq from the manifest. Your users would see the deprecation warning after the next release (October?) and would have to switch by the release after that (March?). Martin
Best regards, Julie
This email message may contain legally privileged and/or...{{dropped:2}}
Thanks Martin! Best, Julie
On Jul 1, 2016, at 10:28 PM, Martin Morgan <martin.morgan at roswellpark.org> wrote:
On 07/01/2016 10:45 AM, Zhu, Lihua (Julie) wrote: Martin, The lab, who developed the GUIDE-seq protocol, just published a python tool called guideseq in Nature Biotechnology, which is too similar to our Bioconductor package name GUIDEseq. I am wondering if there is an easy way to change the package name, or perhaps give it an alias to point to the same package. Thanks!
Changing package names is strongly discouraged, since the internet tends to have a strong memory. However, the recommended approach is like deprecating a function, as described at http://bioconductor.org/developers/how-to/deprecation/ In the current devel, we would clone your current code base to XXX, and add .onLoad <- function(...) { warning("Package 'GUIDEseq' is deprecated, use package 'XXX'") } in the next devel cycle, you'd change that to .onLoad <- function(...) { stop("Package 'GUIDEseq' is defunct, use package 'XXX'") } and remove all code other code / documentation from GUIDEseq. In the devel cycle after that, we'd remove GUIDEseq from the manifest. Your users would see the deprecation warning after the next release (October?) and would have to switch by the release after that (March?). Martin
Best regards, Julie
This email message may contain legally privileged and/or confidential information. If you are not the intended recipient(s), or the employee or agent responsible for the delivery of this message to the intended recipient(s), you are hereby notified that any disclosure, copying, distribution, or use of this email message is prohibited. If you have received this message in error, please notify the sender immediately by e-mail and delete this email message from your computer. Thank you.
2 days later
Hello, If your software was released first, why would you want to change its name ? It would make more sense to write to the creators of the newer software and ask them why they didn't check if someone else already used that software name before releasing their software with an identical name to yours. -------------------------------------- Dario Strbenac PhD Student University of Sydney Camperdown NSW 2050 Australia
Thanks, Dario! That would be one way to deal with this if I had seen the other software before its Nature Biotechnology publication. FYI, we will stick to our original name if reviewers are ok with it. Best, Julie
On Jul 4, 2016, at 4:01 AM, Dario Strbenac <dstr7320 at uni.sydney.edu.au> wrote: Hello, If your software was released first, why would you want to change its name ? It would make more sense to write to the creators of the newer software and ask them why they didn't check if someone else already used that software name before releasing their software with an identical name to yours. -------------------------------------- Dario Strbenac PhD Student University of Sydney Camperdown NSW 2050 Australia
_______________________________________________ Bioc-devel at r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/bioc-devel