We're in the middle of it today, team! Fedora
24 released hours ago. Today is a very busy day across Fedora. Check
out upgrading your own system if you haven't already yet! :)(jflory7,
16:04:41)
The Fedora Cloud Working Group finished their
Fedora Activity Day this past week. Learn all that was accomplished
and what objectives are on the table for the Cloud WG in this
article.(jflory7,
16:05:15)
=== skamath's super cool statistic generation
===(jflory7,
16:05:21)
skamath's tool evaluates different parts of
fedmsg activity to generate statistics about the contributions of
specific contributors and where they spend their time in Fedora. You
can see some of the data that he has collected so far in the above
links. You can find the project source on Pagure!(jflory7,
16:05:41)
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:11:30)
=== decause review the vFAD
goals/objectives/etc ===(jflory7,
16:11:43)
=== decause Work with jzb to organize the
release party in Raleigh, NC area ===(jflory7,
16:12:30)
jzb/decause decided to do a release party
*after* summit (by the time we got the "go" we had little time to
prepare, and lots of other prep for RHT Summit.)(decause,
16:13:18)
=== decause nail down Flock arrangements and
add to fedocal ===(jflory7,
16:13:41)
ACTION: decause nail
down Flock arrangements and add to fedocal(jflory7,
16:14:03)
=== [COMPLETE] decause Finish "final" version
of F24 GA Release Announcement for review after go/no-go meeting on
Thursday ===(jflory7,
16:14:14)
=== [COMPLETE] jflory7 Create a WhenIsGood and
share with CommOps mailing list to decide on vFAD dates of July 2-3
or June 25-26 ===(jflory7,
16:14:23)
=== [INCOMPLETE] jflory7 Open a ticket to look
into drafting an (automated?) check-in email with members of CommOps
to determine activity ===(jflory7,
16:14:56)
ACTION: jflory7 Open
a ticket to look into drafting an (automated?) check-in email with
members of CommOps to determine activity(jflory7,
16:15:03)
=== [COMPLETE] commops File a ticket on the
Pagure repository for Fedora Hubs about creating a News widget that
aggregates different sources of information and puts it together for
easy consumption by a reader ===(jflory7,
16:15:10)
AGREED: Based on
answers from the poll and in-meeting votes, July 3 - 4 seems like
the preferred date for organizing our vFAD to knock out some tasks
in our backlog and get ahead on current tickets. Will plan out final
details ASAP this week in a hack session.(jflory7,
16:23:09)
ACTION: jflory7 Don't
forget to bring up Vector / Matrix.org later on this meeting, during
open floor(jflory7,
16:30:27)
AGREED: Hack session
time tonight: 14:30 US EST == 18:30 UTC == 00:00 IST(jflory7,
16:33:35)
IDEA: Once badge is
published, "core" part of the ticket is completed.(jflory7,
16:38:57)
IDEA: After badge is
out, we can write a CommBlog post advertising the badge, explain how
it fits into the bigger picture of on-boarding for the project, and
how we want to help all other sub-projects have similar paths for
on-boarding(jflory7,
16:39:38)
IDEA: There is an RFE
already filed for Tahrir to point out "paths" for contributors to
earn new badges based on what they have already earned(jflory7,
16:40:32)
ACTION: jflory7 Write
up an initial draft of a wiki page outlining the process for
Ambassadors specifically to request assets from the Design Team,
include plans to reach out to regional Ambassadors from all regions
with this information later(jflory7,
16:53:24)
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,
16:56:36)
ACTION: jflory7 Get
on top of editing this week and schedule some of these articles for
this / next week, reply back to authors waiting for a
response(jflory7,
16:59:35)
jflory7 will be spending extra time on CommBlog
backlog this week to edit existing drafts and get them out and
published(jflory7,
17:02:00)
puiterwijk helped deploy the new CDN from our
sponsor for the Community Blog and Fedora Magazine today. As of now,
this helps lighten the traffic load on the WordPress machines and
helps keep the websites running strong with increased loads!(jflory7,
17:06:41)
Vector is a handy audio/video communication
platform that can be used for text, audio, and video conversations.
It's all FOSS (based off of Matrix) and has support for iOS and
Android devices too. Also works with file transfers if needed during
a call and supports end-to-end crypto.(jflory7,
17:16:34)
decause nail down Flock arrangements and add to fedocal
jflory7 Open a ticket to look into drafting an (automated?) check-in email with members of CommOps to determine activity
decause Drop a line to the devel list to have anyone going to Red Hat Summit add their info to the wiki page
jflory7 Don't forget to bring up Vector / Matrix.org later on this meeting, during open floor
jflory7 Write up an initial draft of a wiki page outlining the process for Ambassadors specifically to request assets from the Design Team, include plans to reach out to regional Ambassadors from all regions with this information later
commops New members, make sure you add your timezone / interests on CommOps wiki [ https://fedoraproject.org/wiki/CommOps ]
jflory7 Get on top of editing this week and schedule some of these articles for this / next week, reply back to authors waiting for a response
jflory7 Create a placeholder article for F22 EoL article in CommBlog so we keep on the agenda
jflory7 Prepare the hack session ticket and CC dhanesh95 so he gets context to what they are for a CommBlog article
Action items, by person
commops
commops New members, make sure you add your timezone / interests on CommOps wiki [ https://fedoraproject.org/wiki/CommOps ]
decause
decause review the vFAD goals / objectives / etc.
decause nail down Flock arrangements and add to fedocal
decause Drop a line to the devel list to have anyone going to Red Hat Summit add their info to the wiki page
dhanesh95
jflory7 Prepare the hack session ticket and CC dhanesh95 so he gets context to what they are for a CommBlog article
jflory7
jflory7 Open a ticket to look into drafting an (automated?) check-in email with members of CommOps to determine activity
jflory7 Don't forget to bring up Vector / Matrix.org later on this meeting, during open floor
jflory7 Write up an initial draft of a wiki page outlining the process for Ambassadors specifically to request assets from the Design Team, include plans to reach out to regional Ambassadors from all regions with this information later
jflory7 Get on top of editing this week and schedule some of these articles for this / next week, reply back to authors waiting for a response
jflory7 Create a placeholder article for F22 EoL article in CommBlog so we keep on the agenda
jflory7 Prepare the hack session ticket and CC dhanesh95 so he gets context to what they are for a CommBlog article