12:23 p.m.
Hey all, started doing this in some other meeting minutes and thought I
would start here too. I'll do a brief written summary of the meeting,
and you can get the rest of the details in the links or minutes below!
Today's meeting featured 13 participants and lasted about a 1hr 20min.
We sent our best wishes out to decause as he begins his new journey in
the FOSS world. We also covered topics like our vFAD and planning for
the CommOps workshop at Flock. We have decided to postpone our vFAD and
refocus efforts on planning the Flock workshop in August. We also
covered the next steps for helping sub-projects / teams with their
on-boarding process. CommOps should be closing out soon, and Modularity
is up next.
See more about what happened today below!
= = = = =
Meeting ended Tue Jun 28 17:15:44 2016 UTC.
Minutes:
https://meetbot.fedoraproject.org/fedora-meeting/2016-06-28/commops.2016-...
Minutes (text):
https://meetbot.fedoraproject.org/fedora-meeting/2016-06-28/commops.2016-...
Log:
https://meetbot.fedoraproject.org/fedora-meeting/2016-06-28/commops.2016-...
* * * * *
============================================
#fedora-meeting: Fedora CommOps (2016-06-28)
============================================
Meeting started by jflory7_ at 15:55:02 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/fedora-meeting/2016-06-28/commops.2016-...
.
Meeting summary
---------------
* Agenda (jflory7_, 15:55:28)
* LINK: https://fedoraproject.org/wiki/Meeting:CommOps_2016-06-28
(jflory7_, 15:55:36)
* (1) Roll Call / Q&A (jflory7_, 15:55:43)
* (2) Announcements (jflory7_, 15:55:50)
* (3) Action items from last meeting (jflory7_, 15:55:58)
* (4) Tickets (jflory7_, 15:56:03)
* (5) Wiki Gardening (jflory7_, 15:56:10)
* (6) Community Blog (jflory7_, 15:56:18)
* (7) Release Schedule (jflory7_, 15:56:26)
* (8) Open Floor (jflory7_, 15:56:33)
* Name; Timezone; Sub-projects/Interest Areas (jflory7_, 15:56:47)
* Justin W. Flory; UTC-4; CommOps, Marketing / Magazine, Ambassadors,
Diversity, Join, and more (jflory7_, 15:57:12)
* Dhanesh B. Sabane, UTC+5:30, CommOps, ML, RPM packaging, Kernel
(dhanesh95, 15:57:26)
* Sachin S. Kamath; UTC +5.30 ; CommOps, GSoC, Metrics, * (skamath,
15:57:27)
* trishnag; UTC +5:30; Infrastructure, Cloud, CommOps (trishnag,
15:57:45)
* Announcements (jflory7_, 16:04:37)
* === "Friends. Features. Freedom. First. Forever." === (jflory7_,
16:04:44)
* LINK:
https://lists.fedoraproject.org/archives/list/commops@lists.fedoraproject...
(jflory7_, 16:04:49)
* On Friday, decause announced on the mailing list that he will be
leaving his position at Red Hat to become the Open Source Campaign
Manager for a candidate in the US elections. We wish decause well in
his future endeavors and will always be happy to see him in Fedora
whenever he has the time to stop by. For the time being, the Fedora
Community Lead position will remain open. (jflory7_, 16:04:56)
* === "Behind the new Fedora Developer Portal" === (jflory7_,
16:05:12)
* LINK: https://fedoramagazine.org/behind-new-fedora-developer-portal/
(jflory7_, 16:05:19)
* The Developer Portal for developers using Fedora or wanting to
contribute to Fedora has had some new changes. Read up on what's new
in the Developer Portal and a little bit of background behind its
inception in the Fedora Magazine article. (jflory7_, 16:05:27)
* === Google Summer of Code midterm evaluations ended === (jflory7_,
16:05:36)
* LINK: https://summerofcode.withgoogle.com/how-it-works/ (jflory7_,
16:05:42)
* Google Summer of Code 2016 midterm evaluations ended yesterday.
Students received a pass/fail rating from their mentor(s) on their
project status so far and are moving on the final period of their
project proposals. Students, make sure to reach out on the mailing
lists, communicate with blog posts, and participate in IRC
discussions for the final phase of your projects! (jflory7_,
16:05:50)
* Tummala Dhanvi ; UTC+5:30 ; CommOps, Security, Docs, GSoC, *
(c0mrad3, 16:09:01)
* GSoC students: Blog posts are required on a weekly basis now - the
slots are a 40 hour work week, and your work should reflect that.
Make sure you are communicating and being detailed in your
communications. (jflory7_, 16:09:12)
* All GSoC students: expect mail tomorrow morning (IST) from kushal.
(jflory7_, 16:12:37)
* Action items from last meeting (jflory7_, 16:13:17)
* LINK:
https://meetbot.fedoraproject.org/fedora-meeting/2016-06-21/commops.2016-...
(jflory7_, 16:13:23)
* 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:13:30)
* === [CHANGED] decause review the vFAD goals / objectives / etc. ===
(jflory7_, 16:13:39)
* ACTION: jflory7 Move forward with making final plans for vFAD or
reconsider plans for Flock workshop (???) (jflory7_, 16:13:48)
* === [CHANGED] decause nail down Flock arrangements and add to
fedocal === (jflory7_, 16:14:00)
* Further Flock arrangements will be handled by the Flock staff for
now, as far as I can tell? --Jflory7 (talk) 03:29, 28 June 2016
(UTC) (jflory7_, 16:14:08)
* ACTION: jflory7 Follow up in #fedora-flock about Fedocal for Flock
or if any previous action items need follow-up (jflory7_, 16:14:31)
* === [INCOMPLETE] jflory7 Open a ticket to look into drafting an
(automated?) check-in email with members of CommOps to determine
activity === (jflory7_, 16:14:40)
* ACTION: jflory7 jflory7 Open a ticket to look into drafting an
(automated?) check-in email with members of CommOps to determine
activity (jflory7_, 16:14:47)
* === [INCOMPLETE] decause Drop a line to the devel list to have
anyone going to Red Hat Summit add their info to the wiki page ===
(jflory7_, 16:15:03)
* Red Hat Summit happening now. (jflory7_, 16:15:09)
* === [INCOMPLETE] 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:15:19)
* 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:15:33)
* === [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:15:41)
* 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:15:50)
* === [COMPLETE] jflory7 Create a placeholder article for F22 EoL
article in CommBlog so we keep on the agenda === (jflory7_,
16:16:49)
* LINK:
https://communityblog.fedoraproject.org/?p=1681&preview=1&_ppp=f5...
(jflory7_, 16:16:56)
* === [COMPLETE] jflory7 Prepare the hack session ticket and CC
dhanesh95 so he gets context to what they are for a CommBlog article
=== (jflory7_, 16:17:20)
* Tickets (jflory7_, 16:17:57)
* LINK: https://fedorahosted.org/fedora-commops/report/9 (jflory7_,
16:18:11)
* === Ticket #10 === (jflory7_, 16:18:17)
* "CommOps vFAD 2016" (jflory7_, 16:18:23)
* LINK: https://fedorahosted.org/fedora-commops/ticket/10 (jflory7_,
16:18:30)
* LINK: https://fedoraproject.org/wiki/FAD_CommOps_2016 (jflory7_,
16:18:36)
* IDEA: At the Flock workshop, we could also revisit the idea of
planning our vFAD too and working on details there. (jflory7_,
16:25:34)
* AGREED: With the decause's departure, we will opt to postpone our
vFAD to a time after Flock or when a new Fedora Community Lead
arrives to assist with planning. Instead of the vFAD, we will shift
our planning efforts over to focusing on our workshop at Flock,
working on getting resources together for it, and putting together
an agenda for what will happen in the window. Hopefully also finding
a way for remote contributions from those who can't at (jflory7_,
16:25:46)
* === Tickets #34, 57 === (jflory7_, 16:26:49)
* #34: "[Onboarding Series] [MASTER TICKET] Creating sub-project
on-boarding badge series" (jflory7_, 16:27:00)
* #57: "[Onboarding Series] CommOps!" (jflory7_, 16:27:13)
* LINK: https://fedorahosted.org/fedora-commops/ticket/34 (jflory7_,
16:27:20)
* LINK: https://fedorahosted.org/fedora-commops/ticket/57 (jflory7_,
16:27:27)
* CommOps Team Onboarding Steps > Badges Team Missing Badges > Hubs
Team Badges Tracks and Widgets (jflory7_, 16:27:36)
* LINK: https://fedorahosted.org/fedora-badges/ticket/464 (jflory7_,
16:27:42)
* LINK:
https://fedorahosted.org/fedora-badges/attachment/ticket/464/commopsmailm...
(skamath, 16:30:24)
* Artwork from decause on CommOps on-boarding badge is uploaded and
can be used - will need to add his awesome explanation about the
Canadian goose as the CommOps mascot to the ticket for added
context. (jflory7_, 16:31:28)
* ACTION: 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:35:39)
* Wiki Gardening (jflory7_, 16:40:38)
* ACTION: commops New members, make sure you add your timezone /
interests on CommOps wiki [ https://fedoraproject.org/wiki/CommOps ]
(jflory7_, 16:40:46)
* Community Blog (jflory7_, 16:45:48)
* 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:45:50)
* === This Week in CommBlog === (jflory7_, 16:45:59)
* No new posts published this week! (jflory7_, 16:46:06)
* === Coming Up in CommBlog === (jflory7_, 16:46:13)
* (1) "Southeast Linux Fest 2016" (jflory7_, 16:46:20)
* LINK:
https://communityblog.fedoraproject.org/?p=1676&preview=1&_ppp=e0...
(jflory7_, 16:46:27)
* (2) "Hosting your own Fedora Test Day" (jflory7_, 16:46:33)
* LINK:
https://communityblog.fedoraproject.org/?p=1667&preview=1&_ppp=c4...
(jflory7_, 16:46:41)
* (3) "Fedora 22: End Of Life, 2016 July 19" (jflory7_, 16:46:50)
* LINK:
https://communityblog.fedoraproject.org/?p=1681&preview=1&_ppp=f5...
(jflory7_, 16:46:57)
* (4) "Getting started with 'update-testing' Fedora QA part 2"
(jflory7_, 16:47:04)
* LINK:
https://communityblog.fedoraproject.org/?p=1609&preview=1&_ppp=b5...
(jflory7_, 16:47:11)
* (5) "Getting started with Fedora QA part 3" (jflory7_, 16:47:19)
* LINK:
https://communityblog.fedoraproject.org/?p=1610&preview=1&_ppp=f8...
(jflory7_, 16:47:26)
* IDEA: A series about contributors and their experiences in the
project, how they got involved, to get involved, and so on. This
could be a recurring series on the Community Blog, similar to to the
"How do you Fedora?" series on the Magazine. (jflory7_, 16:56:36)
* Release Schedule (jflory7_, 16:58:58)
* LINK:
https://fedorapeople.org/groups/schedule/f-24/f-24-key-tasks.html
(jflory7_, 16:59:00)
* IDEA: I wanted to borrow something from the Marketing release
schedule for CommOps. At the end of every Fedora release, the
Marketing team writes a retrospective about how they felt things
went during the release, what worked well, what didn't work so well,
what can be improved, things that were awesome and worth noting,
etc. I'd like to do something similar to this for CommOps to see how
we, as contributors, felt about how this release went. (jflory7_,
17:01:43)
* ACTION: jflory7 Work on getting a wiki page created for the CommOps
F23 retrospective (jflory7_, 17:03:46)
* ACTION: 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_,
17:04:32)
* Open Floor (jflory7_, 17:06:55)
* Closing Thoughts (jflory7_, 17:10:52)
Meeting ended at 17:15:44 UTC.
Action Items
------------
* jflory7 Move forward with making final plans for vFAD or reconsider
plans for Flock workshop (???)
* jflory7 Follow up in #fedora-flock about Fedocal for Flock or if any
previous action items need follow-up
* jflory7 jflory7 Open a ticket to look into drafting an (automated?)
check-in email with members of CommOps to determine activity
* 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
* 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).
* commops New members, make sure you add your timezone / interests on
CommOps wiki [ https://fedoraproject.org/wiki/CommOps ]
* jflory7 Work on getting a wiki page created for the CommOps F23
retrospective
* 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?)
Action Items, by person
-----------------------
* bee2502
* 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?)
* commops
* commops New members, make sure you add your timezone / interests on
CommOps wiki [ https://fedoraproject.org/wiki/CommOps ]
* jflory7
* jflory7 Move forward with making final plans for vFAD or reconsider
plans for Flock workshop (???)
* jflory7 Follow up in #fedora-flock about Fedocal for Flock or if any
previous action items need follow-up
* jflory7 jflory7 Open a ticket to look into drafting an (automated?)
check-in email with members of CommOps to determine activity
* 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 Work on getting a wiki page created for the CommOps F23
retrospective
* skamath
* 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).
* 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?)
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* jflory7_ (254)
* skamath (61)
* dhanesh95 (36)
* zodbot (26)
* trishnag (15)
* decause (15)
* kushal (10)
* roshi (10)
* bee2502 (7)
* pravins (7)
* c0mrad3 (4)
* mark_otaris (4)
* cprofitt (2)
* Southern_Gentlem (2)
* jflory7 (0)
* commops (0)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
--
Cheers,
Justin W. Flory
jflory7(a)gmail.com
