Is there a formal procedure for end-of-lifeing, archiving and otherwise shutting down completed/abandoned projects and mailing lists? It would be good to have some set of written expectations in place before y'all start the migration; it would also allow the rest of us to be a bit more proactive in cleaning up our old messes :-)
Things that would be nice to address (kindof the opposite of project-setup): How to shut down jive gateway(s)? How to shut down mailing list(s)? What to do with existing jive/mailinglist archives? What to do with associated repositories? What to do with website content? I believe that, in many cases, we don't want to lose the historical content of the mailing lists, repos and website, but instead would like them to become read-only-ish and labeled as "archives"... How do we avoid "losing history" as part of this transition? -John On Sun, May 24, 2009 at 8:23 PM, Jim Grisanzio <[email protected]> wrote: > Having abandoned lists and forums is only part of the problem, of course, > but it is a problem we can easily solve with a use-it-or-lose-it policy. I > am working my way through some deal lists/forums now as part of the website > clean up prior to the move. Dead lists are easy to deal with. Low traffic > ones are more difficult since they are, in fact, owned. However, I think we > should start taking down the Jive forums to help this situation. If you > don't absolutely need a forum, I'd love to see people start volunteering to > have the forums deleted. I am happy to do this. Ping me on project-setup. _______________________________________________ website-discuss mailing list [email protected]
