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, 6 months
Self-Introduction: Papa Charlie
by Papa Charlie
Hello All,
I'm Papa Charlie, a big fan of Fedora and open source. I have been using Fedora on my desktop since the Redhat days. I wanted to mirror my desktop screen on my TV and noticed the feature was missing in Fedora. I looked for someplace to make a feature request but could not really find one. In the process I learned the best way to have a feature implemented is to get involved. I have a rudimentary grasp of C++, PHP, Java and web programming(Javascript). I'm willing to contribute in any way possible to the Fedora project and to improve my coding skills. Thank you.
Regards,
Papa Charlie
5 years, 10 months
Introduction
by Alexander Marek
To whom this may concern,
My name is Alex and I'm studying Cybersecurity, with plans to go into the
IT/Information Security field. Recently I've been studying for my Red Hat
Certified System Administrator certification and hope I can bring my new
skillset to help benefit my favourite distribution. I plan to pass my
Offensive Security Certified Professional certification by the end of
August. Alongside this, I'm currently taking college courses part
time.Hopefully I can be useful, and I'm looking forward to seeing what the
Fedora Project has in store!
Regards,
Alexander Marek
5 years, 10 months
Introduction - Anna
by Anna Philips
Hello everyone!
I'm Anna, I go by the username algogator on IRC. I'm the GSoC intern working on the fedora happiness packets project. Huge Python fan, so I'm excited to be working with Django/Python this summer.
This isn't my first rodeo, I contributed to other open source projects (been a student ambassador for Mozilla), but I'm new to Fedora (Ubuntu has been my default OS for the past couple of years).
Looking forward to working with y'all this summer :)
Anna
5 years, 10 months
Fwd: Flock CFP - Final Deadline 15 July 2018
by Justin W. Flory
In case you missed it!
-------- Forwarded Message --------
Subject: Flock CFP - Final Deadline 15 July 2018
Date: Tue, 29 May 2018 17:40:49 +0200
From: Brian (bex) Exelbierd <bexelbie(a)redhat.com>
Reply-To: users(a)lists.fedoraproject.org
To: announce(a)lists.fedoraproject.org
Call for Papers for Flock to Fedora 2018
Flock is the Fedora Project's annual contributor-focused conference. It
alternates between European and North American locations, and this year
will be in Dresden, Germany from August 8-11.
What will we do at Flock?
* Communicate the Fedora Strategy. Everyone in Fedora should understand
and feel well-aligned with the project's goals, both long-term and
tactical. We should all understand the messaging we're using to attract
new users and contributors.
* Plan the Next Strategy. This strategy doesn't come from the top down,
or from thin air, and it's not dictated by our sponsors. It comes from
the community. Because we're so big and distributed, Flock can't be the
only place where we get new ideas, but it is a summit where we present,
learn about, and discuss them.
* Build Community Connections and Engagement. We do amazing work as a
global project, but there's no substitute for direct human interaction.
Flock helps tie us together. In-person discussion, collaboration, and
fun social events help us function better on IRC and mailing lists
throughout the year.
Details about how to submit and what kinds of talks can be submitted can
be found at https://flocktofedora.org/#cfp <https://flocktofedora.org/#cfp>
Talks will be reviewed and accepted in three rounds. The round due
dates are:
Round 1 selection starts on: 15 June 2018
Round 2 selection starts on: 2 July 2018
Final selection starts on: 15 July 2018 (absolute last day for CFP
submission)
Talks not selected in an earlier round, continue to be considered in
future rounds. Submissions must be complete by 15 July 2018.
regards,
bex
--
Brian (bex) Exelbierd | bexelbie(a)redhat.com <mailto:bexelbie@redhat.com>
| bex(a)pobox.com <mailto:bex@pobox.com>
Fedora Community Action & Impact Coordinator
@bexelbie | http://www.winglemeyer.org
5 years, 11 months
Fwd: Migrating fedmsg to AMQP: a proposal
by Justin W. Flory
Exciting changes coming for fedmsg in Fedora Infrastructure world. If
you want a technical deep dive into how events and topics will be done
in the future.
-------- Forwarded Message --------
Subject: Migrating fedmsg to AMQP: a proposal
Date: Thu, 24 May 2018 18:16:56 +0200
From: Aurelien Bompard <abompard(a)fedoraproject.org>
Reply-To: Fedora Infrastructure <infrastructure(a)lists.fedoraproject.org>
To: Fedora Infrastructure <infrastructure(a)lists.fedoraproject.org>
Hey folks!
Jeremy and I have been working on a proposal to migrate fedmsg from our
current brokerless architecture to a broker-based architecture.
The overview and reasons for the migration are described on this page:
https://fedmsg-migration-tools.readthedocs.io/en/latest/migration/overvie...
Head there if you want the details. The plan has the following requirements:
* No flag day.
* Don't disrupt any services or applications.
* Don't break any services outside of Fedora's infrastructure relying on
these messages.
The first step is to deploy a broker in Fedora to use. In order to avoid
a flag day, bridges from AMQP to ZeroMQ and ZeroMQ to AMQP have been
implemented and will be deployed.
In order to validate that the bridges are functioning, a small service
will be run during the transition period that connects to fedmsg and to
the AMQP queues to compare messages.
After the bridges are running, applications are free to migrate. There
are several options when migrating and each has advantages and
disadvantages.
We have written a new library called fedora-messaging that has the
following features:
* A method to define message schemas and offer automatic validation of
messages using those schemas.
* Boilerplate for typical publishers and consumers.
Head over to the document for a demo!
What do you think of this proposal? Any blind spots?
Thanks!
Aurélien
5 years, 11 months
[Minutes] [2018-05-28] Fedora Appreciation Week, Podcast and more
by Alberto Rodriguez Sanchez
Hello team,
In today's meeting, we spent a lot of time focusing on the Fedora
Appreciation Week and the podcast script, look the logs here:
Minutes: https://meetbot.fedoraproject.org/fedora-commops/2018-05-28/co
mmops.2018-05-28-14.32.html
Minutes (text): https://meetbot.fedoraproject.org/fedora-commops/2018-0
5-28/commops.2018-05-28-14.32.txt
Log: https://meetbot.fedoraproject.org/fedora-commops/2018-05-28/commop
s.2018-05-28-14.32.log.html
============================================
#fedora-commops: Fedora CommOps (2018-05-28)
============================================
Meeting started by bt0 at 14:32:37 UTC. The full logs are available at
https://meetbot.fedoraproject.org/fedora-commops/2018-05-28/commops.201
8-05-28-14.32.log.html
.
Meeting summary
---------------
* Agenda (bt0, 14:33:17)
* LINK:
https://infinote.fedoraproject.org/cgit/infinote/tree/meeting-templ
ates/fedora-commops-meeting-next
(bt0, 14:33:17)
* (1) Roll call / Q&A (bt0, 14:33:17)
* (2) Announcements (bt0, 14:33:17)
* (3) Action items from last meeting (bt0, 14:33:17)
* (4) Tickets (bt0, 14:33:19)
* (5) Open floor (bt0, 14:33:21)
* Roll call / Q&A (bt0, 14:33:38)
* Name; Timezone; Sub-projects/Interest Areas (bt0, 14:33:53)
* ACTION: commops New members, make sure you introduce yourself on
the
CommOps mailing list [ https://fedoraproject.org/wiki/CommOps/Join
]
(bt0, 14:33:53)
* Justin W. Flory; UTC-6 (as of now!); CommOps, Diversity & Inclusion
Team, Ambassadors (jwf, 14:37:59)
* Announcements (bt0, 14:49:56)
* CommOps + fedmsg poster at PyCon US earlier this month (jwf,
14:51:36)
* LINK: https://twitter.com/jflory7/status/9956841809976893444 (jwf
,
14:51:38)
* === "Heroes of Fedora (HoF) – F28 Final" === (bt0, 14:53:00)
* LINK:
https://communityblog.fedoraproject.org/heroes-fedora-hof-f28-final
/
(bt0, 14:53:01)
* === "Set up zsh on your Fedora system" === (bt0, 14:53:55)
* LINK: https://fedoramagazine.org/set-zsh-fedora-systemm (bt0,
14:53:56)
* === "May 2018 Elections: Nomination & Campaign period is open" ===
(bt0, 14:55:27)
* LINK:
https://fedoraproject.org/wiki/Development/SteeringCommittee/Nomina
tions
(bt0, 14:55:27)
* LINK: https://fedoraproject.org/wiki/Council/Nominationss (bt0,
14:55:27)
* LINK: https://fedoraproject.org/wiki/Mindshare/Nominationss (bt0,
14:55:27)
* Action items from last meeting (bt0, 15:00:00)
* LINK:
https://meetbot.fedoraproject.org/fedora-commops/2018-05-21/commops
.2018-05-21-14.32.html
(bt0, 15:00:24)
* 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:00:58)
* === [COMPLETED] "bt0 will send a email asking for feedback about
the
podcast commops script" === (bt0, 15:01:34)
* === [COMPLETED] "bt0 will forward the fedora app email to some
mailing list with high traffic" === (bt0, 15:02:13)
* === [IN PROGRESS] "jwf Split up onboarding guidelines ticket (#117)
into smaller sub-tickets for different steps of work to produce the
final deliverable" === (bt0, 15:03:03)
* ACTION: "jwf Split up onboarding guidelines ticket (#117) into
smaller sub-tickets for different steps of work to produce the
final
deliverable" (bt0, 15:04:15)
* Tickets (bt0, 15:06:13)
* LINK:
https://pagure.io/fedora-commops/issues?status=Open&tags=next+meeti
ng
(bt0, 15:06:31)
* Ticket #110: "Fedora Appreciation Week 2017" (bt0, 15:08:34)
* LINK: https://pagure.io/fedora-commops/issue/1100 (bt0, 15:08:34)
* LINK:
https://screenshots.firefox.com/NDyEhhKzQJ4WpXr4/etherpad.persephon
e.cloud
(bt0, 15:08:35)
* LINK:
https://communityblog.fedoraproject.org/?p=5376&preview=1&_ppp=dbe0
f8ee96
(bt0, 15:08:35)
* LINK:
https://screenshots.firefox.com/ZTV0ZlHbq16vevZt/etherpad.persephon
e.cloud
(jwf, 15:10:16)
* LINK: http://209.97.140.39:8000// (bt0, 15:10:19)
* LINK:
https://blog.annaphilips.com/google-summer-of-code-2018-with-fedora
/
(jwf, 15:13:17)
* ACTION: jwf Complete a final draft announcement of Fedora
Appreciation Week 2018 on the Community Blog by Monday, 2018 June
18
(jwf, 15:31:41)
* ACTION: bee2502 bt0 jonatoni x3mboy jwf Submit one contributor
story
to the stories repo (and if you're comfortable, keep it public so
we
can use them as examples for other Fedorans who may not know where
to begin writing one of their own too!) by Monday, 2018 June 11
(jwf, 15:32:57)
* Ticket #117: "How to create on-boarding guidelines for your team"
(bt0, 15:37:53)
* LINK: https://pagure.io/fedora-commops/issue/1177 (bt0, 15:38:11)
* the ticket #117 will be discussed in more detail the next week
(bt0, 15:41:11)
* Ticket #155: "Fedora Podcast Episode" (bt0, 15:41:14)
* LINK: https://pagure.io/fedora-commops/issue/1555 (bt0, 15:41:50)
* ACTION: jwf Review the CommOps podcast script by Monday, June 4
2018
(jwf, 15:47:00)
* Open floor (bt0, 15:50:31)
Meeting ended at 15:56:50 UTC.
Action Items
------------
* commops New members, make sure you introduce yourself on the CommOps
mailing list [ https://fedoraproject.org/wiki/CommOps/Join ]
* "jwf Split up onboarding guidelines ticket (#117) into smaller
sub-tickets for different steps of work to produce the final
deliverable"
* jwf Complete a final draft announcement of Fedora Appreciation Week
2018 on the Community Blog by Monday, 2018 June 18
* bee2502 bt0 jonatoni x3mboy jwf Submit one contributor story to the
stories repo (and if you're comfortable, keep it public so we can use
them as examples for other Fedorans who may not know where to begin
writing one of their own too!) by Monday, 2018 June 11
* jwf Review the CommOps podcast script by Monday, June 4 2018
Action Items, by person
-----------------------
* bee2502
* bee2502 bt0 jonatoni x3mboy jwf Submit one contributor story to the
stories repo (and if you're comfortable, keep it public so we can
use them as examples for other Fedorans who may not know where to
begin writing one of their own too!) by Monday, 2018 June 11
* bt0
* bee2502 bt0 jonatoni x3mboy jwf Submit one contributor story to the
stories repo (and if you're comfortable, keep it public so we can
use them as examples for other Fedorans who may not know where to
begin writing one of their own too!) by Monday, 2018 June 11
* commops
* commops New members, make sure you introduce yourself on the
CommOps
mailing list [ https://fedoraproject.org/wiki/CommOps/Join ]
* jonatoni
* bee2502 bt0 jonatoni x3mboy jwf Submit one contributor story to the
stories repo (and if you're comfortable, keep it public so we can
use them as examples for other Fedorans who may not know where to
begin writing one of their own too!) by Monday, 2018 June 11
* jwf
* "jwf Split up onboarding guidelines ticket (#117) into smaller
sub-tickets for different steps of work to produce the final
deliverable"
* jwf Complete a final draft announcement of Fedora Appreciation Week
2018 on the Community Blog by Monday, 2018 June 18
* bee2502 bt0 jonatoni x3mboy jwf Submit one contributor story to the
stories repo (and if you're comfortable, keep it public so we can
use them as examples for other Fedorans who may not know where to
begin writing one of their own too!) by Monday, 2018 June 11
* jwf Review the CommOps podcast script by Monday, June 4 2018
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* bt0 (106)
* jwf (98)
* zodbot (23)
* fcommops-tg (20)
* jonatoni (7)
* x3mboy_ (6)
* bee2502 (0)
* commops (0)
5 years, 11 months
Asking for feedback - Fedora App UI
by Alberto Rodriguez Sanchez
Hello Everyone,
Let me introduce to Abhishek Sharma , he is one of the Google Summer ofCode students this year for the Fedora Project and I'm helping him to
ask for some valuable feedback about a new user interface for the Fedora App.
This interface is accessible here:
https://www.quant-ux.com/test.html?h=a2aa10albzVO4GPTETM7K8maNo3aObl9zC
rhZx3lcvu7ylZRY5xY4eQ98lPy
Any comment is welcome :) and please CC Abhishek <guywhodesigns(a)gmail.c
om>
Regards,
--
Alberto Rodriguez Sanchez <bt0dotninja(a)fedoraproject.org>
5 years, 11 months
