[New-imc] [imc-commwork] citieslist

[Alster]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hi everyone,

joe ttx wrote:
> Le 21-oct.-07 à 21:23, Alster a écrit :
>> joe ttx wrote:
>>> I'm joe from new-imc. After some reflexions on new-imc, we think that
>>> it would be reagent
>>> that they are the new-imc volonteers who upgrade the citieslist.
>> Are you saying that new-imc has decided that new-imc are (exclusively)
>> going to upgrade the cities list on contact.indymedia.org in the  
>> future?
> 
> no no, I m just involved to the new-imc group and i see often a long  
> delay between the integration of some imcs and the integration in the  
> citieslist

Oh I got you wrong there, sorry for that. I agree such delays do occur
often.

>> I imagine IMC Commwork would appreciate this. However, it should be
>> noted that having a superuser account (so you can edit other IMCs)  
>> also
>> comes with a certain degree of responsibility (and new-imcers already
>> have a lot), and the more superuser accounts are there the higher  
>> is the
>> chance one of their passwords is leaked.
> 
> yes, the concentration of the responsibilities is not always a good  
> idea. Perhaps I do not include/understand very well the  
> responsibility for a superuser

Well, this is mostly about using good and unique passwords and keeping
them secret, as well as to double check every change you make on the
database and to not screw up because of the not-too-intuitive user
interface.

It also means not changing entries if you cannot sufficiently verify
that the requestor is whom she is pretending to be or if the requestor
cannot convince you that she is acting for the group which is usually
making the decisions for changes as the ones they are requesting. I.e.
there's potential for foreign misuse and superusers need to prevent of
making changes on behalf of malevolent people.

This is what I can think of nright now, others from imc-commwork may
have more to add.

>> For the purpose of our information, can you point us to the public
>> mailing list archives where new-imc's discussion on such matters has
>> taken place and the decision was taken?
> 
> is not a decision, just a discussion (to which I was not)

Okay, sorry again, I seem to have misunderstood you there, too.

> boud say : (…) As for the proposed themes: i think many of your  
> questions are to do
> with our contact database contact.indymedia.org, and it would make
> most sense to discuss it with people from imc-commwork. If we had more
> people working on the contact database software, and more new-imc
> people updating the database (e.g. we could consider all old
> applications older than 1 year, where we've heard nothing from them
> for 1 year, as being closed), then i think that might help partly with
> some of these problems.  When/if i have time, i will volunteer some
> time. (…)
> 
> http://lists.indymedia.org/pipermail/new-imc/2007-September/0921-1g.html
> 
> I decided to take a little my time after this reading for upgrading  
> this citieslist
> 
> 
> I see that boud transform my personal request to imc-commwork into a  
> collective decision on
> New-imc.
> http://lists.indymedia.org/pipermail/new-imc/2007-October/1021-68.html
> 
> (Perhaps my error was to make a copy of my mall to new-imc ? Oo)
> 
> When, in my request, i said "i'm from new-imc", it was like a kidly  
> roll call' for imc-commwork, not less, not more. (awkward perhaps)

Nah, I don't think this was kidly or awkward. Welcome to imc-commwork.
Still, may we get to know a little bit more about you, like, which is
your local IMC?

> I agree with ana http://lists.indymedia.org/pipermail/new-imc/2007- 
> October/1021-bo.html
> and anarco babe http://lists.indymedia.org/pipermail/new-imc/2007- 
> October/1022-yb.html
> 
> it is better to invold myself "formally" in imc-commwork, which I  
> will do soon

Well, don't make it all that formal. ;-)

> (sorry for this silly english, but i think understanding english  
> correctly)

It doesn't seem silly to me at all, but then, I'm not a native speaker
either (and sorry for my silly english!).

Alster
- --
GPG key
http://keys2.indymedia.org/cgi-bin/lookup?op=get&search=05059C17
Fingerprint    1B8B 128F 8435 541C B3A5 1B7E CF5A 9D55 0505 9C17
All other      https://docs.indymedia.org/view/Main/AlsteR
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFHH3p3z1qdVQUFnBcRCtevAJ95DDJyI+30Uo3c3I8cr7Ke69/rhACeI5A3
dQAYe7DBNjc3OUgMWge0oLA=
=g2Nl
-----END PGP SIGNATURE-----