[Foundation-l] Process for a project to request a setting

[Simetrical]

On Tue, Jul 8, 2008 at 2:19 AM, Ting Chen <Wing.Philopp at gmx.de> wrote:
> Thanks for your answer. This process does not seem to work well. Here is an example:
>
> https://bugzilla.wikimedia.org/show_bug.cgi?id=14624
>
> Two months already and no response. Also no request for a link. And see the last comment from es-wp, so it seems to be a general problem that can potentially hit every project. My impression is that there are no body who feel responsible for this. If it is so, I think we should set up a responsible person for this. As far as I know it doesn't happen every day and it is surely not a thing that takes a lot of time.
>
> Any opinion or suggestions?

It does take a fair amount of time to handle all the requests
promptly, and by all reports it's horribly boring.  The basic problem
is that with the current setup, anyone with the ability to institute
these changes has root database access, which requires an *extremely*
high level of trust (since anyone with such access can change anything
on any wiki untraceably, including logs and histories).  So it's not
like a few new people could just be given these rights so they can
handle it.  It used to be that Brion would reliably fulfill all the
shell bugs every now and again, but he's too busy for that these days.

One solution, and probably the most sensible, would be to use an
extension like Configure that allows people with much lesser access
levels to change these settings.  The other would be to assign the job
to someone like that new junior developer we're supposed to getting,
which is possibly less reasonable but probably easier (once we do get
some more tech employees who can be assigned stuff like this).