Flock is Fedora's annual contributor conference
where Fedorans across the world get together for talks, sprints,
workshops, and more. The schedule for this year's Flock was recently
published and you can find out what talks and workshops there will
be for this year. Some CommOpsers are giving talks this year!(jflory7,
16:07:14)
=== Google Summer of Code "All-Hands",
2016-05-25, 15:00 UTC ===(jflory7,
16:07:28)
The Google Summer of Coding All-Hands meeting
will be on Wednesday at 15:00 UTC in #fedora-meeting. This will be
the big kick-off, officially, for the summer!(jflory7,
16:07:33)
ACTION: cprofitt File
a ticket for wiki gardening the Python SIG page (others who have
noticed things can also chime in, cc: LinuxHippie /
dhanesh95)(jflory7,
16:19:39)
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.(decause,
16:27:48)
=== [COMPLETE] commops add the 'how it works'
link above to the etherpad under resources ===(decause,
16:27:55)
=== [COMPLETE] decause send out timeslot
requests for GSoC ===(decause,
16:28:03)
=== decause add money dollars to limesurvey
due:Friday ===(decause,
16:28:08)
ACTION: decause
follow-up with tatica and diversity team about limesurvey
avaiability(decause,
16:29:06)
AGREED: Complete!
decause purchased 5000 responses, so there is moneydollars in the
LimeSurvey account. Next steps is getting it to tatica and Diversity
team.(jflory7,
16:29:47)
=== decause talk to spot about scheduling an
EDU FAD after budget gets settled ===(decause,
16:30:21)
ACTION: commops
socialize the wiki page, start drafting a commblog article to go out
before end of June(decause,
16:30:58)
=== [INCOMPLETE] jflory7 Post to the mailing
list with ideas about the FOSS Student Pack, along with links to a
planning pad either on the wiki or in an Etherpad ===(decause,
16:31:16)
ACTION: jflory7 Post
to the mailing list with ideas about the FOSS Student Pack, along
with links to a planning pad either on the wiki or in an
Etherpad(decause,
16:31:24)
=== [INCOMPLETE] jflory7 Open discussion on the
mailing list about Ticket #71 and centralizing Ambassador resources
(to get brainstorming going) ===(decause,
16:31:34)
ACTION: jflory7 Open
discussion on the mailing list about Ticket #71 and centralizing
Ambassador resources (to get brainstorming going)(decause,
16:31:40)
=== [INCOMPLETE] jflory7 Write Bitcamp 2016
article on CommBlog and point to individual event reports by other
Ambassadors ===(decause,
16:31:48)
ACTION: jflory7 Write
Bitcamp 2016 article on CommBlog and point to individual event
reports by other Ambassadors(decause,
16:31:55)
=== [INCOMPLETE] jflory7 Bring the CommOps vFAD
ticket back up to the table, make a wiki page, do the metadata
planning-esque type of tasks ===(decause,
16:32:05)
ACTION: jflory7 Bring
the CommOps vFAD ticket back up to the table, make a wiki page, do
the metadata planning-esque type of tasks(decause,
16:32:11)
=== [COMPLETE] jflory7 Ship F24 Party article
today ===(decause,
16:32:22)
ACTION: decause work
with jzb to possibly organize a release party in RDU(decause,
16:33:01)
=== [IN PROGRESS] jflory7 Remove Ticket #74
from meeting agenda, add info about where to find the pull request
for the ticket ===(decause,
16:33:32)
ACTION: jflory7 Add
info about where to find the pull request for Ticket #74(decause,
16:33:37)
=== decause / commops stop by the docs office
hours tomo to discuss release notes -> release announce flow
===(decause,
16:33:50)
ACTION: decause /
commops stop by the docs office hours tomo to discuss release notes
-> release announce flow(decause,
16:34:04)
ACTION: decause /
commops go to docs office hours at 3pm EST (7pm UTC) to talk release
notes -> GA Announcement(decause,
16:36:13)
=== decause add conf schedule to Fedocal
===(decause,
16:37:17)
ACTION: decause nail
down Flock arrangements, add them to Fedocal(decause,
16:37:58)
=== [COMPLETE] dhanesh95 Fork a wiki page for
the Education FAD from the template linked previously and begin
templating the details for the Education FAD to take place over this
summer ===(decause,
16:38:03)
AGREED: EDU FAD can
be updated in a hack session to include information about what it
is, can be followed by a CommBlog article and mailing list
posts(jflory7,
16:50:03)
(1) Someone can review the contents of their
on-boarding wiki page and pass feedback about them in the ticket, as
compared to other on-boarding methods in Fedora(decause,
16:51:02)
(2) Putting together a badge proposal for
membership in the Modularity WG (in the form of a ticket on the
fedora-badges Trac)(decause,
16:51:08)
(3) A Community Blog article announcing the
presence of the Modularity WG, what they are, what they do, how to
get involved (penned by one of the WG members)(decause,
16:51:13)
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!(decause,
16:56:17)