Since the foundation sometimes needs to deduplicate subsequent
invitations for the same foundation member against invitations sent
by another system, use the member ID as the first field of the
invite instead of using the Gerrit username now that we have that
information available. Use a default member ID of 0 to indicate
non-member invitees who may require additional manual deduplication
or vetting. Also log the member ID in the output of the invite mass
mailer script.
Change-Id: I86d879a5f06144a0889eb852f2cf3d555a12a7aa
Add a human name in the invites sample configuration's from address
value, since this will cause messages to appear with a friendlier
from name than just a raw E-mail address.
Change-Id: Idf16904bcd56692f3a82e41cb52201ed2223fdfd
In the sample settings file, backslash-continue the string literal
opening to avoid introducing an extra leading newline in the
resulting message body.
Change-Id: Ief61f69acb5299ba324af8a897ea4f96fa47711d
Since the send.py script for invites uses print to emit progress
including the names of contacts to which messages are sent,
redirecting stdout of the script to a local file can result in
encoding errors if some of the names include non-ASCII codepoints
(but not when stdout is your interactive terminal). Setting
PYTHONIOENCODING=utf-8 in the calling environment works around this
nicely.
Change-Id: I52b70c64f8b3a20da5143b31c5090192b0c75c99
There only needs to be one sample ATCs file for the invites
mass-mailer, so remove the redundant one which isn't referenced in
the README file. This should help prevent people editing the wrong
sample and then performing a dry-run with the unmodified one.
Change-Id: I61e90ad085e89c466053858518db09a414a07792
The mail merger for summit invites includes Date and Message-ID
headers, because Crocker said so in 1977 that's why.
Change-Id: I2105fe4cd04b7b2042c9e32888cb1f094697d7bf
Literal $ characters in the template which are not part of a
substitution variable should be doubled to to avoid raising a
ValueError exception.
Change-Id: I14fd33571d63d50fc65e8c87fb10577e691b6c8e
The OpenStack Havana release heralds end of support for Folsom, so
stop testing it.
* modules/jenkins/files/slave_scripts/docbook-properties.sh: Remove
folsom-specific settings.
* .../openstack_project/files/gerrit/acls/openstack/ceilometer.config:
Get rid of the stable/folsom ACL override.
* .../jenkins_job_builder/config/devstack-gate.yaml
* .../manuals.yaml
* .../projects.yaml
* .../python-bitrot-jobs.yaml
* modules/openstack_project/files/zuul/layout-dev.yaml
* .../layout.yaml: Remove all folsom-only jobs and clean up
configuration and comments associated with them.
* tools/invite2summit/settings.py.sample: Adjust usage comment to no
longer refer to Folsom.
Change-Id: Ieb38a74e6945abe2e40cd3e1cd23b52fbd826933