Site going live tomorrow unless...

[Henri Yandell <ba...@apache.org>]

I've updated the site with the comments from the previous thread. The
Process section reads:

*********
This won't be defined fully until we actually start moving projects
into the Attic. The following is a rough general plan of action.

   0. Prior to this the Apache Board has moved the oversight of the
project from its prior PMC to the Attic PMC.
   1. Indicate on websites that the project is in the Attic
   2. Make the SVN read only
   3. Inform user email list
   4. Consider killing user email list
   5. Kill the dev list
   6. README on archives for downloads
   7. Kill automated builds
   8. Retire in issue-trackers
   9. Remove from www.apache.org navigation
**********

It gives people an idea while leaving us room to adapt to projects.
I'm going to push this out tomorrow night unless I hear a -1.

We need to get the site up and out to PMCs. An example is that on the
Hivemind list there are users (2 or 3) trying to work on a release and
no committer in sight offering to apply their patch. For their sake
the Attic question needs to come up soon as a forcing function to get
an answer; and then we can have a use case to finish some of our
process (such as the 'if I fork on sf.net, what rules must I abide
by?').

Hen

Re: Site going live tomorrow unless...

[Rahul Akolkar <ra...@gmail.com>]

On Fri, Jan 9, 2009 at 2:56 AM, Henri Yandell <ba...@apache.org> wrote:
> We're live:
>
> http://attic.apache.org/
>
<snip/>

Made a few cosmetic changes (the styles were not pointing to the right
place and updated to say 2009). Waiting for sync.

-Rahul

P.S.-Are you a moderator? Allow rahul AT a.o please for the commits.


> Linked at the bottom of the project list on www.apache.org for now
> (when the servers next sync).
>
> Hen
>
> On Thu, Jan 8, 2009 at 12:52 AM, Henri Yandell <ba...@apache.org> wrote:
>> I've updated the site with the comments from the previous thread. The
>> Process section reads:
>>
>> *********
>> This won't be defined fully until we actually start moving projects
>> into the Attic. The following is a rough general plan of action.
>>
>>   0. Prior to this the Apache Board has moved the oversight of the
>> project from its prior PMC to the Attic PMC.
>>   1. Indicate on websites that the project is in the Attic
>>   2. Make the SVN read only
>>   3. Inform user email list
>>   4. Consider killing user email list
>>   5. Kill the dev list
>>   6. README on archives for downloads
>>   7. Kill automated builds
>>   8. Retire in issue-trackers
>>   9. Remove from www.apache.org navigation
>> **********
>>
>> It gives people an idea while leaving us room to adapt to projects.
>> I'm going to push this out tomorrow night unless I hear a -1.
>>
>> We need to get the site up and out to PMCs. An example is that on the
>> Hivemind list there are users (2 or 3) trying to work on a release and
>> no committer in sight offering to apply their patch. For their sake
>> the Attic question needs to come up soon as a forcing function to get
>> an answer; and then we can have a use case to finish some of our
>> process (such as the 'if I fork on sf.net, what rules must I abide
>> by?').
>>
>> Hen
>>
>

Re: Site going live tomorrow unless...

[Henri Yandell <ba...@apache.org>]

We're live:

http://attic.apache.org/

Linked at the bottom of the project list on www.apache.org for now
(when the servers next sync).

Hen

On Thu, Jan 8, 2009 at 12:52 AM, Henri Yandell <ba...@apache.org> wrote:
> I've updated the site with the comments from the previous thread. The
> Process section reads:
>
> *********
> This won't be defined fully until we actually start moving projects
> into the Attic. The following is a rough general plan of action.
>
>   0. Prior to this the Apache Board has moved the oversight of the
> project from its prior PMC to the Attic PMC.
>   1. Indicate on websites that the project is in the Attic
>   2. Make the SVN read only
>   3. Inform user email list
>   4. Consider killing user email list
>   5. Kill the dev list
>   6. README on archives for downloads
>   7. Kill automated builds
>   8. Retire in issue-trackers
>   9. Remove from www.apache.org navigation
> **********
>
> It gives people an idea while leaving us room to adapt to projects.
> I'm going to push this out tomorrow night unless I hear a -1.
>
> We need to get the site up and out to PMCs. An example is that on the
> Hivemind list there are users (2 or 3) trying to work on a release and
> no committer in sight offering to apply their patch. For their sake
> the Attic question needs to come up soon as a forcing function to get
> an answer; and then we can have a use case to finish some of our
> process (such as the 'if I fork on sf.net, what rules must I abide
> by?').
>
> Hen
>