> 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 like that idea. But we should the folder i.a.o/retiredpodling not simply have a httpd redirect rule pointing to the incubator status page? The state of the podling is reflected there very well and there is even a chance to send a personal message Christian > > 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: [email protected] > For additional commands, e-mail: [email protected] > > -- http://www.grobmeier.de --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
