We could force users to have the latest-and-greatest code
as of release of the Authenticator, but it would be more
courteous to require the oldest version that we could
support and then change these version requirements on
major-point releases.
Partially completes #7 - don't know how much more
work is needed after this. I think it's ok to go down
to the "most major" point version in SemVer
(so if there has been a major release, down to
XXX.0.0, if there has been a minor release,
down to XX.YY.0, if there has been a bugfix,
down to XX.YY.ZZ).
Developer Certificate of Origin Version 1.1
Copyright (C) 2004, 2006 The Linux Foundation and its contributors. 660 York Street, Suite 102, San Francisco, CA 94110 USA
Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
Developer's Certificate of Origin 1.1
By making a contribution to this project, I certify that:
(a) The contribution was created in whole or in part by me and I have the right to submit it under the open source license indicated in the file; or
(b) The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate open source license and I have the right under that license to submit that work with modifications, whether created in whole or in part by me, under the same open source license (unless I am permitted to submit under a different license), as indicated in the file; or
(c) The contribution was provided directly to me by some other person who certified (a), (b) or (c) and I have not modified it.
(d) I understand and agree that this project and the contribution are public and that a record of the contribution (including all personal information I submit with it, including my sign-off) is maintained indefinitely and may be redistributed consistent with this project or the open source license(s) involved.
We could force users to have the latest-and-greatest code as of release of the Authenticator, but it would be more courteous to require the oldest version that we could support and then change these version requirements on major-point releases.
Partially completes #7 - don't know how much more work is needed after this. I think it's ok to go down to the "most major" point version in SemVer (so if there has been a major release, down to XXX.0.0, if there has been a minor release, down to XX.YY.0, if there has been a bugfix, down to XX.YY.ZZ).
Signed-off-by: Tom Kelley distortedsignal@gmail.com