I started writing this a while ago and never got it fully formed. Rather than let it keep rotting in my drafts folder I wanted to share it and see if it made sense to anyone else.
Warning - rough edges ahead!
---
Conversations with several people have resulted in distilling the following idea:
= EasyFix
== Changing metadata
Modify the table that drives fedoraproject.org/easyfix that is located at https://fedoraproject.org/wiki/Easyfix
The table would now include two additional columns (optional)
Col 1 = existing reference to the issue tracker. We should consider adding gitlab.com support
Col 2 = existing point of contact
Col 3 = category of task (documentation, infrastructure, programming-Haskell, programming-Ruby, etc.)
Col 4 = SIG/WG/etc. this project is related too (Design, Council, KDE, etc.)
== Changing fedoraproject.org/easyfix
Today we show only two categories: Issues from Pagure/Github and Bugzillas
I believe those categories are not the right categories for consumers of the page. Using the new category (col 3) above, we would break things out by the kind of contribution. This would serve to let people browse related tasks more easily and to reduce the overwhelming nature of the current lists.
For BZs we are either going to have to guess based on BZ metadata or leave them lumped together.
= WCIDFF
WCDIFF should be extended to show the categories and groups appropriate for the various endpoints. This way the person who navigates WCDIFF has the option of reading a specific task they could work on right now, if they so desire.
= Marketing/Promotion
The categories give us the opportunity to promote our easyfixes as a great way to join or contribute in a targeted manner. This could come in the form of articles, tweets, or live conference appearances.
What do people think?
regards,
bex
Hi commops!
My name is Harris Kenny (kenhara). I am new to contributing to Fedora but
have been running Fedora for several years on my personal machines.
I first learned about Fedora at Open Hardware Summit 2015, where I met Tom
Callaway (spot). I enjoy the active community and stability of Fedora and
have relied on its documentation as a new GNU/Linux user. I would love to
help expand the documentation to help future new users.
I want contribute to the Fedora Wiki because I have experience writing
documentation. I specifically want to start by helping with documentation
for 0 A.D. (0ad <https://apps.fedoraproject.org/packages/0ad>), which I
recently discovered and love.
Though this is a personal application to join commops, my professional work
is relevant too. I work for Aleph Objects, Inc., manufacturer of LulzBot 3D
printers. LulzBot printers are Free/Libre/Open Source, both the first
product certified by the FSF
<https://www.fsf.org/resources/hw/endorsement/respects-your-freedom> and
the first printer certified by OSHWA
<http://certificate.oshwa.org/certification-directory/>.
I started in Marketing at the company, helping establish documentation,
tutorials, email newsletters, social media, digital advertising, trade
shows, public relations, etc. with all Free/Libre tools. Cura LulzBot
Edition software is also packaged for Fedora (see: cura-lulzbot
<https://apps.fedoraproject.org/packages/cura-lulzbot>).
In another personal capacity, I serve as Treasurer on the Board of
Directors at OSHWA. I have also contributed writing to opensource.com,
among other places.
Besides contributions to Wikipedia, this is the first time I'm looking to
personally contribute to an open source project (outside of work). I'd love
any articles or tips on how to get started and avoid obvious new
contributor mistakes :) (Bootstrapped
<https://pagure.io/Fedora-Badges/issue/409> seems like a good start)
Thank you for your time and consideration!
--
*Harris Kenny*
Dear all,
You are kindly invited to the meeting:
CommOps IRC Meeting on 2018-02-26 from 10:30:00 to 12:00:00 US/Eastern
At fedora-meeting-2(a)irc.freenode.net
The meeting will be about:
This meeting is for team members of the Community Operations (CommOps) team. The weekly agenda is mostly comprised of the different tasks detailed on the CommOps wiki page, although it is subject to change depending on time and context of what is going around the Fedora Project.
More information can be found on the [wiki page](https://fedoraproject.org/wiki/CommOps).
Source: https://apps.fedoraproject.org/calendar/meeting/8732/
Dear all,
You are kindly invited to the meeting:
CommOps Hack Session on 2018-02-25 from 17:00:00 to 19:00:00 UTC
At fedora-commops(a)irc.freenode.net
The meeting will be about:
This special meeting is a hack session to work on some ongoing tasks and tickets for the Fedora CommOps team. The meeting format is an audio/video call, where anyone can join to work on tasks and ask for help if needed.
All CommOpsers are welcome to attend, even if it's only for part of the time slot.
More information available at:
[https://fedoraproject.org/wiki/Hack_session](https://fedoraproject.org/wiki…
Source: https://apps.fedoraproject.org/calendar/meeting/8733/
Hey all! The CommOps meeting ended a short while ago.
In today's meeting, we covered:
* GSoC 2018 announcement post (wesleyotugo)
* Fedora Appreciation Week: Tooling (jwf), CommBlog intro (bt0)
* Setting up Grimoire with Elastic's Guard (skamath)
* Repping mentoring advice at Docs FAD next week (jwf)
More details are below. Thanks everyone for taking the time out of your
day to join us, and hope to see you next week. I may be unable to chair
the meeting because of travel, but I will make a best effort to be here.
= = = = =
Meeting ended Mon Feb 19 16:20:08 2018 UTC.
Minutes:
https://meetbot.fedoraproject.org/fedora-meeting-2/2018-02-19/commops.2018-…
Minutes (text):
https://meetbot.fedoraproject.org/fedora-meeting-2/2018-02-19/commops.2018-…
Log:
https://meetbot.fedoraproject.org/fedora-meeting-2/2018-02-19/commops.2018-…
* * * * *
==============================================
#fedora-meeting-2: Fedora CommOps (2018-02-19)
==============================================
Meeting started by jwf at 15:30:09 UTC. The full logs are available at
https://meetbot.fedoraproject.org/fedora-meeting-2/2018-02-19/commops.2018-…
.
Meeting summary
---------------
* Agenda (jwf, 15:30:20)
* LINK:
https://infinote.fedoraproject.org/cgit/infinote/tree/meeting-templates/fed…
(jwf, 15:30:27)
* (1) Roll call / Q&A (jwf, 15:30:27)
* (2) Announcements (jwf, 15:30:27)
* (3) Action items from last meeting (jwf, 15:30:27)
* (4) Tickets (jwf, 15:30:28)
* (5) Open floor (jwf, 15:30:29)
* Roll call / Q&A (jwf, 15:30:44)
* Name; Timezone; Sub-projects/Interest Areas (jwf, 15:30:49)
* ACTION: commops New members, make sure you introduce yourself on the
CommOps mailing list [ https://fedoraproject.org/wiki/CommOps/Join ]
(jwf, 15:30:49)
* Justin W. Flory; UTC-5; CommOps, Diversity Team (jwf, 15:31:09)
* Alberto Rodríguez S.; UTC-5; CommOps, dotNet, Marketing, Infra,
Ambassadors, cats (bt0_, 15:31:16)
* Dennis W. Otugo; UTC+1; CommOps, Infra (wesleyotugo, 15:32:34)
* Announcements (jwf, 15:39:33)
* === "EMEA Ambassadors: 2017 Year in Review" – by edgates++ ===
(jwf, 15:39:38)
* LINK:
https://communityblog.fedoraproject.org/emea-ambassadors-2017-year-review/
(jwf, 15:39:43)
* Quick highlights of the EMEA Ambassadors' activity in 2017. Includes
goals for improved event report coverage and tracking metrics to
measure success. (jwf, 15:39:43)
* Action items from last meeting (jwf, 15:41:25)
* LINK:
https://meetbot.fedoraproject.org/fedora-meeting-2/2018-02-12/commops.2018-…
(jwf, 15:41: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:41:32)
* === [INCOMPLETE] "x3mboy Open new CommOps ticket with expanded idea
on improving communication from public to Ambassadors" === (jwf,
15:41:50)
* ACTION: x3mboy Open new CommOps ticket with expanded idea on
improving communication from public to Ambassadors (jwf, 15:41:50)
* === [IN PROGRESS] "jwf Work on first draft of FAD event report,
share with team for feedback by 2017-02-16" === (jwf, 15:42:00)
* LINK: https://pagure.io/fedora-commops/issue/125#comment-494519
(jwf, 15:42:03)
* ACTION: jwf Work on first draft of FAD event report, share with team
for feedback by 2017-02-23 (jwf, 15:42:07)
* === [COMPLETE] "commops Review Fedora Appreciation Week template to
collect contributor stories, leave any feedback in the Etherpad" ===
(jwf, 15:42:12)
* LINK: https://etherpad.persephone.cloud/p/commops-faw-2018-template
(jwf, 15:42:16)
* Template is ready; need to add template into tooling for Pagure repo
(jwf, 15:42:19)
* === [COMPLETE] "bee2502 jonatoni Start discussion with Fedora Infra
on requirements to host our own Happiness Packet site (inc. Python /
Django, PostgreSQL, etc.)" === (jwf, 15:42:24)
* LINK: https://pagure.io/fedora-infrastructure/issue/6690 (jwf,
15:42:28)
* Idea generally approved; bee2502 and jonatoni to clarify on hardware
needs once we get through the applicant phase of GSoC and Outreachy
(jwf, 15:42:31)
* === [IN PROGRESS] "skamath Finish installing Grimoire on CommOps
cloud instance by 2018-02-19, share link to mailing list when
finished" === (jwf, 15:42:36)
* LINK: http://commops.fedorainfracloud.org/app/kibana (jwf,
15:42:40)
* ACTION: skamath Document log-in instructions to Grimoire on CommOps
cloud instance (jwf, 15:42:44)
* === [COMPLETE] "skamath file an issue in mentored-projects repo for
including perceval project in Outreachy" === (jwf, 15:43:16)
* LINK: https://pagure.io/mentored-projects/issue/25 (jwf, 15:43:21)
* === [COMPLETE] "skamath Follow-up with a2batic and sumantro on GSoC
projects for Outreachy" === (jwf, 15:43:25)
* LINK:
https://screenshots.firefox.com/KcVsMWBWRGi5vS3e/www.outreachy.org
(jwf, 15:43:29)
* Perceval fedmsg plugin and Android projects are officially added as
Summer 2018 Outreachy projects (jwf, 15:43:32)
* Tickets (jwf, 15:44:20)
* LINK: https://pagure.io/fedora-commops/issues?tags=meeting (jwf,
15:44:24)
* === Ticket #137: "New CommBlog article: Fedora accepted into GSoC
2018" === (jwf, 15:44:30)
* LINK: https://pagure.io/fedora-commops/issue/137 (jwf, 15:44:31)
* HELP: Great task for beginner. Need to write an announcement that
Fedora is participating in Google Summer of Code 2018. Past example
is in ticket. (jwf, 15:44:35)
* ACTION: wesleyotugo Write first draft of "Fedora accepted into GSoC
2018" on CommBlog; write to mailing list when ready for review
(final draft due: 2018-02-26) (jwf, 15:49:15)
* === Ticket #110: "Fedora Appreciation Week 2017" === (jwf,
15:49:43)
* LINK: https://pagure.io/fedora-commops/issue/110 (jwf, 15:49:48)
* LINK:
https://screenshots.firefox.com/Gahbf6ED4lAVP9b8/etherpad.persephone.cloud
(jwf, 15:49:59)
* LINK: https://pagure.io/fedora-commops/contributor-stories (jwf,
15:49:59)
* LINK: https://etherpad.persephone.cloud/p/commops-faw-2018-template
(jwf, 15:49:59)
* According to timeline, in February, we create the template for
contributors to submit stories and add the template to repo.
Template was out for review since last meeting; will move forward to
incorporate template into repo (jwf, 15:50:20)
* ACTION: jwf Add FAW template in Etherpad as Pagure issue template in
contributor-stories repo (jwf, 15:50:27)
* Contributor stories CommBlog intro: (1) What they are; (2) Why we're
doing this; (3) How to submit one (jwf, 16:00:21)
* ACTION: bt0 Write first draft of Contributor Stories article for
CommBlog by Monday, Feb. 26 2018 (jwf, 16:00:58)
* === Ticket #114: "Use metrics dashboard to visualize fedmsg data"
=== (jwf, 16:01:18)
* LINK: https://pagure.io/fedora-commops/issue/114 (jwf, 16:01:19)
* LINK:
https://screenshots.firefox.com/Gahbf6ED4lAVP9b8/etherpad.persephone.cloud
(jwf, 16:01:22)
* Revisiting timeline goals; how do we want to document this
information? (jwf, 16:01:25)
* ACTION: skamath Research (possibly implement) Guard to manage
granular permissions between accounts in Kibana by Monday,
2018-02-26 (jwf, 16:06:36)
* Documentation is blocked by understanding how we will manage
accounts; need to look into third-party plugin by Elastic team
called Guard to have advanced permissioning for multiple users in
Kibana; skamath to research this by next Monday's meeting (jwf,
16:07:26)
* === Ticket #133: "Creating summer coding "best practices" docs for
mentors" === (jwf, 16:08:01)
* LINK: https://pagure.io/fedora-commops/issue/133 (jwf, 16:08:06)
* bee2502 mentioned some ideas for advice on supporting mentors in our
intern programs; what other helpful topics are there to include? Do
we want to champion this task at the 2018 Documentation FAD? (jwf,
16:08:13)
* IDEA: Have on-boarding guidelines for selected applicants (jwf,
16:10:14)
* IDEA: Introduce social communication channels for students (jwf,
16:10:20)
* IDEA: Do research + use existing documents from other open source
communities (e.g. MetaBrainz has a private communication channel for
discussions between mentors) (jwf, 16:10:42)
* IDEA: Highlight work of selected applicants on Commblog (jwf,
16:10:56)
* LINK:
http://write.flossmanuals.net/gsoc-mentoring/what-makes-a-good-mentor/
(jwf, 16:13:23)
* LINK:
https://docs.fedoraproject.org/mentored-projects/gsoc/2018/index.html#how-t…
(jwf, 16:13:33)
* skamath linked a helpful guide written by FLOSS Manuals (sponsored
by Google) for mentoring and administering Google Summer of Code.
Instead of reinventing the wheel, point this as a reference and only
document Fedora-specific details in our own mentor docs (jwf,
16:15:27)
* ACTION: jwf Bring #133 as a work task to Docs FAD; pre-prep by
reaching out on Docs list for feedback (?) (jwf, 16:16:15)
* Open floor (jwf, 16:17:40)
Meeting ended at 16:20:08 UTC.
Action Items
------------
* commops New members, make sure you introduce yourself on the CommOps
mailing list [ https://fedoraproject.org/wiki/CommOps/Join ]
* x3mboy Open new CommOps ticket with expanded idea on improving
communication from public to Ambassadors
* jwf Work on first draft of FAD event report, share with team for
feedback by 2017-02-23
* skamath Document log-in instructions to Grimoire on CommOps cloud
instance
* wesleyotugo Write first draft of "Fedora accepted into GSoC 2018" on
CommBlog; write to mailing list when ready for review (final draft
due: 2018-02-26)
* jwf Add FAW template in Etherpad as Pagure issue template in
contributor-stories repo
* bt0 Write first draft of Contributor Stories article for CommBlog by
Monday, Feb. 26 2018
* skamath Research (possibly implement) Guard to manage granular
permissions between accounts in Kibana by Monday, 2018-02-26
* jwf Bring #133 as a work task to Docs FAD; pre-prep by reaching out on
Docs list for feedback (?)
Action Items, by person
-----------------------
* bt0
* bt0 Write first draft of Contributor Stories article for CommBlog by
Monday, Feb. 26 2018
* commops
* commops New members, make sure you introduce yourself on the CommOps
mailing list [ https://fedoraproject.org/wiki/CommOps/Join ]
* jwf
* jwf Work on first draft of FAD event report, share with team for
feedback by 2017-02-23
* jwf Add FAW template in Etherpad as Pagure issue template in
contributor-stories repo
* jwf Bring #133 as a work task to Docs FAD; pre-prep by reaching out
on Docs list for feedback (?)
* skamath
* skamath Document log-in instructions to Grimoire on CommOps cloud
instance
* skamath Research (possibly implement) Guard to manage granular
permissions between accounts in Kibana by Monday, 2018-02-26
* wesleyotugo
* wesleyotugo Write first draft of "Fedora accepted into GSoC 2018" on
CommBlog; write to mailing list when ready for review (final draft
due: 2018-02-26)
* x3mboy
* x3mboy Open new CommOps ticket with expanded idea on improving
communication from public to Ambassadors
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* jwf (185)
* skamath (36)
* zodbot (12)
* wesleyotugo (11)
* bt0_ (9)
* bt0 (8)
* bt0__ (2)
* commops (0)
* x3mboy (0)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
--
Cheers,
Justin W. Flory
jflory7(a)gmail.com
Hi CommOps,
We need help to write a new Community Blog (CommBlog) article by Feb. 26
to announce Fedora was accepted as a participating organization to
Google Summer of Code.
More info on this in this ticket:
https://pagure.io/fedora-commops/issue/137
This is a great task for someone to get started with. There is an
example to reference from a previous year in the Pagure ticket.
If you're interested in helping with this, check out the Pagure ticket
linked above. If you have questions, feel free to ask here and we'd be
happy to help!
--
Cheers,
Justin W. Flory
jflory7(a)gmail.com