Resending with proper mindshare list address.
On Mon, Oct 29, 2018 at 6:29 PM Brian (bex) Exelbierd
<bexelbie(a)redhat.com> wrote:
On Fri, Oct 26, 2018 at 4:08 AM Andrew Ward <award3535(a)tds.net> wrote:
>
> All,
>
> Please read our meeting minutes from the FAmNA meeting held on 25 Oct 2018
> FAmNA will hold our next meeting on 15 Nov 2018 at 9pm east.
>
> Minutes:
>
https://meetbot.fedoraproject.org/fedora-meeting/2018-10-26/famna.2018-10...
> Minutes (text):
>
https://meetbot.fedoraproject.org/fedora-meeting/2018-10-26/famna.2018-10...
> Log:
>
https://meetbot.fedoraproject.org/fedora-meeting/2018-10-26/famna.2018-10...
I am sorry I missed this meeting last night, but I wanted to start a
conversation around a few things. This is an edited transcript to
highlight the areas I wanted to comment on :)
01:06:35 <award3535> I would like to start by saying that the
mindshare ticket system seems to be working with getting things pushed
through for events!
WOO!
01:09:07 <juggler[m]> award3535 that does sound positive! I may
require your assistance later on negotating all of the new ticketing
for filing for our event if/when that does come to pass...
01:09:11 <award3535> the only things that you should know when
completing tickets now, there is no requirement for an event page, all
pertinent information must be entered in the mindshare ticket
01:10:28 <juggler[m]> LOL, I wish I knew that. carefully crafted a
SCALE17x template page last night. sigh
01:11:19 <award3535> juggler(m) the same information (shortened) to fit.
01:11:19 <juggler[m]> question: in lieu of event pages, how do fedora
people find out about new events?
01:12:03 <award3535> juggler use email to get attendees, and place all
that will be attending in the mindshare ticket
01:12:17 <juggler[m]> I mean, how does the Fedora community find out
about events that we were normally linking?
01:12:59 <award3535> juggler, the community will know with entering
the mindshare ticket
I think this is an excellent question, how do people find out about
our events. I think we should figure out how creating event pages
caused this notification and if we have broken it. I believe that we
should email ambassadors@ (or the appropriate list for the people we
need, like devel@) to recruit help and let the ticket serve as a
notification point if we just want to spread information to ourselves.
The larger question here is how do we capitalize on the hard work
going into these events and let the world know. I think the work
being done in Marketing will help:
https://pagure.io/fedora-marketing/issue/263 Can we join/improve this
effort?
01:12:32 <award3535> of course if there is a reimbursement, event
report required
01:10:09 <award3535> juggler(m) the only requirements is event reports
and the reimbursement tickets for NA that I will pay upon completion
of the event report.
01:20:00 <award3535> for the reimbursements, the pagure ticket for NA
is still required so that I can preform the reimbursement. That ticket
must include the mindshare ticket number so that I can reference the
event report tracking by mindshare.
I wonder if we could move these requests to the fedora-budget
repository? award3535 already has access there and it is where we are
sending a bunch of other reimbursement requests. This would allow us
to expand the potential payers for all tickets. Andrew, does this
interest you? If so, let's work on a set of "how do we know when to
pay" docs.
01:20:02 <juggler[m]> curious, how was the swag distribution in
comparison....slower, faster or about the same?
01:20:53 <award3535> juggler that too is undergoing some changes, its
going to be more centralized and shipped from one location to the
event or event attendees residence
01:21:15 <juggler[m]> ah
01:21:37 <award3535> bex and the mindshare committed are working on
what is available and time lines for distro
This could definitely use some help. I've got a few ideas on how to
improve it and would love some refinement/input and help here.
I also want to know how we can capitalize on the value of hte event
box used in NA for other regions. We have the ability to centrally
store those if we want or to keep them distributed. Let's figure out
if we need a change here (we may not) or if there is value. Then we
can translate this from NA to the world.
01:23:54 <award3535> so when we have meetings for NA now, tickets will
be listed as the reimbursement pagure tickets and with any help
needed.
01:25:17 <award3535> #topic == Open Floor ===
01:26:22 <juggler[m]> I've setup a new framework for SCaLE17x. The new
link has been established here:
01:26:58 <juggler[m]> #link
https://fedoraproject.org/wiki/Events#FY20_Q1_.28March_2019_-_May_2019.29
01:27:02 <juggler[m]> and here:
01:27:13 <juggler[m]> #link
https://fedoraproject.org/wiki/SCaLE_17X_Event
01:27:40 <juggler[m]> should I delete the framework link as a result
of the mindshare integrations at this point in time?
01:28:07 <juggler[m]> I added an FY20 Q1 section, but it might be
obsolete as of this writing...thoughts?
01:29:00 <juggler[m]> other news, Paradox has volunteered to be event
owner for SCaLE17x.
I think this will definitely help with the Mindshare ticket. For
larger events like this maybe a wiki page referenced from teh ticket
is better? Let's figure this out.
Regarding SCaLE specifically, should we try to do an education track
there? I've heard buzz about that ...
01:29:17 <award3535> Well, if it helps you plan it no, but one thing
that will come up is Acosta, there have been lots of questions on
attendees that require travel expenses, they more than likely be
required to give a talk at the event
01:30:05 <award3535> and that talk must be fedora based along with
something we do
01:30:07 <juggler[m]> ah
01:31:32 <award3535> there was a lot of discussions on attending with
travel costs other than just working the booth. This was up at the
council as well as the mindshare committee
01:31:35 <juggler[m]> is it not enough that he provides full coverage
throughout most of the conference to field questions from the
community at our vendor table? or would he need to do some formal
talk?
01:32:23 <juggler[m]> he is quite an invaluable resource, especially
with our Spanish speaking community
01:33:51 <award3535> even though he does support everything at the
booth, the cost of travel and lodging would raise questions, and I can
tell you that it probably wont get approved without being a speaker at
the event, even for language barrier that is not 100%
01:35:00 <award3535> the focus is to have local ambassadors that will
work the booth, traveling ambassadors giving talks get funding for
travel and lodging
01:35:42 <juggler[m]> I guess another question would also be if he is
unable to make it based on that restriction who might be sharing the
hotel room with me..
01:37:05 <award3535> that is the question, there are many question
that yet have to be answered in the mindshare documentation that is
not out yet, but you must include a strong pitch to get that kind of
funding now
01:38:04 <juggler[m]> hopefully he'll also read this log later..
01:38:21 <award3535> for example, SELF, it will require kk4ewt, and
Myself to give talks since we are representing all ambassadors in the
south east
01:39:05 <award3535> and require both travel and lodging
01:39:47 <juggler[m]> so if travel and lodging then must be a formal speaker?
01:39:56 <kk4ewt> yep
01:40:28 <award3535> that is what we get out of all the reading of
minutes and from the prior events that we just completed.
01:40:36 <juggler[m]> but the ambassador can't just be a facilitator,
like say for a roundtable discussion?
01:41:38 <award3535> that may work, but you will have to make it
strong, but you can also call for a FAD for ambassadors in your area,
that too may work
01:42:29 <juggler[m]> I think ultimately we'd like to. The bigger
question is if that could be funded, as that might require $$ to get a
room for more than 45 minutes.
01:42:59 <award3535> yes that could pose a problem
I think the gist of this is mostly how I understand it too. It sounds
like having acosta at the event is useful, so let's document that. I
don't think anyone on Mindshare is opposed to travel for the right
reasons. I also think the reason for the local emphasis is that
"parachuting" in for an event can kill the opportunity to do followup.
A local rep can do followup more easily, including additional events.
This doesn't mean there is only one model.
01:43:38 <juggler[m]> I'll ask Paradox to review this log later to ask
for his feedback on how to proceed...
01:44:09 <juggler[m]> how quickly is the turnaround time for
approvals, based on prior events. days, weeks, months?
01:44:44 <award3535> like I said they are looking for local
ambassadors whether they are as active as us or not to attend events,
for example seattle, where stealaworkn is
01:45:09 <juggler[m]> ah
01:45:23 <award3535> the turn around depends on how many votes you
need to get it approved. that depends on the amount of money you are
asking for
01:45:54 <award3535> for example SELF will require 5 mindshare
committee members to approve
01:46:20 <award3535> because it will exceed 1K
01:46:58 <juggler[m]> if we keep it under 1K, is that easier to
approve then? or not necessarily
01:47:55 <award3535> thats why I put a ticket in asking for status of
the documentation from Mindshare, it is still an unknown/unapproved
process right now
01:48:22 <juggler[m]> ah
01:49:17 <award3535> I would say that if it is over $500.00 that it
will required at least five positive votes, and that is why it is some
important to make your pitch strong
01:50:15 <juggler[m]> got it
01:51:46 <award3535> my feelings are that it's going to be hard to
convince some of the mindshare committee for anything over 1K, since
most in other countries cost almost nothing compared to ours
We are trying to get our approvals scaled with $$ to speed things up.
Additionally, I think all of the committee members are fluent in world
economics. I will say that we are working on making it more
predictable so you know what kind of time is needed for votes to be
collected. We are actively trying to push for ticket based workflows
over meetings.
regards,
bex
--
Brian (bex) Exelbierd | bexelbie(a)redhat.com | bex(a)pobox.com
Fedora Community Action & Impact Coordinator
@bexelbie |