Brief overview of Flock 2016 with links to
individual contributor blog posts and reports about the event. Good
way to reflect / review on discussions and focuses from Flock or to
see what happened if you were not able to attend.(skamath,
16:02:45)
Ongoing efforts to introduce FOSS, Fedora
Quality Assurance, and testing to students across India. Sumantro
Mukherjee (sumantrom) is helping lead these efforts. Watch for more
information on the Community Blog in coming weeks!(skamath,
16:03:23)
Reminder that the migration from Trac to Pagure
is targeted for Monday, August 29th, 2016. We will be abandoning
Trac soon. More information to come.(skamath,
16:03: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.(skamath,
16:05:20)
=== [INCOMPLETE] downey Edit original
UnixStickers shirt article to include links / mentions of the
women's sizes / editions too ===(skamath,
16:05:33)
ACTION: downey Ping
jflory7 for editing article / adding paragraph into article(skamath,
16:06:37)
=== skamath file a ticket on fedmsg repo for
the mailman bug ===(skamath,
16:06:44)
=== [INCOMPLETE] jflory7 Work with bee2502 on
writing a report / update on the Flock 2016 CommOps workshop
===(skamath,
16:07:59)
ACTION: jflory7 Work
with bee2502 on writing a report / update on the Flock 2016 CommOps
workshop(skamath,
16:08:31)
=== [INCOMPLETE] jflory7 bee2502 Take workshop
feedback and parse it into more accessible data (e.g. tickets /
commits / CommBlog posts / metrics / etc.) ===(skamath,
16:08:43)
ACTION: jflory7
bee2502 Take workshop feedback and parse it into more accessible
data (e.g. tickets / commits / CommBlog posts / metrics /
etc.)(skamath,
16:08:51)
=== [COMPLETE] jflory7 Review emails for
pending posts on the CommBlog ===(skamath,
16:09:09)
ACTION: jflory7
Review emails for pending posts on the CommBlog(skamath,
16:09:21)
=== [INCOMPLETE] jflory7 File tickets for
Python SIG, add feedback for Ambassadors from workshop ===(skamath,
16:09:35)
ACTION: jflory7 File
tickets for Python SIG, add feedback for Ambassadors from
workshop(skamath,
16:10:06)
=== [INCOMPLETE] jflory7 Update Community Blog
writing guide for writing a new article based on what's actually
happening in 2016 now ===(skamath,
16:10:29)
ACTION: jflory7
Update Community Blog writing guide for writing a new article based
on what's actually happening in 2016 now(skamath,
16:10:38)
=== [INCOMPLETE] jflory7 Sort through ideas on
reviewing old contributor discussion, form proposals in the ticket,
share at next meeting ===(skamath,
16:11:38)
ACTION: jflory7 Sort
through ideas on reviewing old contributor discussion, form
proposals in the ticket, share at next meeting(skamath,
16:11:45)
=== [COMPLETE] jflory7 Remove Ticket #10 from
meeting agenda, collaborate with bee2502 on sorting through feedback
/ ideas from Flock ===(skamath,
16:12:15)
AGREED: Due to lots
of raw ideas and discussion from last week's meeting, would like to
defer further discussion until there are more solid proposals to
discuss / agree on(jflory7,
16:24:00)
Last meeting, we agreed that next target group
(outside of final follow-up on tickets awaiting badges) would be the
Python SIG due to discussions that happened at the CommOps workshop
at Flock 2016(jflory7,
16:28:06)
Background on the Python SIG: Around 20
members, handles reviewing Python packages in Fedora, deals with
Python-specific technical decisions in Fedora, also sometimes
handles security-critical issues with Python packages in
Fedora(jflory7,
16:29:24)
Noted at Flock that the on-boarding process for
new members has difficulties: Unclear process for newcomers to
follow, distinguishment between mailing lists (one public, one
private for security bugs) unclear, need more items to be able to
help guide newcomers to, sometimes there are "human" decisions that
need to be made when reviewing new applicants(jflory7,
16:31:09)
IDEA: Revamping wiki
page / establishing numbered steps for newcomers to follow to become
involved(jflory7,
16:31:49)
IDEA: Making it clear
what info is needed from newcomers for current members of the SIG to
understand what newcomers are familiar with, interested in
contributing towards, or able to do(jflory7,
16:32:17)
IDEA: Coming up with
creative solutions for how something that sometimes requires a
subjective, "human" review process to follow general guidelines or
points for evaluating newcomers (with context to revealing security
bugs or issues)(jflory7,
16:33:21)
IDEA: Improving
communication about Python SIG member list being on the wiki over a
FAS group (and that's the official source for people involved with
the Python SIG)(jflory7,
16:45:05)
IDEA: An
apprentice-esque type approach for newcomers to Python SIG???(jflory7,
16:45:23)
ACTION: skamath File
a ticket in Fedora Infra Trac for proposing an official migration
from fedora-infra GitHub organization into Pagure since it has
stabilized since the last time this was discussed (to jflory7's
knowledge, anyways ;) )(jflory7,
16:54:00)
ACTION: jflory7 Reach
out to decause about the idea of migrating his tools in the CommOps
toolbox to Pagure and granting access to the CommOps group(jflory7,
16:54:46)
ACTION: commops New
members, make sure you add your timezone / interests on CommOps wiki
[ https://fedoraproject.org/wiki/CommOps ](jflory7,
16:56:52)
wikieditor FAS group: Group created not as a
default "join to get access" kind of context, but more for edge
cases where it's more plausible to add them to a standalone FAS
group versus onboarding in a group (also might not have a FAS
group). Example used was remixer who maintains a wiki page but
nothing else.(jflory7,
17:03:20)
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,
17:05:48)
downey Ping jflory7 for editing article / adding paragraph into article
jflory7 Work with bee2502 on writing a report / update on the Flock 2016 CommOps workshop
jflory7 bee2502 Take workshop feedback and parse it into more accessible data (e.g. tickets / commits / CommBlog posts / metrics / etc.)
jflory7 Review emails for pending posts on the CommBlog
jflory7 File tickets for Python SIG, add feedback for Ambassadors from workshop
jflory7 Update Community Blog writing guide for writing a new article based on what's actually happening in 2016 now
jflory7 Sort through ideas on reviewing old contributor discussion, form proposals in the ticket, share at next meeting
skamath File a ticket in Fedora Infra Trac for proposing an official migration from fedora-infra GitHub organization into Pagure since it has stabilized since the last time this was discussed (to jflory7's knowledge, anyways ;) )
jflory7 Reach out to decause about the idea of migrating his tools in the CommOps toolbox to Pagure and granting access to the CommOps group
commops New members, make sure you add your timezone / interests on CommOps wiki [ https://fedoraproject.org/wiki/CommOps ]
jflory7 Do a social media blast promoting the FOSS Wave article for Bhopal
jflory7 Revisit wiki spam article with context of current situation with FAS groups
Action items, by person
bee2502
jflory7 Work with bee2502 on writing a report / update on the Flock 2016 CommOps workshop
jflory7 bee2502 Take workshop feedback and parse it into more accessible data (e.g. tickets / commits / CommBlog posts / metrics / etc.)
commops
commops New members, make sure you add your timezone / interests on CommOps wiki [ https://fedoraproject.org/wiki/CommOps ]
downey
downey Ping jflory7 for editing article / adding paragraph into article
jflory7
downey Ping jflory7 for editing article / adding paragraph into article
jflory7 Work with bee2502 on writing a report / update on the Flock 2016 CommOps workshop
jflory7 bee2502 Take workshop feedback and parse it into more accessible data (e.g. tickets / commits / CommBlog posts / metrics / etc.)
jflory7 Review emails for pending posts on the CommBlog
jflory7 File tickets for Python SIG, add feedback for Ambassadors from workshop
jflory7 Update Community Blog writing guide for writing a new article based on what's actually happening in 2016 now
jflory7 Sort through ideas on reviewing old contributor discussion, form proposals in the ticket, share at next meeting
skamath File a ticket in Fedora Infra Trac for proposing an official migration from fedora-infra GitHub organization into Pagure since it has stabilized since the last time this was discussed (to jflory7's knowledge, anyways ;) )
jflory7 Reach out to decause about the idea of migrating his tools in the CommOps toolbox to Pagure and granting access to the CommOps group
jflory7 Do a social media blast promoting the FOSS Wave article for Bhopal
jflory7 Revisit wiki spam article with context of current situation with FAS groups
skamath
skamath File a ticket in Fedora Infra Trac for proposing an official migration from fedora-infra GitHub organization into Pagure since it has stabilized since the last time this was discussed (to jflory7's knowledge, anyways ;) )