17:32:57 <riecatnor> #startmeeting Mindshare
17:32:57 <zodbot> Meeting started Wed Feb 12 17:32:57 2020 UTC.
17:32:57 <zodbot> This meeting is logged and archived in a public location.
17:32:57 <zodbot> The chair is riecatnor. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:32:57 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
17:32:57 <zodbot> The meeting name has been set to 'mindshare'
17:34:31 <riecatnor> #meetingname Mindshare Committee
17:34:31 <zodbot> The meeting name has been set to 'mindshare_committee'
17:34:57 <riecatnor> first lets look at tickets, one sec
17:35:19 <riecatnor> https://pagure.io/mindshare/issue/182
17:36:05 <riecatnor> seems fine to me, I will give a +1 and direct them to fedora-budget
17:36:15 <bt0> already voted :)
17:36:44 <hhlp> I just voted
17:37:11 <riecatnor> Thanks :)
17:37:23 <riecatnor> https://pagure.io/mindshare/issue/181
17:37:38 <riecatnor> so this one is a bit deeper. let's pause and go to some of the others
17:38:28 <riecatnor> https://pagure.io/mindshare/issue/180
17:38:33 <riecatnor> this just needed triage.
17:39:20 <riecatnor> https://pagure.io/mindshare/issue/169
17:39:49 <riecatnor> the newest request seems fine unless anyone objects
17:40:07 <bt0> it is fine for me
17:40:39 <riecatnor> my one concern is keeping the logo as it should be
17:40:49 <riecatnor> It might need to go through the design track
17:42:10 <bt0> ok, good point
17:45:21 <bt0> great response :)
17:45:24 <riecatnor> ok I think that is it for new tickets.. we can go back to 181 if everyone is up to it
17:45:33 <hhlp> ok
17:46:57 <bt0> ok
17:46:57 <riecatnor> @hhlp I am reading your comment and looking into this script you are linkin
17:47:54 <riecatnor> linging*
17:47:57 <riecatnor> linking** lol
17:48:10 <hhlp> ok. :) , we need to name it in one formal way -> Policy for no-response member
17:48:21 <riecatnor> My question is will this script be easily adaptable to all FAS groups?
17:48:27 <riecatnor> If so, I am all for it
17:48:28 <bt0> will be
17:48:30 <bt0> :)
17:48:36 <riecatnor> And I want to see metrics on more than just mindshare ;)
17:48:55 <bt0> I'm working on it
17:49:44 <riecatnor> I thank you! and everyone else who is giving input.. there is a lot of value in this
17:50:47 <riecatnor> I think it will be interesting to see the outcome. Also it makes me wonder if it will be more or less applicable to some teams
17:51:41 <bt0> the idea is get general stats for all kind of teams and handle some special cases too
17:52:16 <riecatnor> Yes, it can highlight those cases so we can look into the health of the teams. It's great. I think this is adaptable to the Mindshare team situation.
17:52:42 <riecatnor> We still need to come up with a guideline for what amount of activity seems reasonable
17:52:58 <riecatnor> For example, what percentage of meetings do we feel people should be able to attend?
17:53:11 <bt0> good metric
17:53:18 * bt0 is taking notes
17:53:21 <nasirhm> +1 on the Metric
17:53:24 <riecatnor> Thank you bt0
17:53:40 <nasirhm> Kindly share afterwards :bt0
17:53:41 <riecatnor> Beyond coming to meetings, how many tickets are they commenting on
17:54:25 <riecatnor> Besides those two places, what other kinds of things can we track with this script
17:54:52 <riecatnor> and to be in attendance at a meeting I think we have to do a more formal roll call at the beginning which is ok by me :)
17:55:03 <riecatnor> or can you just do, "who talks during a meeting"
17:55:59 <bt0> zodbot can help me with that
17:57:12 <riecatnor> are there other things we could track with this script for the mindshare team?
17:58:54 <riecatnor> hhlp, yes agreed on a formal policy
17:59:50 <riecatnor> I also think part of the policy should just be to reach out to the person individually.. understand what is going on
18:00:01 <bt0> I think is fine
18:00:24 <hhlp> altought all people help in mindhsare team would be in _FAS_ Group to keep tracked
18:01:33 <bt0> that is right
18:01:50 <bt0> hhlp is not in the group
18:02:13 <riecatnor> oh hmm we can fix that
18:03:48 <riecatnor> should be all set
18:04:50 <bt0> cool
18:05:05 <riecatnor> ok, so we've agreed that the script is a good way to measure this.
18:05:15 <hhlp> +1
18:05:25 <riecatnor> What do we feel is an acceptable amount of meetings to be in attendance
18:05:36 <riecatnor> 75%?
18:05:53 <riecatnor> I realize this is not peoples day job tho. Maybe 50% is more reasonable
18:05:57 <bt0> sounds a good number but we need to set a timeframe
18:06:35 <riecatnor> I would say, we take the last year to start and it will give us a good indication. Problem is I don't believe mindshare meetings were being tracked?
18:06:57 <riecatnor> I think if that is the case, we take from the start date, and evaluate after 3 months.
18:07:36 <bt0> good
18:08:53 <riecatnor> Seems good to me as well :)
18:09:17 <riecatnor> bt0 please update us when things progress.. thank you again!
18:09:32 <bt0> :)
18:09:50 <riecatnor> I believe last time we were talking about ambassadors?
18:09:56 <riecatnor> is nb around?
18:11:22 <bt0> ping nb
18:12:02 <hhlp> this is a nice script to clean up any _FAS_ Group for example ambassador
18:14:06 <riecatnor> hhlp, good point
18:14:34 <riecatnor> I think the ambassador program and situation is more complex than those metrics at this point though.
18:15:14 <riecatnor> I believe thoughtful consideration needs to go into re-crafting ambassadors/advocates/outreach.. I think the council should be a part of that kind of restructuring as well.
18:15:58 <riecatnor> It might be useful to make some kind of document that gives a summary of all 3 of those initiatives/groups.
18:15:59 <bt0> i do that work back in the Flock
18:16:12 <riecatnor> bt0, please share!
18:16:18 <bt0> i can runn the old script and get the active members
18:16:48 <hhlp> at least they can know how many incative user they have
18:17:31 <riecatnor> I agree, it will most likely provide some value. The point I am trying to make is that because things were restructured to an extent already, I am not sure how much activity there will be to measure.
18:17:59 <riecatnor> For example things the ambassador group used to vote on became mindshare's responsibilities, if I understand that correctly.
18:18:09 <hhlp> uhmm. ok
18:18:59 <bt0> yes...https://plot.ly/~hotgalan/25/fedora-ambassadors-by-country/#/
18:19:48 <riecatnor> cool!
18:20:14 <bt0> https://pagure.io/fedora-commops/issue/203
18:20:28 <bt0> has a taticaresquest.ods
18:20:52 <bt0> wait Ambys2.ods
18:22:26 <riecatnor> bt0, can you clarify?
18:24:00 <bt0> i mean a file with the raw data showing number of activities in certain timeframes
18:24:28 <bt0> the name of that file is Ambys2.ods and it's attached to that ticket
18:25:29 <riecatnor> got it :P
18:26:11 <bt0> I can reproduce this same updated output
18:26:40 <riecatnor> I think that is a good idea. We can take a look at how things stand currently
18:26:41 <bt0> in a few hours, tha script is in my home computer
18:26:52 <riecatnor> ok, great!
18:27:19 <riecatnor> It seems we are almost out of time.. I think we made some good progress :)
18:28:02 <hhlp> ok good, I think the TOTAL is a value but not a good Metric, ACTIVE MEMBER is it
18:28:46 <bt0> yep,
18:29:51 <hhlp> I can apply for ambasador then forge it and take part of the TOTAL but I don't produce any value
18:31:08 <bt0> the it is the total, i have some active sisnce jan 1, 2019
18:31:17 <bt0> *since
18:31:33 <hhlp> :)
18:31:45 <riecatnor> Thanks bt0 and hhlp !
18:31:52 <riecatnor> #endmeeting