Re: [jira] [Created] (OPENMEETINGS-516) After graduation tasks

["seba.wagner@gmail.com" <se...@gmail.com>]

We can potentially create the INFRA tasks to migrate our ressources now.

Is there anybody requesting to use the CMS now or are we happy to use the
existing website?

Sebastian


2013/1/25 SebastianWagner (JIRA) <ji...@apache.org>

> SebastianWagner created OPENMEETINGS-516:
> --------------------------------------------
>
>              Summary: After graduation tasks
>                  Key: OPENMEETINGS-516
>                  URL:
> https://issues.apache.org/jira/browse/OPENMEETINGS-516
>              Project: Openmeetings
>           Issue Type: Bug
>             Reporter: SebastianWagner
>
>
> Per: ASF Graduation Guide:
> http://incubator.apache.org/guides/graduation.html#life-after-graduation
>
> 1. Update PMC Chair details (under https://svn.apache.org/repos/private ,
> 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
> TODO
>
>
> 2. PMC Chair to subscribe to:
> - board@apache.org (via board-subscribe@apache.org) DONE
> - infrastructure@apache.org (via infrastructure-subscribe@apache.org) TODO
>
> DONE, subscriptions approved by the moderators of both lists.
>
>
> 3. Infra transfer tasks
>
> as per: http://incubator.apache.org/guides/graduation.html#transfer, (1)
>   - INFRA-???? created as an umbrella (top-level task can be cloned from
> INFRA-4069, umbrella for JMeter TPL)
>
> TODO
>
> 3a. root tasks
>
> subtask INFRA-???? (cf INFRA-4070 from JMeter)
> - create a DNS entry "openmeetings.apache.org".
> - create:
>   - the LDAP unix group "openmeetings"
>   - the LDAP committee group "openmeetings"
>
> TODO
>
>
> 3b. add the OpenMeetings PMC/committers list as initial members of both:
>
> EXAMPLE:
> ssh -l danhaywood people.apache.org
>
> modify_committee.pl isis
> --add=danhaywood,rmatthews,kevin,themalkolm,dslaughter,jcvanderwal,mnour,struberg
> modify_unix_group.pl isis
> --add=danhaywood,rmatthews,kevin,themalkolm,dslaughter,jcvanderwal,mnour,struberg
>
> TODO
>
>
> 3c. Move source code
>
> subtask INFRA-????
>
> EXAMPLE
> from: https://svn.apache.org/repos/asf/incubator/isis
> to: https://svn.apache.org/repos/asf/isis
>
> TODO
>
>
> 3d. Move mailing lists
>
> EXAMPLE
> subtask INFRA-???? (cf INFRA-4071 from JMeter)
> - Please create new mailing lists
>   - isis-users@incubator.apache.org -> users@isis.apache.org
>   - isis-dev@incubator.apache.org -> dev@isis.apache.org
>   - isis-private@incubator.apache.org -> private@isis.apache.org
>   - isis-commits@incubator.apache.org -> commits@isis.apache.org
>
> - migrate existing subscribers
>
> TODO.
> (EXAMPLE
>  Confirmed existing subscribers by sending an email to
> users-list@isis.apache.org and dev-list@isis.apache.org.)
>
>
> 3e. Create website (our prereqs)
>
> per http://www.apache.org/dev/cmsref.html#svn
>
> committed to https://svn.apache.org/repos/asf/incubator/isis/site
>
> other refs:
> [1] http://www.apache.org/dev/#web
> [2] http://www.apache.org/dev/cms.html#layout
> [3] http://www.apache.org/dev/cmsref.html#walkthrough
> [4] http://www.apache.org/dev/project-site.html
>
> TODO
>
>
> 3f. Move website
>
> EXAMPLE
> The Isis website must be moved to http://incubator.apache.org/isis to
> http://isis.apache.org
>
> 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: path.pm, build_cms.sh, maven/ant/forrest. |
>
> Specified https://svn.apache.org/repos/asf/incubator/isis/site (but will
> be https://svn.apache.org/repos/asf/isis/site after INFRA-5484)
>
> TODO
>
>
> 3g. Wiki and JIRA
>
> EXAMPLE
> - these do not need any changes (cf JMeter examplar INFRA-4069 which did
> require subtasks)
>
> TODO
>
> 3h. Update builds.apache.org for new SVN directory
>
> TODO
>
>
> 4. Mailing list tidy up tasks
>
> EXAMPLE
> - 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 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 )
> - change svn commit hook to mail the new commits@isis.apache.org 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...)
>
> TODO
>
> 5. Update incubator's podling status page
>
> EXAMPLE
> - http://incubator.apache.org/projects/isis.html
> (by updating
> https://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/isis.xml,
> and published as per http://incubator.apache.org/guides/website.html)
>
> TODO
>
> 6. Checked/updated Apache branding on site
>
> as per:
> * http://www.apache.org/foundation/marks/pmcs.html#attributions
> * http://www.apache.org/foundation/marks/pmcs.html#navigation
>
> 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.
>
> TODO
>
>
> 7. Update infra build tools, DOAP files
>
> checkout
> https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects
> as per the README_NEWTLP:
> - create RDF in data_files/
> - update files.xml with location of DOAP file
> - update xdocs/create.xml
>
> TODO
>
> --
> 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
>



-- 
Sebastian Wagner
https://twitter.com/#!/dead_lock
http://www.webbase-design.de
http://www.wagner-sebastian.com
seba.wagner@gmail.com