Managing GitHub Issues: Distinguishing Between Community and Core Team Contributions

[raisedadead]

Asked via my booking page AMA:

Hi Mrugesh,

I am [redacted]. I started my open source journey with freeCodeCamp. Do you remember me? :D Nice to see you after so long!

Then I did GSoC 2021 and I'm with [redacted] as a full-stack engineer (Django, Vue) since then.

I wanted to ask how does freeCodeCamp handles GitHub issues that are meant for community contributors and issues that are meant for the internal core team?

I am asking this because in our org we have lots of issues that only the internal team has the insights to solve. But we want to give open source contributors good issues to solve as well. So I want to know how does freeCodeCamp balances this situation? We will use some inspiration.

[raisedadead]

Hello [redacted],

Thank you for reaching out to me. Here is my recommendation:

• Triaging GitHub Issues: Efficiently sort issues into project boards for better organization. More on triaging.
• Utilizing GitHub Project Boards: Implement project boards for significant projects, such as developing new certifications or platforms.
• Leveraging GitHub Teams: Establish teams for specific roles like platform engineers and curriculum designers.
• Applying Automation and Agile Practices: Streamline tasks using automation, ensure issues are clearly labeled, and assign them to designated individuals for focused management.

This works for us, but you should study other large-scale organizations like Node.js or Next.js for inspiration.

[vkWeb]

Thanks for the answer ❤️