Author: henkp
Date: Tue Apr 24 16:47:41 2018
New Revision: 1830014
URL: http://svn.apache.org/viewvc?rev=1830014&view=rev
Log:
cleanup
Added:
attic/site-lua/docs/data/index.txt
attic/site-lua/docs/data/page.tmpl
- copied unchanged from r1830013, attic/site-lua/docs/layouts/project.html
attic/site-lua/docs/data/process.txt (with props)
attic/site-lua/docs/data/resolution.txt
Removed:
attic/site-lua/docs/layouts/
attic/site-lua/docs/projects.html
Modified:
attic/site-lua/docs/mk-stuff
Added: attic/site-lua/docs/data/index.txt
URL:
http://svn.apache.org/viewvc/attic/site-lua/docs/data/index.txt?rev=1830014&view=auto
==============================================================================
--- attic/site-lua/docs/data/index.txt (added)
+++ attic/site-lua/docs/data/index.txt Tue Apr 24 16:47:41 2018
@@ -0,0 +1,78 @@
+<div class="section-content">
+<p>
+ The Apache Attic was created in
+ <a
href="http://www.apache.org/foundation/records/minutes/2008/board_minutes_2008_11_19.txt";>November
2008</a>
+ to provide process and solutions to make it clear when an Apache project
has reached its
+ end of life. Specifically to be:
+ </p>
+<p style="font-family: monospace">
+ "responsible for the oversight of projects which otherwise would not have
+ oversight; and be it further ... is not authorized to actively develop and
release the
+ projects under its oversight"
+ </p>
+<p>It is intended to: </p>
+<ul>
+ <li>Be non-impacting to users</li>
+ <li>Provide restricted oversight for these codebases</li>
+ <li>Provide oversight for active user lists with no Project Management
Committee (PMC)</li>
+ </ul>
+<p>It is not intended to: </p>
+<ul>
+ <li>Rebuild community</li>
+ <li>Make bugfixes</li>
+ <li>Make releases</li>
+ </ul>
+</div>
+
+<h4 id="incoming">
+ Getting into the Attic
+</h4>
+<div class="section-content">
+<p>There are two expected mechanisms by which a project may enter the Attic.
Either the managing
+ Project Management Committee (PMC) decides it would like to move the
project, or The
+ Apache Software Foundation's board dissolves the PMC and chooses to move
the project. </p>
+<p>In either case, the following may be useful: <a
href="resolution.html">Template Board Resolution</a>. </p>
+</div>
+
+<h4 id="candidates">
+ When should a project move to the Attic?
+</h4>
+<div class="section-content">
+<p>Projects whose PMC are unable to muster 3 votes for a release, who have no
active committers or
+ are unable to fulfill their reporting duties to the board are all good
candidates for the Attic. </p>
+</div>
+
+<h4 id="process">
+ Process of moving into the Attic
+</h4>
+<div class="section-content">
+<p>This is defined in the separate <a href="process.html">process</a>
document. </p>
+</div>
+
+<h4 id="departure">
+ Process of leaving the Attic again
+</h4>
+<div class="section-content">
+<p>Options are: </p>
+<ul>
+ <li>Forking the project - we'll link to any forks which have been created
so please let us know</li>
+ <li>Restarting the community in the Apache Incubator</li>
+ <li>Recreating a PMC for the project</li>
+ </ul>
+</div>
+
+<h4 id="contact">
+ Contacting the Attic PMC
+</h4>
+<div class="section-content">
+<p>The Attic is managed by a Project Management Committee (PMC). Discussions
are found on
+ the <a
href="http://mail-archives.apache.org/mod_mbox/attic-general/";>general@ mailing
list</a>
+ and you are welcome to subscribe. </p>
+</div>
+
+<h4 id="incubator">
+ Retired Incubator Projects
+</h4>
+<div class="section-content">
+<p>The Apache Incubator project is the entry path into The Apache Software
Foundation for projects and codebases wishing to become part of the
Foundation's efforts. Not all projects 'graduate' out of the Incubator and are
instead retired. Those retired projects may be found on the Incubator's <a
href="http://incubator.apache.org/projects/index.html#retired";>Project
page</a>. </p>
+</div>
Added: attic/site-lua/docs/data/process.txt
URL:
http://svn.apache.org/viewvc/attic/site-lua/docs/data/process.txt?rev=1830014&view=auto
==============================================================================
--- attic/site-lua/docs/data/process.txt (added)
+++ attic/site-lua/docs/data/process.txt Tue Apr 24 16:47:41 2018
@@ -0,0 +1,213 @@
+<div class="section-content">
+<p>At some point a project will vote to join the Attic. The following defines
a process
+ to move that project into the Attic and gently close it down. </p>
+<ol>
+ <li>A Project PMC decides to move to the Attic.
+ <ul>
+ <li>Conduct a discussion on whether to dissolve the PMC and move the
project to the Attic on the public dev list. Do not conduct it on the private
PMC list. </li>
+ <li>Consider an appeal to the user list for interested users to
provide their interest in helping out more. </li>
+ <li>Conduct a PMC vote on the public dev list. </li>
+ <li>If the PMC votes to dissolve the PMC and move the project to the
Attic, inform the board of the successful vote (linking or forwarding the
'successful' vote) and add a <a href="resolution.html">resolution</a> to
dissolve the PMC to the next board meeting agenda. </li>
+ <li>If the PMC can't get enough people to vote to dissolve the PMC
(and there are not three -1 votes), then that is grounds for moving the project
to the Attic. They should inform the board as above, noting that the vote
failed to get enough votes. </li>
+ </ul>
+ </li>
+ <li>If the board approve the resolution, open a JIRA item - 'Move
${project} to the Attic'.<br /> Copy/paste the following items to the details
(see "How to" below for a description of each step):
+ <ol type="1">
+ <li>Confirm Board Resolution (if TLP)</li>
+ <li>Delete from committee-info.txt (if TLP)</li>
+ <li>Remove VP entry on <a
href="http://www.apache.org/foundation/";>http://www.apache.org/foundation/</a>
(if TLP)</li>
+ <li>Inform users of the move to the Attic</li>
+ <li>Create project page on Attic site:
http://attic.apache.org/projects/${project}.html</li>
+ <li>Obtain source control karma and point source control mails to
general at attic
+ <ul>
+ <li>i. Update the project DOAP file (if any):
https://projects.apache.org/project.html?${project}</li>
+ <li>ii. Make source control read-only</li></ul></li>
+ <li>Move committee's PMC data file to retired (if TLP)</li>
+ <li>Remove from <a
href="http://www.apache.org/#projects-list";>http://www.apache.org/#projects-list</a>
navigation (if TLP)</li>
+ <li>Announce on <a
href="http://mail-archives.apache.org/mod_mbox/www-announce/";>announce at
apache.org</a></li>
+ </ol>
+ </li>
+ <li>Open an <a
href="https://issues.apache.org/jira/browse/INFRA";>Infrastructure JIRA</a>
issue identifying the resources that need turning off/making read only.
Typically:
+ <ul>
+ <li>Remove files from <a
href="http://www.apache.org/dist/";>www.apache.org/dist</a></li>
+ <li>Closing down of dev@, commits@ and private@ <a
href="http://mail-archives.apache.org/mod_mbox/";>mailing lists</a></li>
+ <li>Close down the user mailing list (unless still active - in which
case propose a moderator to Infra)</li>
+ <li>Make JIRA|Bugzilla read-only</li>
+ <li>Make the wiki (Confluence|Moinmoin) read-only</li>
+ <li>Delete unix/ldap group</li>
+ <li>Turn off automated builds</li>
+ </ul>
+ </li>
+ </ol>
+</div>
+
+<h4 id="General-pointers">
+ How to: General pointers
+</h4>
+<div class="section-content">
+<p>The following are usefull svn/https locations:
+ <ul>
+ <li>svn site <a
href="http://svn.apache.org/repos/asf/attic";>http://svn.apache.org/repos/asf/attic</a></li>
+ <li>site <a
href="http://attic.apache.org";>http://attic.apache.org</a></li>
+ <li>jira <a
href="https://issues.apache.org/jira/browse/ATTIC";>https://issues.apache.org/jira/browse/ATTIC</a></li>
+ <li>committees.xml <a
href="https://svn.apache.org/repos/asf/comdev/projects.apache.org/data/committees.xml";>https://svn.apache.org/repos/asf/comdev/projects.apache.org/data/committees.xml</a></li>
+ </ul>
+ </p>
+</div>
+
+<h4 id="confirm-resolution">
+ How to: 1. Confirm Board Resolution (if TLP)
+</h4>
+<div class="section-content">
+<p>Check previous Board minutes (in SVN or to committers@) to confirm project
was retired.</p>
+</div>
+
+<h4 id="delete-pmc">
+ How to: 2. Delete from committee-info.txt (if TLP)
+</h4>
+<div class="section-content">
+<p>Remove the PMC from <a
href="https://svn.apache.org/repos/private/committers/board/committee-info.txt";>https://svn.apache.org/repos/private/committers/board/committee-info.txt</a></p>
+</div>
+
+<h4 id="update-foundation-site">
+ How to: 3. Remove VP entry on http://www.apache.org/foundation/
+</h4>
+<div class="section-content">
+<p>Access the CMS <a
href="https://cms.apache.org/redirect?uri=http://www.apache.org/foundation/";>here</a>
+ and update the text. </p>
+<p>Check if the outgoing PMC chair is not chair of any other PMCs, then ask
infra to adjust the 'pmc-chairs' LDAP group accordingly.</p>
+</div>
+
+<h4 id="informing">
+ How to: 4. Inform users of the move to the Attic
+</h4>
+<div class="section-content">
+<p>Let the users know that the project is moving into the Attic. Use the
following template: </p>
+<pre>
+A heads up for the ${project} user community that the ${project} project has
+been 'moved to the Attic'. This means that the ${project} developers (more
+formally its Project Management Committee) have voted to retire ${project}
+and move the responsibility for its oversight over to the Attic project.
+
+Loosely speaking this means that the projects resources will be moved to a
+read-only state.
+
+You can read more about the Apache Attic and the process of moving to the
+Attic at http://attic.apache.org.
+
+You can follow this process in JIRA:
+
+ https://issues.apache.org/jira/browse/ATTIC-${#}
+
+Thanks,
+
+${Name} on behalf of ${project} + the Attic.
+ </pre>
+<p>Remember to subscribe to the user list <a
href="https://whimsy.apache.org/committers/subscribe";>https://whimsy.apache.org/committers/subscribe</a>
to avoid moderation. Also bear in mind that the user mailing list may
+ already know and you can skip this stage. Make sure you read that thread
if it does exist. </p>
+</div>
+
+<h4 id="atticsite">
+ How to: 5. Create project page on Attic site:
http://attic.apache.org/projects/${project}.html
+</h4>
+<div class="section-content">
+<p>The Attic website is built using Anakia. Anakia is an old site technology
built on top of Apache Velocity.
+ You can get the source for the site from Subversion: </p>
+<pre>svn co https://svn.apache.org/repos/asf/attic/site</pre>
+<p>Signal that <i>retired</i> banners must be added to ${project}.a.o. :</p>
+<ul>
+ <li><code>mkdir docs/flagged/${project}.apache.org ;</code></li>
+ <li><code>touch
docs/flagged/${project}.apache.org/${project}.apache.org</code></li>
+ </ul>
+<p>To create a project page do:</p>
+<ul>
+ <li>in xdocs/projects/ copy one of the files to the new project name (eg.
devicemap.xml)</li>
+ <li>Add the new file as a link in the xdocs/stylesheets/project.xml
navigation</li>
+ <li>Run 'ant' from the root (ie: the attic/site/ directory you checked
out)</li>
+ <li>Review the generated files in docs/** in your browser</li>
+ <li>SVN commit all changes. Remember to add both the new xdocs/ project
file and the new generated docs/ project file</li>
+ <li>The new pages should go live quickly</li>
+ </ul>
+</div>
+
+<h4 id="svnkarma">
+ How to: 6. Obtain source control karma and point source control mails to
general at attic
+</h4>
+<div class="section-content">
+<p>follow the workflow <a
href="https://cwiki.apache.org/confluence/display/INFRA/Git+workflow+for+infrastructure-puppet+repo";>https://cwiki.apache.org/confluence/display/INFRA/Git+workflow+for+infrastructure-puppet+repo</a>,<br
/>
+sometimes it helps chatting with infra <a
href="https://www.hipchat.com/gIjVtYcNy";>https://www.hipchat.com/gIjVtYcNy</a>,<br
/>
+all work are done in
"{infra-repo}/modules/subversion_server/files/authorization/"</p>
+<ul>
+ <li>Change "asf-authorization-template" so that the attic-pmc has
karma instead of the defunct project. </li>
+ <li>Change "asf-mailer.conf" so that the attic-pmc has karma instead
of the defunct project. Add project to attic regex, and if there are a project
entry remove it</li>
+ </ul>
+</div>
+
+<h4 id="doap">
+ How to: 6.ii Update the project DOAP file (if any):
https://projects.apache.org/project.html?${project}
+</h4>
+<div class="section-content">
+<p>The files referenced are in <a
href="https://svn.apache.org/repos/asf/comdev";>https://svn.apache.org/repos/asf/comdev</a></p>
+<p>Identify whether the project has a DOAP file (see the <comdev
repo>/projects.apache.org/data/projects.xml file if update the rdf file with
PMC to the Attic and add a category of <em>retired</em>: </p>
+<pre>pmc change: <asfext:pmc rdf:resource="http://attic.apache.org"; />
+new category: <category
rdf:resource="http://projects.apache.org/category/retired"; /></pre>
+</div>
+
+<h4 id="PMCdata">
+ How to: 7. Move committee's PMC data file to retired (if TLP)
+</h4>
+<div class="section-content">
+<p>If committee appears in <a
href="https://projects.apache.org/committees.html";>committees list</a>, moving
data to retired will remove it from the list.
+ Notice that <a
href="https://issues.apache.org/jira/browse/COMDEV-182";>this task is being
automated</a>, then not necessary to track any more in the future...</p>
+<p>Comment PMC data files index entry (see the <a
href="https://svn.apache.org/repos/asf/comdev/projects.apache.org/data/committees.xml";>committees.xml</a>
file
+ and old <a
href="https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects/pmc_list.xml";>pmc_list.xml</a>
file) and move PMC data file
+ from <a
href="https://svn.apache.org/repos/asf/comdev/projects.apache.org/data/committees";>committees/</a>
directory
+ to <a
href="https://svn.apache.org/repos/asf/comdev/projects.apache.org/data/committees-retired";>committees-retired/</a>.
+ </p>
+</div>
+
+<h4 id="www.apache">
+ How to: 8. Remove from http://www.apache.org/#projects-list navigation (if
TLP)
+</h4>
+<div class="section-content">
+<p>As a retired project, a <a href="http://www.apache.org/#projects-list";>link
on the front page of Apache site</a> is no longer necessary. Remove the link
and regenerate the main Apache site.
+ This is done via the <code>trunk/templates/blocks/projects.mdtext</code>
of the <a
href="https://cms.apache.org/redirect?uri=http://www.apache.org/index.html";>www.apache.org
CMS</a>. </p>
+<p>It's also worth checking that the VP link from <a
href="http://www.apache.org/foundation/";>http://www.apache.org/foundation/</a>
has been removed. </p>
+</div>
+
+<h4 id="announce">
+ How to: 9. Announce on annou...@apache.org
+</h4>
+<div class="section-content">
+<p>Announce that the project is now retired. Consider the following template.
</p>
+<pre>
+Announcing that the Apache ${project} committers have voted to retire
+the project due to inactivity. ${project} was {boilerplate}.
+
+Retiring a project is not as simple as turning everything off, as
+existing users need to both know that the project is retiring and
+retain access to the necessary information for their own development
+efforts.
+
+You can read more about ${project}'s retirement at:
+
+ http://attic.apache.org/projects/${project}.html
+
+The user mailing list remains open, while the rest of the project's
+resources will continue to be available in a read-only state -
+website, wikis, svn, downloads and bug tracker with no change in url.
+
+Providing process and solutions to make it clear when an Apache
+project has reached its end of life is the role of the Apache Attic,
+and you can read more about that at:
+
+ http://attic.apache.org/
+
+Thanks,
+
+${NAME}
+on behalf of the Apache Attic and the now retired Apache ${project} project
+ </pre>
+<p>It's important to include the boilerplate from the project's site so people
+ know what we're talking about. </p>
+</div>
Propchange: attic/site-lua/docs/data/process.txt
------------------------------------------------------------------------------
svn:executable = *
Added: attic/site-lua/docs/data/resolution.txt
URL:
http://svn.apache.org/viewvc/attic/site-lua/docs/data/resolution.txt?rev=1830014&view=auto
==============================================================================
--- attic/site-lua/docs/data/resolution.txt (added)
+++ attic/site-lua/docs/data/resolution.txt Tue Apr 24 16:47:41 2018
@@ -0,0 +1,27 @@
+<div class="section-content">
+<p>The following is a sample resolution to move a project to the Apache Attic.
A project's
+ chair should include this in the agenda for the next board meeting. </p>
+<pre>
+ ?. Terminate the Apache {PROJECT} Project
+
+ WHEREAS, the Project Management Committee of the Apache {PROJECT}
+ project has chosen by vote to recommend moving the project to the
+ Attic; and
+
+ WHEREAS, the Board of Directors deems it no longer in the best
+ interest of the Foundation to continue the Apache {PROJECT} project
+ due to inactivity;
+
+ NOW, THEREFORE, BE IT RESOLVED, that the Apache {PROJECT}
+ project is hereby terminated; and be it further
+
+ RESOLVED, that the Attic PMC be and hereby is tasked with
+ oversight over the software developed by the Apache {PROJECT}
+ Project; and be it further
+
+ RESOLVED, that the office of "Vice President, Apache {PROJECT}" is
+ hereby terminated; and be it further
+
+ RESOLVED, that the Apache {PROJECT} PMC is hereby terminated.
+ </pre>
+</div>
Modified: attic/site-lua/docs/mk-stuff
URL:
http://svn.apache.org/viewvc/attic/site-lua/docs/mk-stuff?rev=1830014&r1=1830013&r2=1830014&view=diff
==============================================================================
--- attic/site-lua/docs/mk-stuff (original)
+++ attic/site-lua/docs/mk-stuff Tue Apr 24 16:47:41 2018
@@ -4,9 +4,12 @@ use strict ;
use warnings ;
use JSON ;
-my $DEF_JSON_FILE = 'data/projects.json' ;
-my $DEF_LAYOUT = 'layouts/project.html' ;
-my $DEF_DEST = '.' ;
+my $JSON_FILE = 'data/projects.json' ;
+my $PAGE_TMPL = 'data/page.tmpl' ;
+my $INDX_TXT = 'data/index.txt' ;
+my $PROC_TXT = 'data/process.txt' ;
+my $RESO_TXT = 'data/resolution.txt' ;
+my $DEST = '.' ;
my $prog = substr $0, rindex ( $0, '/' ) + 1 ;
my $Usage = <<USAGE ;
@@ -38,16 +41,19 @@ $opt{v} ||= $opt{d} ;
my $TAG = $opt{f} ? 'DID' : 'WOULD' ;
my $mods = 0 ;
-my $JSON_FILE = shift || $DEF_JSON_FILE ;
-my $LAYOUT = shift || $DEF_LAYOUT ;
-my $DEST = $DEF_DEST ;
+if ( $opt{v} ) { print "using page templ '$PAGE_TMPL'\n" ; }
-if ( $opt{v} )
- { print "using layour file '$LAYOUT'\n" ; }
-
-Error "no layout file ($LAYOUT)" unless -f $LAYOUT ;
+Error "no page tmpl ($PAGE_TMPL)" unless -f $PAGE_TMPL ;
Error "no dest dir ($DEST)" unless -d $DEST ;
+sub get_file ($)
+ { my $file = shift ;
+ open FILE, '<', $file or Error "can't open $file ($!)" ;
+ my $res = join '', <FILE> ;
+ close FILE ;
+ $res ;
+ }
+
sub mk_tag
{ my $hash = shift ;
my $res = $hash -> {id} ;
@@ -59,23 +65,21 @@ sub mk_tag
}
sub get_json
- { open JSON, '<', $JSON_FILE or Error "can't open $JSON_FILE ($!)" ;
- my $json = from_json join '', <JSON> ;
- close JSON ;
+ { my $json = from_json get_file $JSON_FILE ;
return { map { ( mk_tag ( $_ ) => $_ ) } @$json } ;
}
-sub get_layout
+sub get_page
{ my $res = '' ;
- open LAYOUT, '<', $LAYOUT or Error "can't open $LAYOUT ($!)" ;
- while ( <LAYOUT> )
+ open PAGE, '<', $PAGE_TMPL or Error "can't open $PAGE_TMPL ($!)" ;
+ while ( <PAGE> )
{ last if /class="section-content"/ ; $res .= $_ ; }
$res .= "%BODY%\n" ;
- while ( <LAYOUT> )
+ while ( <PAGE> )
{ last if m!^</div>! ; }
- while ( <LAYOUT> )
+ while ( <PAGE> )
{ $res .= $_ ; }
- close LAYOUT ;
+ close PAGE ;
$res =~ s/Apache \{\{ page.json.name \}\} - Apache Attic/%TITLE%/g ;
$res =~ s/Apache \{\{ page.json.name \}\}/%TITLE%/g ;
$res =~ s/\{\% include project.list \%\}/%PROJS%/g ;
@@ -98,18 +102,17 @@ sub mail_url
{ my ( $p, $l ) = @_ ;
url ( "https://mail-archives.apache.org/mod_mbox/$p-$l/";, $l ) ;
}
-# https://issues.apache.org/jira/browse/ACE/
sub jira_url
{ my $p = shift ;
( $p ? url ( "https://issues.apache.org/jira/browse/$p/";, 'JIRA' ) : '' ) ;
}
sub bugz_url
- { my $p = shift ;
- ( $p ? url ( "https://bugzilla.apache.org/$p/";, $p ) : '' ) ;
+ { my $b = shift ;
+ my $u = "https://bz.apache.org/bugzilla/buglist.cgi?product=%s"; ;
+ ( $b ? url ( sprintf ( $u, $b ), 'Bugzilla' ) : '' ) ;
}
sub wiki_url
{ my $u = shift ; ( $u ? url ( $u, $u ) : '' ) ; }
-# https://whimsy.apache.org/board/minutes/ace.html
sub minutes_url
{ my $p = shift ;
( $p
@@ -179,370 +182,37 @@ TAB
my $json = get_json ;
# print to_json( $json, { canonical => 1, pretty => 1 } );
-my $layout = get_layout ;
+my $page = get_page ;
my $projs = mk_proj_list $json ;
-$layout =~ s/%PROJS%/$projs/ ;
-# print $layout ;
+$page =~ s/%PROJS%/$projs/ ;
+# print $page ;
gen_page
- ( PAGE => $layout
+ ( PAGE => $page
, FILE => 'index.html'
, TITLE => 'Apache Attic'
- , BODY => INDEX()
+ , BODY => get_file $INDX_TXT
) ;
gen_page
- ( PAGE => $layout
+ ( PAGE => $page
, FILE => 'resolution.html'
, TITLE => 'Board Resolution to move to the Attic'
- , BODY => RESOLUTION()
+ , BODY => get_file $RESO_TXT
) ;
gen_page
- ( PAGE => $layout
+ ( PAGE => $page
, FILE => 'process.html'
, TITLE => 'Moving a project to the Attic'
- , BODY => PROCESS()
+ , BODY => get_file $PROC_TXT
) ;
for my $tag ( sort keys %$json )
{ gen_page
- ( PAGE => $layout
+ ( PAGE => $page
, FILE => "projects/$tag.html"
, TITLE => "Apache Attic -- Apache $tag"
, BODY => mk_proj ( $tag, $json -> { $tag } )
) ;
}
-
-sub INDEX
- { <<INDEX ;
-<div class="section-content">
-<p>
- The Apache Attic was created in
- <a
href="http://www.apache.org/foundation/records/minutes/2008/board_minutes_2008_11_19.txt";>November
2008</a>
- to provide process and solutions to make it clear when an Apache project
has reached its
- end of life. Specifically to be:
- </p>
-<p style="font-family: monospace">
- "responsible for the oversight of projects which otherwise would not have
- oversight; and be it further ... is not authorized to actively develop and
release the
- projects under its oversight"
- </p>
-<p>It is intended to: </p>
-<ul>
- <li>Be non-impacting to users</li>
- <li>Provide restricted oversight for these codebases</li>
- <li>Provide oversight for active user lists with no Project Management
Committee (PMC)</li>
- </ul>
-<p>It is not intended to: </p>
-<ul>
- <li>Rebuild community</li>
- <li>Make bugfixes</li>
- <li>Make releases</li>
- </ul>
-</div>
-
-<h4 id="incoming">
- Getting into the Attic
-</h4>
-<div class="section-content">
-<p>There are two expected mechanisms by which a project may enter the Attic.
Either the managing
- Project Management Committee (PMC) decides it would like to move the
project, or The
- Apache Software Foundation's board dissolves the PMC and chooses to move
the project. </p>
-<p>In either case, the following may be useful: <a
href="resolution.html">Template Board Resolution</a>. </p>
-</div>
-
-<h4 id="candidates">
- When should a project move to the Attic?
-</h4>
-<div class="section-content">
-<p>Projects whose PMC are unable to muster 3 votes for a release, who have no
active committers or
- are unable to fulfill their reporting duties to the board are all good
candidates for the Attic. </p>
-</div>
-
-<h4 id="process">
- Process of moving into the Attic
-</h4>
-<div class="section-content">
-<p>This is defined in the separate <a href="process.html">process</a>
document. </p>
-</div>
-
-<h4 id="departure">
- Process of leaving the Attic again
-</h4>
-<div class="section-content">
-<p>Options are: </p>
-<ul>
- <li>Forking the project - we'll link to any forks which have been created
so please let us know</li>
- <li>Restarting the community in the Apache Incubator</li>
- <li>Recreating a PMC for the project</li>
- </ul>
-</div>
-
-<h4 id="contact">
- Contacting the Attic PMC
-</h4>
-<div class="section-content">
-<p>The Attic is managed by a Project Management Committee (PMC). Discussions
are found on
- the <a
href="http://mail-archives.apache.org/mod_mbox/attic-general/";>general@ mailing
list</a>
- and you are welcome to subscribe. </p>
-</div>
-
-<h4 id="incubator">
- Retired Incubator Projects
-</h4>
-<div class="section-content">
-<p>The Apache Incubator project is the entry path into The Apache Software
Foundation for projects and codebases wishing to become part of the
Foundation's efforts. Not all projects 'graduate' out of the Incubator and are
instead retired. Those retired projects may be found on the Incubator's <a
href="http://incubator.apache.org/projects/index.html#retired";>Project
page</a>. </p>
-</div>
-INDEX
- }
-
-sub RESOLUTION
- { <<RESOLUTION ;
-<div class="section-content">
-<p>The following is a sample resolution to move a project to the Apache Attic.
A project's
- chair should include this in the agenda for the next board meeting. </p>
-<pre>
- ?. Terminate the Apache {PROJECT} Project
-
- WHEREAS, the Project Management Committee of the Apache {PROJECT}
- project has chosen by vote to recommend moving the project to the
- Attic; and
-
- WHEREAS, the Board of Directors deems it no longer in the best
- interest of the Foundation to continue the Apache {PROJECT} project
- due to inactivity;
-
- NOW, THEREFORE, BE IT RESOLVED, that the Apache {PROJECT}
- project is hereby terminated; and be it further
-
- RESOLVED, that the Attic PMC be and hereby is tasked with
- oversight over the software developed by the Apache {PROJECT}
- Project; and be it further
-
- RESOLVED, that the office of "Vice President, Apache {PROJECT}" is
- hereby terminated; and be it further
-
- RESOLVED, that the Apache {PROJECT} PMC is hereby terminated.
- </pre>
-</div>
-RESOLUTION
- }
-
-sub PROCESS
- { <<'PROCESS' ;
-<div class="section-content">
-<p>At some point a project will vote to join the Attic. The following defines
a process
- to move that project into the Attic and gently close it down. </p>
-<ol>
- <li>A Project PMC decides to move to the Attic.
- <ul>
- <li>Conduct a discussion on whether to dissolve the PMC and move the
project to the Attic on the public dev list. Do not conduct it on the private
PMC list. </li>
- <li>Consider an appeal to the user list for interested users to
provide their interest in helping out more. </li>
- <li>Conduct a PMC vote on the public dev list. </li>
- <li>If the PMC votes to dissolve the PMC and move the project to the
Attic, inform the board of the successful vote (linking or forwarding the
'successful' vote) and add a <a href="resolution.html">resolution</a> to
dissolve the PMC to the next board meeting agenda. </li>
- <li>If the PMC can't get enough people to vote to dissolve the PMC
(and there are not three -1 votes), then that is grounds for moving the project
to the Attic. They should inform the board as above, noting that the vote
failed to get enough votes. </li>
- </ul>
- </li>
- <li>If the board approve the resolution, open a JIRA item - 'Move
${project} to the Attic'.<br /> Copy/paste the following items to the details
(see "How to" below for a description of each step):
- <ol type="1">
- <li>Confirm Board Resolution (if TLP)</li>
- <li>Delete from committee-info.txt (if TLP)</li>
- <li>Remove VP entry on <a
href="http://www.apache.org/foundation/";>http://www.apache.org/foundation/</a>
(if TLP)</li>
- <li>Inform users of the move to the Attic</li>
- <li>Create project page on Attic site:
http://attic.apache.org/projects/${project}.html</li>
- <li>Obtain source control karma and point source control mails to
general at attic
- <ul>
- <li>i. Update the project DOAP file (if any):
https://projects.apache.org/project.html?${project}</li>
- <li>ii. Make source control read-only</li></ul></li>
- <li>Move committee's PMC data file to retired (if TLP)</li>
- <li>Remove from <a
href="http://www.apache.org/#projects-list";>http://www.apache.org/#projects-list</a>
navigation (if TLP)</li>
- <li>Announce on <a
href="http://mail-archives.apache.org/mod_mbox/www-announce/";>announce at
apache.org</a></li>
- </ol>
- </li>
- <li>Open an <a
href="https://issues.apache.org/jira/browse/INFRA";>Infrastructure JIRA</a>
issue identifying the resources that need turning off/making read only.
Typically:
- <ul>
- <li>Remove files from <a
href="http://www.apache.org/dist/";>www.apache.org/dist</a></li>
- <li>Closing down of dev@, commits@ and private@ <a
href="http://mail-archives.apache.org/mod_mbox/";>mailing lists</a></li>
- <li>Close down the user mailing list (unless still active - in which
case propose a moderator to Infra)</li>
- <li>Make JIRA|Bugzilla read-only</li>
- <li>Make the wiki (Confluence|Moinmoin) read-only</li>
- <li>Delete unix/ldap group</li>
- <li>Turn off automated builds</li>
- </ul>
- </li>
- </ol>
-</div>
-
-<h4 id="General-pointers">
- How to: General pointers
-</h4>
-<div class="section-content">
-<p>The following are usefull svn/https locations:
- <ul>
- <li>svn site <a
href="http://svn.apache.org/repos/asf/attic";>http://svn.apache.org/repos/asf/attic</a></li>
- <li>site <a
href="http://attic.apache.org";>http://attic.apache.org</a></li>
- <li>jira <a
href="https://issues.apache.org/jira/browse/ATTIC";>https://issues.apache.org/jira/browse/ATTIC</a></li>
- <li>committees.xml <a
href="https://svn.apache.org/repos/asf/comdev/projects.apache.org/data/committees.xml";>https://svn.apache.org/repos/asf/comdev/projects.apache.org/data/committees.xml</a></li>
- </ul>
- </p>
-</div>
-
-<h4 id="confirm-resolution">
- How to: 1. Confirm Board Resolution (if TLP)
-</h4>
-<div class="section-content">
-<p>Check previous Board minutes (in SVN or to committers@) to confirm project
was retired.</p>
-</div>
-
-<h4 id="delete-pmc">
- How to: 2. Delete from committee-info.txt (if TLP)
-</h4>
-<div class="section-content">
-<p>Remove the PMC from <a
href="https://svn.apache.org/repos/private/committers/board/committee-info.txt";>https://svn.apache.org/repos/private/committers/board/committee-info.txt</a></p>
-</div>
-
-<h4 id="update-foundation-site">
- How to: 3. Remove VP entry on http://www.apache.org/foundation/
-</h4>
-<div class="section-content">
-<p>Access the CMS <a
href="https://cms.apache.org/redirect?uri=http://www.apache.org/foundation/";>here</a>
- and update the text. </p>
-<p>Check if the outgoing PMC chair is not chair of any other PMCs, then ask
infra to adjust the 'pmc-chairs' LDAP group accordingly.</p>
-</div>
-
-<h4 id="informing">
- How to: 4. Inform users of the move to the Attic
-</h4>
-<div class="section-content">
-<p>Let the users know that the project is moving into the Attic. Use the
following template: </p>
-<pre>
-A heads up for the ${project} user community that the ${project} project has
-been 'moved to the Attic'. This means that the ${project} developers (more
-formally its Project Management Committee) have voted to retire ${project}
-and move the responsibility for its oversight over to the Attic project.
-
-Loosely speaking this means that the projects resources will be moved to a
-read-only state.
-
-You can read more about the Apache Attic and the process of moving to the
-Attic at http://attic.apache.org.
-
-You can follow this process in JIRA:
-
- https://issues.apache.org/jira/browse/ATTIC-${#}
-
-Thanks,
-
-${Name} on behalf of ${project} + the Attic.
- </pre>
-<p>Remember to subscribe to the user list <a
href="https://whimsy.apache.org/committers/subscribe";>https://whimsy.apache.org/committers/subscribe</a>
to avoid moderation. Also bear in mind that the user mailing list may
- already know and you can skip this stage. Make sure you read that thread
if it does exist. </p>
-</div>
-
-<h4 id="atticsite">
- How to: 5. Create project page on Attic site:
http://attic.apache.org/projects/${project}.html
-</h4>
-<div class="section-content">
-<p>The Attic website is built using Anakia. Anakia is an old site technology
built on top of Apache Velocity.
- You can get the source for the site from Subversion: </p>
-<pre>svn co https://svn.apache.org/repos/asf/attic/site</pre>
-<p>Signal that <i>retired</i> banners must be added to ${project}.a.o. :</p>
-<ul>
- <li><code>mkdir docs/flagged/${project}.apache.org ;</code></li>
- <li><code>touch
docs/flagged/${project}.apache.org/${project}.apache.org</code></li>
- </ul>
-<p>To create a project page do:</p>
-<ul>
- <li>in xdocs/projects/ copy one of the files to the new project name (eg.
devicemap.xml)</li>
- <li>Add the new file as a link in the xdocs/stylesheets/project.xml
navigation</li>
- <li>Run 'ant' from the root (ie: the attic/site/ directory you checked
out)</li>
- <li>Review the generated files in docs/** in your browser</li>
- <li>SVN commit all changes. Remember to add both the new xdocs/ project
file and the new generated docs/ project file</li>
- <li>The new pages should go live quickly</li>
- </ul>
-</div>
-
-<h4 id="svnkarma">
- How to: 6. Obtain source control karma and point source control mails to
general at attic
-</h4>
-<div class="section-content">
-<p>follow the workflow <a
href="https://cwiki.apache.org/confluence/display/INFRA/Git+workflow+for+infrastructure-puppet+repo";>https://cwiki.apache.org/confluence/display/INFRA/Git+workflow+for+infrastructure-puppet+repo</a>,<br
/>
-sometimes it helps chatting with infra <a
href="https://www.hipchat.com/gIjVtYcNy";>https://www.hipchat.com/gIjVtYcNy</a>,<br
/>
-all work are done in
"{infra-repo}/modules/subversion_server/files/authorization/"</p>
-<ul>
- <li>Change "asf-authorization-template" so that the attic-pmc has
karma instead of the defunct project. </li>
- <li>Change "asf-mailer.conf" so that the attic-pmc has karma instead
of the defunct project. Add project to attic regex, and if there are a project
entry remove it</li>
- </ul>
-</div>
-
-<h4 id="doap">
- How to: 6.ii Update the project DOAP file (if any):
https://projects.apache.org/project.html?${project}
-</h4>
-<div class="section-content">
-<p>The files referenced are in <a
href="https://svn.apache.org/repos/asf/comdev";>https://svn.apache.org/repos/asf/comdev</a></p>
-<p>Identify whether the project has a DOAP file (see the <comdev
repo>/projects.apache.org/data/projects.xml file if update the rdf file with
PMC to the Attic and add a category of <em>retired</em>: </p>
-<pre>pmc change: <asfext:pmc rdf:resource="http://attic.apache.org"; />
-new category: <category
rdf:resource="http://projects.apache.org/category/retired"; /></pre>
-</div>
-
-<h4 id="PMCdata">
- How to: 7. Move committee's PMC data file to retired (if TLP)
-</h4>
-<div class="section-content">
-<p>If committee appears in <a
href="https://projects.apache.org/committees.html";>committees list</a>, moving
data to retired will remove it from the list.
- Notice that <a
href="https://issues.apache.org/jira/browse/COMDEV-182";>this task is being
automated</a>, then not necessary to track any more in the future...</p>
-<p>Comment PMC data files index entry (see the <a
href="https://svn.apache.org/repos/asf/comdev/projects.apache.org/data/committees.xml";>committees.xml</a>
file
- and old <a
href="https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects/pmc_list.xml";>pmc_list.xml</a>
file) and move PMC data file
- from <a
href="https://svn.apache.org/repos/asf/comdev/projects.apache.org/data/committees";>committees/</a>
directory
- to <a
href="https://svn.apache.org/repos/asf/comdev/projects.apache.org/data/committees-retired";>committees-retired/</a>.
- </p>
-</div>
-
-<h4 id="www.apache">
- How to: 8. Remove from http://www.apache.org/#projects-list navigation (if
TLP)
-</h4>
-<div class="section-content">
-<p>As a retired project, a <a href="http://www.apache.org/#projects-list";>link
on the front page of Apache site</a> is no longer necessary. Remove the link
and regenerate the main Apache site.
- This is done via the <code>trunk/templates/blocks/projects.mdtext</code>
of the <a
href="https://cms.apache.org/redirect?uri=http://www.apache.org/index.html";>www.apache.org
CMS</a>. </p>
-<p>It's also worth checking that the VP link from <a
href="http://www.apache.org/foundation/";>http://www.apache.org/foundation/</a>
has been removed. </p>
-</div>
-
-<h4 id="announce">
- How to: 9. Announce on annou...@apache.org
-</h4>
-<div class="section-content">
-<p>Announce that the project is now retired. Consider the following template.
</p>
-<pre>
-Announcing that the Apache ${project} committers have voted to retire
-the project due to inactivity. ${project} was {boilerplate}.
-
-Retiring a project is not as simple as turning everything off, as
-existing users need to both know that the project is retiring and
-retain access to the necessary information for their own development
-efforts.
-
-You can read more about ${project}'s retirement at:
-
- http://attic.apache.org/projects/${project}.html
-
-The user mailing list remains open, while the rest of the project's
-resources will continue to be available in a read-only state -
-website, wikis, svn, downloads and bug tracker with no change in url.
-
-Providing process and solutions to make it clear when an Apache
-project has reached its end of life is the role of the Apache Attic,
-and you can read more about that at:
-
- http://attic.apache.org/
-
-Thanks,
-
-${NAME}
-on behalf of the Apache Attic and the now retired Apache ${project} project
- </pre>
-<p>It's important to include the boilerplate from the project's site so people
- know what we're talking about. </p>
-</div>
-PROCESS
- }
