Jim Grisanzio writes:
> So, that`s how I am addressing John`s question (which was a reasonable
> one). We don`t lose any history when xyz community opened in 2005 and
> remains empty today with spam living on its lists and all the project
> leads sitting on the beach. It`s those extreme cases like that I`d like
> to clean up.
Two points:
- You really need to have this discussion out in the communities
where it'll have some effect. Engage that thread and see if you
can quiet the concerns about deleting old junk. The OGB echo
chamber doesn't count, nor do I. ;-}
- Even in those extreme cases of long-dead projects, the technical
areas are different. We've got unchanged documents from two
decades ago that are still quite relevant and useful for people
trying to understand how old parts of the code still work. When a
project goes dormant, there needs to be some way to (a) make sure
that newbies don't trip on it and (b) the important information
[even if it grows somewhat stale over time] is preserved
somewhere.
On that second point, it seems like the community consensus for (a) is
that we should just paste a big "this is dead now" sticker on the
front and leave everything alone rather than deleting anything, and,
assuming that isn't possible, then for (b) there should be some sort
of dead project archive where these can be moved rather than deleting
them.
--
James Carlson, Solaris Networking <[email protected]>
Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
_______________________________________________
website-discuss mailing list
[email protected]
