Release a beta tag once the API has stabilised a bit more

[robbieaverill]

So that TOTP can pin to the v2 release line

[Firesphere]

So that TOTP can pin to the v2 release line

I think we had a discussion, and make the SS4 version of bootstrap V4, and the SS3 version V3, same as the recipe version bump happened some time ago.
Otherwise, the SS3 version would have a newer version number than the SS4 one, which would be a bit strange

[SimoTod]

@Firesphere @ScopeyNZ Do you know when the stable version will be released? Thanks

[ScopeyNZ]

There's a team here at SilverStripe Ltd. that's about to pick up work on a few MFA options. Development is set to pick up soon. There's a bit of plan of things to do before we can tag a stable for MFA sub-modules to consume:

• We want to make MFA submodules version agnostic - ie. you can install the same version of your TOTP (for example) module regardless of the SilverStripe version you are using
• We want to ensure that the advertised features of this module are working well and are secure (backup codes, resets, etc)
• Need to assert that there are extension points for additions like the auditor module etc.

Are you interested in helping to contribute? Were you thinking about creating an MFA module?

[SimoTod]

I'd be happy to help. I'm a full time employee, though, so I can dedicate a limited amount of time to the project.
I'm not building another MFA module but I'm currently working on a project were I'd like to add TOTP and I was thinking about using elliot-sawyer/totp-authenticator (I think you contributed to that project as well). At the moment, I had to lock my composer to specific commits for both dependencies and add aliases to avoid BC. I'd be happy to have a chat soon to understand your dev workflow and see where I could help. I'm in a different timezone though (I live in UK) so we need to arrange a time which would suit both of us.