freeCodeCamp/chapter

Good first issues

ojeytonwilliams opened this issue ยท 18 comments

We'd love to have more people taking part in Chapter. The following issues have both limited scope and an implementation guide. If you're new, would like to help, but are not sure where to start, then these should be perfect for you.

To get set up locally, take a look at our contribution docs. And, if you'd like to discuss more, you can head on over to Discord and say hi. Or just comment here if you prefer.

@ojeytonwilliams There is a "Beginner Friendly" label.

I'm not sure we've used that label, but we could use one for tagging newbie issues in addition to, or instead of, using an issue.

If we used a label for that purpose, then it would likely make sense to add a link from the CONTRIBUTING.md, perhaps in the new "Adding a New Feature" section, to the dynamic list of issues with that label.

Or, if we'd prefer to use this issue as the main landing spot for newbies, then we could link from the same place in the CONTRIBUTING.md to here.

Thoughts?

How did I miss this label... Honestly, I'm not sure which gives them greater visibility, but my gut instinct is that pinned issues are more obvious. If that's reasonable, we could just link between here and "Adding a New Feature" section and just make more use of this label.

That way, if someone sees the issue first, they're guided to the right bit of the docs and vice versa.

I'm not sure it's a good idea to both recommend this issue and the dynamic list of beginner friendly ones. A simple, linear path makes more sense to me. How does that sound?

I think this issue was good specifically for the CTA we posted, but in general the label approach is more effective.

That being said, I think Beginner Friendly should be changed to the standard Good First Issue so we can leverage GitHub's native features for contributors looking for such issues.

Okay, so how about:?

  • tag the appropriate issues with 'Good First Issue' and delete 'Beginner Friendly' label
  • leave the current issue open and pinned
  • link from the CONTRIBUTING.md to the dynamic label 'Good First Issue' list.
  • add a link to the 'Good First Issue' label at the top of this #691 post just so people are aware we are going to use that label and in case we start labeling other issues that are beyond the scope of this call to action

I think that's a great plan,.

Is it enough to rename the label @nhcarrigan ? Will GitHub then pick them up?

I've created a new label and moved the old ones over #608 #430 #276 #275. @ojeytonwilliams you should probably look at those issues to confirm they are still "Good First Issues"

Yep label looks good.

Here's the link to the dynamic list.

This includes the issues mentioned in this issue and the 4 previously tagged as Beginner Friendly.

Thanks, Jim. I removed the URL validation (#430) because it looked like a technical decision still needs to be made, but the others seem reasonable to me.

We can link to https://github.com/freeCodeCamp/chapter/contribute now (thanks, Nick!). It's got a cleaner UI than the issue list, imo.

Alright, how would someone navigate to that page if they didn't have the link?

No idea. I suggest we just link to it ourselves. Edit: I've add a link in here: #690

Hi All,
I am new to open source and looking for some projects to contribute to.
Let me know if I can take this issue.

Welcome @aayush89890 Yes, feel free to pick something on the Good First Issues list
Good First Issue This issue is beginner friendly! It shouldn't take much experience to get up and running.

If you have questions, then please post them on the specific issue or in the chat.

Reading the README and CONTRIBUTING.md are the best way to understand how the project and development is setup.

Thanks @allella will start looking for the issues and take up.

Hi
I am new to open source and looking for some projects to contribute to.
Let me know if I can take this issue.
and I am good at these kind of issues.

Hi @Misba9 this is an umbrella issue that highlights other issues that are good for new contributors, so you're in the right place. I recommend taking a look at the first comment, #691 (comment) and see if there's anything you'd like to take on.