[Imc-aotearoa-tech] site passwords etc

[Miles Thompson]

Hello everyone,

Finn wrote:

>Whoa, hang on there. It's cool that duncan wants to get ssh access, as long as he knows the difference between ssh and ftp, and promises not to format any text with white backgrounds :-P Oh and you should let me show you around via irc.
>
>But . . 
>  
>

OK then. I guess thats an objection right there. So I'm certainly not 
gonna just give Rovin' the password any more. Personally my experience 
was that I received the password to the NYC imc site quite quickly but I 
guess they had seen me working up close and in person which is a bit 
different.

I like the idea that we have a proper process, and so I am into the idea 
of using the process that Finn outlines. Doing things the same as 
catKore sounds good.

Whatever we do Id like to reiterate how important I think it is that 
processes should be OPEN. That is everyone should know what the process 
is and how it works. Also its important that you do not route around the 
process in any 'special' situations, such as when you know someone 
personally, or trust them implicitly etc. This is not just because its 
'improper' but because doing things like that then results people 
outside of the 'inner circle' not knowing what the process is and 
feeling shut out of things. We need to have clear processes in order to 
be welcoming to new people.

::Proposed process for getting an ssh account ::

>- Someone establishes who they are on a list and in general makes themselves known by their work
>  either before joining AIM, or after. This can take any amount of time. As appropriate.
>- Someone asks for access (on the main collective list) and explains why they need it.
>- If no one objects within a week then they get it.
>

Of course now we have to also bootstrap the process of agreeing to the 
new process ;-) Just because I'd hate to see Rovin' or Leith waiting too 
long, perhaps we should give one week after Rovin' writes to the list 
for people to raise objections to the actual process too. That is if 
nobody objects we give Rovin' the password after one week, and establish 
that as the new process at the same time.

Incidentally, Rovin' already suggested that maybe the request should go 
to the main list,

I replied (off list) that..

> Part of me doesn't want to get into a situation where the main 
> collective needs to approve giving the password because they will get 
> confused between giving the password for editorial reasons whereby you 
> are basically giving people the right to change content on the site 
> (quite a big thing) and the technical password where technically sure, 
> you can change the content, but in practice one should be expected to 
> change only the technical bits.
>
> But anyway yeah, maybe you should do an email to the main list? 


I think we will have to be careful to explain the difference between the 
different passwords to the main list. Right ?

While we are at it maybe we should have  Leith go through the same process ?

--


Miles