[Boston-editorial] Proposal: hide half-assed hacking coverage

[Robert]

Seeing as how Boston was not as devastated as other area IMCs, thanks to
having a smart and willing tech team inhouse, I recommend we combine an
brief explanation of what happened into a larger press release/welcome to
the new site the day we move to a new codebase.  A paragraph of what
happened, a line about our decision to move, and then right into the good
stuff about added security and new features.  I'd certainly like to see
writers working on a feature list rather than dwelling on this subject,
which has already been covered in the comments.

Thanks,

r


Jonathan D. Proulx said:
>
> I agree it's not feature material, but it's a good talking point.  I see
> no
> advantage in trying to pretend it didn't happen, and even if there were
> it's
> far too late now.
>
> It might be a good idea to write up something of our experience, I notice
> that Boston isn't on any of the lists posted all over, presumably because
> we
> didn't take any down time.
>
> Most of the techie folks are spending all their free cycles getting the
> new
> site in order, but I could write a two or three paragraph brief for the
> newswire, but I'd need the following questions answered:
>
> should we run an article on it? if so:
>
> when was the defacement noticed, how long was it up, do we want to mention
> the new site
> in development?
>
> -Jon
> _______________________________________________
> Boston-editorial mailing list
> Boston-editorial at lists.indymedia.org
> http://lists.indymedia.org/mailman/listinfo/boston-editorial
>