Mailing-List: contact isis-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: isis-dev@incubator.apache.org
Date: Mon, 29 Oct 2012 14:20:14 +0000 (UTC)
From: "Jeroen van der Wal (JIRA)" <jira@apache.org>
To: isis-dev@incubator.apache.org
Message-ID: <541300169.39022.1351520414465.JavaMail.jiratomcat@arcas>
Subject: [jira] [Created] (ISIS-279) Move mailinglists
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Jeroen van der Wal created ISIS-279:
---------------------------------------

             Summary: Move mailinglists
                 Key: ISIS-279
                 URL: https://issues.apache.org/jira/browse/ISIS-279
             Project: Isis
          Issue Type: Sub-task
            Reporter: Jeroen van der Wal


>From the ASF guide:
- Request that podlings lists be transferred to their new home. Any new mailing lists should be requested at the same time.
- When this has been executed by infrastructure, post an announcement to user and development lists.
- When using Maven: update pom.xml for the new mailing list address(es). Also update any documents on your website that show how to subscribe to the lists and/or find archives.
- Send notice to Markmail.org and Nabble.com that the address has changed, and the location of the project 
- Update website: replace links to old archives with links to new ones and add new links to historic archives from incubation.
- Check project-private mailing list membership. Mentors should be allowed to remain if they wish to do so. The subscriber list should otherwise match that on the resolution. See this and the EZMLM "Moderator's and Administrator's Manual".
- Update mail addresses including:
svn commit messages (see infrastructure/trunk/subversion/authorization/asf-mailer.conf )
confluence commit messages (see adminstration documentation)
issue tracking messages (see administration documentation)
The chair should have karma to perform these tasks.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira