On Thu, Nov 2, 2017 at 6:17 PM Dave Fisher <[email protected]> wrote:
> > > Sent from my iPhone > > > On Nov 2, 2017, at 3:08 PM, sebb <[email protected]> wrote: > > > >> On 2 November 2017 at 21:07, Dave Fisher <[email protected]> wrote: > >> Actually when the podling is retired the SVN and or GIT must be > deleted. It’s mean, but if people cared they could have contributed and > kept it going. > > > > Huh? > > > > The website is deleted, but AFAIK SVN/Git is just made read-only. > > I guess I may be wrong and misremembering something Greg Stein wrote in > the past. > I'm not even sure I agree with deleting the websites. It was a project. Now it's not. That doesn't mean the information should no longer be available. But not sure the resources need to be covered. > > Regards, > Dave > > > > >> Regards, > >> Dave > >> > >> Sent from my iPhone > >> > >>> On Nov 2, 2017, at 1:56 PM, Christopher <[email protected]> wrote: > >>> > >>> Should the Apache Incubator update the README on all retired podlings, > to > >>> more clearly indicate their retired status? > >>> > >>> For example, from the README at > https://github.com/apache/incubator-pirk , > >>> it's not obvious that the podling is retired. > >>> > >>> I know there's a RETIRED.txt file, but that's easily overlooked. I > suggest > >>> the Incubator PMC updating the retired projects' README's with an > >>> indication that the podling is retired, perhaps with a link to an > >>> explanation of what that means: > >>> https://incubator.apache.org/guides/retirement.html#what_is_retirement > >>> > >>> For example, simply inserting the following line at the top of retired > >>> podlings README's may suffice: > >>> > >>> This project is [retired]( > >>> https://incubator.apache.org/guides/retirement.html#what_is_retirement > ) > >>> > >>> I don't think this is a big deal, but might be something nice to do. > >>> Another option is to stop mirroring retired podlings to GitHub, but > that > >>> just seems mean. > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [email protected] > >> For additional commands, e-mail: [email protected] > >> > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
