Many thanks Valerie for the feedback! On 7 May 2018 at 15:03, Obenchain, Valerie < valerie.obench...@roswellpark.org> wrote:
> Lluis, > > A little follow up on this. When a new package is submitted, the email in > DESCRIPTION is checked against the Support Site so those 2 fields are in > sync for new packages ... at least for awhile. Right now we don't have > plans to sync the App with DESCRIPTION and the Support Site but it may be > considered in the future. > > Valerie > > > > On 04/19/2018 07:59 AM, Obenchain, Valerie wrote: > > Hi Lluis, > > We (or at least I) had not considered linking the profile in the > credentials app with the profile in the Support Site and currently they are > not aware of each other. The email in DESCRIPTION was used to get some > emails for the credentials app but it is not the case that an email change > in the app will propagate to DESCRIPTION. > > We do require package maintainers to be registered on the Support Site in > order to submit a package but I'm not sure if this email is checked against > the DESCRIPTION. > > I see what you mean by having this information in 3 places, DESCRIPTION > file, credentials app and Support Site. I think the 'if' and 'how' of > connecting these pieces needs some thought. I'll discuss with the group at > our next meeting and will follow up here. > > Thanks for bringing this up. > > Valerie > > > > > On 04/19/2018 06:35 AM, Lluís Revilla wrote: > > Hi all, > > I have a couple of doubts related to the new app. > > I've seen that one can update mail, and github id, and add new keys > (Nice!). However I couldn't find if this account will be somehow linked to > the user profile in the support site. Are there any plans in this direction? > At the moment the email of the maintainer of a package should be > registered in the support site, which is the same one used for the app. > When someone updates the email in the app is it updated in other sites of > Bioconductor? Will the email of the Description files of the packages and > the account in the support site be updated? > > Many thanks, > > Lluís > > > On 18 April 2018 at 17:13, Obenchain, Valerie <Valerie.Obenchain@ > roswellpark.org> wrote: > >> The Web App for managing SSH keys is now available at >> >> https://git.bioconductor.org/BiocCredentials/ >> >> Accounts have been created for all package maintainers. Note the central >> identifier, i.e., how you login is your email. This email was taken from >> the DESCRIPTION of your package or the Google Sheet if you registered a key >> there. >> >> When you first visit the App you'll need to activate your account. An >> activation link will be sent to your email. Once your account is activated >> you can login. Trying to login without activation will lead to an error. >> >> Let us know if you have any questions or problems. >> >> >> >> On 04/18/2018 05:56 AM, Obenchain, Valerie wrote: >> This transition will start at 9am EST today. We'll post back when it's >> done. >> >> Valerie >> >> >> On 04/17/2018 10:27 AM, Obenchain, Valerie wrote: >> >> Hi developers, >> >> Tomorrow we are bringing a web app online to help with the management of >> SSH keys. The app will replace the Google Sheet currently used to add keys. >> Through the web interface you'll be able to add keys and change your email >> or github username. There is also an option to see what packages you have >> access to. >> >> Using the app is not a requirement. It's intended to help package authors >> get setup with keys and access to their package in the Bioconductor git >> repository. Those of you already set up with keys and access may never need >> to use it. >> >> Tomorrow, April 18, we'll have downtime from 9-11am EST while we take >> down the Google Sheet and bring up the app. >> >> Thanks. >> >> Valerie and 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. >> [[alternative HTML version deleted]] >> >> _______________________________________________ >> Bioc-devel@r-project.org<mailto: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. >> [[alternative HTML version deleted]] >> >> _______________________________________________ >> 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. > [[alternative HTML version deleted]] _______________________________________________ Bioc-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/bioc-devel