From kde-scm-interest  Thu Jul 31 22:05:01 2008
From: Thiago Macieira <thiago () kde ! org>
Date: Thu, 31 Jul 2008 22:05:01 +0000
To: kde-scm-interest
Subject: Re: [Kde-scm-interest] Accountability, concrete suggestion
Message-Id: <200808010005.01496.thiago () kde ! org>
X-MARC-Message: https://marc.info/?l=kde-scm-interest&m=121754193228109
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--===============0891662185=="

--===============0891662185==
Content-Type: multipart/signed;
  boundary="nextPart5059514.1LmhfC08ZB";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart5059514.1LmhfC08ZB
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Stephen Kelly wrote:
>It seems strange that this isn't a solved problem. How does the linux
>kernel, or firefox (using Hg I believe) or any other big project using a
>DVCS handle accountability? One of the big selling points of DVCS is
> being able to have a few developers commit to a project at a local
> sprint, and push it later. Is it something specific to the structure of
> KDE that makes this an issue? We want to know the creater of every
> commit, but that's not something other projects are so concerned with,
> is it?

I don't know of other projects using DVCS and how they handle the=20
accountability. On the kernel side, it's all in the social network. Linus=20
trusts his closest lieutenants, who trust someone else in their turn, and=20
so forth. So all patches in Linus's tree come from someone he trusts.

But, then again, I do think that well thought-out patches coming from a=20
random person on the Internet could get applied if sent to the proper=20
people.

They don't try to have that accountability we're searching for here. And,=20
to tell you the truth, I also think all of this is overkill.

=2D-=20
=A0 Thiago Macieira =A0- =A0thiago (AT) macieira.info - thiago (AT) kde.org
=A0 =A0 PGP/GPG: 0x6EF45358; fingerprint:
=A0 =A0 E067 918B B660 DBD1 105C =A0966C 33F5 F005 6EF4 5358

--nextPart5059514.1LmhfC08ZB
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iD8DBQBIkjcNM/XwBW70U1gRApMEAKDApFqipnxA2u1HioTz9o0OBRbxXACeOIsP
GImVSbCeI9E4pPgeQY5ZIag=
=FCOo
-----END PGP SIGNATURE-----

--nextPart5059514.1LmhfC08ZB--

--===============0891662185==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
https://mail.kde.org/mailman/listinfo/kde-scm-interest

--===============0891662185==--