[ https://issues.apache.org/jira/browse/ISIS-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Haywood updated ISIS-279: ----------------------------- Issue Type: Task (was: Sub-task) Parent: (was: ISIS-276) > Move mailinglists > ----------------- > > Key: ISIS-279 > URL: https://issues.apache.org/jira/browse/ISIS-279 > Project: Isis > Issue Type: 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