Two new lists are added to the contributor-agreement config section:
1. matchProjects will apply the enforcement only to matching projects.
When omitted, enforcement applies to all projects.
2. excludeProjects will cause the enforcement to skip matches.
When omitted, enforcement applies to all projects per matchProjects.
Change-Id: Ide2d8c4718ffcfb3cf1701465fe08bea58e9d7c6
With the new stylesheet example blocks (delimited with ====) are
rendered as rather intrusive boxes with large padding in yellow
and grey.
This patch replaces the example blocks with simple code blocks
(delimited with ----) that better match the overall style of the
documentation.
Change-Id: Id95387cdb153332c2066e2d5e378697647dbca52
Signed-off-by: Michael Ochmann <michael.ochmann@sap.com>
Class loading of PGP functionality has never worked out of the box,
from which we can conclude that this feature is unused in the wild.
PGP functionality has never been located in bcprov-*.jar, at least as
long as the original library download configuration has existed.
3bccd773 points to bcprov-jdk16-144.jar, which does not contain PGP
classes:
$ curl -sOL http://www.bouncycastle.org/download/bcprov-jdk16-144.jar && jar tf bcprov-jdk16-144.jar | grep -i pgp
org/bouncycastle/crypto/modes/OpenPGPCFBBlockCipher.class
org/bouncycastle/crypto/modes/PGPCFBBlockCipher.class
Even before that commit, in 44671f5c, we were checking for the
presence of PGPPublicKey.class in the havePGP() helper method.
This functionality at one point was used by Google to implement CLA
checking, but that used a different build system and so did not see
the breakage caused by incorrect library download configuration. These
days, Google does not even use the same contact store mechanism for
googlesource.com; CLAs are managed using a different system.
Also delete UI associated with storing contact information. Although
it was possible to configure a CLA to prompt the user for contact
information, looking at the logic in AccountSecurityImpl, this info
was dropped on the floor unless a ContactStore was configured. As we
know, this was never the case, so claiming to store encrypted contact
information in the UI was basically a lie.
Similarly, the contactFiledOn field in Account was only set in the
same ContactStore-enabled codepath, so we can kill that as well.
Change-Id: I497cd374566c7d56262dafeeb96e4612fee54e8f
We previous use the section title style like:
Section level 1
===============
Section level 2
---------------
Which have a problem in Asciidoctor that the number of "="s or "-"s must match
the number of characters in the header exactly, as a result it's easy to make
mistakes while changing the titles. Asciidoctor provides a better style like:
= Section level 1
== Section level 2
So we switched to this style.
Also fixed a bug in replace_macros.py, which will not cause any problem in the
old style.
Change-Id: I811dd7238735d98f662767c17086152cd69aea02
- New config-cla.txt file.
- Fix config-gerrit.txt:
- auth.contributorAgreements now talks about project.config instead of
database table.
- Added reference to config-cla.txt.
- Added link to config-cla.txt in index.txt.
Change-Id: I89b26434267c58479425577891d4823c483c7c75