[IMC-Tech] Draft: How to properly shut down an IMC

[john duda]

it would also be cool to have some sort of freeze and archive
procedure in place - would be nice to keep dead sites alive (with
publishing turned off, transformed to static html, maybe with a frame
explaining the site is dead) for historical reasons.  ideally there'd
be some way to do so that doesn't break existing inbound links...

-john


On Mon, Sep 07, 2009 at 10:24:51AM -0700, mark burdett wrote:
> IMO it would be a good idea to have a formal process to shut down an 
> imc, e.g. letting a proposal sit on the imc-process list for 7 or 14 
> days, similar to the process for adding a new imc.  since the sites 
> are often inactive for a year before anyone notices, an extra week or 
> two wouldn't be bad.
> 
> Also, might be nice to have a working group to focus on this task. or 
> maybe an existing working group like commwork would be up to the job.
> 
> --mark
> 
> On Mon, 07 Sep 2009 18:15:11 +0200, Alster wrote:
> > Hi,
> > 
> > taking part in some tech working groups which handle shared (between
> > several IMCs) services such as Listwork (lists.indymedoa.org), I realize
> > that we often do not get to know it when an IMC shuts down. As a result,
> > their services remain available, but are no longer maintained.
> > 
> > Depending on the type of service, this can cause this service to be
> > abused, such as by email or blog spammers or for exploit hosting. Even
> > if this does not happen, it is a waste of our limited resources. As
> > such, I'm putting together this document "How to properly shut down an
> > IMC". Its audience is meant to be both
> > * people who are shutting down their own IMC for the variety of reasons
> >   there can be and
> > * people who have become aware that an IMC is no longer maintained
> >   (whether or not they have volunteered as an Indymedia activist before)
> > 
> > The document should be usable both by people knowing the global
> > Indymedia structures and those who do not. It should be usable by any
> > person whether or not they have a broad or just a small tech background.
> > 
> > !!! I'm sending this draft here asking for your help in making it fit
> > !!! these requirements, correcting and completing it.
> > 
> > Once this is done, this should be resent to the working groups
> > references inside the draft. My hopes are that this document will be
> > used by new-imc, imc-tech and all the working groups references within
> > the document to notify the other relevant parties if they become aware
> > of an IMC which is no longer maintained.
> > 
> > _______________________________________________________________________
> > 
> > HOW TO PROPERLY SHUT DOWN AN IMC
> > 
> > If you become aware of an IMC which is no longer maintained, or if you
> > want to shut down your own IMC with a clear cut, please follow the steps
> > listed below.
> > 
> > 1. Look on the website of said IMC and on http://lists.indymedia.org for
> > contact addresses (email) of this IMC. Send an email to all of them,
> > saying that you think this IMC appears to be dead and state why you
> > think so. Ask them to get back to you within 14 days. If you receive no
> > reply within 14 days or the replies you receive support your impression
> > of this IMC being inactive, proceed to step 2. Otherwise, stop here.
> > 
> > 2. Send email to the following, reporting the results of step 1, the
> > name of the unmaintained or closing IMC, ideally their website and
> > mailing lists:
> > new-imc at lists.indymedia.org
> > imc-tech at lists.indymedia.org
> > imc-commwork at lists.indymedia.org
> > listwork at sos.indymedia.org
> > dns at sos.indymedia.org
> > 
> > 3. If you have the ability to determine their web hosting provider(s),
> > please do so, and contact them, too. The general way to do so is to
> > determine their IP addresses from their IMCNAME.indymedia.org domain
> > name, then run a whois and DNS reverse lookup on these IP addresses, and
> > determine the tech collective or ISP from this. Once you know this,
> > determine their email address and send an explanatory email to them,
> > similar to what you sent in step two.
> > 
> > _______________________________________________________________________
> > 
> > Alster
> > -- 
> > GPG key   http://zimmermann.mayfirst.org/pks/lookup?search=0x05059C17
> > GPG FP    1B8B 128F 8435 541C B3A5 1B7E CF5A 9D55 0505 9C17
> > Info      https://docs.indymedia.org/view/Main/AlsteR
> > 
> 
> 
> 
> > _______________________________________________
> > imc-tech mailing list
> > imc-tech at lists.indymedia.org
> > http://lists.indymedia.org/mailman/listinfo/imc-tech
> 
> _______________________________________________
> imc-tech mailing list
> imc-tech at lists.indymedia.org
> http://lists.indymedia.org/mailman/listinfo/imc-tech

-- 

this is where my public key can be found:
gpg --keyserver pgp.mit.edu --recv-keys 03817826
Key fingerprint = 6C11 8D70 2ADE EFA9 498D  72CB 77EA 391A 0381 7826