[Imc-aotearoa-ed] writing 'how-to' - good v bad articles - geo relevance - ed pol - me@indy.nz - links

Sat, 18 Jan 2003 16:01:57 +1300

--Message-Boundary-19107
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: Quoted-printable
Content-description: Mail message body

OK Duncan, here's the text file. Ken

On 17 Jan 2003 at 18:40, rovin nz wrote:

> --writing how-to:
> Ken, your notes from that session were sent in mime format so I couldn't=
 read them and
> they're not readable in the archive. If you send them to the list in tex=
t it should be
> fine. Otherwise email them to me and I can put them into wiki as a start=
ing place for
> whatever we do next.
> 
> --'good' vs 'stupid' articles:
> Finn reminded Danyl that 'bad journalism' doesn't mean we can hide it. I=
'm guessing that
> when we move to DadaImc =F6r SFActive we will have that 'rating' system =
working - then we
> can see wether people think an article is any good or not. Here is a Dad=
aImc site with
> ratings on the newswire: http://baltimore.indymedia.org/newswire/
> 
> --geographic relevance:
> While I happen to agree with finn saying this is just a technical issues=
 i think we have
> to make things work with the site we have now and not wait for something=
 better. So, we
> should keep this discussion alive and probably be very strict with overs=
eas stories.
> 
> --editorial policy:
> Danyl, when you get a chance can you repost your suggestion from the arc=
hive with an
> obvious header. i would find it now but the mailserver is (unbelievably)=
 down yet
> again!!! But, danyl - i'd love to work together with you on a new ed pol=
icy, we'll do
> that on this list like you suggested and then post it to the general lis=
t when we have a
> draft. there is a wiki we can use which has the current policy with some=
 tweaks in it
> http://docs.indymedia.org/view/Aotearoa/EditorialPol13 ... i just read t=
hrough the
> changes, all made by me and didn't find anything where i'd changed the a=
ctual policy,
> only where I'd tried to make it easier to understand by changing a few w=
ords or
> reformatting. anyway, you're welcome to check it yourself. maybe we shou=
ld start again on
> a new page?
> 
> --me@indymedia.org:
> Danyl, thanks for being polite even though you seem to be quite pissed o=
ff with me. I've
> never 'blocked' this initiative, i just keep saying that the pros and co=
ns need to be
> carefuly documented before there is anypoint asking the list for concens=
us. "Do you want
> this? It's free and might be useful" gets an easy "yes please!" but does=
n't get much
> thoughtful input. I would refer to the archive but it's done. I want one=
 of us to go
> through and find all the questions and their answers and post them as
> "you@indymedia.org.nz FAQ" or somesuch. Then we can have a proper discus=
sion...
> 
> Danyl mentions "I think giving our volunteers a free email address is th=
e same as giving
> trusted volunteers admin passwords for the site, mailing lists etc. I do=
n't see Rovin
> proposing to give everyone (or nobody) admin access to the site in case =
secure passwords
> are perceived as conferring special authority over Indymedia to those wh=
o have them."
> Actually, the fact that you haven't seen me do that is only because I ha=
ven't 'earned'
> the site passwords myself so don't feel I can talk about ALL the passwor=
ds. As it happens
> I would love it if all passwords were rotated - so that once you were in=
 each
> 'trust-ring' you periodically had each password. Anyone whose been on gl=
obal lists has
> heard the problems some IMCs have when 'tight' tech crews getting out of=
 hand.
> 
> --links:
> I have a set of nz political and activist links at the moment in a sorry=
 state
> http://kropotkin.indymedia.org/~rovin/nz_links02.html . I have finally g=
ot all the things
> i need working on the computer at home to develop a databased, openpubli=
shing version of
> those links. I've just found php3links ( http://sourceforge.net/projects=
/php3links/ ) and
> will probably be basing my project on that. If we can make it work the w=
ay we want i
> would like to see it included in the AIM site.
> 
> cheers, rovin
> (who now has a computer password again so he can get online)
> 
> Har du problemer med din hjemmecomputer? F=E5 hj=E6lp med Yahoo!s PC-sup=
port p=E5 http://dk.shopping.yahoo.com/pcsupport/index.html
> 
> _______________________________________________
> Imc-aotearoa-ed mailing list
> Imc-aotearoa-ed@lists.indymedia.org
> http://lists.indymedia.org/mailman/listinfo/imc-aotearoa-ed
> 

--Message-Boundary-19107
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Content-description: Text from file 'Writing for Indymedia.txt'

Writing and Publishing for Indymedia

Why
To counter the corporate media's distortions and unwillingness to 
cover the efforts to free humanity.

What
Researched, topical articles
Eye-witness accounts of progressive actions and demonstrations
Local, regional, national and international issues and events
Media analysis
Investigative reports exposing social and economic injustices
Stories about events affecting under-represented groups
Media produced by under-represented groups
Text, audio and video recordings, photographs

How
In both Te Reo and English ('Dialogue, Decode, Decolonise')
'Copyleft' - stories free for non-profit re-use
Around 300-600 words. Short words are better!
Heading - interesting, short, summary, question
First sentence - ditto
Paragraphs - short e.g. 3-4 sentences
Signature, pseudonym or anonymous
Acronyms - explain after first use
References - publication or website for further reading
Use bold/italics where helpful
Check spelling of names (Google is useful)
Avoid libel, unsubstantiated opinion, plagiarism, or racist, sexist, 
etc. comments

--Message-Boundary-19107--