ACTION: commops New
members, make sure you introduce yourself on the CommOps mailing
list [ https://fedoraproject.org/wiki/CommOps/Join ](jwf,
16:31:32)
Eduard Lucena; UTC-3;CommOps, Marketing,
Magazine, Social Media(x3mboy,
16:31:37)
Justin W. Flory; UTC+2; CommOps, Marketing,
Magazine, Diversity, Ambassadors, and more…(jwf,
16:32:03)
Alberto Rodriguez S;UTC-5;Commops, Metrics,
Infra, DotNet(bt0,
16:32:24)
HELP: Native English
speakers are needed to help bring the Fedora user handbook to
English. Check out this CommBlog post to see how you can
help.(jwf,
16:40:58)
The Opensource.com blogging challenge continues
this week, asking for people like you to share your experience about
open source communities. This week's topic are difficult
conversations. Check it out on the Fedora Magazine.(jwf,
16:41:13)
=== "FLISoL 2017 – Linux in Latin America"
===(jwf,
16:41:32)
FLISoL is an international open source event
held across LATAM each year since 2005. Fedora was a part of it, and
you can get a quick overview in this introductory article by
x3mboy!(jwf,
16:41:43)
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,
16:44:22)
=== [COMPLETE] jwf File ticket upstream with
FAmSCo about Ambassador event reports ===(jwf,
16:44:28)
Survey was given out during FLISoL by x3mboy
and bt0 (some still in progress, so not yet finalized).(jwf,
16:57:18)
Most feedback about the most common software
used by students and how they see Linux and open source(jwf,
16:57:39)
Next steps are to create draft list about what
tools in Fedora would be helpful to include and also running a
survey to Fedora community about how to present the pack(jwf,
17:00:31)
Once this feedback is collected, a first draft
of what this looks like can be expected around end of June(jwf,
17:01:00)
ACTION: x3mboy Work
on collecting FLISoL feedback to use for putting together a first
draft of what to include in Student Pack(jwf,
17:09:38)
ACTION: x3mboy Begin
drafting a Community Blog article to poll community on ways they
think the student pack should be presented(jwf,
17:10:24)
AGREED: Meeting tag
will be removed from this ticket until there are more updates, but
x3mboy will add it back when feedback / thoughts are needed(jwf,
17:12:06)
ACTION: jwf Finish
rewriting Fedora Appreciation Week ticket based on feedback from old
ticket, comments in Diversity WG Pagure, and in-person
discussions(jwf,
17:13:31)
IDEA: Every active
ticket should have an owner or assignee, and during meetings, it is
the ticket assignee's responsibility to give updates or ask for
feedback, if it's needed. Otherwise, if the assignee doesn't have
anything to share, the ticket can be kept off of the meeting agenda
until feedback is needed. Tickets without assignees can be brought
up during meetings to find out how to move forward.(jwf,
17:17:59)
IDEA: if a ticket get
more than a X time (fixed and voted for the team), can be taken by
other to work on(x3mboy,
17:19:00)
#109 (Metrics based on Geographical location in
FAS) is still a work in progress. bt0 is working through this
ticket, needs review by bee2502 / skamath(jwf,
17:24:15)