12:32 p.m.
============================================
#fedora-meeting: Fedora CommOps (2016-07-05)
============================================
Meeting started by jflory7 at 15:56:11 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/fedora-meeting/2016-07-05/commops.2016-...
.
Meeting summary
---------------
* Agenda (jflory7, 15:56:27)
* LINK: https://fedoraproject.org/wiki/Meeting:CommOps_2016-07-05
(jflory7, 15:56:32)
* (1) Roll Call / Q&A (jflory7, 15:56:41)
* (2) Announcements (jflory7, 15:56:46)
* (3) Action items from last meeting (jflory7, 15:56:51)
* (4) Tickets (jflory7, 15:56:55)
* (5) Wiki Gardening (jflory7, 15:57:00)
* (6) Community Blog (jflory7, 15:57:14)
* (7) Release Schedule (jflory7, 15:57:22)
* (8) Open Floor (jflory7, 15:57:27)
* Roll Call / Q&A (jflory7, 15:57:43)
* Name; Timezone; Sub-projects/Interest Areas (jflory7, 15:57:43)
* Trishna Guha; UTC +5:30; Infrastructure, Cloud, CommOps (trishnag,
15:58:20)
* Justin W. Flory; UTC-4; CommOps, Marketing / Magazine, Ambassadors,
Diversity, Join, Infrastructure-fi, and more (jflory7, 15:58:27)
* Sachin S. Kamath ; UTC +5.30 ; CommOps, GSoC, Metrics, Onboarding
and more .. (skamath, 15:58:31)
* Tummala Dhanvi ; UTC 5:30 ; CommOps, Docs, Security, GSoC *
(c0mrad3, 15:58:52)
* bee2502 ; UTC +2 ; Metrics,GSoC (bee2502, 16:01:34)
* Announcements (jflory7, 16:05:28)
* === "Fedora 22: End Of Life, 2016 July 19" === (jflory7, 16:05:34)
* LINK: https://fedoramagazine.org/fedora-22-end-of-life-2016-july/
(jflory7, 16:05:38)
* 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)
* LINK: http://athosribeiro.com/post/fedora24-rp-sp/ (jflory7,
16:06:09)
* LINK:
http://danielammorais.com/2016/07/04/fedora-24-release-party-in-sao-paulo/
(jflory7, 16:06:14)
* LINK: https://yoseft7.wordpress.com/2016/07/03/f24-release-party-pa/
(jflory7, 16:06:19)
* LINK: https://www.facebook.com/events/1625975777730164/ (jflory7,
16:06:22)
* LINK: https://www.facebook.com/events/1141198245938476/ (jflory7,
16:06:27)
* LINK:
http://www.abdelmartinez.com/2016/07/fedora-24-release-party-panama-repor...
(jflory7, 16:06:33)
* LINK: https://nmilosev.svbtle.com/fedora-24-release-party-novi-sad
(jflory7, 16:06:38)
* 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)
* LINK:
https://communityblog.fedoraproject.org/fedora-24-have-a-party/
(jflory7, 16:06:47)
* === Flock 2016: August 2-5, 2016 === (jflory7, 16:07:09)
* LINK: https://flocktofedora.org/ (jflory7, 16:07:13)
* Reminder that Flock, Fedora's annual contributor conference, is
coming up at the beginning of next month. (jflory7, 16:07:20)
* LINK:
http://sumantrom.blogspot.in/2016/07/fedora-24-release-party-post-event.html
(jflory7, 16:07:50)
* Action items from last meeting (jflory7, 16:09:05)
* LINK:
https://meetbot.fedoraproject.org/fedora-meeting/2016-06-28/commops.2016-...
(jflory7, 16:09:10)
* 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)
* LINK: https://fedorahosted.org/fedora-commops/ticket/79 (jflory7,
16:09:31)
* LINK: https://fedoraproject.org/wiki/CommOps/Flock_2016 (jflory7,
16:09:37)
* === [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)
* LINK: https://fedorahosted.org/fedora-commops/ticket/78 (jflory7,
16:10:43)
* === [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)
* LINK: https://fedoraproject.org/wiki/Ambassadors/Design (jflory7,
16:11:00)
* === [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)
* LINK: https://fedorahosted.org/fedora-badges/ticket/466 (jflory7,
16:11:25)
* === [COMPLETE] jflory7 Work on getting a wiki page created for the
CommOps F23 retrospective === (jflory7, 16:11:31)
* LINK: https://fedoraproject.org/wiki/F24_CommOps_retrospective
(jflory7, 16:11:35)
* === 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)
* Tickets (jflory7, 16:13:36)
* LINK: https://fedorahosted.org/fedora-commops/report/9 (jflory7,
16:13:41)
* === Ticket #79 === (jflory7, 16:13:45)
* "Flock 2016 CommOps Workshop" (jflory7, 16:13:52)
* LINK: https://fedorahosted.org/fedora-commops/ticket/79 (jflory7,
16:13:56)
* LINK: https://fedoraproject.org/wiki/CommOps/Flock_2016 (jflory7,
16:14:00)
* === Tickets #34, 69 === (jflory7, 16:24:13)
* #39: "[Onboarding Series] [MASTER TICKET] Creating sub-project
on-boarding badge series" (jflory7, 16:24:20)
* #49: "[Onboarding Series] CommOps!" (jflory7, 16:24:25)
* LINK: https://fedorahosted.org/fedora-commops/ticket/34 (jflory7,
16:24:29)
* LINK: https://fedorahosted.org/fedora-commops/ticket/69 (jflory7,
16:24:33)
* LINK: https://fedorahosted.org/fedora-badges/ticket/466 (jflory7,
16:24:37)
* 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)
* === Ticket #71 === (jflory7, 16:42:18)
* "Centralizing Ambassadors / Events resources and utilities"
(jflory7, 16:42:22)
* LINK: https://fedorahosted.org/fedora-commops/ticket/71 (jflory7,
16:42:37)
* LINK: https://fedoraproject.org/wiki/Ambassadors/Design (jflory7,
16:42:42)
* 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)
* Wiki Gardening (jflory7, 16:52:05)
* ACTION: commops New members, make sure you add your timezone /
interests on CommOps wiki [ https://fedoraproject.org/wiki/CommOps ]
(jflory7, 16:52:12)
* Community Blog (jflory7, 16:53:23)
* 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)
* === This Week in CommBlog === (jflory7, 16:53:37)
* (1) "Fedora Design Suite considered “best of the basics”" (jflory7,
16:53:42)
* LINK:
https://communityblog.fedoraproject.org/fedora-design-suite-best-basics/
(jflory7, 16:53:48)
* Total Views (June 30 - July 5): 49 (jflory7, 16:53:53)
* LINK:
https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&...
(jflory7, 16:54:00)
* === Coming Up in CommBlog === (jflory7, 16:54:06)
* (1) "Southeast Linux Fest 2016" (jflory7, 16:54:11)
* LINK:
https://communityblog.fedoraproject.org/?p=1676&preview=1&_ppp=7b...
(jflory7, 16:54:17)
* ACTION: jflory7 Review and schedule SELF 2016 CommBlog post
due:2016-07-12T12:00 (jflory7, 16:54:23)
* (2) "Hosting your own Fedora Test Day" (jflory7, 16:54:28)
* LINK:
https://communityblog.fedoraproject.org/?p=1667&preview=1&_ppp=fb...
(jflory7, 16:54:34)
* Already reviewed, waiting for follow-up from author (jflory7,
16:54:40)
* (3) "Heroes of Fedora (HoF) – F23 Final" (jflory7, 16:54:45)
* LINK:
https://communityblog.fedoraproject.org/?p=1697&preview=1&_ppp=e2...
(jflory7, 16:54:55)
* Scheduled: 2016-07-07, 08:15 UTC (jflory7, 16:54:59)
* (4) "Fedora 24 Release Party: San Fernando Valley Linux Users Group
(2016) Event Report – Van Nuys, California" (jflory7, 16:55:37)
* LINK:
https://communityblog.fedoraproject.org/?p=1703&preview=1&_ppp=c6...
(jflory7, 16:55:39)
* 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)
* Release Schedule (jflory7, 17:01:06)
* LINK:
https://fedorapeople.org/groups/schedule/f-24/f-24-key-tasks.html
(jflory7, 17:01:10)
* 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)
* LINK: https://fedoraproject.org/wiki/F24_CommOps_retrospective
(jflory7, 17:01:25)
* ACTION: commops Add thoughts and feedback about CommOps performance
this release to the retrospective page (jflory7, 17:01:30)
* ACTION: jflory7 Add personal thoughts to F24 CommOps retrospective
(jflory7, 17:01:36)
* ACTION: skamath Figure out how to add statistics to the CommOps
retrospective wiki (skamath, 17:02:26)
* Congrats, you survived the Fedora 24 release cycle! commops++
(jflory7, 17:05:17)
* Open Floor (jflory7, 17:05:39)
Meeting ended at 17:09:56 UTC.
Action Items
------------
* 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
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* jflory7 (264)
* skamath (68)
* zodbot (28)
* trishnag (27)
* meskarune (17)
* mailga (7)
* c0mrad3 (6)
* devyani7 (5)
* GIANT_CRAB (4)
* bee2502 (2)
* commops (0)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
https://meetbot.fedoraproject.org/fedora-meeting/2016-07-05/commops.2016-...
--
You received this message due to your preference settings at
https://apps.fedoraproject.org/notifications/fmnmeetingminutes.id.fedorap...