Mailing-List: contact clerezza-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: clerezza-dev@incubator.apache.org
Date: Tue, 26 Feb 2013 03:36:16 +0000 (UTC)
From: "Hasan (JIRA)" <jira@apache.org>
To: clerezza-dev@incubator.apache.org
Message-ID: <JIRA.12634047.1361849224491.339100.1361849776252@arcas>
In-Reply-To: <JIRA.12634047.1361849224491@arcas>
References: <JIRA.12634047.1361849224491@arcas>
Subject: [jira] [Updated] (CLEREZZA-732) Tasks to be performed after
 graduation
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CLEREZZA-732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hasan updated CLEREZZA-732:
---------------------------

    Description: 
Once appointed, the new Chair needs to:

a. Subscribe to the board mailing list
DONE

b. Subscribe to the infrastructure mailing list
DONE

c. Ensure that they have been added to the PMC chairs group (pmc-chairs) in LDAP.
DONE

d. Check out the foundation/officers folder from the private repository. Users with member or pmc-chairs karma can do this.
DONE

e. Add yourself to the foundation/officers/affiliations.txt and the foundation/officers/irs-disclosures.txt files with the appropriate information.
DONE

f. Review appropriate documentation:
- PMC Chair Duties
- PMC documentation
- Jakarta Chair guide
- Incubator Chair guide
- Reporting calendar

g. Work out a reporting schedule with the Board. For the first three months after graduation this will be monthly. After that, the project should slot into a quarterly reporting schedule. Now is a good time to remove the project from the Incubator reporting schedule.

h. Work with the Apache Infrastructure team to set up the top level project infrastructure. The various infrastructure tasks that are required (see check list) should be consolidated into a single issue (see this for example). This should be created in the category TLP Admin.

i. Add the PMC chair details to the foundation web site Officer list at http://www.apache.org/foundation/index.html
DONE

j. Add the new project's PMC chair to the foundation/officers/irs-disclosures.txt file. You will need a member to help with this task.
??? same as e ?

k. Ensure the PMC is added to the committee-info.txt file at https://svn.apache.org/repos/private/committers/board/committee-info.txt
There are 3 sections which need to be updated; see instructions in the file. You may need to get a member to help with this.
DONE

l. They should then be able to start assembling the new PMC. The starting membership is listed in the resolution. However, the Chair of the new project needs to ensure that private list is created and the membership subscribed.


Members of the new PMC need to:
1. Subscribe to the private mailing list for the project
2. Review appropriate documentation:
- Apache PMC Guide
- Related documentation

Once all this is in place, resources can start to be handed over to the new project.


  was:
Once appointed, the new Chair needs to:

a. Subscribe to the board mailing list
b. Subscribe to the infrastructure mailing list
c. Ensure that they have been added to the PMC chairs group (pmc-chairs) in LDAP.
d. Check out the foundation/officers folder from the private repository. Users with member or pmc-chairs karma can do this.
e. Add yourself to the foundation/officers/affiliations.txt and the foundation/officers/irs-disclosures.txt files with the appropriate information.
f. Review appropriate documentation:
- PMC Chair Duties
- PMC documentation
- Jakarta Chair guide
- Incubator Chair guide
- Reporting calendar
g. Work out a reporting schedule with the Board. For the first three months after graduation this will be monthly. After that, the project should slot into a quarterly reporting schedule. Now is a good time to remove the project from the Incubator reporting schedule.
h. Work with the Apache Infrastructure team to set up the top level project infrastructure. The various infrastructure tasks that are required (see check list) should be consolidated into a single issue (see this for example). This should be created in the category TLP Admin.
i. Add the PMC chair details to the foundation web site Officer list at http://www.apache.org/foundation/index.html
j. Add the new project's PMC chair to the foundation/officers/irs-disclosures.txt file. You will need a member to help with this task.
k. Ensure the PMC is added to the committee-info.txt file at https://svn.apache.org/repos/private/committers/board/committee-info.txt
There are 3 sections which need to be updated; see instructions in the file. You may need to get a member to help with this.

They should then be able to start assembling the new PMC. The starting membership is listed in the resolution. However, the Chair of the new project needs to ensure that private list is created and the membership subscribed.


Members of the new PMC need to:
1. Subscribe to the private mailing list for the project
2. Review appropriate documentation:
- Apache PMC Guide
- Related documentation

Once all this is in place, resources can start to be handed over to the new project.


> Tasks to be performed after graduation
> --------------------------------------
>
>                 Key: CLEREZZA-732
>                 URL: https://issues.apache.org/jira/browse/CLEREZZA-732
>             Project: Clerezza
>          Issue Type: Task
>            Reporter: Hasan
>            Assignee: Hasan
>
> Once appointed, the new Chair needs to:
> a. Subscribe to the board mailing list
> DONE
> b. Subscribe to the infrastructure mailing list
> DONE
> c. Ensure that they have been added to the PMC chairs group (pmc-chairs) in LDAP.
> DONE
> d. Check out the foundation/officers folder from the private repository. Users with member or pmc-chairs karma can do this.
> DONE
> e. Add yourself to the foundation/officers/affiliations.txt and the foundation/officers/irs-disclosures.txt files with the appropriate information.
> DONE
> f. Review appropriate documentation:
> - PMC Chair Duties
> - PMC documentation
> - Jakarta Chair guide
> - Incubator Chair guide
> - Reporting calendar
> g. Work out a reporting schedule with the Board. For the first three months after graduation this will be monthly. After that, the project should slot into a quarterly reporting schedule. Now is a good time to remove the project from the Incubator reporting schedule.
> h. Work with the Apache Infrastructure team to set up the top level project infrastructure. The various infrastructure tasks that are required (see check list) should be consolidated into a single issue (see this for example). This should be created in the category TLP Admin.
> i. Add the PMC chair details to the foundation web site Officer list at http://www.apache.org/foundation/index.html
> DONE
> j. Add the new project's PMC chair to the foundation/officers/irs-disclosures.txt file. You will need a member to help with this task.
> ??? same as e ?
> k. Ensure the PMC is added to the committee-info.txt file at https://svn.apache.org/repos/private/committers/board/committee-info.txt
> There are 3 sections which need to be updated; see instructions in the file. You may need to get a member to help with this.
> DONE
> l. They should then be able to start assembling the new PMC. The starting membership is listed in the resolution. However, the Chair of the new project needs to ensure that private list is created and the membership subscribed.
> Members of the new PMC need to:
> 1. Subscribe to the private mailing list for the project
> 2. Review appropriate documentation:
> - Apache PMC Guide
> - Related documentation
> Once all this is in place, resources can start to be handed over to the new project.

--
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