bee2502 has started working on generating some
ideas on community metric generation. Check out the wiki page with
more information on metric collection with regards to discussion at
the CommOps Flock workshop there.(jflory7,
16:08:47)
HELP: Feel free to add
some of your own ideas, thoughts, or wishes for metrics to this page
too!(jflory7,
16:09:01)
=== "Docs Project update from Flock 2016"
===(jflory7,
16:09:07)
On jflory7's "must read list of 2016" - very
informative post about the state of the Fedora Docs team and adds a
lot of insight into the issues they are facing and how they plan to
overcome them. If you haven't been following the Docs team and want
to see what's up in a single post, this is a good one to
read.(jflory7,
16:09:24)
=== "Women in technology: Fedora campus
presence" ===(jflory7,
16:09:34)
Outreach efforts towards women are ongoing in
local Indian communities. Read this brief report to see what is
getting started by a2batic and sumantrom.(jflory7,
16:09:47)
=== "Żegnajcie! Fedora Flock 2016 in words"
===(jflory7,
16:10:24)
jflory7's event report on Flock 2016. There's a
section dedicated to the Fedora CommOps workshop and feedback
related to the workshop. It may be worth a read for anyone
interested in the workshop and what kinds of results we got out of
holding it.(jflory7,
16:10:34)
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:15:43)
=== [INCOMPLETE] jflory7 Write a promo on the
CommBlog about the ultimate women's Fedora t-shirt ===(jflory7,
16:17:22)
ACTION: downey Edit
original UnixStickers shirt article to include links / mentions of
the women's sizes / editions too(jflory7,
16:17:46)
=== [INCOMPLETE] skamath file a ticket on
fedmsg repo for the mailman bug ===(jflory7,
16:17:59)
ACTION: skamath file
a ticket on fedmsg repo for the mailman bug(jflory7,
16:18:04)
=== [IN PROGRESS] jflory7 Work with bee2502 on
writing a report / update on the Flock 2016 CommOps workshop
===(jflory7,
16:18:10)
ACTION: jflory7 Work
with bee2502 on writing a report / update on the Flock 2016 CommOps
workshop(jflory7,
16:18:21)
jflory7 and bee2502 did some parsing of info on
Saturday from the workshop, but there's still a little more to do -
jflory7 needs to start a draft in the CommBlog next(jflory7,
16:18:27)
=== [IN PROGRESS] jflory7 Review emails for
pending posts on the CommBlog ===(jflory7,
16:18:34)
ACTION: jflory7
Review emails for pending posts on the CommBlog(jflory7,
16:18:40)
This is getting done every week, but there's a
consistent amount of more coming in each week for new posts and
authors, which is awesome. :)(jflory7,
16:18:49)
=== [IN PROGRESS] jflory7 bee2502 Take workshop
feedback and parse it into more accessible data (e.g. tickets /
commits / CommBlog posts / metrics / etc.) ===(jflory7,
16:18:59)
ACTION: jflory7
bee2502 Take workshop feedback and parse it into more accessible
data (e.g. tickets / commits / CommBlog posts / metrics /
etc.)(jflory7,
16:19:09)
jflory7 and bee2502 did some parsing of info on
Saturday from the workshop, but there's still a little more to do -
jflory7 needs to start a draft in the CommBlog next(jflory7,
16:19:15)
=== [INCOMPLETE] jflory7 File tickets for
Python SIG, add feedback for Ambassadors from workshop ===(jflory7,
16:19:27)
ACTION: jflory7 File
tickets for Python SIG, add feedback for Ambassadors from
workshop(jflory7,
16:19:39)
=== [COMPLETE] jflory7 Close ticket#80
===(jflory7,
16:19:45)
It is now possible for us to migrate from Trac
to Pagure (the importer tool was recently completed by cverna). A
staging repo of what the import looks like exists on the Pagure
staging instance. Since we now have the tooling, we should set a
hard date for migrating the entire Trac over to Pagure and begin
retiring it. Rough timeline detailed in ticket.(jflory7,
16:22:51)
Two ways to do it: Infra-style with a manual
post sent monthly, or could use Fedocal to automate this once a
month as check-in calendar event to query members on regular,
consistent basis. Non-responders would be removed from the FAS group
hypothetically. Need to discuss implementation and if this is
something we want to do.(jflory7,
16:27:07)
IDEA: Would this be
necessary for active members to also complete every month? Is it
better to separate into two "groups" - apprentices and regular
members?(jflory7,
16:27:13)
IDEA: Blatantly
removing people is the wrong approach: it will be demotivating and
isolate people from wanting to contribute(jflory7,
16:35:26)
IDEA: If any kind of
consistent follow-up is to be done, it really should be automated so
it will always be consistent(jflory7,
16:35:43)
IDEA: Start in a
beginner group, then move to an "alumni" group for contributors who
are consistent and active (i.e. they no longer have to do the
regular check-in)(jflory7,
16:36:21)
IDEA: A single ping is
easy to miss and it could cause someone still interested to be left
out(jflory7,
16:36:37)
IDEA: Responding to one
email may not be the best gauge of activity / contributions, so
makes it difficult to use as a tool to evaluate merits(jflory7,
16:37:06)
IDEA: Every team could
have "three big things" an active person does, follow up on them
around a 3-month interval, judge inactivity on those criteria(jflory7,
16:37:56)
IDEA: Automated tools
don't flag some for removal, but just review / follow-up(jflory7,
16:38:22)
IDEA: Instead of
removing contributors, "retire" them - could de-provision by
removing from group, but note them somewhere along with their
contributions, kind of like a wall of fame sort of idea(jflory7,
16:40:24)
ACTION: jflory7 Sort
through ideas on reviewing old contributor discussion, form
proposals in the ticket, share at next meeting(jflory7,
16:42:03)
AGREED: Lots of ideas
and discussion on this ticket - jflory7 will sort through these
ideas, try turning them into separate proposals, and then we can
vote on them at the next meeting(jflory7,
16:42:39)
Based on Flock outcome, likely reasonable to
begin planning out our own FAD event. Can opt for an in-person FAD
at first, and if necessary, fall back to virtual event. Would be
held in 2017 (after February / March when budget for next fiscal
year allocated). First steps would be for defining purpose and
matching up to outcomes and results that align with Fedora mission.
We can start now by using mattdm's logic model template and(jflory7,
16:44:26)
...identifying key areas for us to focus on as
team.(jflory7,
16:44:36)
Key thing to get out of this is less on
physical / costly items, more on providing resources / tools to
point people towards contributing to open source and subsequently
Fedora, e.g. IRC client, bouncer service, development tools,
software in Fedora, etc.)(jflory7,
16:49:56)
IDEA: Key to the gate:
FAS account (guide to register and what a FAS account gives you
access to)(jflory7,
16:50:55)
IDEA: IRC client:
HexChat (IRC beginner guide, how to use HexChat, etc.)(jflory7,
16:51:07)
IDEA: Photo editing:
DarkTable (what it does, guides for using it, etc.)(jflory7,
16:51:14)
IDEA: Creating Fedora
USB media: Whatever the preferred tool now is for creating media
correctly and with stability (Fedora Media Writer?)(jflory7,
16:51:20)
IDEA: IRCCloud
temporary membership / full account as part of the starter pack?
[Warning: This would be a relationship we would have to actively
maintain](jflory7,
16:54:55)
IDEA: Starting small by
identifying the "Fedora Essentials 101" for what a student would
need for Linux / FOSS(jflory7,
16:58:22)
HELP: What tool helped
you get started with Linux and FOSS? What made Fedora so great for
you? What could we offer students to help introduce to FOSS, Linux,
and then Fedora? Please add your ideas and thoughts to the ticket so
we can start building a first edition of the pack!(jflory7,
17:01:18)
Infrastructure ticket put on hold while current
blocking issues are resolved. More detail in the ticket. For now, we
need to decide and focus on a new sub-project / team to focus on.
jflory7 would like to propose the Python SIG as a team that is in
need of some assistance and help. Having difficulties on-boarding
new members effectively. Need to find ways for communicating this
better and how to make it simpler for getting involved. See(jflory7,
17:03:25)
...rough notes for Flock as a primer on this
one.(jflory7,
17:03:33)
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:12:23)