OK, it sounds like there is enough that this isn't a blocker - and even if it were, the pace of process changes is probably slow enough to cope anyway. So the question is still whether there are members who really can't work with github. I still haven't seen any effort to determine that systematically, which I think we should undertake both as sanity check and courtesy.

I'll send a mail with a clear subject, and if we don't hear that there are problems I'll move forward with this…

05.01.2017, 09:35, "Terence Eden" <terence.eden@digital.cabinet-office.gov.uk>:

Github supports TOTP or SMS or Printed recovery codes

https://help.github.com/articles/about-two-factor-authentication/

So you can have an authenticator app on your phone, tablet, watch...

You're not tied in to receiving SMS for your login codes.

On 5 January 2017 at 06:36, <chaals@yandex-team.ru> wrote:

03.01.2017, 19:14, "Norman Walsh" <Norman.Walsh@marklogic.com>:
> Terence Eden <terence.eden@digital.cabinet-office.gov.uk> writes:
>> Our department requires that internal users have 2FA enabled.
>
> That seems like a plausible requirement for write access to me.

It does. Except that without a solution for easily swapping the number for second factor message nor free SMS everywhere, it's likely to be a reason for not making merges when I'm not at home. Which is fairly often.

cheers

--
Charles McCathie Nevile - standards - Yandex
chaals@yandex-team.ru - - - Find more at http://yandex.com

Terence Eden

Open Standards Lead

+44 7717 512 963

Government Digital Service

Charles McCathie Nevile - standards - Yandex
chaals@yandex-team.ru - - - Find more at http://yandex.com