Project:Infrastructure/Email alias management

This page Article description::nicely and simply details the management of mail aliases on dev.g.o for new project teams, architectures, etc.

Creation
Using the keyword as an example new arch team, follow the steps below:


 * 1) Login to dev.gentoo.org
 * 2) Navigate to relevant directory (e.g.  if an arch team).
 * 3) Edit  with members matching wiki.
 * 4) Wait ~10 minutes for Postfix to rebuild.
 * 5) Add yourself to the file for testing.
 * 6) Send a test email to the new alias @g.o
 * 7) Once received, remove yourself from the list.
 * 1) Once received, remove yourself from the list.

Non-mail part

 * 1) Update Bugzilla fields to include new arch for the Hardware field (via the admin interface).
 * 2) In  (on the bugstest branch), two template files to add to the arch CC list on bugs:
 * 3) Commit changes on the bugstest branch, log in to bugstest.gentoo.org via SSH, run  in
 * 4) Test it out on bugstest.gentoo.org
 * 5) If it works fine, go back to git, commit to master, and tag (increment last version)
 * 6) Bump Bugzilla version to new tag just created in manifests/site.pp in puppet.git.
 * 1) If it works fine, go back to git, commit to master, and tag (increment last version)
 * 2) Bump Bugzilla version to new tag just created in manifests/site.pp in puppet.git.