#96 Community blog post explaining how to use the easyfix tag to get tickets to show up on the easyfix list
Closed: Stale 4 years ago Opened 5 years ago by ankursinha.

https://fedoraproject.org/wiki/Easyfix#Projects -> just a quick commblog post making people aware of this would be nice - more easyfix, easier to get newbies started too.

I'll work on this. @jflory, please assign it to me when you have the cycles. :)

@ankursinha Done! I have assigned this one to you. Better yet, I've also added you to the CommOps Pagure group so you should be able to triage tickets independently on your own. :smile:

@ankursinha Do you still have the time to write this article? Or would you prefer if we clear the assignee field?

Metadata Update from @jflory7:
- Issue set to the milestone: None (was: Fedora 25)

4 years ago

Metadata Update from @jflory7:
- Issue priority set to: no deadline (was: critical (next week))
- Issue set to the milestone: Fedora 27 (to Nov. 2017)

4 years ago

I'll work on it, but maybe clear the asignee field anyway - that way others can pick it up if they wish too :)

Metadata Update from @jflory7:
- Assignee reset
- Issue set to the milestone: Fedora 28 (to May 2018) (was: Fedora 27 (to Nov. 2017))
- Issue tagged with: help wanted

4 years ago

One thing that might help is to start by better publicizing the easy fixes we have. If contributors see those getting worked, they will be more motivated to list and create them.

Metadata Update from @jflory7:
- Issue tagged with: meeting

4 years ago

Discussed in 2018-01-15 meeting.

We put a call for help out on this ticket, and @nauticalnexus agreed to help work on this!

The expected deliverable is a short Community Blog article that explains how someone can get their project added to the Easyfix page. It is supposed to be a friendlier version of the instructions found here.

@nauticalnexus, if you need any help, feel free to leave a comment here. :smile:

Metadata Update from @jflory7:
- Issue untagged with: help wanted
- Issue assigned to nauticalnexus
- Issue priority set to: normal (1-2 weeks) (was: no deadline)

4 years ago

Metadata Update from @jflory7:
- Issue untagged with: meeting

4 years ago

Can I take a work at this?

@nauticalnexus Do you have any updates or need help, or can @wesleyotugo try this one out?

I could use some help. I had something but then I forgot about it and
rebooted, didn't save it unfortunately :(

On Mon, Mar 26, 2018, 10:09 Justin W. Flory pagure@pagure.io wrote:

jflory7 added a new comment to an issue you are following:
@nauticalnexus Do you have any updates or need help, or can @wesleyotugo try this one out?

To reply, visit the link below or just reply to this email

@nauticalnexus The instructions on how to do it can be found here:


You can start there for the how-to post. It doesn't need to be too long, but the goal is that someone knows how to get their project listed on that page after reading the article.

Fedora 28 milestone deadline

This issue is tagged for completion during the Fedora 28 (F28) milestone. The F28 milestone ends on Tuesday, May 1, 2018. This issue will be bumped to the Fedora 29 release cycle.

Metadata Update from @jflory7:
- Issue priority set to: minor (3-4 weeks) (was: normal (1-2 weeks))
- Issue set to the milestone: Fedora 29 (to Oct. 2018) (was: Fedora 28 (to May 2018))

4 years ago

Closing ticket: stale

From previous discussions, we were stuck if a Community Blog post made the most sense for this. In light of the new Fedora Docs tools and platform, this content is better moved to the Fedora Docs website than a blog post. For now, since the ticket has not had any progress, I am closing the issue as stale, so we can better focus on our current team goals and objectives.

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

4 years ago

Login to comment on this ticket.