PyCon US 2016 is this week, and many members of
the Fedora contributor community can be found there this week. There
will be Fedora sprints coming up later on in the week, so stay tuned
for any news from the team there. If you're at PyCon, stop by the
Fedora table and say hello!(jflory7,
16:07:25)
=== Developing the story of Fedora 24
===(jflory7,
16:07:43)
There is ongoing discussion about how to
develop the "story" of Fedora 24 for this past release cycle. This
discussion is going to be used in the release announcement for F24.
If you have ideas about how to develop this story, chime in on the
mailing list thread and add your thoughts! F24 is growing closer
fast!(jflory7,
16:07:58)
skamath has started work on the statstool,
which can be found on Pagure(skamath,
16:09:26)
jflory7 GSoC update: Working through Ansible
resources and writing experimental playbooks on personal server.
Hoping to start working with WordPress multi-site setups this week
and also studying Ansible playbooks already in Fedora Infra. Hoping
to learn more about differences between 1.0 and 2.0 API soon.(jflory7,
16:09:52)
devyani7 GSoC update: Working on *EDIT*
bookmarks feature that will list down the hub-pages bookmarked by
the user, following with the frequently opened ones. Hoping to get
this done this week, following which we'll try to provide
suggestions to user to change the order of the bookmarks.(devyani7,
16:14:55)
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,
16:15:44)
=== [COMPLETE] 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:15:59)
=== [IN PROGRESS] decause follow-up with tatica
and diversity team about limesurvey avaiability ===(jflory7,
16:16:09)
ACTION: decause
Follow up with tatica and diversity team about LimeSurvey
availability(jflory7,
16:16:14)
tatica has been offline due to illness, so
might be a slight delay in getting this one done(jflory7,
16:16:19)
=== [IN PROGRESS] 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 ===(jflory7,
16:16:28)
Email draft is started, will be sent out by end
of day(jflory7,
16:16:33)
=== [INCOMPLETE] jflory7 Open discussion on the
mailing list about Ticket #71 and centralizing Ambassador resources
(to get brainstorming going) ===(jflory7,
16:16:40)
ACTION: jflory7 Open
discussion on the mailing list about Ticket #71 and centralizing
Ambassador resources (to get brainstorming going)(jflory7,
16:16:46)
=== [CLOSED] jflory7 Write Bitcamp 2016 article
on CommBlog and point to individual event reports by other
Ambassadors ===(jflory7,
16:17:30)
Article has gone past its prime publishing
period (event was in early April); there are individual Ambassador
reports for the event, so this should suffice for the time
being.(jflory7,
16:17:36)
=== [INCOMPLETE] jflory7 Bring the CommOps vFAD
ticket back up to the table, make a wiki page, do the metadata
planning-esque type of tasks ===(jflory7,
16:17:43)
ACTION: jflory7 Bring
the CommOps vFAD ticket back up to the table, make a wiki page, do
the metadata planning-esque type of tasks(jflory7,
16:17:48)
=== [IN PROGRESS] decause work with jzb to
possibly organize a release party in RDU(jflory7,
16:17:54)
ACTION: decause Work
with jzb to organize the release party in Raleigh, NC area(jflory7,
16:18:00)
=== [COMPLETE] jflory7 Add info about where to
find the pull request for Ticket #74(jflory7,
16:18:07)
ACTION: skamath File
a ticket in the Fedora Badges Trac for a CommOps on-boarding badge
that is dependent on other badges and/or hooks to be awarded; ask in
#fedora-commops if assistance is needed. :)(jflory7,
16:30:25)
AGREED: Will remove
this ticket from agenda for now until we have more information from
spot and decause about further plans for the FAD(jflory7,
16:33:08)
IDEA: Having a Pagure
repo to serve as an index for all existing resources (questions to
ask: how to maintain it, who will add to it?)(jflory7,
16:42:23)
IDEA: Centralizing all
the resources together in a single place and making them easily
accessible, e.g. a package (questions to ask: what are teams doing
now, will they have to change their practices? Is this something
they will want to do?)(jflory7,
16:43:00)
ACTION: jflory7 Reach
out to the Design Team about centralizing Design / Marketing
resources for Fedora and get their thoughts about the discussions
from today's meeting on Ticket #71(jflory7,
16:48:03)
ACTION: Update Ticket
#71 with the ideas and discussion from this meeting(jflory7,
16:48:42)
IDEA: Automating with
code would be a good idea, but the question is how. A scraper on the
Design Team Trac for certain file extensions? Parsing GitHub repos?
To be discussed with Design Team.(jflory7,
16:51:12)
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,
17:02:51)
AGREED: The extra 30
minutes to the meeting time was great for fitting more quality
discussion in and not rushing through ideas or discussion
topics.(jflory7,
17:09:22)
IDEA: Planning a new
hack session time: want to check in with decause about PyCon Fedora
sprints and maybe coordinating around that? Need to find out what
days and times those are.(jflory7,
17:12:13)
ACTION: jflory7 Reach
out to decause about days / times for Fedora sprints at PyCon for
planning a hack session(jflory7,
17:13:22)
decause Follow up with tatica and diversity team about LimeSurvey availability
jflory7 Open discussion on the mailing list about Ticket #71 and centralizing Ambassador resources (to get brainstorming going)
jflory7 Bring the CommOps vFAD ticket back up to the table, make a wiki page, do the metadata planning-esque type of tasks
decause Work with jzb to organize the release party in Raleigh, NC area
decause nail down Flock arrangements, add them to Fedocal
decause / dhanesh95 / spot look into booking conference rooms in the Tower (Fedora on 9 if it is available)
decause / jflory7 Get article source from maxamillion, decause will make edits, clear with maxamillion, then push
skamath File a ticket in the Fedora Badges Trac for a CommOps on-boarding badge that is dependent on other badges and/or hooks to be awarded; ask in #fedora-commops if assistance is needed. :)
jflory7 Reach out to the Design Team about centralizing Design / Marketing resources for Fedora and get their thoughts about the discussions from today's meeting on Ticket #71
Update Ticket #71 with the ideas and discussion from this meeting
commops New members, make sure you add your timezone / interests on CommOps wiki [ https://fedoraproject.org/wiki/CommOps ]
jflory7 Follow up with decause and maxamillion to see if where the original content is and if we can pull the source
jflory7 Reach out to decause about days / times for Fedora sprints at PyCon for planning a hack session
Action items, by person
commops
skamath File a ticket in the Fedora Badges Trac for a CommOps on-boarding badge that is dependent on other badges and/or hooks to be awarded; ask in #fedora-commops if assistance is needed. :)
commops New members, make sure you add your timezone / interests on CommOps wiki [ https://fedoraproject.org/wiki/CommOps ]
decause
decause Follow up with tatica and diversity team about LimeSurvey availability
decause Work with jzb to organize the release party in Raleigh, NC area
decause nail down Flock arrangements, add them to Fedocal
decause / dhanesh95 / spot look into booking conference rooms in the Tower (Fedora on 9 if it is available)
decause / jflory7 Get article source from maxamillion, decause will make edits, clear with maxamillion, then push
jflory7 Follow up with decause and maxamillion to see if where the original content is and if we can pull the source
jflory7 Reach out to decause about days / times for Fedora sprints at PyCon for planning a hack session
dhanesh95
decause / dhanesh95 / spot look into booking conference rooms in the Tower (Fedora on 9 if it is available)
jflory7
jflory7 Open discussion on the mailing list about Ticket #71 and centralizing Ambassador resources (to get brainstorming going)
jflory7 Bring the CommOps vFAD ticket back up to the table, make a wiki page, do the metadata planning-esque type of tasks
decause / jflory7 Get article source from maxamillion, decause will make edits, clear with maxamillion, then push
jflory7 Reach out to the Design Team about centralizing Design / Marketing resources for Fedora and get their thoughts about the discussions from today's meeting on Ticket #71
jflory7 Follow up with decause and maxamillion to see if where the original content is and if we can pull the source
jflory7 Reach out to decause about days / times for Fedora sprints at PyCon for planning a hack session
skamath
skamath File a ticket in the Fedora Badges Trac for a CommOps on-boarding badge that is dependent on other badges and/or hooks to be awarded; ask in #fedora-commops if assistance is needed. :)