Update contributing guidelines for adding project lifeline.

I know I’m not a consistent contributor to the project, maybe I’m missing something. It took me a while (30 minutes) to find an issue that’s not being worked on and is ready for development that hasn’t been worked on.

I’m not sure how you can tell what’s important, what needs to get worked on next, if it’s ready to be worked on, if someone is actively working on it. For me to do that now I need to look into and spelunk around issues.

Yes, the labeling system helps, but there are a bunch of issues that have help wanted that are out of date.

I think there’s a better way for attacking issues and building features for this product (ends rant). Is anyone else having this issue?

[JosephLivengood]

Perhaps adding in progress or changing help wanted to in progress when someone takes the issue would help and requiring a solid estimated time frame when a user takes the issue so Mods know when its safe to throw a help wanted back on! I’ve seen this work great on some other repos

[raisedadead]

@JosephLivengood @Greenheart Thanks for the feedback, I have seen in the past whole year that the flow I mentioned above https://github.com/freeCodeCamp/freeCodeCamp/issues/13494#issuecomment-281355649 seems to keep things async and reduces the clutter from a maintainers perspective, and keeps things async considering, a major chunk of the development focuses on curriculum.

We should maybe add more clarity in the guidelines on that. But again that’s just my thought. Feel free to modify.

Workflow:

• Look for issues that are help wanted, confirmed or bug and are not assigned to collaborators, they are open for contributions, and do not need prior permissions. Feel free to open Pull request to those.
• If you found a bug, or an issue, that is not in the tracker you can open a pull request directly if you have a fix ready. Else just log a new issue, just make a comment that you are interested in working on it. We will confirm that and add a in progress label to it.
• Occasionally stale issues will be closed decayed and we would re-open if activity on those pick up.
• Feel free to check out the projects, for our long term goals, which group together issues from the main tracker, but in every case the above rules apply for triaging.
• Join the Contributors chat room to meet other contributors and get assistance or clarifications.