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:
== 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.
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.
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?
In today's APAC Ambassadors meeting we were talking about how tickets were
not moving through the system despite ambassadors ready to do events.
We've tried a few things in the past, but it has been super hard to get
real-time meetings working or to get ticket voting to happen in all cases.
Questions seems to block events from being approved, even when the question
is about details not related to the approvals.
You can read the conversation here:
The end result of this was to use APAC as the leading edge of the Mindshare
movement. The proposal is to ask Mindshare to start working with APAC
events/requests immediately. This provides the following benefits:
1. APAC gets a group of people to help move tickets through a process
and it unblocks ambassadors to do what they do best -- FANTASTIC FEDORA
2. Mindshare gets a queue of real requests to apply the strategy they
are working on too. This will expose gaps and holes.
3. It gives Mindshare the ability to generate their procedures as they
work on translating their proposal into procedures using real issues.
The request in this email is to find out if both groups are willing to do
Mindshare can review this in their next meeting on Monday. This is opened
in their ticket queue as: https://pagure.io/mindshare/issue/26
Because APAC ambassadors is a large group across many timezones and doesn't
meet as frequently, let's use a modified lazy consensus model. Let's get
some +1s in the Mindshare ticket to indicate sentiment and address any -1s
to identify challenges and respond to them. I strongly encourage anyone
who has concerns to raise them and to note what could be done to solve
their concern as well solve the overall issues.
Please continue the conversation in ticket
bex on behalf of the APAC Ambassadors Meeting
Brian (bex) Exelbierd | bexelbie(a)redhat.com | bex(a)pobox.com
Fedora Community Action & Impact Coordinator
@bexelbie | http://www.winglemeyer.org
Since we discussed this at our FAD and were blocked by documentation
then, I deleted most of the duplicate content in the wiki and pointed to
the documentation page as the canon resource for information.
However, the content on the wiki page is _also_ a duplicate of what is
already in the docs. My question is, do we even need a wiki page at all?
Do we want to put a permanent wiki redirect on the Mindshare page to
redirect to the documentation?
I wasn't sure if it was premature to put the redirect in place yet, so I
wanted to ask you all here and see what you thought.
Justin W. Flory
I wanted to take this chance to welcome Sumantro to the Mindshare
Committee as the newly elected member from the community! Welcome
Brian or Robert, could one of you please sponsor Sumantro into the FAS
As I understand, he is replacing Nick's seat; however, Nick is still
serving as the Ambassadors representative because of his role with FAmA.
I'm following up on jkurik's ticket to update the membership list of the
Committee. I have updated the wiki page and Pagure group membership.
Only Brian and Robert have permissions for the FAS group, but I don't
think this is significant since the FAS group doesn't mean any real
privileges as of now.
On the topic of on-boarding and off-boarding, I filed a new ticket so we
can try to improve this process. Any feedback is welcome, or an
improvement to the short list I've started.
Welcome again, Sumantro. :-) Looking forward to having you here.
Justin W. Flory
The elections for Mindshare - May 2018  have concluded, and the
results are shown below.
Mindshare committee is electing 1 seat this time.
A total of 107 ballots were cast, meaning a candidate could accumulate
up to 321 votes (107 * 3).
The results for the elections are as follows:
# votes | name
205 | Sumantro Mukherjee (sumantrom)
188 | Nick Bebout (nb)
114 | Itamar Peixoto (itamarjp)
Congratulations to the winning candidate, and thank you all candidates
for running this elections!
JBoss EAP Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic