www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tomaz Muraus (JIRA)" <j...@apache.org>
Subject [jira] [Created] (INFRA-3647) Apache Libcloud TLP setup
Date Thu, 19 May 2011 20:06:48 GMT
Apache Libcloud TLP setup 
--------------------------

                 Key: INFRA-3647
                 URL: https://issues.apache.org/jira/browse/INFRA-3647
             Project: Infrastructure
          Issue Type: New Feature
      Security Level: public (Regular issues)
          Components: TLP Admin
            Reporter: Tomaz Muraus


The board has agreed to graduate Libcloud from the Incubator to a top level project. 

To aid in the process, would the Infrastructure team please do the following:

#=======================================

[0] Root tasks:

Create unix group "libcloud"

Create DNS entry libcloud.apache.org and configure website server instance

#=======================================

[1] Mailing List (i) addresses

Please migrate the existing archives, subscribers and moderators to
the following lists:

   dev@libcloud.apache.org from libcloud@incubator.apache.org
   commits@libcloud.apache.org from libcloud-commits@incubator.apache.org
   private@libcloud.apache.org from libcloud-private@incubator.apache.org

[2] Create a new mailing list address for the security issues

security@libcloud.apache.org

Only people who currently have access to "libcloud-private@incubator.apache.org" should have
read access to this new list, but everyone should be able to post to it.

[3] Add Tomaz "tomaz" Muraus (PMC chair) to appropriate authorizations in auth file.

#=======================================

[4] Initial Committer list

woodser,jed,oremj,jerry,rbogorodskiy,tom,tomaz,pquerna

#=======================================

[5] Source Tracker

Subversion

Move the existing incubator/libcloud tree to TLP 

[6] Create "libcloud" directory in /www/www.apache.org/dist directory for publishing software.

We are also using the Apache CMS. I assume this means you also need to enable it at the new
location?

Thanks

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message