Why would someone care or even see them ? Are you regularly crawling the maven repo for new artifacts ? We don't have to be ashamed if a podling does not graduate, so I don't think we have to try erasing the memory of this podling. A non graduated podling could still be revived at a later time or being forked outside of the ASF.
On Mon, Jun 2, 2008 at 6:21 PM, James Carman <[EMAIL PROTECTED]> wrote: > On Mon, Jun 2, 2008 at 12:17 PM, Brian E. Fox <[EMAIL PROTECTED]> wrote: >>>Part of the Incubation process is to ensure that there is sufficient >>>community to maintain the code after incubation. >> >> >>>It seems a bad idea to allow artefacts into the main repository where >>>they can become dependencies unless there is some chance that they >>>will be maintained. >> >> This is an argument for saying that TLP Apache projects can't depend on >> incubator artifacts then. Otherwise those projects suddenly don't work >> because a dependency disappeared. >> >> I personally don't think this should be the case. If they are released >> and someone wants to use them, then they should go into central where >> they live forever like everything else. Just because the community goes >> away does not mean the artifact should disappear too. >> > > But, doesn't that somewhat hurt the Apache name if we have a bunch of > orphaned projects sitting out there in limbo with our name on it? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
