Community: Newbie community pinboard

Created on 7 Feb 2019  路  70Comments  路  Source: ansible/community

Github easyfix issues Newbie pinboard

Lot of people ask me same question in lot of meetups and conferences - how we can contribute back to Ansible and where can I find easyfix issue to get started.

We would like to help such people by starting this community pinboard where we can post easyfix or low hanging fruits from the Ansible issues list.

Please feel free to ping other people and add issue which you feel can help newbies/newcomers/want-to-be-contributors.

Here is shortcut link for finding easyfix

Thanks.

newbie pinboard

Most helpful comment

Maybe for the next time, when picking a topic from a source like here (where others might be interested too), announce first when you're starting, so that others can see that someone else is already doing it. That's less frustrating for everyone else :)

All 70 comments

cc @Devendrabhat @sbulage @digitronik @ptoraskar

cc @raghavtan

Thanks, @Akasurde. I'll go through that link.

@Akasurde Thanks

Would love to know how you get on with this.
You may also be interested in HOW TO MAKE YOUR MARK: ANSIBLE COMMUNITY CONTRIBUTIONS
slides & video are linked from this page.

Please do shout out if we can help in anyway. I'm happy to guide/mentor anyone.

There is list of open issues segregated by file name - https://ansibullbot.eng.ansible.com/metadata/byfile_sorted.html

cc @kylix3511

cc @amolkahat

cc @akshay196

Adding @crackcodecamp @ganeshhubale in the thread.

cc @sohamdigheoss

cc @anis016

cc @anurag03

cc @Yadnyawalkya

~Fix typo just like - https://github.com/ansible/ansible/blob/46fbcf08bc1998db821714ad65a2b271e4e74f89/lib/ansible/modules/network/fortios/fortios_firewall_auth_portal.py#L48~

~Change 'adress' to 'address'. There are ~92 matches in Ansible repo.~

FIXED

Fix typo just like - https://github.com/ansible/ansible/blob/46fbcf08bc1998db821714ad65a2b271e4e74f89/lib/ansible/modules/network/fortios/fortios_firewall_auth_portal.py#L48

Change 'adress' to 'address'. There are ~92 matches in Ansible repo.

I have fixed it, raising PR

I was almost done! :(

@sbulage @anis016 We have PR from @amolkahat https://github.com/ansible/ansible/pull/52143

Maybe for the next time, when picking a topic from a source like here (where others might be interested too), announce first when you're starting, so that others can see that someone else is already doing it. That's less frustrating for everyone else :)

@felixfontein Good point. There was no issue for this typo so no central place to announce. But going forward we can formalise this. Do you have any easyfix so people here can work on that ? Thanks.

@sbulage already raised one: https://github.com/ansible/ansible/pull/52143

CC: @Akasurde

@Akasurde Yes, got something: in the FAQ, there are a lot of places where a single backtick is used instead of a double backtick (see source of FAQ). These are formatted in italics instead as code, while most of them propbably should have been the later. This is a common mistake for people more used to Markdown.

I don't know if it also appears in other places in the documentation, or whether all places with a single backtick should be a double backtick, so it is somewhat tedious. There might also other documents ith the same problem.

AFAIR there's no ticket for this.

Before starting work on any issue mentioned here or GH issue page, please add a note saying that you are working on it. So that others will be aware and avoid duplicate efforts.

hy @Akasurde, can I work on this issue https://github.com/ansible/ansible/issues/51421 ?

@anis016 Sure.

Typo fixes - While working on issue, please add a note

I plan to work on the typos! I will submit a PR today.

Typo fixes - While working on issue, please add a note

merge request submitted: https://github.com/ansible/ansible/pull/52426

Typo -

  • change from "registed" to "registered"
  • change from "formating" to "formatting"
  • change from "digeset" to "digest"

cc @userimack let me know if you are interested on working any of the above mentioned easyfixes.

Typo -

* change from "registed" to "registered"

* change from "formating" to "formatting"

* change from "digeset" to "digest"

Hi @Akasurde I would like to give a shot to them, can i take this up?

Thanks

@championshuttler yes, you can take it up, thanks

Thank you @Akasurde! Really Appreciate!

Typo -

Change 'dicionaries' to 'dictionaries' overall repo

Thanks @Akasurde

Typo fix - 'Mutiple' to 'Multiple'

@Akasurde Working on it.

@valaparthvi

Help required in extending document - ~https://github.com/ansible/ansible/issues/59125~

@Akasurde working on it.

@Akasurde working on it.

On it

Thanks @Akasurde

Help required in extending document - ansible/ansible#59125

I'm using this bug as an example on easyfix labeled bug.

Just adding easyfix label can helps spotting what are for fixes for developers that can be quick or simple from their point-of-view but for someone without any experience it is not easy, for a ton of reason. Perhaps because she does not know well python or the internals of the projects, or because she does not know how to check her code is correct.

Somethings can be automatically done, the bot can spot bug with easyfix label and add link to a page that help starting the project

  • how to check out the code
  • install the tools
  • ...

We can also direct her to a specific room on IRC or distribution-list for supporting her.
But more than that I expect mentor and developer tagging easyfix to provide some guidance the moment they tagged easyfix with few word:

  • the general idea to fix the bug or to find information
  • the place where to fix in the repo.

Back to the example, for me this is not an easifix, because there is no direction to help the person to fix the problem

"regex can be configured to perform other tests as well".

I would expect, that the person put a comment with the other tests that could be done and possible a source (like the integration code) where there is examples.

Hopes it helps

... (continuing)

Perhaps there is a misunderstand on the word easyfix because easy is quite a relative word. (we discuss about that on #ansible-devel). The text of the label easyfix is "The issue is considered easy to fix by aspiring contributors" seems subject to improvement.

I'd replace easyfix label by new_contributor and the criteria to be:

  • code that can be fixed without a lot of knowledge on the internals (even the word lot is subject to discussion). Module are a good examples.
  • impact of the code is quite low.
  • integration test / unit code are fine I'd say
  • is time a criteria ?

But more than that I expect mentor and developer tagging easyfix to provide some guidance the moment they tagged easyfix with few word:

I really like the idea of the new_contributor label and most doing mentoring for new contributors. Personally I think some of us wouldn't mind to reserve some time to guide new contributors using IRC and using some examples. I try to do with people near me but I think having a "mentoring" community will open the door of new ideas and opportunities.

Thanks for your comments @bmillemathias

This is a really good initiative for beginners. It has many forks and contributions. Just added Ansible as a reference https://github.com/firstcontributions/first-contributions

https://firstcontributions.github.io/

I'd replace easyfix label by new_contributor and the criteria to be:

actually there is already a tag new_contributor given to people doing their first PR,

Question. Is there any procedure or meeting to request and label an issue to be easyfix?

Thank you

Help required - ansible-collections/community.general#1537

Was this page helpful?
0 / 5 - 0 ratings

Related issues

gundalow picture gundalow  路  3Comments

gregdek picture gregdek  路  17Comments

gundalow picture gundalow  路  11Comments

gundalow picture gundalow  路  11Comments

gundalow picture gundalow  路  22Comments