ACTION: commops New
members, make sure you introduce yourself on the CommOps mailing
list [ https://fedoraproject.org/wiki/CommOps/Join ](jflory7,
17:30:09)
Haïkel Guémar (hguemar / number80) is a
long-time Fedora contributor passionate about on-boarding new users
into Fedora. Learn more in his interview with Chris Ward as the last
episode of the Flock Stories 2016 series!(jflory7,
17:36:39)
=== "Fedora at PyCon CZ 2016" ===(jflory7,
17:36:45)
Fedora Ambassadors in the Czech Republic and
around Europe attended PyCon CZ in Brno, Czech Republic. Learn more
about what happened at PyCon (including the Pythonic staff of
enlightenment) in ishcherb's event report!(jflory7,
17:36:56)
We're working on doing a partnership with
freenode to publicize the open source projects living on freenode. A
first draft of an initial article to publish was shared on the
mailing list. Please take a moment to review and offer any
feedback.(jflory7,
17:37:38)
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.(jflory7,
17:39:30)
=== jflory7 Open up discussion about Fedora
Appreciation Day date on the mailing list ===(jflory7,
17:39:39)
- Better done as a ticketed discussion - we can
talk in a meeting, update the ticket, and go from there. We have
extra time to plan this now until we determine a date to shoot
for.(jflory7,
17:40:19)
=== jflory7 Take the discussion points from
Marketing pow-wow meeting, lay out the earlier problems, expand on
solutions, and try to offer mock implementations in the Marketing
ticket ===(jflory7,
17:40:44)
ACTION: jflory7 Take
the discussion points from Marketing pow-wow meeting, lay out the
earlier problems, expand on solutions, and try to offer mock
implementations in the Marketing ticket(jflory7,
17:40:52)
jflory7 will do this today, guaranteed, no
exceptions, no ifs, ands, or buts(jflory7,
17:41:12)
=== jflory7 Post to the mailing list breaking
down how to help with Ticket #93 ===(jflory7,
17:41:27)
- This ticket is added to the meeting agenda
for today, and we should discuss together how to break it down and
move forward with this into smaller tasks for CommOpsers to take
on(jflory7,
17:41:53)
=== [COMPLETE] Rhea Update the #95 ticket after
the first dotnet meeting ===(jflory7,
17:42:47)
=== FranciscoD work on "Review existing roles
and responsibilities of committees, find any other places where
their roles may be explained (wiki pages, personal blog posts,
etc.)." ===(jflory7,
17:43:06)
ACTION: FranciscoD
Review existing roles and responsibilities of committees, find any
other places where their roles may be explained (wiki pages,
personal blog posts, etc.) ===(jflory7,
17:44:09)
IDEA: Current objective
for Fedora Appreciation Day: Establish a timeline for planning by
choosing a month or date to aim for, break up smaller tasks for how
we can prepare for it (messaging, communication, options for
contributors to thank each other)(jflory7,
17:51:49)
AGREED: Next steps
will be to update ticket with proposed timeline for events, pending
bexelbie's thoughts. After, we will try setting a date in the
calendar. Then, we will (1) create a public wiki page to hold info,
and (2) write a CommBlog post announcing it to come in the
summer(jflory7,
18:00:46)
ACTION: jflory7
Update Ticket #92 with the proposed timeline and agreed points after
the meeting(jflory7,
18:02:24)
IDEA: Better explaining
roles and responsibilities of Council and FESCo so people know what
they are expected to do if they choose to run(jflory7,
18:09:08)
IDEA: Go over benefits
for running, e.g. the sorts of skills you would use and also improve
on(jflory7,
18:09:26)
IDEA: Having a
mentorship period or "training" for first-time candidates elected
into the Council or FESCo(jflory7,
18:12:01)
ACTION: meskarune
File a ticket in the Fedora Council Pagure suggesting the idea of
having a mentorship or training period for first-time candidates who
are elected into the Council to help them get started and familiar
with the position(jflory7,
18:16:42)
ACTION: dhanesh95
Reach out to the Fedora Council, either on the mailing list or IRC,
to work with them on updating the wiki page to better explain the
roles, responsibilities, benefits, and skills needed to be a Council
member no later than end of day, Friday, Dec. 2, 2016(jflory7,
18:18:44)
ACTION: jflory7 Reach
out to FESCo, either on the mailing list or IRC, to work with them
on updating the wiki page to better explain the roles,
responsibilities, benefits, and skills needed to be a FESCo member,
no later than end of day, Friday, Dec. 2, 2016(jflory7,
18:19:05)
AGREED: Action items
delegated, will check in on progress next meeting!(jflory7,
18:20:12)
ACTION: jflory7
Really do update Ticket #48 today with the key points discussed in
Oct. 18 meeting, share with Marketing mailing list to have more to
discuss next week(jflory7,
18:22:31)
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!(jflory7,
18:25:57)
=== The past couple of weeks in CommBlog
===(jflory7,
18:26:15)
(1) "Where to point newcomers to Fedora" -
FranciscoD++(jflory7,
18:26:23)
commops New members, make sure you introduce yourself on the CommOps mailing list [ https://fedoraproject.org/wiki/CommOps/Join ]
jflory7 Take the discussion points from Marketing pow-wow meeting, lay out the earlier problems, expand on solutions, and try to offer mock implementations in the Marketing ticket
FranciscoD Review existing roles and responsibilities of committees, find any other places where their roles may be explained (wiki pages, personal blog posts, etc.) ===
jflory7 Update Ticket #92 with the proposed timeline and agreed points after the meeting
meskarune File a ticket in the Fedora Council Pagure suggesting the idea of having a mentorship or training period for first-time candidates who are elected into the Council to help them get started and familiar with the position
dhanesh95 Reach out to the Fedora Council, either on the mailing list or IRC, to work with them on updating the wiki page to better explain the roles, responsibilities, benefits, and skills needed to be a Council member no later than end of day, Friday, Dec. 2, 2016
jflory7 Reach out to FESCo, either on the mailing list or IRC, to work with them on updating the wiki page to better explain the roles, responsibilities, benefits, and skills needed to be a FESCo member, no later than end of day, Friday, Dec. 2, 2016
jflory7 Really do update Ticket #48 today with the key points discussed in Oct. 18 meeting, share with Marketing mailing list to have more to discuss next week
jflory7 Update featured image in PyCon CZ article to use an actual picture of Brno, as provided by mhroncok
Action items, by person
commops
commops New members, make sure you introduce yourself on the CommOps mailing list [ https://fedoraproject.org/wiki/CommOps/Join ]
dhanesh95
dhanesh95 Reach out to the Fedora Council, either on the mailing list or IRC, to work with them on updating the wiki page to better explain the roles, responsibilities, benefits, and skills needed to be a Council member no later than end of day, Friday, Dec. 2, 2016
jflory
jflory7 Take the discussion points from Marketing pow-wow meeting, lay out the earlier problems, expand on solutions, and try to offer mock implementations in the Marketing ticket
jflory7 Update Ticket #92 with the proposed timeline and agreed points after the meeting
jflory7 Reach out to FESCo, either on the mailing list or IRC, to work with them on updating the wiki page to better explain the roles, responsibilities, benefits, and skills needed to be a FESCo member, no later than end of day, Friday, Dec. 2, 2016
jflory7 Really do update Ticket #48 today with the key points discussed in Oct. 18 meeting, share with Marketing mailing list to have more to discuss next week
jflory7 Update featured image in PyCon CZ article to use an actual picture of Brno, as provided by mhroncok
jflory7
jflory7 Take the discussion points from Marketing pow-wow meeting, lay out the earlier problems, expand on solutions, and try to offer mock implementations in the Marketing ticket
jflory7 Update Ticket #92 with the proposed timeline and agreed points after the meeting
jflory7 Reach out to FESCo, either on the mailing list or IRC, to work with them on updating the wiki page to better explain the roles, responsibilities, benefits, and skills needed to be a FESCo member, no later than end of day, Friday, Dec. 2, 2016
jflory7 Really do update Ticket #48 today with the key points discussed in Oct. 18 meeting, share with Marketing mailing list to have more to discuss next week
jflory7 Update featured image in PyCon CZ article to use an actual picture of Brno, as provided by mhroncok
meskarune
meskarune File a ticket in the Fedora Council Pagure suggesting the idea of having a mentorship or training period for first-time candidates who are elected into the Council to help them get started and familiar with the position