Sure. There's no rush at all; in fact, this is probably a decent topic for our next face-to-face.
> On Sep 14, 2016, at 2:46 PM, r...@open-mpi.org wrote: > > I’d want to _fully_ understand the implications before forcing something on > everyone that might prove burdensome, especially when it “solves” a currently > non-existent problem > > >> On Sep 14, 2016, at 11:43 AM, Jeff Squyres (jsquyres) <jsquy...@cisco.com> >> wrote: >> >> On Sep 14, 2016, at 2:40 PM, r...@open-mpi.org wrote: >>> >>>> - Code reviews got better / more organized >>>> - Some project management tools now available >>>> - We can enforce the use of 2-factor authentication >>> >>> Please don’t do that... >> >> Certainly wouldn't do the last one without talking it through with the >> community first. >> >> Is there a reason not to do it? It's not 2-factor on every push -- it's >> 2-factor for web logins only, gmail-style (periodically prompt for 2nd >> factor on trusted machines, yadda yadda yadda) >> >> -- >> Jeff Squyres >> jsquy...@cisco.com >> For corporate legal information go to: >> http://www.cisco.com/web/about/doing_business/legal/cri/ >> >> _______________________________________________ >> devel mailing list >> devel@lists.open-mpi.org >> https://rfd.newmexicoconsortium.org/mailman/listinfo/devel > > _______________________________________________ > devel mailing list > devel@lists.open-mpi.org > https://rfd.newmexicoconsortium.org/mailman/listinfo/devel -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/ _______________________________________________ devel mailing list devel@lists.open-mpi.org https://rfd.newmexicoconsortium.org/mailman/listinfo/devel
