You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Consider adding a Github sign in button on the login page to be able to track developer's projects. The reason is that you can track how developers are using the data and the outcome can be tracked.
The text was updated successfully, but these errors were encountered:
My personal opinion would be no, usually you add this for a page that involves development, so I this is unnecessary, but I am willing to be convinced.
Given that people who don't authenticate using edugain need to be separately approved, I'd support adding support for it. The more login backends supported the easier it is for anyone to access.
I agree with driusan. Also even if users choose to use a different authentication method if users choose to supply their github username info about their public repos and stuff from could be pulled from the github API
--
Shawn T. Brown, PhD.
Associate Director of Research Software Development / CBRAIN Platform
McGill Centre for Integrative Neuroscience (MCIN)
McGill University
Montreal, QC, Canada
Email: stbrown@mcin.ca
Phone: 514-237-2960
On Mar 14, 2019, at 10:15, Dawn E. Smith ***@***.***> wrote:
I agree with driusan. Also even if users choose to use a different authentication method if users choose to supply their github username info about their public repos and stuff from could be pulled from the github API
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub <#5 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAAl9zUwDIrvxAoFDgftCrbZDBALAaTNks5vWll_gaJpZM4bhrxR>.
Consider adding a Github sign in button on the login page to be able to track developer's projects. The reason is that you can track how developers are using the data and the outcome can be tracked.
The text was updated successfully, but these errors were encountered: