ACTION: commops New
members, make sure you introduce yourself on the CommOps mailing
list [ https://fedoraproject.org/wiki/CommOps/Join ](jwf,
15:30:34)
Justin W. Flory; UTC-5; CommOps, Diversity,
Ambassadors, sysadmin-badges(jwf,
15:31:03)
Year in Reviews are back! We're asking
sub-projects and teams to share their 2017 highlights and a goal for
2018. Are you involved with another team in Fedora? Please spread
the word in your other teams!(jwf,
15:35:40)
=== "Outreachy 2017: Meet the interns!"
===(jwf,
15:35:45)
chhavi_ interviewed Fedora's two newest
Outreachy interns. See what they're working on and what they want to
accomplish in this Outreachy cycle on the Community Blog!
chhavi++(jwf,
15:36:00)
=== "Fedora 27 Server classic release after all
— and Modularity goes back to the drawing board" ===(jwf,
15:36:07)
The Fedora 27 Modular Server beta didn't pan
out as expected. The team went back to the drawing board, and a
"classic" Fedora Server for F27 was released.(jwf,
15:36:15)
Sumantro and coremodule lead another Fedora
Classroom to teach Fedora QA! The next session is Friday, December
22 at 16:00 UTC. Hope to see you there!(jwf,
15:36:32)
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 if needed. If no status, we'll try to get a quick update
and move forward.(jwf,
15:38:01)
=== [COMPLETE] "commops FAD attendees, please
research your travel costs and add them to the wiki as soon as
possible!" ===(jwf,
15:38:08)
The FAD was approved at the last Council
meeting, on the condition that we _do_ produce a logic model
too.(jwf,
15:38:49)
=== [???] "skamath Add comment to ticket #114
(Grimoire ticket) that estimates a timeline for the Perceval fedmsg
plugin development. What is required? About how much work is
involved? Do you foresee any possible blockers?" ===(jwf,
15:38:57)
ACTION: skamath Add
comment to ticket #114 (Grimoire ticket) that estimates a timeline
for the Perceval fedmsg plugin development.(skamath,
15:40:52)
=== [???] "dhanesh95 Reach out to Fedora
Magazine team to get feedback on helpful data to incorporate into
fedmsg via WordPress's REST API (note limitations of REST API too –
what's helpful for what we can extract?)" ===(jwf,
15:41:13)
ACTION: dhanesh95
Reach out to Fedora Magazine team to get feedback on helpful data to
incorporate into fedmsg via WordPress's REST API (note limitations
of REST API too – what's helpful for what we can extract?)(jwf,
15:41:29)
IDEA: Using some of our
ticket requests as a template for future funding request
tickets(jwf,
15:44:46)
skamath and dhanesh95 both have research work
to do for the FAD (see previous action items). jwf is working on
Appreciation Week / elections prep work to jumpstart discussions at
FAD(jwf,
15:45:50)
skamath prepping "Getting started with metrics"
guide in near future(jwf,
15:46:18)
ACTION: commops If
needed, please file funding request tickets for other events, e.g.
DevConf, with EMEA Ambassadors(jwf,
15:47:27)
skamath set up a local dev environment and is
reading training manuals. There are no blockers as of now. As he
explores plugins more, he will update the ticket with his findings.
See previous action item for this.(jwf,
15:49:39)
Removing from meeting agenda for now – skamath
will re-add it when feedback is needed or we need to discuss as a
group(jwf,
15:50:46)
=== Ticket #108: "Metrics for Community Blog
and Fedora Magazine" ===(jwf,
15:50:58)
This ticket blocks on the previous action item
from dhanesh95. Removing from the meeting agenda and will leave it
to dhanesh95 to re-add it to meeting agenda when group discussion /
feedback is needed.(jwf,
15:53:38)
=== Ticket #129: "Run 2017 "Year in Review"
series on CommBlog" ===(jwf,
15:54:01)
IDEA: Migrating from
FedoraHosted to Pagure(jwf,
16:00:14)
IDEA: 2018 goal:
Docs-ify ALL the things (in CommOps with docs toolchain)(jwf,
16:01:14)
ACTION: jwf File new
ticket to track a CommOps Year in Review with ideas from this
meeting(jwf,
16:01:33)
HELP: If you have extra
time, consider helping other teams write their own Year in Reviews!
For example, a specific Fedora Infrastructure application!(jwf,
16:05:21)
IDEA: Diversity Team
outreach for a YiR: Consider diversity survey, #fedora-women
reinvigoration, Fedora Women Day 2017, etc.(jwf,
16:08:24)
ACTION: meskarune
Open new ticket in Fedora CommOps Pagure for our Year in Review, and
a ticket in Fedora Diversity Pagure for Year in Review(jwf,
16:11:09)
commops New members, make sure you introduce yourself on the CommOps mailing list [ https://fedoraproject.org/wiki/CommOps/Join ]
jwf Create a logic model based on the current FAD template
skamath Add comment to ticket #114 (Grimoire ticket) that estimates a timeline for the Perceval fedmsg plugin development.
dhanesh95 Reach out to Fedora Magazine team to get feedback on helpful data to incorporate into fedmsg via WordPress's REST API (note limitations of REST API too – what's helpful for what we can extract?)
commops If needed, please file funding request tickets for other events, e.g. DevConf, with EMEA Ambassadors
jwf File new ticket to track a CommOps Year in Review with ideas from this meeting
meskarune Open new ticket in Fedora CommOps Pagure for our Year in Review, and a ticket in Fedora Diversity Pagure for Year in Review
Action items, by person
commops
commops New members, make sure you introduce yourself on the CommOps mailing list [ https://fedoraproject.org/wiki/CommOps/Join ]
commops If needed, please file funding request tickets for other events, e.g. DevConf, with EMEA Ambassadors
jwf
jwf Create a logic model based on the current FAD template
jwf File new ticket to track a CommOps Year in Review with ideas from this meeting
meskarune
meskarune Open new ticket in Fedora CommOps Pagure for our Year in Review, and a ticket in Fedora Diversity Pagure for Year in Review
skamath
skamath Add comment to ticket #114 (Grimoire ticket) that estimates a timeline for the Perceval fedmsg plugin development.