On Wed, May 27, 2009 at 11:47 AM, Bonnie Corwin <[email protected]> wrote: > I think perhaps multiple issues are getting confused on this thread. And I > think Jim's been trying to clear that up.
+1 > If people see a need to differentiate between different kinds of inactive > projects, it would be helpful if the OGB would define categories and specify > banner text to go on each. I'd rather see the website community propose such a policy, and (if the website community agrees), implement it. The OGB doesn't really need to invent or impose this kind of policy on other people. That said, as a website community member (taking off my OGB hat), I propose that Jim keep on doing what he has already described. If it needs more formalism, then: The lifecycle policy for collectives (user groups, projects and communities) currently covers the creation mechanisms. It needs to be extended to cover additional scenarios for inactive and never got started collectives: For collectives that are empty and dead (that never started, never got "unhid", or are otherwise content-free and unused for some reasonable length of time), the "project setup folks" may simply garbage collect the mess: Turn off the forums and email lists, delete the associated (presumably effectively empty) mail and forum archives, delete the web site and repo content (again, presumably effectively blank), etc... Collectives that were actually started and generated non-trivial artifacts should probably not be deleted, but become inactive instead. For collectives that have content, but are inactive or completed, the community leaders should be able to request that the collective become "inactive". They (or the tonic team or ...?) would then cause the web content to be marked (via CSS?) as "inactive", turn off the forum stuff and disable the mailing list. All web content, repos and mailing list archives will be kept as-is with the expectation that they will be read-only. If an inactive project becomes active again, the preceding steps need to be able to be reversed. Does this cover everything? -John _______________________________________________ website-discuss mailing list [email protected]
