Skip to content

[Bioc-devel] write access to RTNduals and RTNsurvival

6 messages · Vinicius Saraiva Chagas, m castro, Turaga, Nitesh +1 more

#
Hi Mauro

Please always forward your git questions to bioc-devel. There is more than one person handling the issues about git. 

RTNsurvival, ? Clari Groeneveld is the maintainer hence you don?t have write access. 

RTNduals ? Vinicius Chagas is the listed maintainer on our system. 

This issue is because our SVN system also had only Clari and Vinicius as primary maintainers. I am adding them in my reply as well, and I?m guessing they are both fine with me adding you to our system for these packages?

Best,

Nitesh
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.
#
Hello Nitesh,

Thank you very much for the support. I totally agree with that.

Best,
Vinicius

On Mon, Oct 2, 2017 at 10:44 AM Turaga, Nitesh <
Nitesh.Turaga at roswellpark.org> wrote:

            

  
  
#
Hi Nitesh,

Thank you.

In the submission of these packages, Vinicius and Clarice had included
all the team as maintainers (I can confirm in the packages' homepages,
below), not sure why it did not work at that occasion.

http://bioconductor.org/packages/RTNduals/

http://bioconductor.org/packages/RTNsurvival/

Best,

Mauro

On 2 October 2017 at 10:50, Vinicius Saraiva Chagas
<chagas.vis at gmail.com> wrote:
#
Hi Mauro,

You should have access to those packages now. 

Please let me know if it has worked.

Best,

Nitesh
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.
#
On 10/02/2017 09:57 AM, m castro wrote:
We encourage just a single maintainer, so that we do not have to engage 
in 'whack-a-maintainer' when issues come up.

For this reason, only a single person is given write access, unless 
other permissions are explicitly requested. If your package is 
maintained in github and then pushed to Bioconductor, it is easy for one 
person to serve as maintainer and regulate who else contributes to the 
project through github collaborators or pull requests; this kind of 
administrative structure is likely both more flexible and robust for 
managing group contributions.

Martin
This email message may contain legally privileged and/or...{{dropped:2}}
#
Thank you Martin, that makes sense to me. In this case, the next
package that my lab contribute to bioc I will probably submit it
myself. The structure of a laboratory involves team members coming and
going, and we need to ensure continuous maintenance. This is certainly
an issue that is not related to bioc, but I presume other PIs may
experience similar scenarios.

Mauro
On 2 October 2017 at 11:04, Martin Morgan <martin.morgan at roswellpark.org> wrote: