On Sat, Aug 20, 2011 at 7:06 PM, Marvin Humphrey <[email protected]> wrote: > 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.
Btw, the work is a search and replace on the <body... > tag. I generally find one that works on the site content but fails on javadoc (as inserting a header into a <frame> system is painful). Hen --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
