#55 Write commblog explaining how easyfix works
Closed: Invalid 6 days ago by ankursinha. Opened 3 years ago by ankursinha.

Based on our findings, we write a detailed commblog post on how easyfix works, and possibly discuss ideas on how it can be improved.


Metadata Update from @ankursinha:
- Issue marked as depending on: #54

3 years ago

I think we have enough information on how easyfix works. So we can now work on this, @dhanesh95

The post would contain:

  • what is easy fix
  • how to set it up for projects on pagure/github/gitlab
  • how to choose what tickets to label as easyfix
  • how to follow up on these tickets
  • a request for feedback on how this can be improved (another survey?)

Anything else?

I think we have enough information on how easyfix works. So we can now work on this, @dhanesh95
The post would contain:

what is easy fix
how to set it up for projects on pagure/github/gitlab
how to choose what tickets to label as easyfix
how to follow up on these tickets
a request for feedback on how this can be improved (another survey?)

The information required to work on this post can be found in this comment on ticket #54.

Anything else?

I think that's pretty much it. The request for feedback can give us more ideas later on.

Do you want to take this up @dhanesh95 ? I'm writing a commblog + magazine article on docs writing based on the classroom session.

@dhanesh95 will write the draft, and @ankursinha will help polish it up if needed

Metadata Update from @ankursinha:
- Issue assigned to dhanesh95

3 years ago

We have a draft in the works. We'll complete it and hope to publish before the next meeting.

Metadata Update from @ankursinha:
- Issue untagged with: on-hold, tooling
- Issue priority set to: High

3 years ago

This is the link to the preview for others: https://communityblog.fedoraproject.org/?p=6230&preview=1&_ppp=97a717de9c

I'm going through it now and will provide my comments to @dhanesh95 by the end of the day.

@dhanesh has my feedback already. He's just too busy with dayjob at the moment.

@dhanesh95 - please upgrade the tag to "next-meeting" when this is ready for discussion.

Metadata Update from @ankursinha:
- Issue untagged with: next-meeting
- Issue priority set to: Normal (was: High)
- Issue tagged with: meeting

3 years ago

It's been a long time coming and my sincere apologies for the delay. I studied the feedback from @ankursinha and have made some changes to the post. Please have a look -

https://communityblog.fedoraproject.org/?p=6230&preview=true

and let me know your thoughts. I'm sure we can make this even better. Specifically, I'd like to get some suggestions on two parts of the post:

  1. The title - we need something catchy

  2. Following up on Easyfix tasks - maybe we can elaborate more on how project owners can check in on progress

Metadata Update from @dhanesh95:
- Issue untagged with: S: Future-meeting
- Issue tagged with: S: Needs-comment, S: Next-meeting

2 years ago

Hello. Could you please share the text of the article? I think I haven't the rights to see it on community blog

Here's the post I came up with. As I mentioned in my previous comment, I'd like to get some suggestions on the title for the blog post.


There are plenty of tasks in the community that are simple enough for most community members and newbies to work on. These tasks provide an excellent way for new contributors to get themselves involved! Seldom do new contributors find their way to such tasks. Easyfix tries to bridge this gap, benefiting new contributors and project owners alike.

Easyfix, a TLDR;

Easyfix provides a list of tasks considered as easy entry points for contributors. This list of tasks, divided sub-project wise, has a person in charge for every task. Contributors can reach out to this person for all sorts of help required. The Easyfix wiki page contains a list of projects added by respective project owners. Tickets with an 'easyfix' tag are fetched from these projects and display them on the Easyfix page. At the time of writing this article, Easyfix supports fetching issues from projects hosted on GitHub, GitLab, Pagure or Bugzilla.

How can project owners make use of Easyfix?

It's a simple three step process:

1) Choose issues/tasks from your project

We trust you to choose the right tasks to be included in Easyfix. But as a general guideline, note that the task:
- Does not require extensive research on the project and
- Is simple enough to be completed in a few hours

2) Make your project more accessible

Here's how you can do it:

  • Add a tag to your project's issues. We suggest using "easyfix" but don't let us hold back your creative genius. ;)
  • Add your project on the wiki page. Please note the correct format for the project information as per the hosting service.

    • For GitHub: github:username/projectname tag/label contact-person

    • For Pagure: pagure.io:projectname tag/label contact-person

    • For Gitlab.com: gitlab.com:username/projectname tag/label contact-person`

    • For Bugzilla: Tickets that have "EasyFix" keyword, or have "Trivial" in their whiteboard are retrieved.

3) Point newbies to the Easyfix list

Once the project is added to the list, it should show up on the Easyfix page. Just point folks over to the link - https://fedoraproject.org/easyfix/

Following up on Easyfix tasks

Remember that Easyfix is meant to be a way for newbies to get started, so from time to time, drop in a word to check on progress.

How can contributors benefit from Easyfix?

As this is a compilation of "getting-started" tasks, contributors can keep an eye on this list and take up any task/project that interests them. Just choose a task, read the description and get cracking! :)

Request for feedback

Everything in the Fedora Project is always evolving and we're hoping to improve Easyfix too. Contributors have shared their ideas on the improvements and we'd love to hear your thoughts too. Let us know your thoughts on the Pagure ticket.

TODO: Add link to Pagure ticket

@bcotton what do you think about this article?

Looks good to me at first pass. I'm a little concerned about the long-term viability of the existing Easyfix, but we might as well use what we have for now.

When everyone is ready, go ahead and submit it following the CommBlog contribution instructions.

Metadata Update from @hhlp:
- Issue marked as blocking: #59

11 months ago

Metadata Update from @ankursinha:
- Issue close_status updated to: Invalid
- Issue status updated to: Closed (was: Open)

6 days ago

Login to comment on this ticket.