openmeetings-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "SebastianWagner (JIRA)" <>
Subject [jira] [Created] (OPENMEETINGS-516) After graduation tasks
Date Fri, 25 Jan 2013 05:13:13 GMT
SebastianWagner created OPENMEETINGS-516:

             Summary: After graduation tasks
                 Key: OPENMEETINGS-516
             Project: Openmeetings
          Issue Type: Bug
            Reporter: SebastianWagner

Per: ASF Graduation Guide:

1. Update PMC Chair details (under , requires karma to
have been granted to PMC Chair or an ASF member):
- foundation/officers/affiliations.txt
  - DONE
- foundation/officers/irs-disclosures.txt
  - DONE
- committers/board/committee-info.txt
  - Section 1: Change chair
  - Section 2: selected Jan/Apr/Jul/Oct as 3 monthly schedule Feb/March/April will be monthly
for first 3 months
  - Section 3: Update old chair, update new chair
  - DONE

Updated PMC details on project website

2. PMC Chair to subscribe to:
- (via DONE
- (via TODO

DONE, subscriptions approved by the moderators of both lists.

3. Infra transfer tasks

as per:, (1)
  - INFRA-???? created as an umbrella (top-level task can be cloned from INFRA-4069, umbrella
for JMeter TPL)


3a. root tasks

subtask INFRA-???? (cf INFRA-4070 from JMeter)
- create a DNS entry "".
- create:
  - the LDAP unix group "openmeetings"
  - the LDAP committee group "openmeetings"


3b. add the OpenMeetings PMC/committers list as initial members of both:

ssh -l danhaywood isis --add=danhaywood,rmatthews,kevin,themalkolm,dslaughter,jcvanderwal,mnour,struberg isis --add=danhaywood,rmatthews,kevin,themalkolm,dslaughter,jcvanderwal,mnour,struberg


3c. Move source code

subtask INFRA-????



3d. Move mailing lists 

subtask INFRA-???? (cf INFRA-4071 from JMeter)
- Please create new mailing lists
  - ->
  - ->
  - ->
  - ->

- migrate existing subscribers

 Confirmed existing subscribers by sending an email to and

3e. Create website (our prereqs)


committed to

other refs:


3f. Move website

The Isis website must be moved to to

subtask INFRA-????
Please set up for CMS.

<danielsh> danhaywood: +| Create a **CMS-based site** | URL of the [layout-compliant](cmsref#layout)
site source, and what build system to use | Build system types include:,,
maven/ant/forrest. |

Specified (but will be
after INFRA-5484)


3g. Wiki and JIRA

- these do not need any changes (cf JMeter examplar INFRA-4069 which did require subtasks)


3h. Update for new SVN directory


4. Mailing list tidy up tasks

- When podling lists have been transferred to their new home (by infrastructure), post an
announcement to user and development lists. 
- When using Maven: update pom.xml for the new mailing list address(es).
- Update any documents on your website that show how to subscribe to the lists and/or find
- Send notice to and 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 ) 
- change svn commit hook to mail the new mailing list
confluence commit messages (see adminstration documentation) 
issue tracking messages (see administration documentation) 
- The existing mailing lists should then be removed/cancelled (whatever is normally done...)


5. Update incubator's podling status page

(by updating,
and published as per


6. Checked/updated Apache branding on site

as per:

specifically: make sure have (TM) in banner; make sure description of project on home page
and on download page; make sure have standard links to top-level Apache pages.


7. Update infra build tools, DOAP files

as per the README_NEWTLP:
- create RDF in data_files/
- update files.xml with location of DOAP file
- update xdocs/create.xml


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:

View raw message