Easyfix + WhatCanIDoForFedora
by Brian Exelbierd
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
5 years, 1 month
[help wanted] New Community Blog post: meet the interns!
by Justin W. Flory
Hi all,
I wanted to put a call for help on writing a new Community Blog article
that introduces the Google Summer of Code interns working on Fedora this
summer and a bit about them and their projects.
Bee suggested this idea on Pagure in the ticket linked below. She
suggested some sample interview questions we could use to ask the
interns working across different projects. We could compile them
together into a short post that highlights the students and some of the
work they are doing.
https://pagure.io/fedora-commops/issue/163
The work needed for this ticket would be something like:
1) Finalize a set of interview questions
2) Get a list of emails for Fedora GSoC students
3) Send interview questions
4) Compile answers into a Q&A-style post on the CommBlog
Is anyone interested in helping with this? If you want to help out with
this, please reply back here on the mailing list or drop a comment in
the Pagure ticket. If you are not sure with a step (like finding out the
emails for interns), we are happy to help with that. :-)
--
Cheers,
Justin W. Flory
jflory7(a)gmail.com
5 years, 5 months
Intro :)
by James Thornber
Hello all,
I'd like to join your team, as it seems really interesting! :)
Not sure what to say, so I'm going to use those handy notes on the website:
-
Why are you interested in contributing to Fedora?
I like the fact that Fedora ships cutting-edge but very stable products,
and it seems like a really nice community. I've only recently been
seriously interested in linux, and I've built my own PC and only running
Fedora28 workstation on it. I've been using HP-UX, and more recently RHEL
and CentOS at work, so my home pc is my play-pit to be able to keep ahead
of new linux packages, and try things out that I don't have time to do at
work really!
-
Why are you interested in contributing to CommOps?
To me it's about people; it's the people that make a community and
that's a huge part in what I think helps make Fedora successful. I'd like
to help to be able to shine a light on interesting packages/technology
that's in the dev-pipeline for upcoming releases, or showing people how
others use Fedora. I think also because I can't code to save my life then
I see CommOps as being a better fit for me, and my skills i.e. i'm much
more of a people person :)
-
If you’re involved with other things in Fedora, what are/were you
working on?
Nothing, so far! :)
-
Do you have any experience in open source or online communities? If so,
what?
I'm an admin for a couple of genealogical DNA groups, does that count?
-
What parts of CommOps were interesting to you?
Helping to support different teams, communicating relevant info to a
wider audience, meeting interesting people and helping them to share a
story or information, and aligning this to technology that supports the
community as a whole. I'm quite happy planning, and organising things too
:)
-
Do you have any questions for us? How can we help *you* get started?
I can see that you have some tasks in pageur without an assignee, if you
would like me to get involved in one of those tasks then I'm more than
happy to - just email me; if you feel I'd be better suited in a different
team then please feel free to signpost me :)
Thanks :)
5 years, 5 months
[Minutes] [2018-06-18] CommOps FLOCK proposal, podcast and FAW
by Alberto Rodriguez Sanchez
Hi team,
We have a nice and quiet meeting today, here the minutes:
Minutes: https://meetbot.fedoraproject.org/fedora-commops/2018-06-18/co
mmops.2018-06-18-14.44.html
Minutes (text): https://meetbot.fedoraproject.org/fedora-commops/2018-0
6-18/commops.2018-06-18-14.44.txt
Log: https://meetbot.fedoraproject.org/fedora-commops/2018-06-18/commop
s.2018-06-18-14.44.log.html
============================================
#fedora-commops: Fedora CommOps (2018-06-18)
============================================
Meeting started by bt0 at 14:44:51 UTC. The full logs are available at
https://meetbot.fedoraproject.org/fedora-commops/2018-06-18/commops.201
8-06-18-14.44.log.html
.
Meeting summary
---------------
* Agenda (bt0, 14:45:29)
* LINK:
https://infinote.fedoraproject.org/cgit/infinote/tree/meeting-templ
ates/fedora-commops-meeting-next
(bt0, 14:45:43)
* (1) Roll call / Q&A (bt0, 14:45:43)
* (2) Announcements (bt0, 14:45:43)
* (3) Action items from last meeting (bt0, 14:45:44)
* (4) Tickets (bt0, 14:45:46)
* (5) Open floor (bt0, 14:45:48)
* Roll call / Q&A (bt0, 14:46:02)
* Name; Timezone; Sub-projects/Interest Areas (bt0, 14:46:31)
* ACTION: commops New members, make sure you introduce yourself on
the
CommOps mailing list [ https://fedoraproject.org/wiki/CommOps/Join
]
(bt0, 14:46:47)
* Alberto Rodriguez S; UTC-5;CommOps (Metrics, Community engagement),
DotNet (Testing), Infrastructure(Apprentice), Marketing (Member),
Ambassadors (Member), Cats (lover) (bt0, 14:47:45)
* Ankur Sinha, UTC +1: Packaging, classrooms, join (FranciscoD,
14:55:36)
* Announcements (bt0, 14:57:39)
* === "Fedora Classroom Session: Fedora QA 101/102" === (bt0,
14:58:32)
* LINK: https://fedoramagazine.org/classroom-session-qa-2018-06-19/
(bt0, 14:58:42)
* === "Happiness Packets and Fedora GSoC 2018" === (bt0, 14:59:52)
* LINK:
https://communityblog.fedoraproject.org/happiness-packets-fedora-gs
oc-2018
(bt0, 15:00:04)
* Action items from last meeting (bt0, 15:04:45)
* LINK:
https://meetbot.fedoraproject.org/teams/commops/commops.2018-06-11-
14.41.html
(bt0, 15:05:00)
* 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. (bt0,
15:05:14)
* === [In Progress] "bt0 Split up onboarding guidelines ticket (#117)
into smaller sub-tickets for different steps of work to produce the
final deliverable" === (bt0, 15:05:40)
* ACTION: "bt0 Split up onboarding guidelines ticket (#117) into
smaller sub-tickets for different steps of work to produce the
final
deliverable" (bt0, 15:06:02)
* === [COMPLETED] A session proposal was submitted for the FLOCK ===
(bt0, 15:11:38)
* LINK: https://pagure.io/fedora-commops/issue/160#comment-517032
(bt0, 15:11:44)
* Tickets (bt0, 15:13:47)
* LINK:
https://pagure.io/fedora-commops/issues?status=Open&tags=next+meeti
ng
(bt0, 15:13:57)
* Ticket #110: "Fedora Appreciation Week 2017" (bt0, 15:14:48)
* LINK: https://pagure.io/fedora-commops/issue/1100 (bt0, 15:14:59)
* LINK:
https://screenshots.firefox.com/ZTV0ZlHbq16vevZt/etherpad.persephon
e.cloud
(bt0, 15:15:12)
* LINK:
https://communityblog.fedoraproject.org/?p=5376&preview=1&_ppp=dbe0
f8ee96
(bt0, 15:15:30)
* IDEA: invite the podcast audience to write their own CS (bt0,
15:26:07)
* Ticket #155: "Fedora Podcast Episode" (bt0, 15:31:08)
* LINK: https://pagure.io/fedora-commops/issue/1555 (bt0, 15:31:16)
* ACTION: bt0 will add one or two lines to the script about invite
the
podcast audience to write their own CS (bt0, 15:33:01)
* Ticket #160: "Plan a CommOps session for Flock 2018" (bt0, 15:42:56)
* LINK: https://pagure.io/fedora-commops/issue/1600 (bt0, 15:43:14)
* LINK: https://pagure.io/fedora-commops/issue/160#comment-517032
(bt0, 15:43:42)
* LINK: https://pagure.io/flock/issue/511 (bt0, 15:45:58)
* Open floor (bt0, 15:52:26)
* LINK: https://pagure.io/fedora-commops/issue/1611 (bt0, 15:54:33)
* Selecting new CommOps Mindshare representative for F29-F30 (bt0,
15:54:55)
Meeting ended at 16:00:27 UTC.
Action Items
------------
* commops New members, make sure you introduce yourself on the CommOps
mailing list [ https://fedoraproject.org/wiki/CommOps/Join ]
* "bt0 Split up onboarding guidelines ticket (#117) into smaller
sub-tickets for different steps of work to produce the final
deliverable"
* bt0 will add one or two lines to the script about invite the podcast
audience to write their own CS
Action Items, by person
-----------------------
* bt0
* "bt0 Split up onboarding guidelines ticket (#117) into smaller
sub-tickets for different steps of work to produce the final
deliverable"
* bt0 will add one or two lines to the script about invite the
podcast
audience to write their own CS
* commops
* commops New members, make sure you introduce yourself on the
CommOps
mailing list [ https://fedoraproject.org/wiki/CommOps/Join ]
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* bt0 (93)
* fcommops-tg (19)
* zodbot (12)
* FranciscoD (2)
* wesleyotugo (1)
* bee2502 (0)
* commops (0)
5 years, 5 months
