ACTION: commops New
members, make sure you introduce yourself on the CommOps mailing
list [ https://fedoraproject.org/wiki/CommOps/Join ](jwf,
17:31:59)
Dhanesh B. Sabane, UTC+5:30, CommOps,
Marketing, Join, ML, Packaging, Python and more to come. :P(dhanesh95,
17:32:26)
A quick overview of the past year's events in
North America by the Ambassadors. A good overview of the activities
and what all is going on in the North American continent with
Fedora!(jwf,
17:36:56)
A new version of Pagure was released and pushed
to the staging instance. It will likely make it ways over to
production in the next few days.(jwf,
17:37:14)
Ongoing discussion in the Marketing Team to
choose and narrow down target audiences for talking points. Knowing
target audiences of Fedora 26 is also of interest to us too – feel
free to follow along in the ticket!(jwf,
17:37:34)
How This Works: We look at past #action items
from the last meeting for quick follow-up. If a task is completed,
we move on to the next one. If it isn't, we get an update and
re-action it if needed. If no status, we'll try to get a quick
update and move forward.(jwf,
17:39:26)
=== [COMPLETE] bt0 Add bulletpoint list with a
quick summary of each major area to the top of fp.o/wiki/Join page,
close ticket #62 when completed ===(jwf,
17:39:34)
=== [INCOMPLETE] jwf Start thread on CommOps
mailing list (CC: bexelbie) on the best way to store and host a
"directory" or database of Fedora contributors actively involved
with EDU efforts ===(jwf,
17:39:48)
ACTION: jwf Start
thread on CommOps mailing list (CC: bexelbie) on the best way to
store and host a "directory" or database of Fedora contributors
actively involved with EDU efforts(jwf,
17:40:13)
=== [INCOMPLETE] jwf Follow up with schyken to
confirm that the article is ready to be published / apply necessary
edits as needed ===(jwf,
17:40:19)
ACTION: jwf Follow up
with schyken to confirm that the article is ready to be published /
apply necessary edits as needed(jwf,
17:40:26)
=== [COMPLETE] jwf Add pictures sent from
award3535 to post, create featured image, schedule ASAP ===(jwf,
17:40:31)
This is an older ticket that we wanted to try
to revisit this release cycle. To best approach this, it's worth
discussing what type of content event reports should tell. What
narrative are we looking for? What should Ambassadors focus on in
their event reports? Does it differ from region to region? Let's
focus on determining the goals and aims of what an Ambassador event
report should have.(jwf,
17:41:12)
IDEA: Reaching out to
Ambassadors / posting guidelines for event reports that encourage
something like, "We'd like to help you, if you get us X,Y,Z, we can
pre-event publicity; if you get us A,B,C, we can help with
post-event reporting; here's some ideas for a post"(jwf,
17:49:53)
IDEA: Offering
suggestions of what types of photos are better for what kinds of
content(jwf,
17:51:54)
ACTION: x3mboy Follow
up with LATAM Ambassadors about if a CommBlog article suffices for
reimbursement, update ticket #21 with feedback(jwf,
17:58:14)
AGREED: Pre-event
reporting goals: Critical event information (time, day, location),
info about Fedora's location and participation in event, how to
engage with Fedora at event(jwf,
18:04:02)
AGREED: Post-event
reporting goals: Info about how *and* why Fedora participated,
forming a conclusion about why Fedora's presence mattered at the
event, showing our role in the event with visual aids(jwf,
18:16:21)
ACTION: jwf Update
ticket #21 with proposed guidelines based on agreed objectives/goals
for pre- and post-event reports(jwf,
18:16:55)
We also wanted to follow up on this ticket this
release cycle. This one focuses on building an active list or
directory of active Fedora contributors who are involved with
universities or schools already. Ideally, this people would be
"first adopters" of any efforts we aim for with education-related
outreach, like in the Marketing team. But where is the best place to
keep and maintain this data?(jwf,
18:17:19)
AGREED: To make sure
this ticket fits into the overall Objective and working towards
accomplishing its goals, this ticket will be closed and there will
be additional conversation somewhere, soon, about moving forward
with the Objective as a whole(jwf,
19:05:18)
ACTION: jwf Make a
thread/wiki page/ticket with regards to University Involvement
Initiative discussion(jwf,
19:05:30)
Another older ticket to circle back to for this
release cycle and possibly the next. This could have two different
audiences. Do we want a student pack for new contributors to Fedora
with resources for getting them started? Do we want to feature cool
Fedora apps or general infrastructure a student could use for any
open source project? What are the goals of a student pack and what
do we want to get out of it? What should the student get out
of(jwf,
19:05:51)
SKIPPED - ran out of time in meeting, will
revisit next week(jwf,
19:06:00)
How This Works: There is a quick blast of
information about what was published in the past week with some
metrics, followed by posts that are being drafted. After the
information blast, the floor is opened for any Community
Blog-related discussion. Here we go!(jwf,
19:06:12)
commops New members, make sure you introduce yourself on the CommOps mailing list [ https://fedoraproject.org/wiki/CommOps/Join ]
jwf Start thread on CommOps mailing list (CC: bexelbie) on the best way to store and host a "directory" or database of Fedora contributors actively involved with EDU efforts
jwf Follow up with schyken to confirm that the article is ready to be published / apply necessary edits as needed
x3mboy Follow up with LATAM Ambassadors about if a CommBlog article suffices for reimbursement, update ticket #21 with feedback
jwf Update ticket #21 with proposed guidelines based on agreed objectives/goals for pre- and post-event reports
jwf Make a thread/wiki page/ticket with regards to University Involvement Initiative discussion
Action items, by person
bexelbie
jwf Start thread on CommOps mailing list (CC: bexelbie) on the best way to store and host a "directory" or database of Fedora contributors actively involved with EDU efforts
commops
commops New members, make sure you introduce yourself on the CommOps mailing list [ https://fedoraproject.org/wiki/CommOps/Join ]
jwf
jwf Start thread on CommOps mailing list (CC: bexelbie) on the best way to store and host a "directory" or database of Fedora contributors actively involved with EDU efforts
jwf Follow up with schyken to confirm that the article is ready to be published / apply necessary edits as needed
jwf Update ticket #21 with proposed guidelines based on agreed objectives/goals for pre- and post-event reports
jwf Make a thread/wiki page/ticket with regards to University Involvement Initiative discussion
x3mboy
x3mboy Follow up with LATAM Ambassadors about if a CommBlog article suffices for reimbursement, update ticket #21 with feedback