ACTION: commops New
members, make sure you introduce yourself on the CommOps mailing
list [ https://fedoraproject.org/wiki/CommOps/Join ](jflory7,
16:31:43)
Justin W. Flory; UTC-4; CommOps, Marketing,
Magazine, Ambassadors, Diversity Team, sysadmin-badges, and
more(jflory7,
16:32:15)
Sachin S. Kamath; UTC +5.30; CommOps, Metrics,
GSoC, Join, *(skamath,
16:32:24)
Dhanesh B. Sabane, UTC+5:30, CommOps, RPM
Packaging, Python, Kernel(dhanesh95,
16:36:38)
Brian Exelbierd (bexelbie) officially took his
new role as the Fedora Community Action and Impact Coordinator
(a.k.a. F-cake) yesterday. Expect to see him even more around the
project soon!(jflory7,
16:42:03)
Fedora Ambassadors Charles Profitt and Justin
W. Flory attended HackMIT two weeks ago. In the event report, they
cover the anticipated impact with Fedora's participation and
evaluate engagement and interaction. Read the full report on the
Community Blog for more information.(jflory7,
16:42:22)
=== "Heroes of Fedora (HoF) – F25 Alpha"
===(jflory7,
16:42:36)
The Heroes of Fedora 25 Alpha was published
last week on the Community Blog. Special thanks and shout-out to the
amazing team of QA contributors who put forth a great amount of time
helping and develop this software!(jflory7,
16:42:45)
=== "Test Day: Internationalization (i18n)
features of Fedora 25" ===(jflory7,
16:42:50)
A Test Day for Fedora 25 internationalization
features recently came to a close. Many key features were tested.
Expect a longer event report in the future.(jflory7,
16:43:02)
Helpful guide explaining and detailing how to
get Hubs installed locally on a system and fight through technical
troubles often encountered by beginners.(jflory7,
16:43:37)
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:45:22)
=== [INCOMPLETE] jflory7 Write an introductory
post for Outreachy 2016 on the CommBlog ===(jflory7,
16:45:55)
ACTION: adityakonarde
Create a first draft of a Fedora + Outreachy Fall 2016 post by
Thursday evening, share link with the CommOps mailing list when
ready for review(jflory7,
16:51:04)
=== [COMPLETE] jflory7 Review emails for
pending posts on the CommBlog ===(jflory7,
16:51:46)
All pending review posts in the Community Blog
are currently reviewed and scheduled!(jflory7,
16:51:52)
=== skamath File a ticket in Fedora Infra Trac
for proposing an official migration from fedora-infra GitHub
organization into Pagure ===(jflory7,
16:51:59)
ACTION: skamath Open
a ticket in the Fedora Infrastructure Pagure repo proposing the idea
of officially migrating all Fedora apps projects to Pagure and
deprecating the use of GitHub(jflory7,
16:55:04)
=== skamath Research Bugzilla datagrepper
queries for new bug report tickets ===(jflory7,
16:55:24)
On-going discussion on how to implement, but
should be wrapping up this week. Goal of closing fedora-commops#84
by our next meeting and close out with the Python SIG!(jflory7,
17:03:10)
=== [INCOMPLETE] jflory7 Look into
possibilities of wiki template for hack session to help store the
data afterwards ===(jflory7,
17:03:21)
ACTION: jflory7 Look
into possibilities of wiki template for hack session to help store
the data afterwards(jflory7,
17:03:30)
=== [INCOMPLETE] commops Look into centralizing
/ making more clear what a member of Council or FESCo does, what
their responsibilities are, and centralize the info in a wiki page
or CommBlog article (more info to be put into ticket) ===(jflory7,
17:03:37)
ACTION: jflory7 File
ticket for looking into centralizing / making more clear what a
member of Council or FESCo does, what their responsibilities are,
and centralize the info in a wiki page or CommBlog article(jflory7,
17:03:45)
(1) Create clear guidelines and ways for
participants to express gratitude. Make sure this is somewhere
public and open.(jflory7,
17:10:55)
(2) Communicate ahead of time of the event, as
far as one month ahead of time.(jflory7,
17:11:04)
(3) Create a "community thank you pad", either
as a wiki page or otherwise, that can serve as a public wall of
thanks.(jflory7,
17:11:14)
(4) Focus on awareness the week leading up to
the event so users and contributors both are aware of the planned
event.(jflory7,
17:11:23)
(5) Monitor what's going on for the day of the
event and try to make observations about the result and impact of
the event (e.g. number of wiki edits on gratitude page, number of
karma cookies given on day, etc.).(jflory7,
17:11:32)
IDEA: Using an Etherpad
or wiki page as a public "thank you" wall(jflory7,
17:20:32)
ACTION: jflory7 Begin
drafting a Community Blog post for Fedora Appreciation Day no later
than Oct. 10 2016(jflory7,
17:21:49)
ACTION: FranciscoD
Look into creating a .thank command for zodbot that thanks a
specified contributor for doing awesome work(jflory7,
17:25:05)
IDEA: Setting up
streams / interviews during the week of Fedora Appreciation Day to
talk with contributors about their work / show some of the amazing
things people are working on every day (cc: Rhea)(jflory7,
17:25:53)
IDEA: Using a hashtag
to synchronize social media postings about the day
#FedoraAppreciation(jflory7,
17:26:34)
Focus on inclusion and making sure contributors
in some less visible sides of the project get thanks(jflory7,
17:29:02)
AGREED: Lots of
discussion and ideas! jflory7 will make a post on the mailing list
about Fedora Appreciation Day to summarize the points mentioned in
the meeting today(jflory7,
17:29:25)
HELP: More help is
needed on the Eleections process discussion! If you are interested
in the idea of improving the election process and having a nearly
*immediate* impact on the project community, please review this
ticket and add your feedback here (or even just leave a comment like
"I'm interested in this" if you want to get email notifications on
further discussion).(jflory7,
17:38:46)
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:44:21)
Stats seem to be inaccessible right now, but
will work on finding a resolution for this!(jflory7,
17:44:26)
commops New members, make sure you introduce yourself on the CommOps mailing list [ https://fedoraproject.org/wiki/CommOps/Join ]
adityakonarde Create a first draft of a Fedora + Outreachy Fall 2016 post by Thursday evening, share link with the CommOps mailing list when ready for review
skamath Open a ticket in the Fedora Infrastructure Pagure repo proposing the idea of officially migrating all Fedora apps projects to Pagure and deprecating the use of GitHub
skamath Work with fedbadges#491 to write the badges rule file for giving a badge to people who file bugs in Bugzilla
jflory7 Add thoughts on Pagure for Etherpad data storage to ticket #83
jflory7 Look into possibilities of wiki template for hack session to help store the data afterwards
jflory7 File ticket for looking into centralizing / making more clear what a member of Council or FESCo does, what their responsibilities are, and centralize the info in a wiki page or CommBlog article
jflory7 Begin drafting a Community Blog post for Fedora Appreciation Day no later than Oct. 10 2016
FranciscoD Look into creating a .thank command for zodbot that thanks a specified contributor for doing awesome work
jflory7 Close ticket #81 about Pagure migration
jflory7 Post to the mailing list about selecting a new sub-project to work with on the on-boarding process due:today
Action items, by person
adityakonarde
adityakonarde Create a first draft of a Fedora + Outreachy Fall 2016 post by Thursday evening, share link with the CommOps mailing list when ready for review
commops
commops New members, make sure you introduce yourself on the CommOps mailing list [ https://fedoraproject.org/wiki/CommOps/Join ]
FranciscoD
FranciscoD Look into creating a .thank command for zodbot that thanks a specified contributor for doing awesome work
jflory7
jflory7 Add thoughts on Pagure for Etherpad data storage to ticket #83
jflory7 Look into possibilities of wiki template for hack session to help store the data afterwards
jflory7 File ticket for looking into centralizing / making more clear what a member of Council or FESCo does, what their responsibilities are, and centralize the info in a wiki page or CommBlog article
jflory7 Begin drafting a Community Blog post for Fedora Appreciation Day no later than Oct. 10 2016
jflory7 Close ticket #81 about Pagure migration
jflory7 Post to the mailing list about selecting a new sub-project to work with on the on-boarding process due:today
skamath
skamath Open a ticket in the Fedora Infrastructure Pagure repo proposing the idea of officially migrating all Fedora apps projects to Pagure and deprecating the use of GitHub
skamath Work with fedbadges#491 to write the badges rule file for giving a badge to people who file bugs in Bugzilla
zodbot
FranciscoD Look into creating a .thank command for zodbot that thanks a specified contributor for doing awesome work