[Bioc-devel] Maintainers submit your SSH public keys

Thu Jul 13 12:23:03 CEST 2017

Hi,

Yes, Jason your Github username is the Github id.

I have a question about one social feature of github: the topics of a
repository. Should we tag the repositories with packages included (or
intended to be included) in Bioconductor with the tag "bioconductor" or
"biocondcutor-package"?
I am asking this because some repositories might be related to bioconductor
but they aren't a package.

Regards,

Lluís

On 13 July 2017 at 11:43, Jason Serviss <jason.serviss at ki.se> wrote:

> Hello,
>
> What exactly is ment with “Github id”? My Github username?
>
> Kind Regards,
> Jason
>
>
> On 12 Jul 2017, at 18:16, Turaga, Nitesh <Nitesh.Turaga at RoswellPark.org
> <mailto:Nitesh.Turaga at RoswellPark.org>> wrote:
>
> Hi Samuel,
>
>
> This is a great question.
>
>
> You are not required to create a Github repository for your package. But,
> if you are actively maintaining your package, and would like to take
> advantage of the social coding features and the extended Bioconductor
> community it is a really good idea.
>
>
> If you want to just maintain it on our Git server, once you have SSH
> access, you are welcome to do that as well. This is highlighted in our
> documentation https://github.com/Bioconductor/bioc_git_
> transition/blob/master/doc/scenario-11-maintain-without-github.md.
>
>
> We welcome feedback on the documentation, and FAQ section (
> https://github.com/Bioconductor/bioc_git_transition/blob/master/doc/faq.md
> )
>
>
>
> Best Regards,
>
>
> Nitesh
>
>
>
> ________________________________
> From: Samuel E Zimmerman <sezimmer at einstein.yu.edu<mailto:
> sezimmer at einstein.yu.edu>>
> Sent: Wednesday, July 12, 2017 11:49 AM
> To: Turaga, Nitesh; Ramon Diaz-Uriarte; bioc-devel at r-project.org<mailto:
> bioc-devel at r-project.org>
> Subject: RE: [Bioc-devel] Maintainers submit your SSH public keys
>
> Dear Nitesh,
>
> This may seem like an obvious question, but if we have not created a
> repository for our packages yet, should we create a GitHub repository using
> the directions here:
>
> https://github.com/Bioconductor/bioc_git_transition/blob/master/doc/
> scenario-1-svn-to-github.md
>
>
> Thank you.
>
> Best,
> Sam
> ________________________________________
> From: Bioc-devel [bioc-devel-bounces at r-project.org<mailto:
> bioc-devel-bounces at r-project.org>] on behalf of Turaga, Nitesh
> [Nitesh.Turaga at RoswellPark.org<mailto:Nitesh.Turaga at RoswellPark.org>]
> Sent: Wednesday, July 12, 2017 11:29 AM
> To: Ramon Diaz-Uriarte; bioc-devel at r-project.org<mailto:
> bioc-devel at r-project.org>
> Subject: Re: [Bioc-devel] Maintainers submit your SSH public keys
>
> Hi Ramon,
>
> This is a good question. Your key will be processed every 24 hours. If you
> have already submitted, then, you should be able to work through the
> documentation provided
> (https://github.com/Bioconductor/bioc_git_transition/tree/master/doc).
> Working through the documentation to check everything is in order helps
> everyone in the Bioconductor community too.
>
> Or a simple way to check is, make a change in your cloned package, ideally
> it is a �version bump� in the DESCRIPTION file. Then, try to git add �>
> commit �> push the change up to the new git server. These steps are given
> in our documentation,
>
> https://github.com/Bioconductor/bioc_git_transition/blob/master/doc/
> scenari
> o-11-maintain-without-github.md#clone-and-setup-the-
> package-on-your-local-m
> achine
>
>
> https://github.com/Bioconductor/bioc_git_transition/blob/master/doc/
> scenari
> o-11-maintain-without-github.md#make-and-commit-changes-to-
> your-local-repos
> itory
>
>
> We appreciate feedback on this.
>
> Best,
>
> Nitesh
>
> P.S We have already processed your previous submission. Don�t worry, we
> don�t process duplicate submissions.
>
>
> Dear Nitesh,
>
> I just filled it up again, though I think I did fill up and hit
> send/submit
> a few days ago. Is there a way for me to confirm it has worked?
>
>
> Best,
>
>
> R.
>
>
>
> On Wed, 12-07-2017, at 14:50:14, Turaga, Nitesh
> <Nitesh.Turaga at RoswellPark.org<mailto:Nitesh.Turaga at RoswellPark.org>>
> wrote:
> Hi Maintainers,
>
> Please submit your (SSH public key or GitHub id) and SVN id in this
> google
> form https://goo.gl/forms/eg36vcBkIUjfZfLe2. It will only take a minute
> [https://lh6.googleusercontent.com/aTIh4yWF4TsFYR95qIA_
> lBuCgvLJ88Q4WzDmdBuie6ndQirxWI0jhfRBF7eO-n3W6SE=w1200-h630-p]<
> https://goo.gl/forms/eg36vcBkIUjfZfLe2>
>
> git / svn transition: ssh keys<https://goo.gl/forms/eg36vcBkIUjfZfLe2>
> goo.gl<http://goo.gl/>
> Use this form to link your existing svn credentials with access
> permissions to the new Bioconductor git repository. To do this, we need an
> ssh public key. You might have added these to github, see
> https://github.com/your-github-id.keys. Alternatively, you may provide
> the ssh public key directly, e.g., copy-pasting ~/.ssh/id_rsa.pub. To
> generate ssh key pairs, see https://help.github.com/
> articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/
>
>
>
> or
> less.
>
> This is a crucial step to the transition, which is going to happen soon.
> You will be able to test/complain/learn about the new git server during
> Bioc2017 (Boston - July 26th onwards), and will be good to go from the
> day
> of transition. It is critical for maintainers who are actively
> maintaining
> their package on Bioconductor.
>
> We have received very few SSH public keys so far from the 1300+
> maintainers in Bioconductor.
>
>
> Best Regards,
>
> 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.
> _______________________________________________
> Bioc-devel at r-project.org<mailto:Bioc-devel at r-project.org> mailing list
> https://stat.ethz.ch/mailman/listinfo/bioc-devel
> Bioc-devel Info Page - stat.ethz.ch<http://stat.ethz.ch/><
> https://stat.ethz.ch/mailman/listinfo/bioc-devel>
> stat.ethz.ch<http://stat.ethz.ch/>
> Your email address: Your name (optional): You may enter a privacy password
> below. This provides only mild security, but should prevent others from
> messing with ...
>
>
>
>
>
> --
> Ramon Diaz-Uriarte
> Department of Biochemistry, Lab B-25
> Facultad de Medicina
> Universidad Aut�noma de Madrid
> Arzobispo Morcillo, 4
> 28029 Madrid
> Spain
>
> Phone: +34-91-497-2412
>
> Email: rdiaz02 at gmail.com<mailto:rdiaz02 at gmail.com>
>      ramon.diaz at iib.uam.es<mailto:ramon.diaz at iib.uam.es>
>
> http://ligarto.org/rdiaz
> Ramon Diaz-Uriarte - ligarto.org<http://ligarto.org/><
> http://ligarto.org/rdiaz>
> ligarto.org<http://ligarto.org/>
> Home page of Ramon Diaz-Uriarte ... Ram�n D�az-Uriarte. I am an Associate
> Professor at the Department of Biochemistry, Universidad Aut�noma de Madrid
> (UAM).
>
>
>
>
>
>
> 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 at r-project.org<mailto:Bioc-devel at r-project.org> mailing list
> https://stat.ethz.ch/mailman/listinfo/bioc-devel
> Bioc-devel Info Page - stat.ethz.ch<http://stat.ethz.ch/><
> https://stat.ethz.ch/mailman/listinfo/bioc-devel>
> stat.ethz.ch<http://stat.ethz.ch/>
> Your email address: Your name (optional): You may enter a privacy password
> below. This provides only mild security, but should prevent others from
> messing with ...
>
>
>
>
>
> 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.
> [[alternative HTML version deleted]]
>
> _______________________________________________
> Bioc-devel at r-project.org<mailto:Bioc-devel at r-project.org> mailing list
> https://stat.ethz.ch/mailman/listinfo/bioc-devel
>
>
>         [[alternative HTML version deleted]]
>
> _______________________________________________
> Bioc-devel at r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/bioc-devel
>

	[[alternative HTML version deleted]]