On Sun, Feb 18, 2018 20:30:38 -0500, Justin W. Flory wrote:
On 02/15/2018 01:17 PM, Brian Exelbierd wrote:
> == Changing metadata
> Modify the table that drives fedoraproject.org/easyfix
that is located at
> The table would now include two additional columns (optional)
> Col 1 = existing reference to the issue tracker. We should consider adding
> Col 2 = existing point of contact
> Col 3 = category of task (documentation, infrastructure, programming-Haskell,
> Col 4 = SIG/WG/etc. this project is related too (Design, Council, KDE, etc.)
I like this page structure. I see it as more engaging to the people
reading the page too. Given some time to research it, I think this is
something that we could work on in CommOps.
From what I see, the current system provides the option to use a tag
other than "easyfix" to mark tickets as such, but we can standardise
this and ask everyone to stick to a case insensitive "easyfix" to make
it somewhat simpler.
> == Changing fedoraproject.org/easyfix
> Today we show only two categories: Issues from Pagure/Github and
> 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.
Recently, I was looking at the Github docs, and they have a very nice
"contact a human" link on all their pages. Can we add this to the
easyfix page somehow? I think Hubs is to be moved to prod soon, so this
may not be needed. We can use Col 3 above to link to the SIG's landing
page on Hubs which, as I remember, will have the IRC/ML status in the
sidebars or somewhere.
> = 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.
I've wanted this functionality for a long time but needs dedicated
development time full-time. If not, then an active effort is needed to
create a roadmap with easyfixes rolled in to attract contributors.
In retrospect, all of this sounds like a good GSoC proposal. Not sure if
it's too late to expand on the idea and find a mentor for it.
I'd love a "contact a human" link on WCIDFF too. It could either take
folks to the related SIG's landing page on hubs, or to their IRC channel
using webchat/matrix/whatever. Even our "Communicating and getting help"
page would be a start, although, there's quite a bit of info there and
people new to the community may find it confusing
(I just noticed that telegram, matrix etc. are not mentioned on this
page yet :o )
Ideally, I'd like a "contact a human" link on all our footers. We have
~40 channels and even more mailing lists. There is no shortage of
communication methods for everything Fedora related, so would be a bad
idea to help folks get to them?
> = Marketing/Promotion
> The categories give us the opportunity to promote our easyfixes as a
> great way to join or contribute in a targeted manner.
+1. Super helpful for writing even outside of the Fedora community or
for anyone that wants to highlight a call to action to participate.
Thinking aloud here:
- would an RSS feed of the easyfix page be useful?
- a bot that posts a daily update of the easyfix issues to the planet
maybe? (and so this post will also go out on the fedobot twitter
handle I think?)
> What do people think?
I'm interested in all the above, but skeptical to whether all pieces are
solvable by CommOps.
I'm interested in it too, and can help with some of the bits I'm sure.
I don't think -join is as active as I'd like it to be, and this is
partly because we haven't reached a critical mass where it becomes
self-sustaining yet. So, I'm open to any ways at all that will encourage
folks to talk to us (whether new folks or seasoned contributors).
Thanks for bringing this up :)
Ankur Sinha "FranciscoD"