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.mor...@roswellpark.org> wrote: > On 10/02/2017 09:57 AM, m castro 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. > > > 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 > >> >> http://bioconductor.org/packages/RTNduals/ >> >> http://bioconductor.org/packages/RTNsurvival/ >> >> Best, >> >> Mauro >> >> On 2 October 2017 at 10:50, Vinicius Saraiva Chagas >> <chagas....@gmail.com> wrote: >>> >>> 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.tur...@roswellpark.org> wrote: >>>> >>>> >>>> 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 >>>> >>>> >>>> >>>>> On Oct 2, 2017, at 9:29 AM, Nitesh <nitesh.tur...@gmail.com> wrote: >>>>> >>>>> >>>>> >>>>> ---------- Forwarded message --------- >>>>> From: m castro <mauro.a.cas...@gmail.com> >>>>> Date: Mon, 2 Oct 2017 at 09:13 >>>>> Subject: Re: write access to RTNduals and RTNsurvival >>>>> To: Obenchain, Valerie <valerie.obench...@roswellpark.org> >>>>> Cc: Clarice Groeneveld <clari.groenev...@gmail.com>, Vinicius Saraiva >>>>> Chagas <chagas....@gmail.com>, Nitesh <nitesh.tur...@gmail.com> >>>>> >>>>> >>>>> Hi Valerie, >>>>> >>>>> I just thought the subject would not be of interest to a large list of >>>>> bioc developers. But yes, thank you very much for forwarding to >>>>> Nitesh. >>>>> >>>>> Regards, >>>>> >>>>> Mauro >>>>> >>>>> >>>>> On 2 October 2017 at 09:36, Obenchain, Valerie >>>>> <valerie.obench...@roswellpark.org> wrote: >>>>>> >>>>>> Hi Maruo, >>>>>> >>>>>> Was there a particular reason you didn't write to >>>>>> bioc-devel@r-project.org? >>>>>> That's where all svn ->git transition questions are being answered and >>>>>> it's >>>>>> much easier to manage than forwarding personal emails. >>>>>> >>>>>> Nitesh and Martin have been handling the svn -> git transition and >>>>>> I've cc'd >>>>>> Nitesh on this message. @Nitesh, can you please help Mauro? >>>>>> >>>>>> Thanks. >>>>>> Val >>>>>> >>>>>> >>>>>> >>>>>> On 09/29/2017 04:02 PM, m castro wrote: >>>>>> >>>>>> Dear Valerie, >>>>>> >>>>>> I am sorry for writing this email directly to you (not via >>>>>> r-project.org mailing list). >>>>>> >>>>>> It is related to write access to two packages of my group (RTNduals >>>>>> and RTNsurvival). I am one of the active maintainers of these >>>>>> packages, but it seems I no-longer have write access via git. Given >>>>>> that I've successfully concluded the migration process (from svn to >>>>>> git) for other packages (e.g. RTN, RedeR and geneplast), then I >>>>>> decided I should contact you for this help. >>>>>> >>>>>> Here is my GitHub ID and contact information at the packages' >>>>>> homepage. >>>>>> >>>>>> # GitHub id: castromaa >>>>>> # Bioc maintainer contact: Mauro A. A. Castro <mauro.a.castro at >>>>>> gmail.com> >>>>>> >>>>>> For reference, please see below the message when I try to push >>>>>> RTNduals via >>>>>> git: >>>>>> >>>>>> $ git push origin master >>>>>> FATAL: W any packages/RTNduals m.castro DENIED by fallthru (or you >>>>>> mis-spelled the reponame) >>>>>> fatal: Could not read from remote repository. >>>>>> Please make sure you have the correct access rights >>>>>> and the repository exists. >>>>>> >>>>>> If possible, there is another member of my group that is facing the >>>>>> same problem (Clarice Groeneveld). She is also an active maintainer of >>>>>> RTNduals (as indicated at the package's homepage): >>>>>> >>>>>> # GitHub id: csgroen >>>>>> # Bioc maintainer contact: Clarice Groeneveld <clari.groeneveld at >>>>>> gmail.com> >>>>>> >>>>>> Please let me know if I need to provide any additional information. >>>>>> >>>>>> Best, >>>>>> >>>>>> Mauro >>>>>> >>>>>> --- >>>>>> >>>>>> Prof. Mauro Castro, MD, PhD >>>>>> Bioinformatics & Systems Biology Lab >>>>>> Polytechnic Center >>>>>> Federal University of Parana - UFPR >>>>>> Rua Alcides Vieira Arcoverde, 1225 >>>>>> Curitiba - PR 81520-260 - Brazil >>>>>> >>>>>> e-mail: mauro.cas...@ufpr.br / mauro.a.cas...@gmail.com >>>>>> phone: +55-41-33614906 >>>>>> skype: mauro.a.castro >>>>>> http://lattes.cnpq.br/6484877487662355 >>>>>> >>>>>> >>>>>> >>>>>> 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. >>>>> >>>>> -- >>>>> Nitesh Turaga >>>> >>>> >>>> >>>> >>>> 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. >> >> >> _______________________________________________ >> Bioc-devel@r-project.org mailing list >> https://stat.ethz.ch/mailman/listinfo/bioc-devel >> > > > 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. _______________________________________________ Bioc-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/bioc-devel
