With the recent release of Fedora 24, Fedora 22
will officially enter End Of Life (EOL) status on July 19th, 2016.
After July 19th, all packages in the Fedora 22 repositories will no
longer receive security, bugfix, or enhancement updates, and no new
packages will be added to the Fedora 22 collection.(jflory7,
16:05:44)
=== Fedora 24 release parties in progress
===(jflory7,
16:05:57)
There are Fedora 24 release parties happening
all over the world both this month and the end of last month. You
can see reports or event pages from Ambassadors at all of the above
links. See if there are any release parties happening in your
region! If you're interested in organizing one, check out this post
on the Community Blog.(jflory7,
16:06:42)
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:09:19)
=== [COMPLETE] jflory7 Move forward with making
final plans for vFAD or reconsider plans for Flock workshop (???)
===(jflory7,
16:09:25)
=== [COMPLETE] jflory7 Follow up in
#fedora-flock about Fedocal for Flock or if any previous action
items need follow-up ===(jflory7,
16:09:44)
=== [COMPLETE] jflory7 Open a ticket to look
into drafting an (automated?) check-in email with members of CommOps
to determine activity ===(jflory7,
16:10:38)
=== [COMPLETE] 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:10:56)
=== [IN PROGRESS] 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:11:09)
ACTION: jflory7
Continue working through Community Blog queue after receiving
feedback from authors(jflory7,
16:11:15)
=== [COMPLETE] skamath File a Badges ticket for
the Modularity WG on-boarding badge, write basic YAML file for
awarding the badge based on previous badge ticket (#464) ===(jflory7,
16:11:21)
=== skamath Work on generating data from
CommOps contributions and shaping interpretations from the data for
the retrospective (cc: bee2502 to help relate this to GSoC work,
possibly?) ===(jflory7,
16:11:39)
jflory7 skamath and bee2502 have root access to
commops.fedorainfracloud.org and should be able to deploy metrics
tasks/crons there(skamath,
16:12:52)
CommOps Team Onboarding Steps > Badges Team
Missing Badges > Hubs Team Badges Tracks and Widgets(jflory7,
16:24:42)
ACTION: jflory7
Update Ticket #69 about Modularity WG on-boarding badge
ticket(jflory7,
16:24:51)
IDEA: Tracking activity
and contributions in Pagure forks in fedmsg will be helpful
measuring contributions and taking a look at activity(jflory7,
16:37:11)
ACTION: skamath File
a Pagure issue about adding listeners for tracking activity in forks
via fedmsg(jflory7,
16:38:00)
IDEA: For existing
sub-projects / sub-groups, most have wiki pages already about
getting started, but they are all different from each other in how
they are formatted or organized. Hubs should help unify this
information for us.(jflory7,
16:38:33)
IDEA: Creating NEW
pages for sub-projects / sub-groups is helpful to contributors
short-term and also later on for the Hubs team when it comes time
for creating sub-$THING hubs(jflory7,
16:39:10)
CommOps ticket is still in progress and
awaiting artwork to be designed before it is closed out in
Trac.(jflory7,
16:39:34)
Modularity WG responded and left feedback on
the ticket in fedbadges for their on-boarding badge. This is an
ongoing process, and hopefully the ticket can be triaged and
awaiting artwork by the end of the week.(jflory7,
16:40:02)
Infrastructure will be up next, but an
interesting challenge. Already have badges for FAS sponsorships, so
other ideas (e.g. mailing list and Pagure activity) will be more
useful not only to Infra but many other sub-projects. Next steps for
Infra might be studying fedmsg and writing the YAML files, testing
how expensive the operations are, etc.(jflory7,
16:41:01)
Wiki page written up detailing communication
process between Ambassadors and Design team, based on feedback from
mizmo and gnokii. Page was sent off to the Design Team mailing list
and awaits review from Design members. Once approved, next action is
to socialize it with Ambassadors and specific regional leaders, i.e.
storytellers and treasurers.(jflory7,
16:42:47)
IDEA: Write a Community
Blog article about the process(jflory7,
16:44:52)
IDEA: Share the link
with the Ambassadors mailing list(jflory7,
16:45:00)
IDEA: Send directly to
regional storytellers and treasurers(jflory7,
16:45:11)
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:53:25)
In progress by author, will revisit once
complete.(jflory7,
16:55:44)
ACTION: jflory7 Take
a look at the FOSCo status page closer, see if there's anything to
add from CommOps / Marketing perspective
https://fedoraproject.org/wiki/FOSCo_status(jflory7,
16:59:25)
HELP: Writers for the
Community Blog wanted! Working on cool stuff in Fedora? Want to get
the word out about future changes? Need to get more opinions or eyes
on a topic? Consider writing a short post for the Community Blog!
Check out #fedora-commops for more info!(jflory7,
17:00:45)
The CommOps Fedora 24 retrospective wiki page
is now up. Anyone who has contributed or participated in CommOps
this release cycle is HIGHLY encouraged to add feedback to the page
with their thoughts and opinions about our performance as a team
this release. Please take 10 - 20 minutes to add your own thoughts
and ideas to the page this week. This helps us improve and grow as a
team.(jflory7,
17:01:16)
jflory7 Continue working through Community Blog queue after receiving feedback from authors
jflory7 Update Ticket #69 about Modularity WG on-boarding badge ticket
skamath File a Pagure issue about adding listeners for tracking activity in forks via fedmsg
commops New members, make sure you add your timezone / interests on CommOps wiki [ https://fedoraproject.org/wiki/CommOps ]
jflory7 Review and schedule SELF 2016 CommBlog post due:2016-07-12T12:00
jflory7 Take a look at the FOSCo status page closer, see if there's anything to add from CommOps / Marketing perspective https://fedoraproject.org/wiki/FOSCo_status
commops Add thoughts and feedback about CommOps performance this release to the retrospective page
jflory7 Add personal thoughts to F24 CommOps retrospective
skamath Figure out how to add statistics to the CommOps retrospective wiki
Action items, by person
commops
commops New members, make sure you add your timezone / interests on CommOps wiki [ https://fedoraproject.org/wiki/CommOps ]
commops Add thoughts and feedback about CommOps performance this release to the retrospective page
jflory7
jflory7 Continue working through Community Blog queue after receiving feedback from authors
jflory7 Update Ticket #69 about Modularity WG on-boarding badge ticket
jflory7 Review and schedule SELF 2016 CommBlog post due:2016-07-12T12:00
jflory7 Take a look at the FOSCo status page closer, see if there's anything to add from CommOps / Marketing perspective https://fedoraproject.org/wiki/FOSCo_status
jflory7 Add personal thoughts to F24 CommOps retrospective
skamath
skamath File a Pagure issue about adding listeners for tracking activity in forks via fedmsg
skamath Figure out how to add statistics to the CommOps retrospective wiki