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 accountability. On the kernel side, it's all in the social network. Linus trusts his closest lieutenants, who trust someone else in their turn, and 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 random person on the Internet could get applied if sent to the proper people. They don't try to have that accountability we're searching for here. And, to tell you the truth, I also think all of this is overkill. -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org PGP/GPG: 0x6EF45358; fingerprint: E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Kde-scm-interest mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-scm-interest
