Easyfix + WhatCanIDoForFedora

[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

[Justin W. Flory]

On 02/15/2018 01:17 PM, Brian Exelbierd wrote:
>  == 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.)
>   
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.

>  == 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.
>   
+1.

>  = 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.

>  = 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.

>  What do people think?
>   
I'm interested in all the above, but skeptical to whether all pieces are
solvable by CommOps.

-- 
Cheers,
Justin W. Flory
jflory7(a)gmail.com

[Ankur Sinha]

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
> 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.)
>  > 
>  
>  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. 
+1

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
>  > 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.
>  > 
>  
>  +1. 
+1

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

https://fedoraproject.org/wiki/Communicating_and_getting_help

(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. 
+1

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 :)

-- 
Thanks,
Regards,

Ankur Sinha "FranciscoD"

https://fedoraproject.org/wiki/User:Ankursinha

[Brian (bex) Exelbierd]

On Tue, Feb 27, 2018 at 9:18 PM Ankur Sinha <sanjay.ankur(a)gmail.com&gt; wrote:
>  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
> 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.)
>  > >
>  >
>  > 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.
>
>  +1
>
>  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. 
I think encouraging a single tag is great, but allowing projects to do
what makes sense is also good.  I believe, but haven't checked, that
hte current page allows for any arbitrary tag.  Lets put in a sane
default, but not break existing projects.

>  >
>  > > == 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.
>  > >
>  >
>  > +1.
>
>  +1
>
>  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. 
I think a click to email is great.  A click to chat too.  Hubs is not
going into production as the project is no longer under development,
aiui.  Therefore we should consider what easy efforts we could take.

>  >
>  > > = 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
>
>  https://fedoraproject.org/wiki/Communicating_and_getting_help
>
>  (I just noticed that telegram, matrix etc. are not mentioned on this
>  page yet :o ) 
I think we should consider using an email link, a pagure issue link,
and an IRC link.  The Telegram channels are not official and it causes
some consternation if we treat them as such.  Matrix is a good option
for IRC connections.

>  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? 
How would you design the page that helps a person find the human in
those 40+ methods?

>  > > = 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.
>
>  +1
>
>  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?) 
I'd rather see that effort go into a twitter or social media feed.
Most people reading our Planet probably don't need easyfix guidance.
This isn't saying we should exclude them, but newbies are, imho, more
likely to see our social media traffic than one post buried in the
planet.

>  >
>  > > 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 :) 
Could you help mentor a student in the next round of projects?

regards,

bex

>  --
>  Thanks,
>  Regards,
>
>  Ankur Sinha "FranciscoD"
>
>  https://fedoraproject.org/wiki/User:Ankursinha
>  _______________________________________________
>  Fedora Community Operations (CommOps) mailing list -- commops(a)lists.fedoraproject.org
>  To unsubscribe send an email to commops-leave(a)lists.fedoraproject.org 


-- 
Brian (bex) Exelbierd | bexelbie(a)redhat.com | bex(a)pobox.com
Fedora Community Action & Impact Coordinator
@bexelbie | http://www.winglemeyer.org

[Mindshare] Re: Re: Easyfix + WhatCanIDoForFedora

[Ankur Sinha]

On Thu, Oct 04, 2018 10:39:35 +0200, Brian (bex) Exelbierd wrote:
>  On Tue, Feb 27, 2018 at 9:18 PM Ankur Sinha
> <sanjay.ankur(a)gmail.com&gt; wrote:
>  <snip>
>  >
>  > 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.
>  
>  I think encouraging a single tag is great, but allowing projects to do
>  what makes sense is also good.  I believe, but haven't checked, that
>  hte current page allows for any arbitrary tag.  Lets put in a sane
>  default, but not break existing projects. 
+1 

I had a look at the script recently when I submitted a PR or two, but
I've forgotten how it uses tags. I think it allows any tags for
Github/Pagure/Gitlab as long as they are listed on the wiki page, but
for bugs from Bugzilla, one must use "EasyFix".

>  <snip>
>  >
>  > 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.
>  
>  I think a click to email is great.  A click to chat too.  Hubs is not
>  going into production as the project is no longer under development,
>  aiui.  Therefore we should consider what easy efforts we could take. 
Ah, that's sad to hear. I was really looking forward to hubs :(

>  <snip>
>  > 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
>  >
>  > https://fedoraproject.org/wiki/Communicating_and_getting_help
>  >
>  > (I just noticed that telegram, matrix etc. are not mentioned on this
>  > page yet :o )
>  
>  I think we should consider using an email link, a pagure issue link,
>  and an IRC link.  The Telegram channels are not official and it causes
>  some consternation if we treat them as such.  Matrix is a good option
>  for IRC connections. 
I'll file a ticket on our pagure. This shouldn't be too hard to add to
asknot-ng.


>  
>  >
>  > 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?
>  
>  How would you design the page that helps a person find the human in
>  those 40+ methods? 
We could simply link to "communicating and getting help" to start with?
It lists most mailing lists and IRC channels.

I see that the footer in getfedora.org already does this as "Get
help"---should we rephrase that to "Get in touch" or something more
general that doesn't have a "troubleshooting" connotation?

The new docs website does not use a similar footer yet, and neither do
the wikis or the web apps I've used recently.


>  <snip>
>  
>  I'd rather see that effort go into a twitter or social media feed.
>  Most people reading our Planet probably don't need easyfix guidance.
>  This isn't saying we should exclude them, but newbies are, imho, more
>  likely to see our social media traffic than one post buried in the
>  planet. 
Now that I know how easyfix works internally, it doesn't lend itself
to publishing automated updates on either RSS or social media. It does
not update incrementally like the planet does (venus). It simply fetches
all tickets each time and puts the info through a template to generate
the HTML. So it isn't aware of a new ticket being added. We'll have to
re-design the backend to support such updates.

>  <snip>
>  
>  Could you help mentor a student in the next round of projects? 
Sure, but I wouldn't want to be the single point of contact. I'm trying
to squeeze out whatever free cycles I can to work on NeuroFedora
nowadays. NeuroFedora + join + classroom is all the free time away from
my research work that I can manage at the moment :(

-- 
Thanks,
Regards,

Ankur Sinha "FranciscoD"

https://fedoraproject.org/wiki/User:Ankursinha
Time zone: Europe/London

[Fedora-join] Re: Easyfix + WhatCanIDoForFedora

[Brian (bex) Exelbierd]

On Thu, Oct 4, 2018 at 10:04 AM Justin W. Flory <jflory7(a)gmail.com&gt; 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
> 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.)
>  >
>
>  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.
>
>  > == 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.
>  >
>
>  +1.
>
>  > = 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. 
We should get this moved into an issue in the mentored projects repo.
This needs to be written up and could be either GSoC or Outreachy.

Do you have time to do this?

>  > = 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.
>
>  > What do people think?
>  >
>
>  I'm interested in all the above, but skeptical to whether all pieces are
>  solvable by CommOps. 
Agreed.  We probably need two mentors.  A "vision" and a "code"
mentor.  They could be one person, easier if two.

regards,

bex

>  --
>  Cheers,
>  Justin W. Flory
>  jflory7(a)gmail.com
>
>  _______________________________________________
>  fedora-join mailing list -- fedora-join(a)lists.fedoraproject.org
>  To unsubscribe send an email to fedora-join-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail]... 


-- 
Brian (bex) Exelbierd | bexelbie(a)redhat.com | bex(a)pobox.com
Fedora Community Action & Impact Coordinator
@bexelbie | http://www.winglemeyer.org