Re: [Kde-scm-interest] accountability

2009-11-14 Thread Jeff Mitchell
Thomas Zander wrote: > On Saturday 14. November 2009 22.23.22 Chani wrote: >> I still don't understand why we need access to email addresses from some >> gitorious database anyways. > > I don't know if we do, Johan said that this is not really a solution anyway. > Thats why I put up 2 usecases w

Re: [Kde-scm-interest] accountability

2009-11-14 Thread Thomas Zander
On Friday 13. November 2009 14.17.24 Ian Monroe wrote: > I was thinking of asking Gitorious if they could keep a simple log of > commit hashs and the user name or id that pushed it. Since commit > hashs are completely unique this would be enough information. That log is indeed what is required, AF

Re: [Kde-scm-interest] accountability

2009-11-14 Thread Thomas Zander
On Saturday 14. November 2009 22.23.22 Chani wrote: > I still don't understand why we need access to email addresses from some > gitorious database anyways. I don't know if we do, Johan said that this is not really a solution anyway. Thats why I put up 2 usecases which will be solution independe

Re: [Kde-scm-interest] accountability

2009-11-14 Thread argonel
2009/11/14 Chani > On November 13, 2009 08:06:49 Jeff Mitchell wrote: > > Ian Monroe wrote: > > > Which is why I like my simple flat-file log idea (a log of commit > > > hash, user id, maybe time). It doesn't open up any privacy issues > > > (since the info is already public) and would solve the

Re: [Kde-scm-interest] accountability

2009-11-14 Thread Chani
On November 13, 2009 08:06:49 Jeff Mitchell wrote: > Ian Monroe wrote: > > Which is why I like my simple flat-file log idea (a log of commit > > hash, user id, maybe time). It doesn't open up any privacy issues > > (since the info is already public) and would solve the problem by > > using the comm