1 |
Happy Thursday/Friday Daniel & Rich, |
2 |
(and hi to all thread participants) |
3 |
|
4 |
I favour the idea of data-driven decision making. |
5 |
|
6 |
For what it's worth, I would like to help on the aspect, if y'all decide to |
7 |
go forward with automated data gathering/collection projects. |
8 |
|
9 |
Cheers, |
10 |
Seemant |
11 |
|
12 |
|
13 |
*--* |
14 |
*Oakland Finish Up Weekend* |
15 |
Be Amazed. Be Amazing. |
16 |
Get Mentored | Get Inspired | *Finish* *Up* |
17 |
http://oaklandfinishup.com |
18 |
|
19 |
|
20 |
On Thu, Oct 6, 2016 at 5:43 PM, Daniel Campbell <zlg@g.o> wrote: |
21 |
|
22 |
> On 10/03/2016 09:00 AM, William L. Thomson Jr. wrote: |
23 |
> > On Friday, September 30, 2016 8:59:15 PM EDT Rich Freeman wrote: |
24 |
> >> |
25 |
> >> The Issue |
26 |
> >> Recently there has been some questioning of whether we have the right |
27 |
> >> balance of privacy in Comrel disputes. |
28 |
> > |
29 |
> > Anonymous stats can be produced and released without releasing any |
30 |
> private |
31 |
> > information. |
32 |
> > |
33 |
> > Such as but not limited to the following: |
34 |
> > |
35 |
> > # of cases brought to comrel |
36 |
> > # of cases resolved amicably |
37 |
> > # of warnings issued |
38 |
> > # of cases resulting in policing action, suspension, ban, etc |
39 |
> > # of developers kicked/booted |
40 |
> > # of developers recruited |
41 |
> > |
42 |
> > For each of the above, there would be another field, # of comrel members |
43 |
> who |
44 |
> > voted or took part in such action. That will show if it is just |
45 |
> individuals |
46 |
> > having their way, or if comrel is working as a team. May even go so far |
47 |
> as to |
48 |
> > record votes, x number for, x number against for each. |
49 |
> > |
50 |
> > There could be more, but such information is very useful. All of such |
51 |
> will |
52 |
> > provide a measure of accountability. It does not reveal any sensitive |
53 |
> > information. This would be like annually at minimum, monthly at maximum. |
54 |
> > |
55 |
> > This could even be produced retroactively so we could see if this had an |
56 |
> > impact on the project at any given point in time. I suspect that might |
57 |
> be the |
58 |
> > case in the past. |
59 |
> > |
60 |
> I really like this idea. We already have a script that tells us the |
61 |
> latest additions and removals for ebuilds; why not something for |
62 |
> developers as well? It could give us concrete ideas of not only how |
63 |
> Comrel is 'performing', but also how proxy-maint or other recruiting |
64 |
> avenues are increasing our staffing to meet bug or package maintenance |
65 |
> demands. |
66 |
> |
67 |
> Of course, I don't think writing that script would be quite as easy, so |
68 |
> one or two stats at a time would be a great start. |
69 |
> |
70 |
> -- |
71 |
> Daniel Campbell - Gentoo Developer |
72 |
> OpenPGP Key: 0x1EA055D6 @ hkp://keys.gnupg.net |
73 |
> fpr: AE03 9064 AE00 053C 270C 1DE4 6F7A 9091 1EA0 55D6 |
74 |
> |
75 |
> |