19:02:37 #startmeeting nonatc 19:02:38 Meeting started Thu May 12 19:02:37 2016 UTC and is due to finish in 60 minutes. The chair is shamail. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:02:40 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 19:02:41 bye 19:02:43 The meeting name has been set to 'nonatc' 19:02:48 bye 19:02:58 Hi everyone, who is here for the recognition meeting? 19:03:00 o/ 19:03:00 bye 19:03:04 0/ 19:03:06 o/ 19:03:11 maishsk: big head 19:03:11 shamail: sorry for the delay in ending! 19:03:13 #chair maishsk 19:03:14 Current chairs: maishsk shamail 19:03:20 Np SumitNaiksatam! 19:03:26 o/ 19:03:28 dabukalam: :) 19:03:35 maishsk: do you mind leading this session? 19:03:55 shamail: I can give it a shot but will need your help every now and again 19:03:57 I am trying to put out an internal fire that just started before I need a fire extinguisher 19:03:57 o/ 19:03:58 :) 19:04:08 I'll monitor the meeting and chime in as needed 19:04:46 #agenda https://wiki.openstack.org/wiki/NonATCRecognition 19:04:57 #topic Review outcomes from F2F working session 19:05:05 Thanks! 19:05:34 Unfortunately I was not at the summit - so if someone would like to take the lead on giving us a summary of what was discussed? 19:05:58 #link https://etherpad.openstack.org/p/uc-recog-m2-output 19:06:11 #link https://etherpad.openstack.org/p/uc-recognition-roles 19:06:25 The team used the same etherpads from milestone-2 during the F2F 19:06:30 yes, we ran through those, and discussed 19:06:48 In general there was agreement with the approach and definition of activities (with the new addition of AskOpenStack) 19:07:17 I wanted to finalize the name of this WG based on the session 19:07:18 We also gained insight into how the Ops tag was generated for badges pre-summit 19:07:29 dabukalam: +1 19:07:52 Was the Ops tag beneficial in the summit? 19:08:05 maishsk: I think there was mixed response. I liked it, others didn't. 19:08:30 those that did not - was there any particular reason? 19:08:35 Many were unsure how it ended up on their badge 19:08:49 (it was also given to anyone who completed the user survey) 19:09:06 hrmmm. 19:09:10 or I believe anyone who was involved in organising an active usergroup 19:09:26 the idea being that it takes 30 mins to complete that survey, but we also covered that at the summit meeting 19:09:42 * shamail has to step away for a few minutes 19:09:48 Perhaps with the outcome of the WG - the criteria will be clearer 19:10:00 I think the general view was that while we appreciate filling in the survey, it's probably not going to end up on our list of contributions 19:10:12 Good point Dabukalam, i think we agreed to not inclide user survey completion for now 19:10:21 As Shamail already linked, this was the final list https://etherpad.openstack.org/p/uc-recog-m2-output 19:11:17 Anyone else have anything to add to readout? 19:11:52 if not then let’s move on to the next item 19:12:05 cool 19:12:07 #topic Close out milestone-2 and move to milestone-3 19:12:30 So milestone 2 is "Identify which community members are included in constituency and group-related activities into roles" 19:12:55 Are we all satisfied with the list that was proposed on the output? 19:13:13 #link https://etherpad.openstack.org/p/uc-recog-m2-output 19:13:18 I think based on the session, we should be able to close this milestone there is agreement 19:13:23 shamail: +1 19:13:28 +1 19:14:12 Can you add a #agree message Maishk? 19:14:15 #agreed List of contributors to be recognized are as noted on the etherpad above 19:14:25 #agree List of contributors to be recognized are as noted on the etherpad above 19:14:52 what about organizing community events? should that be included? 19:15:13 pholland: this was already covered and is part of the existing list I believe 19:15:18 pholland: does that not fall under - Official User Group organizers? 19:15:23 That is included but for the first phase it will only be officially recognize organizers and contributors 19:15:44 I don't see it on the etherpad 19:16:28 pholland: https://etherpad.openstack.org/p/uc-recog-m2-output 19:16:29 line #11 19:16:31 bullet point 1 19:16:53 although it only says organizers - not contributors 19:16:55 ok - that wasn't obvious to me 19:17:26 maishsk: I think we can safely say that anyone who contributes to the organisation of a user group falls under "organizer" 19:17:29 contributors - are defined as what role then? 19:18:03 dabukalam: I would agree 19:18:21 so on to the next item then? 19:18:44 yes please 19:18:45 #topic Obtain volunteers to research metrics collection methods for various activities 19:19:09 milestone-3 is defined as “Provide recommendations on how to gather identified metrics (favoring automation whenever possible)” 19:19:26 I will help with this task. 19:19:30 So let’s take the list one from above one by one 19:19:49 User group organizers - is there an official list? 19:20:05 maishsk: there is a list of official usergroups 19:20:12 is this something Tom can help us with - he was pulling some metrics during the meeting 19:20:12 there are a number of OpenStack groups on meetup.com 19:20:13 but not an official list of organisers 19:20:15 so, whoever volunteers to do this will need to co-ordinate with fifieldt and mrmartin to 19:20:18 get this information 19:20:24 MeganR: +1 19:20:30 We should also try to reuse the work Tom did for operator recognition. I don't have the link to the repository handy at the moment. 19:20:51 shamail: not only that, but turn it into a structure that can be automated and openly visible 19:21:04 So who would like to take this one? 19:21:12 +1 19:21:20 shamail: perhaps also talk to the maintainer of stackalytics to see if that's something that he can easily add to his web interface 19:21:25 I'll take it 19:21:30 stackalytics feels like a good place for this to belong 19:21:39 I agree 19:21:51 #action shamail to follow up on item #1 User group organizers 19:22:05 Next up - Active members of official UC Working Groups 19:22:33 So the group chairs should know who the active members are 19:22:44 Do we have a list of official UC working groups? 19:24:09 I would assume that the members of the UC have a list of working groups ? 19:24:36 And one more thing - are there WG’s that do not belong to the UC ? 19:25:15 there is a list here, I don't know how up to date it is https://wiki.openstack.org/wiki/Governance/Foundation/UserCommittee 19:26:10 That list looks right to me, or at least nothing glaring is missing 19:27:14 Would anyone like to take this point then? 19:27:44 OK then… 19:27:52 Not to my knowledge 19:27:58 do we need to reach out to the WG leaders? 19:28:07 There are cross project teams but they fall under ATC generally 19:28:22 Yes, we do meganr 19:28:22 just making certain they are active, I can also look at Wiki pages and meting notes 19:28:25 MeganR: I would start there - and come up with a recommendation on how this can be quantified 19:28:36 and hopefully automated 19:28:36 maishsk: are you looking for a volunteer to research into metrics for each bullet? I assumed shamail was volunteering to research into metrics for all contributors? 19:28:40 ok: I can take that item 19:29:06 WG don't have a standard meeting method some use IRC and others don't so we need to A) find membership and B) find out how they meet so we can try to automate collection in the future 19:29:08 #action MeganR Provide recommendations on how to gather identified metrics for Active members of official UC Working Groups 19:29:15 dabukalam: that is correct 19:29:25 I did indeed volunteer for all as a first step 19:29:37 But fine with dividing the load 19:29:44 shamail: I am sure that we can all pitch in 19:29:48 While I focus on alignment with Tom 19:29:50 next one Ops meetup moderators 19:30:04 This should be pretty easy - Tom should have a list 19:30:40 +1 19:30:49 I think our goal should be to discuss how we can take all of this information and put it in a centralised location so that it updates itself automatically 19:30:49 There is a google spreadsheet that he used 19:31:11 #action maishsk - Provide recommendations on how to gather identified metrics for Ops meetup moderators 19:31:17 dabukalam: +1, one off collection is fine but we need long term solutions too 19:31:37 dabukalam: +1 but to do that I think we first have to identify where all the info is 19:31:41 shamail: right, the one of collection can be our seed db 19:32:07 Next item - Contributions to any repository under UC governance (ops repositories, user stories repository, etc.) 19:32:08 but then we need to find a way to automate that, which may involve mandating that various groups document things differently from now on 19:33:06 Stackalytics - could be the way to get this 19:33:11 * dabukalam can see the conversation happening now. WG Organiser: "Well, why didn't I get a tag on my badge, or recognition?" ATCWG: "Well, did you update the wiki page with your name as an organiser?" 19:33:38 * persia expresses a worry that polling data from repos ends up confusing things, because repo contribution is the criteria for ATC, so suddenly the person isn't non-ATC anymore 19:33:41 maishsk: I think Stackalytics is one potential place for it to be, yes, but someone needs to talk to Ilya about how that swould work 19:34:08 persia: mind elaborating? 19:34:08 is there anything in Stackalytics for "non-technical" contributions, or something along those lines, or would something need to be built out? 19:34:17 not all repos qualify for ATC 19:34:47 MeganR: I think there are currently non-technical metrics in stackalytics 19:34:53 MeganR: I don’t see why it cannot cover all OpenStack repos as well 19:35:03 for example http://stackalytics.com/?metric=emails 19:35:09 Ah, if there is no overlap between repos that qualify for ATC and repos for this agenda item, I have no worries. 19:35:41 We will need to build it 19:35:47 ty 19:35:54 Once we identify what we are capturing metrics wise 19:36:08 I have to drop off, sorry everyone :( 19:36:13 I'll review etherpad 19:36:19 ah that makes sense - I am trying to jump ahead 19:36:22 Please feel free to assign action items to me as needed 19:36:30 bye Shamail and good luck 19:36:41 dabukalam: do you want to take a crack at this item? 19:37:03 maishsk: yes, I can take a look 19:37:04 thanks shamail 19:37:25 I'm also happy to look at the next one, track chairs 19:37:41 #action dabukalam - Provide recommendations on how to gather identified metrics for Contributions to any repository under UC governance 19:38:05 #action dabukalam - Provide recommendations on how to gather identified metrics for Track chairs for OpenStack Summits 19:38:08 Thanks 19:38:23 Next one - Contributors to Superuser (articles, interviews, user stories, etc.) 19:38:52 Nicole runs Superuser afaik 19:39:21 Any takers? If not then I will grab this one 19:39:22 I expect she will have a list/sheet somewhere with past/planned articles 19:39:59 #action maishsk - Provide recommendations on how to gather identified metrics for Contributors to Superuser 19:40:11 Next item - Submission for eligibility to review panel 19:40:23 Someone mind explaining some context ? 19:41:08 maishsk: Sorry, I actually can't recall what that is 19:42:01 Ah, perhaps it is an "other" section? 19:42:02 is that regarding reviewing the "additional" submissions 19:42:14 MeganR: not sure 19:42:17 perhap 19:42:18 s 19:42:28 I think that was the "other" category where a significant contribution could come from a category not previously listed 19:42:35 pholland: yes, that makes sense 19:42:59 so that's relatively easy, and doesn't require gathering metrics, but rather formation of a panel 19:42:59 and that there would be a review panel to evaluate 19:43:20 So what I understand from this is a set of criteria / metrics that will allow people to submit their nomination ? 19:43:45 maishsk: I think it needs to be a catchall 19:43:48 so hard to have metrics for that 19:43:50 So that would be coming up with a recommendation of what these criteria would be. 19:43:56 dabukalam: +1 19:44:05 maybe the action here should be to investigate what a panel should look like 19:44:16 Using a mechanism like extra-ATC is probably the easiest: where there is a list of identities in some repo, and gerrit is used to decide if changes are acceptable. Folk who might qualify are proposed for the list and voted by the panel. 19:44:29 we wouldn't need metrics though, these would be evaluated case by case 19:44:31 I think that is already part of milestone-4 19:44:35 yes, I think it would include the list of criteria/metrics for everything else and then an explanation of where to submit a significant contribution not covered in the other categories 19:44:39 “Establish/identify review board for self-nominated members” 19:44:46 maishsk: ah yes, you're right 19:44:58 persia: that does seem like a logical way 19:45:05 it's basically extra-AUC 19:45:40 persia: Do you want lead this point then? 19:46:21 maishsk: That wouldn't be a good idea: I almost never get to any of my todo items 19:46:39 Any other takers? 19:46:42 I'd be happy to provide a couple pointers to someone else if they need a hand finding info about extra-ATC 19:46:49 I can look at that as well 19:46:54 dabukalam: thanks 19:47:05 #action dabukalam - Provide recommendations on how to gather criteria / metrics for “extra-AUC” 19:47:15 Last one - Active moderators on ask.openstack 19:47:53 This information probably exists - just have to find out how to collect it 19:48:31 maishsk: yes, we discussed the moderator system there 19:48:43 I am going to pass this one off to shamail 19:48:45 I believe a.o.o already has metrics and a class/rewards system 19:49:28 #action shamail - Provide recommendations on how to gather identified metrics for Active moderators on ask.openstack 19:49:42 And that concludes the list (for now) 19:49:49 maishsk: cool 19:50:22 We have 10 minutes left 19:50:31 maishsk: we don't have to use them :) 19:50:37 dabukalam: +1 19:50:55 #topic Free-for-all 19:51:15 Anyone have anything else that they want to raise / discuss? 19:51:23 no, thanks 19:51:43 I'm good 19:51:49 Ok then 19:52:06 So that concludes my first time a meeting chair :) 19:52:16 excellent work! 19:52:17 Thank you all ! 19:52:36 maishsk: cool, thanks for taking over and running it 19:53:40 #endmeeting