[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-scm-interest
Subject:    Re: [Kde-scm-interest] accountability
From:       Johan_Sørensen <johan () johansorensen ! com>
Date:       2009-11-13 14:28:35
Message-ID: 9e0f31700911130628g60f962bera689087619032ab3 () mail ! gmail ! com
[Download RAW message or body]

On Fri, Nov 13, 2009 at 8:01 AM, Boudewijn Rempt <boud@valdyas.org> wrote:
> After all, once the e.V. can have the backups of the database, as discussed
> already, the rest is a simple matter of writing a policy document and pointing
> external contributors at it.

OK, I'm not sure exactly how this turned into a common idea. We simply
cannot provide anyone with complete database dumps. Period.
We have a privacy policy with all existing Gitorious.org users and an
internal policy against any form of data-sharing against users' will.
I just want to make that clear before it turns into something that's
commonly accepted by stating it enough times.
Now, obviously that does not in any way rule out an exit strategy, as
long as it complies with our privacy rules (or is accepted by the
affected users).


As for the actual topic of the thread; aren't you trying to find a
cure for a symptom here? Even if you knew exactly who committed it,
the code would still be bad and/or evil. So either the ring of people
you trust with commit access is too big or you don't have enough peer
reviews as I see it. Not that I'm against the idea of implementing
some kind of tracking here, it just seems like the wrong place to try
and fix things to me. But then again, I'm not really part of the KDE
community so my point is probably moot here..


Cheers,
JS
_______________________________________________
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
https://mail.kde.org/mailman/listinfo/kde-scm-interest
[prev in list] [next in list] [prev in thread] [next in thread]