12:30:57 <bexelbie> #startmeeting Mindshare
12:30:58 <zodbot> Meeting started Mon Apr 30 12:30:57 2018 UTC.  The chair is bexelbie. Information about MeetBot at http://wiki.debian.org/MeetBot.
12:30:58 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
12:30:58 <zodbot> The meeting name has been set to 'mindshare'
12:31:03 <bexelbie> #topic roll call
12:31:05 <bexelbie> .hello bex
12:31:06 <zodbot> bexelbie: bex 'Brian (bex) Exelbierd' <bexelbie@redhat.com>
12:31:17 <bexelbie> #chair jflory7 jsmith mleonova nb  jwf robyduck x3mboy
12:31:17 <zodbot> Current chairs: bexelbie jflory7 jsmith jwf mleonova nb robyduck x3mboy
12:31:30 <jwf> .hello jflory7
12:31:30 <jsmith> .hello2
12:31:31 <zodbot> jwf: jflory7 'Justin W. Flory' <jflory7@gmail.com>
12:31:37 <zodbot> jsmith: jsmith 'Jared Smith' <jsmith.fedora@gmail.com>
12:32:02 <bexelbie> #chair jwf
12:32:03 <zodbot> Current chairs: bexelbie jflory7 jsmith jwf mleonova nb robyduck x3mboy
12:32:12 * bexelbie isn't sure if zodbot needs that or not
12:32:38 <jwf> All good :-)
12:32:41 <robyduck> .hello robyduck
12:32:42 <zodbot> robyduck: robyduck 'Robert Mayr' <robyduck@gmail.com>
12:32:46 <jwf> Wasn't as late as I thought I would be
12:33:45 <bexelbie> I haven't heard from mleonova[m] x3mboy or nb
12:35:32 <jwf> I have not either
12:36:02 <bexelbie> two of our new tickets involve x3mboy so let's skip them for now
12:36:07 <jsmith> WORKSFORME
12:36:15 <bexelbie> #topic Monthly update
12:36:18 <robyduck> bexelbie: I think mleonova[m] still has no IRC, or at least limited
12:36:22 <bexelbie> #link https://pagure.io/mindshare/issue/17
12:36:32 <bexelbie> anyone had a chance to read the bullet points?
12:36:37 <bexelbie> anything missing?
12:36:43 * jwf clicks
12:36:56 <jwf> Oh, I didn't get an email for your comment! Weird
12:37:18 * jsmith has no other bullets to add at this time
12:37:32 <jwf> Not from me. I think the Ambassador discussion drove this month
12:37:51 <robyduck> +1 for this monthly update, it's pretty full of news already
12:38:15 <bexelbie> ok, I'll try to get a draft started that covers those bullet points
12:38:28 <bexelbie> shall I move to the next topic?
12:38:38 <jsmith> bexelbie: Sure... let me know if you want me to proof it :-)
12:38:44 <bexelbie> jsmith, I do
12:38:48 <jwf> bexelbie: If there's anything we can do to help review, let us know
12:38:56 <jwf> Nothing else on this topic from my side
12:39:04 <bexelbie> #topic next meeting chair
12:39:09 <bexelbie> figured I'd do another easy thing
12:39:12 <bexelbie> I am at a conference next week
12:39:17 <bexelbie> who can chair?
12:39:39 <bexelbie> #info bexelbie is traveling next week - we need a chair
12:39:44 <jwf> I won't be able to make the next two, possibly three, meetings :-(
12:40:46 <bexelbie> anyone able to drive the meeting?  If not this suggests we cancel as we won't have active attendance
12:41:24 * robyduck is not sure he is around 100%, but if I am I can chair
12:41:37 <robyduck> we should see how may we are, and can cancel also next monday
12:41:41 <jwf> bexelbie: It may help to put this to the mailing list too
12:41:45 <robyduck> (if needed)
12:42:03 <bexelbie> jwf, if we cancel, yes.  is that what you mean?
12:42:10 <jwf> We're not at 100% today, but I know x3mboy might be wiped out from FLISoL this weekend
12:42:41 <bexelbie> ok, let's put this in robyduck's hands? sound good?
12:42:52 <jwf> +1
12:42:57 <robyduck> ok for me
12:43:12 <bexelbie> #action robyduck to chair next meeting or cancel it based on attendance
12:43:27 <bexelbie> #topic ambassadors discussion
12:44:06 <bexelbie> we've had more good feedback.  I think it is definitely time to start writing the actual policy.  I know I can start on it, but I'd really like some experienced ambassadors who know where there is policy we can borrow and edit to help
12:44:12 * bexelbie was hoping nb would be here
12:44:27 * bexelbie was hoping this is something robyduck and nb could help drive as FAMA
12:45:41 * jwf nods
12:46:10 <robyduck> we have many policies flying arund in the wiki....
12:46:21 <jwf> I'm happy to help with feedback or review but not enough bandwidth to write it
12:46:42 <robyduck> I think nb and me can help
12:47:19 <robyduck> but jwf is welcome
12:47:30 <bexelbie> robyduck, if you all could pull together the existing policies that might be worth keeping/editing that would be a huge start
12:47:43 <bexelbie> I suggest actually copying the text into something we can edit
12:47:47 <bexelbie> as opposed to just having links
12:47:55 <bexelbie> that way we can build a good starter system
12:48:19 <bexelbie> I think we all agreed last week (iirc) that we'd like to get a solid base and iterate, not try to build perfect from the start
12:48:26 <bexelbie> is my memory correct?
12:48:42 <robyduck> bexelbie: yes, this also is the moment we need to filter out all the outdated and invalid content on the wiki and maybe put these policies into docs
12:49:11 <jwf> bexelbie: There's never such thing as "perfect" anyways :-)
12:49:12 <jwf> +1
12:49:17 <jsmith> bexelbie: Yes, iterating is best
12:49:18 <robyduck> bexelbie: it's impossible to build perfect from the start, let's start small and then improve
12:49:32 <bexelbie> robyduck, +100 to filtering out the wiki
12:49:49 <bexelbie> I think keeping a list of urls to mark as "outdated" when we are done would be a good thing to do at the same time
12:50:01 <bexelbie> robyduck, are you ok with me making this an action for you and nb?
12:50:02 <robyduck> nod nod
12:50:15 <robyduck> yes
12:50:31 * jwf also likes the idea of redirecting all these old policy pages to the documented policy later
12:50:38 <jwf> So taking note of the policy pages is probably helpful to do
12:50:44 <robyduck> but as we are mostly all ambassadors too, anyone's help is very welcome
12:51:21 <bexelbie> #action robyduck and nb to create an editable document that contains the text of the existing policies that apply to what mindshare envisions so we can edit them.  We will build a base we can implement an iterate from.  Robyduck and nb will also build a list of urls that should be outdated when the new policy goes live.  Everyone will help edit the text robyduck and nb create.
12:51:27 <bexelbie> sound good?
12:51:35 <bexelbie> besides being long :d
12:52:33 <jwf> +1
12:52:40 <jsmith> +1
12:53:06 <robyduck> yeh
12:53:47 <bexelbie> #topic open floor
12:53:51 <bexelbie> anything else from folks?
12:54:03 <bexelbie> I suggest we hold the two tickets involving x3mboy until next week
12:54:14 <jwf> I'm hoping to drive the conversation for the CommOps rep this week
12:54:19 <jwf> (on the CommOps side)
12:54:21 <bexelbie> +1
12:54:37 * nb here
12:55:21 <nb> FYI I should be here every week but will be ~30 min late
12:55:28 <nb> since I am usually commuting to work
12:55:30 <bexelbie> ok
12:55:31 <nb> but i am here now
12:55:46 <bexelbie> can you read back for what we are "volunteering" you for?
12:55:57 <bexelbie> This ----> robyduck and nb to create an editable document that contains the text of the existing policies that apply to what mindshare envisions so we can edit them.  We will build a base we can implement an iterate from.  Robyduck and nb will also build a list of urls that should be outdated when the new policy goes live.  Everyone will help edit the text robyduck and nb create.
12:55:59 <nb> yes, i can help with that
12:56:03 <bexelbie> sweet
12:56:30 <robyduck> nb++
12:56:59 <nb> FYI everyone gets to give more cookies tomorrow, so if you wnat to give people cookies for f27, give them today
12:57:03 <bexelbie> any other topics for discussion? if not I can move to close
12:57:42 <robyduck> bexelbie: At every release I wonder if the release announcement shouldn't be under mindshare wings, at least the outreach part (put all the bullet points into something we can publish)
12:58:11 <robyduck> it's always a "we release in 10 minutes, please review" thing
12:58:28 <bexelbie> robyduck, I think we should contribute for sure - I believe the way to influence it is via the beta announcement, but I amnot usre
12:58:34 <bexelbie> I think x3mboy may know more of hte process
12:58:35 <jwf> I feel like the release announcement is definitely a Marketing task
12:58:46 <jwf> Fitting the definition of "marketing execution" that we covered in the FAD
12:58:57 <jwf> I think we should have input and Mindshare should provide feedback if needed
12:59:18 <jwf> But actually, I think Marketing formally handed this over to mattdm now
12:59:48 <jsmith> bexelbie: The only thing I have for the open floor is some feedback from itamarjp in the LATAM meeting late last week
13:00:05 <robyduck> jwf: not that we need to overrule mattdm, but at least work with him. Just a thought for future releases, to be discussed with marketing
13:00:28 <jwf> robyduck: +1 on working together on it
13:01:07 <bexelbie> sounds good
13:01:12 <bexelbie> #topic (WAS) Release Announcement
13:01:31 <bexelbie> #info work with marketing and mattdm to include some marketing strategy and mindshare comments in the release announcement
13:01:38 <bexelbie> #topic LATAM Swag
13:01:39 <bexelbie> ?
13:01:47 <bexelbie> everyone good with the topic and summary and change?
13:02:06 <nb> yes
13:02:45 <bexelbie> jsmith, ?
13:04:17 <jwf> bexelbie: +1 to topic notes and change
13:04:30 <bexelbie> jsmith, you're up
13:06:38 * bexelbie thinks we lost jsmith
13:07:27 <jsmith> Sorry, I'm back
13:07:38 <jsmith> Just some quick feedback from last week's LATAM meeting
13:08:04 <jsmith> itamarjp is still really upset about two things... one is a swag ticket that seemed to languish due to poor communication, and the other is about reimbursements
13:08:52 <jsmith> I don't know anything about the reimbursement side of things, but I looked at the swag ticket, and it seems it was just poor communication -- lack of clarity on whether or not the request had been approved, lack of specificity on the items ordered, lack of clarity on where to ship the items, etc.
13:09:43 <jsmith> I think having a more formalized process (especially for who approves swag requests, how to identify that they've been approved, etc.) would help
13:10:07 <jsmith> Of course, I've been out of the swag world for many many years now, so maybe it's documented and I just don't know about it
13:10:25 <jsmith> But it seems to my untrained eye like a place we can help improve things
13:10:36 <jsmith> Thoughts?
13:10:57 <bexelbie> I agree, and I think we have touched on the idea of event approvals as a vehicle for getting swag
13:11:01 <bexelbie> not just "send me swag" tickets
13:11:09 <bexelbie> that is what I understood
13:11:20 * bexelbie is not aware of any pending reimbursements in LATAM
13:12:07 <Southern_Gentlem> jsmith, really hasnt changed since you were fpl
13:13:30 <bexelbie> it varies quite a bit across regions I've learned - a single process without great reasons for an exception will help a lot, imho
13:13:43 <jsmith> Southern_Gentlem: Good to know :-)
13:13:57 <jsmith> Southern_Gentlem: That means there's still lots of room for improvement, at least in LATAM then :-)
13:14:08 <jsmith> bexelbie: +`
13:14:11 <jsmith> I mean, +1
13:15:13 <jwf> jsmith: I see this as being resolved within the written policy that nb and robyduck are working together on, as far as swag requests work.
13:15:19 <jwf> What do you think?
13:15:48 <jsmith> jwb: I think that will certainly help -- especially if we float that as "Hey, this is our thoughts -- please give us feedback before we treat this as law"
13:16:53 <bexelbie> +1
13:17:17 * jwf nods
13:19:09 <jsmith> Anyhoo -- that's everything from me with regards to LATAM
13:19:55 <bexelbie> other comments?
13:20:09 <jwf> None from me
13:20:13 <jwf> Thanks jsmith for following up there.
13:23:21 <jsmith> Anything else?
13:23:24 <jsmith> Should we end the meeting?
13:23:32 <bexelbie> works for me :)
13:23:39 <bexelbie> #topic open floor
13:23:47 <bexelbie> ending meeting in 30 barring objections
13:23:50 <jwf> I have nothing else to bring up or share.
13:24:03 <jwf> Thanks bexelbie for chairing!
13:24:05 <jwf> .thank bexelbie
13:24:05 <zodbot> jwf thinks bexelbie is awesome and is happy they are helping! (Please don't forget to bexelbie++ also)
13:24:26 <jsmith> bexelbie++
13:24:29 <bexelbie> thank you all
13:24:39 <bexelbie> #endmeeting