[Imc-communication] Re: [IMC-Process] PROPOSAL: Principles of Unity / Principes d'Unité / Principios de Unidad

joe ttx joe.ttx at blablaxpress.org
Fri Apr 8 00:45:45 PDT 2005


[fr] salut tous le monde

Avant de vouloir "figer" les PoU, je pense qu'il serait intéressant  de 
rediscuter, un a un ces principes… et ca risque de prendre du temps, 
mais le réseau, je crois, a besoin de ces clarifications.

aussinon, j'ai créer un chan #pou sur chan.indymedia.org  bienvenu :)


[en silly]

ey all

Before wanting "to solidify" the PoU, I think that it would be 
interesting to discuss again,  one by one these principles...  there's 
a lot of chance that it takes some time, but the network, I believe, 
needs these clarifications. anyway, I have to create a chan #pou on 
http://chan.indymedia.org … so welcome :)

[es systran]

hola tod at s

Antes de querer "solidificar" el a PoU, pienso que sería interesante 
discutir de nuevo, el tiene unos estos principios... y Ca riesgo de 
tomar tiempo, pero la red, creo, necesita estos aclaraciones.

  tengo crear un chan #pou  sobre http://chan.indymedia.org  : 
bienvenida :)


in solidarity
joe



Le 07-avr.-05, à 19:30, sheri at speakeasy.org a écrit :

> hi onto,
>
> i think an irc discussion(s), spontaneous and scheduled, would be a 
> great idea and supplement to the proposal discussion, especially since 
> there are issues being brought up that would be better off resolved 
> through diverse communication channels.
>
> anyone can set up a room in irc.  once you've named it, just let 
> people know what the name is.  perhaps #pou makes the most sense.  i'm 
> sure anyone who regularly is in irc can easily do that :) just make 
> sure there are logs if the conversation gets interesting.
>
> i'd be happy to help coordinate with others for a scheduled irc 
> discussion.  it's probably long overdue :)
>
> i've also included communication list.
>
> love
> sheri
>
>> -----Original Message-----
>> From: onto [mailto:onto at riseup.net]
>> Sent: Thursday, April 7, 2005 04:27 PM
>> To: imc-process at lists.indymedia.org
>> Subject: Re: [IMC-Process] PROPOSAL: Principles of Unity / Principes 
>> d'Unité / Principios de Unidad
>>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> [en]
>>
>> Hi,
>>   Is there a room in http://chat.indymedia.org for a discussion of
>> these PoU? Maybe there can be meetings, scheduled and spontaneous,
>> inter-imc and intra-imc, in that potential room to further the
>> debate? Can someone set up such a room?
>>
>> [Should I be sending this out to imc-communication instead of
>> imc-process?]
>>
>>
>> [es]
>>
>> Hola,
>> ¿Hay un cuarto en el http://chat.indymedia.org para una discusión de
>> estos PoU? ¿Quizá puede haber las reuniones, planificado y
>> espontáneo, entierra-imc e intra-imc, en que el espacio potencial a
>> aún más el debate? ¿Puede establecer alguien tal espacio?
>>
>> ¿ [lo debo estar mandando yo fuera a la imc-comunicación en vez del
>> imc-proceso?]
>>
>>
>>
>> [fr]
>> Il y a une pièce dans http://chat.indymedia.org pour une discussion
>> de ces PoU ? Peut-être il peut y avoir des réunions, planifiées et
>> spontanées, l'inter-imc et le dans-imc, dans que la pièce potentielle
>> à plus le débat ? Peut-quelqu'un établir une telle pièce ?
>>
>> [devrais-j'envoyer ceci hors à l'imc-communication au lieu de
>> l'imc-procédé ?]
>>
>>
>> [de]
>>
>> Gibt es ein Zimmer in http://chat.indymedia.org für eine Besprechung
>> über diese PoU? Kann vielleicht es Versammlungen, geplant und
>> spontan, beerdigt imc und intra imc, in das potenzielles Zimmer
>> geben, die Debatte zu fördern? Kann jemand so ein Zimmer aufstellen?
>>
>>
>> [Soll ich imc Kommunikation dies statt imc-Verfahren schicken?]
>>
>> - -------------------------
>>
>> caminando preguntar,
>> onto
>>
>> http://sandiego.indymedia.org
>>
>>
>> encrypted mail preferred; my public key can be found like this:
>> gpg --keyserver pgp.mit.edu --recv-keys AC53B55C
>> Key fingerprint = F31E EFE8 78C4 3B11 F7CE  8979 5FB3 F737 AC53 B55C
>>
>>
>>
>> Anna wrote:
>>> question of process:
>>>
>>> since imc-process is a liaison list (and bilingual!) that debates
>> and
>>> decides about proposals by imc *groups* i propose that if
>> individuals
>>> and/or liaisons feel the need to discuss this proposal: this should
>>
>>> happen on imc-communication. (anyone active with indymedia can
>> subscribe
>>> and is invited to share their views)
>>>
>>> once a consensus seems near it can move as a proposal (with a
>> deadline)
>>> back to imc-process, where liaisons can translate and relay the
>> proposal
>>> to their groups.
>>>
>>> ----
>>>
>>> verfahrensfrage:
>>>
>>> da imc-process eine liaison-, oder vertreterInnenliste ist (und
>>> zweisprachig!), die vorschlaege (proposals) von imc-*gruppen*
>> diskutiert
>>> und entscheidet schlage ich vor, dass, falls einzelpersonen
>> und/oder
>>> liaisons den vorschlag weiter diskutieren wollen, dies auf
>>> imc-communication stattfinden sollte. (alle koennen die liste
>> abonnieren
>>> und sind eingeladen, sich mitzuteilen)
>>>
>>> sobald ein konsend gefunden scheint, kann der als vorschlag (mit
>>> deadline) zurueck nach imc-process, wo die liaisons ihn uebersetzen
>> und
>>> an ihre gruppen weiterleiten koennen.
>>>
>>> Anna
>>>
>>> xmux schrieb:
>>>
>>>> GarconDuMonde wrote:
>>>>
>>>>>
>>>>> this is a proposal that the draft Principles of Unity be accepted
>> as no
>>>>> longer draft, i.e. that the Principles of Unity become "official"
>> within
>>>>> the IMC Network.
>>>>>
>>>>
>>>> I didn't actually realize that the PoUs were only at draft status
>> but
>>>> if you're going to talk about making them official I guess this is
>> my
>>>> last opportunity to complain about one of them:
>>>>
>>>> " 9. All IMC's shall be committed to the use of free source code,
>>
>>>> whenever
>>>> possible, in order to develop the digital infrastructure, and to
>> increase
>>>> the independence of the network by not relying on proprietary
>> software."
>>>>
>>>> I will never been able to accept this how it is written.  After
>> people
>>>> confronted me about my lack of respect for the free software
>> movement
>>>> and pointed this 'rule' out to me I thought about it and concluded
>>
>>>> that I was unable to continue to do technical work for my local
>> IMC or
>>>> the Indymedia network.
>>>>
>>>> I won't go into detail about my personal objections to the FOSS
>>>> movement because that discussion does not belong here.  Likewise,
>> this
>>>> vaguely worded 'rule of thumb' does not belong in the list of
>>>> principles and should be removed and replaced with an unspoken
>>>> understanding that people making decisions about the technical
>>>> infrastructure of Indymedia should be rational and use common
>> sense.
>>>>
>>>> A summary of my argument against PoU #9:
>>>>
>>>> 1) The way it is worded makes it difficult to know what it means
>> or
>>>> how it should be applied.
>>>>
>>>> 2) It is not universally adhered to or respected across the
>> network
>>>> anyways.  There are Windows and Apple workstations in many
>> indymedia
>>>> centers including my local IMC.  One of the three most popular
>>>> codebases is written on a development platform that is pretty much
>>
>>>> proprietary.
>>>>
>>>> 3)  It's hard to see what relevance free software advocacy has to
>> an
>>>> organization whose primary purpose is to publish independent news.
>>
>>>> Not only that but it gives free software advocates the power to
>> force
>>>> IMC journalists to waste their time trying to do their work with
>>>> awkward, unfamiliar, and incomplete free software tools when
>> superior
>>>> alternatives are available.   Let's let the people that are
>> actually
>>>> doing the work decide what tools they need to get the job done.
>>>>
>>>> xmux
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> imc-process mailing list
>>>> imc-process at lists.indymedia.org
>>>> http://lists.indymedia.org/mailman/listinfo/imc-process
>>>>
>>>>
>>> _______________________________________________
>>> imc-process mailing list
>>> imc-process at lists.indymedia.org
>>> http://lists.indymedia.org/mailman/listinfo/imc-process
>>>
>>
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.2.1 (MingW32) - WinPT 0.7.96rc1
>>
>> iD8DBQFCVV9XX7P3N6xTtVwRAo/RAKCZuIDRC/zCVp1m+2aIvLlZonl1BwCgqSiJ
>> FTeKtaemRQAFvZGLxFhiFVE=
>> =u/1U
>> -----END PGP SIGNATURE-----
>>
>> _______________________________________________
>> imc-process mailing list
>> imc-process at lists.indymedia.org
>> http://lists.indymedia.org/mailman/listinfo/imc-process
>>
>
>
> _______________________________________________
> imc-process mailing list
> imc-process at lists.indymedia.org
> http://lists.indymedia.org/mailman/listinfo/imc-process
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/enriched
Size: 9315 bytes
Desc: not available
Url : http://lists.indymedia.org/pipermail/imc-communication/attachments/20050408/8f718c1e/attachment.bin 


More information about the IMC-communication mailing list