-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I was reading "developer policy" and noticed that cvs access seemed to be different than developer access. Is there different policy for both? I assume that developer access means direct ssh access to the server.
Concerned about your privacy? Follow this link to get FREE encrypted email: https://www.hushmail.com/?l=2
Free, ultra-private instant messaging with Hush Messenger https://www.hushmail.com/services.php?subloc=messenger&l=434
Promote security and make money with the Hushmail Affiliate Program: https://www.hushmail.com/about.php?subloc=affiliate&l=427
On Mar 13, 2004, at 07:42, perl@hush.ai wrote:
I was reading "developer policy" and noticed that cvs access seemed to be different than developer access. Is there different policy for both? I assume that developer access means direct ssh access to the server.
"Developer access" is a marker on wiki user accounts. It is largely obsolete, but used to allow read-write access to the database through an interface in the wiki. This is just a little too potentially dangerous (unencrypted connection with weak authentication + ability to alter or erase the entire database) so was removed. Having "developer access" doesn't necessarily make you a developer (only doing work to develop the software does that!) and being a developer doesn't necessarily mean you have "developer access".
CVS access is the ability to check code updates into our CVS repository on sourceforge. It doesn't relate to our servers at all.
A number of developers have login access on our servers to install and configure things there and to maintain backups, statistics, etc.
-- brion vibber (brion @ pobox.com)
Brion Vibber wrote:
On Mar 13, 2004, at 07:42, perl@hush.ai wrote:
I was reading "developer policy" and noticed that cvs access seemed to be different than developer access. Is there different policy for both? I assume that developer access means direct ssh access to the server.
"Developer access" is a marker on wiki user accounts. It is largely obsolete, but used to allow read-write access to the database through an interface in the wiki. [...]
It seems that you haven't actually answered his question (about the policy with regards to this kind of access).
I've also asked questions about it before and I've been ignored. Is there something we're not supposed to know? :-p
CVS access is the ability to check code updates into our CVS repository on sourceforge. It doesn't relate to our servers at all.
Thing is, there are a number of tasks ([[Wikipedia:Changing attribution for an edit]] for example) for which write-access to the DB is necessary, and CVS access doesn't help.
What is being done about this? Clearly, we need more people with write-access if we want less-than-important tasks like this to get handled, but of course I'm very aware of the potential risk associated with an account that has DB write-access. This is why I asked if it was possible to grant this access only temporarily (e.g. for 24 hours), so someone can perform the task without all these risks associated with it.
Timwi
On Mar 13, 2004, at 14:23, Timwi wrote:
Brion Vibber wrote:
On Mar 13, 2004, at 07:42, perl@hush.ai wrote:
I was reading "developer policy" and noticed that cvs access seemed to be different than developer access. Is there different policy for both? I assume that developer access means direct ssh access to the server.
"Developer access" is a marker on wiki user accounts. It is largely obsolete, but used to allow read-write access to the database through an interface in the wiki. [...]
It seems that you haven't actually answered his question (about the policy with regards to this kind of access).
There is no policy about it because it isn't used anymore.
I've also asked questions about it before and I've been ignored. Is there something we're not supposed to know? :-p
What was your question?
CVS access is the ability to check code updates into our CVS repository on sourceforge. It doesn't relate to our servers at all.
Thing is, there are a number of tasks ([[Wikipedia:Changing attribution for an edit]] for example) for which write-access to the DB is necessary, and CVS access doesn't help.
What is being done about this?
I believe a tool for this is being added to the software in the next versions. Currently there's a command-line hack since it's a relatively rare task.
Clearly, we need more people with write-access if we want less-than-important tasks like this to get handled, but of course I'm very aware of the potential risk associated with an account that has DB write-access. This is why I asked if it was possible to grant this access only temporarily (e.g. for 24 hours), so someone can perform the task without all these risks associated with it.
That doesn't make a lot of sense; somebody with regular write access would still have to grant the temporary access, negating the benefit.
-- brion vibber (brion @ pobox.com)
wikitech-l@lists.wikimedia.org