On Sat, Aug 20, 2011 at 05:25:00PM -0400, Benson Margulies wrote:
> >> On Sat, Aug 20, 2011 at 02:59:33PM +0300, Daniel Shahaf wrote:
> >> > Gavin McDonald wrote on Sat, Aug 20, 2011 at 16:35:47 +1000:
> >> > > The retirement guide [1] makes no mention of removing podling
> >> > > websites but I think they should all be removed at retirement,
> >> > > thoughts?
> >> >
> >> > This doesn't need to be on private@...
> >>
> >> Good catch, Daniel. My preference would be to avoid erasing podling web
> >> presences on retirement,
>
> If an RO svn is retained, some sort of web presence explaining it
> makes sense to me. But I agree that a pseudo-active-project web site
> is not the right sort of web presence.
Yes, I also agree that a site which misleads visitors into thinking that a
retired podling is active is not desirable.
When a top-level project enters the Attic, its website gets updated to reflect
the fact that it has been retired. For instance, all of Hivemind's web pages
have a big red banner alerting visitors to the project's status:
http://hivemind.apache.org/
http://hivemind.apache.org/download.html
Provided that someone is willing to do that work, that there is zero ongoing
maintenance burden, and that there are no practical or legal difficulties, I
think something similar would also be OK for a retired podling -- however,
that's not necessarily my preferred approach.
Another option which might be cleaner and less burdensome to administer would
be to create a boilerplate "Retired Podling" static html page which would
replace the website for any podling which does not graduate. This page would
give a brief explanation of the project's history and status and point at any
remaining resources, such as read-only SVN if the podling completed a
successful code grant.
If there is interest in that idea, I volunteer to help create the template for
the "Retired Podling" page.
I have two objectives with this proposal. The first is practical: we should aid
users who may come looking for a project to learn what happened to it with
minimal effort.
The other goal is to help podlings retire with dignity. Every software project
has a life cycle, there are many reasons why a podling might not make it
to graduation, and a lot may have been accomplished during an attempt at
incubation. I think our default policy should be to recognize and celebrate
the contributions that a podling's volunteers made while it was active.
Marvin Humphrey
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
