Currently, CONTRIBUTING.md is not rendered by g3doc due to being in an unsupported location:

https://g3doc.corp.google.com/third_party/tink/CONTRIBUTING.md?cl=head

This fixes that problem and still works in the github context:

"To help your project contributors do good work, you can add a file with contribution guidelines to your project repository's root, docs, or .github folder."

https://help.github.com/articles/setting-guidelines-for-repository-contributors/

PiperOrigin-RevId: 197563787
GitOrigin-RevId: ac25aa8817f5e8c8cca9dcd2f64ab8891bd98bda

This will align the repository with Github's guidelines:
https://help.github.com/articles/setting-guidelines-for-repository-contributors/

Also, fix a bunch of broken/inconsistent links.

PiperOrigin-RevId: 197562610
GitOrigin-RevId: 21fc894ae8c806d24eae0dd20fe67140acb31b56

PiperOrigin-RevId: 197562584
GitOrigin-RevId: 7a6cee671c5e79c23b1a151e97396eadd5e7da82

PiperOrigin-RevId: 197062882
GitOrigin-RevId: 98b347af1a1207828560ec9701fa901de232adc8

PiperOrigin-RevId: 197023823
GitOrigin-RevId: 165a2fe66d39cc5f315643dca626ec4bd90a007f

PiperOrigin-RevId: 196880687
GitOrigin-RevId: 2dcc7441d189d63b6ea1763fbdfdc267357af67b

* Listing Guava as an explicit dependency and excluding it in all other dependencies.

* Reinstalling maven-enforcer-plugin in helloworld's pom.xml because it helps detect dependency conflicts.

* Fixing a typo in test-snapshot.sh and making it executable.

PiperOrigin-RevId: 196761172
GitOrigin-RevId: ab5097eeef801671426f26fe90e9c77cd0c5928d

I don't actually know how Maven works, but the error message indicates that we actually need Gauva.

Also I added a test to prevent this bug from happening, but I forgot to make it run =).

PiperOrigin-RevId: 196337621
GitOrigin-RevId: 3cdbc775903204bf11762c80a296c1876a9bda3f

1/ Replacing tink.Registry().Blah() with tink.Blah().

2/ Updating the APIs and code structure, following latest Java APIs. The Golang implementation was developed following Java 1.0.0, but many things have changed since then.

Next:
* Adding missing APIs such as KeysetReader, KeysetWriter.
* Removing tink.CleartextKeysetHandle().
* Adding RegistryConfig.
* Adding missing primitives such as envelope encryption, hybrid encryption, etc.
PiperOrigin-RevId: 196266656
GitOrigin-RevId: f4fe243c4501017922eaed1b464da70d3936c7ac

PiperOrigin-RevId: 196154901
GitOrigin-RevId: 8df5e4e030d9b4cc854b385f2100b37748542444

PiperOrigin-RevId: 196035052
GitOrigin-RevId: 691793e830caf9b52e77d2ed010c55271404eabb

PiperOrigin-RevId: 195874639
GitOrigin-RevId: 5e8911b5e1b21611d06a9e7355260a449cce9c65

While I'm here, refactoring hybrid factory tests.

PiperOrigin-RevId: 195738591
GitOrigin-RevId: d5719f8a243cc65213571019ff701d1a754022ea

PiperOrigin-RevId: 195732837
GitOrigin-RevId: 5c60f66c260706021ae6186b499c667978496098

PiperOrigin-RevId: 194872230
GitOrigin-RevId: 3975640de97ec4b4774d59696b9d8a5036e8551e

Doc: https://docs.google.com/document/d/1-2zhISCbvQ0kt82w3cBpKRPB6ln17ORQNCOZi9Uy3mA/edit?usp=sharing
PiperOrigin-RevId: 194640671
GitOrigin-RevId: e6bb697ae43c0e2c11d616697c13ea63c55f35f5

Also adding a stack trace if we cannot find a provider. This would allows us to know what caused encryption failures.

PiperOrigin-RevId: 194574786
GitOrigin-RevId: b0520278ab4b9b639044cc5037a0a3492a9d8537

Removing references to NIST P-224 and SHA224, which we never supported and are not used in many places.

We keep SHA1 because HMAC-SHA1 is safe and a popular MAC.

PiperOrigin-RevId: 193747110
GitOrigin-RevId: 2f657666903fc8e7c3963017a7462ac33bb7b20d

PiperOrigin-RevId: 193732292
GitOrigin-RevId: 5d7dab7e3cc335b21c2412bbc221f59905e058e6

We want to reserve the right to modify subtle.

NO_RELEASE_NOTE
NO_BUG

PiperOrigin-RevId: 193699784
GitOrigin-RevId: b36e441a29478ff9d84d4d9bea928b4a54bb5738

PiperOrigin-RevId: 193597877
GitOrigin-RevId: 2001a6d0ca410a41e6afe268a1e35d4b4a42ab9b

PiperOrigin-RevId: 193553145
GitOrigin-RevId: 137ef485e98928f3bbae67feb777896b3ef0a7e5

PiperOrigin-RevId: 193437447
GitOrigin-RevId: f9e0c3d9f88297cca3de81120836c9fc88020c6e

PiperOrigin-RevId: 193436986
GitOrigin-RevId: 61c97a3e27b5e03f3e6e23b904321a8aa27e6c6f

We're only using @Immutable, but it's not really needed.

Also cleaning up a few unused Blaze/Bazel deps.

PiperOrigin-RevId: 193430556
GitOrigin-RevId: cab4cfed7ce0c88fd61d836d4d55b4dd5ccf67e8

Also adding a roadmap, a hacking guide for Java, and updating docs.

PiperOrigin-RevId: 193400792
GitOrigin-RevId: d78fbf17c2bd90240a411ed196cf430904347847

PiperOrigin-RevId: 193369732
GitOrigin-RevId: 25f4f629da47398feb31cb0c76cf9bffe6c4e024

PiperOrigin-RevId: 193368740
GitOrigin-RevId: 4779818fadc24653c6e7f05fd7fc555bffec83af

It seems that Java 7 doesn't allow converting from List<<anonymous SenderVerifyingKeysProvider>> to List<SenderVerifyingKeysProvider>.

PiperOrigin-RevId: 193312049
GitOrigin-RevId: 8d1f7068ce34f0ed638cede52ba7e258d3f3bfb4

PiperOrigin-RevId: 193307775
GitOrigin-RevId: 6487e1b655081da5031a828f97ec98d166852c05

PiperOrigin-RevId: 193259480
GitOrigin-RevId: e312eea2405c747e630040bfa29a0935e8982aef

Java rules should depend on java_proto_library rules instead.

The Blaze team is migrating Java users of proto_library to the new
java_proto_library rule.

Remove attribute in BUILD.bazel incorrectly added by migration script.

PiperOrigin-RevId: 193255568
GitOrigin-RevId: bf8ea1d7a0e114f7bb1802dbb96ef6342c43a126

PiperOrigin-RevId: 193252341
GitOrigin-RevId: a67ebc47a8eac8ebb61f1359b8dd4fd1c1667057

PiperOrigin-RevId: 193219796
GitOrigin-RevId: d1944bd1a2d691cde2f653ae4f0cbfbc5ebc22c7

Changes:
- Renamed all references of something_cc_proto to something_portable_proto.
- Added //cc/util/protobuf_helper which creates a namespace portable_port that maps to the correct namespace.
- Replaced all deps to //net/proto2/ with //cc/util:protobuf_helper.
- Replaced all instances of the proto2:: namespace with portable_proto::
- Deleted the line 'namespace util = crypto::tink::util' because it was conflicting with //util/task/status.h (a dependency of portable_proto_lib). Also, it wasn't really used in any of the files.

Notes:
- When adding a new proto you will need to whitelist it in proto/portable_tink_filter.asciipb
- For google3 (BUILD) we should use portable_proto_lib, for opensource (BUILD.bazel) we should use cc_proto_lib.
PiperOrigin-RevId: 193084414
GitOrigin-RevId: 266a0dbb7f66549655e521350b70b10d4a872286

Learn more at go/new-proto-library.

Created by:
$ blaze run java/com/google/devtools/build/newprotolibrary/migration/java:Main -- --addLangProtoLibraryForProtoLibraryCreatedByMacros=serving_proto_library --rpc_deadline=90 third_party/...

BEGIN_PUBLIC
Internal change
END_PUBLIC

PiperOrigin-RevId: 192981122
GitOrigin-RevId: eaab7225f05b9367e0d9f18c3b4bf4652627f826

PiperOrigin-RevId: 192841538
GitOrigin-RevId: fc764bfd75fad54812d2598b6edade53490e874a

Having to remove the MyPaymentMethodTokenRecipientKem class example because Javadoc refuses to process curly braces, see https://google.github.io/tink/javadoc/apps-paymentmethodtoken/HEAD-SNAPSHOT/.

PiperOrigin-RevId: 192699427
GitOrigin-RevId: 63bf2ea58f8258d93efe9d69d65e10fb7a9451f7

While I'm here, use the correct link for the Google Payment Method Token standard.

PiperOrigin-RevId: 192651210
GitOrigin-RevId: 404e51455339f629f1307a8e57383e824b134f71

This is needed to facilitate KEYS.KEYSET_LENGTH from go/googlesql_encryption.

PiperOrigin-RevId: 192582377
GitOrigin-RevId: 6fa9c27f603f64c77c8e80b29d2743fc4c1dc916