To continue our series in which I interview prominent open-source maintainers to find out some best practices for contributing, I spoke with Mark Thompson, Developer Relations Engineer at Google and Angular Core Team member. If you would like to check out that interview, you can see it here.
What is Angular?
Angular is a Typescript-based open source framework created and maintained by Google and used for building web and mobile applications.
Mark Thompson is a Developer Relations Engineer who began working for the Angular Core Team as a component of his employment at Google.
What to Know Before You Get Started
If developers are interested in contributing to Angular, they will want to start out by visiting the official Angular repository. Once there, they can find the contributing.md file to get an idea of the guidelines for contributing. After that, contributors will be able to explore the various projects within Angular such as Components, CLI, and more.
- Spend time going through the contribution guide, and learn the rules so the Core Team can best help you! There are a lot of automated processes involved!
- Sign the CLA before sending any pull request! This is required before the Core Team can accept your PRs!
The Best Way to Get Started
The easiest place for new contributors to start is in the documentation! Working on the documentation gives you a place to use your existing knowledge, or even your proofreading skills! Anytime you see an issue in the documentation, you can submit an issue and follow it up with a PR!
- Don’t come in too hot! Don’t use issues as opportunities to attack other developers. No Core Team member or contributor creates anything with the intention of causing intentional harm.
- Don’t spam the comments. The Core Team keeps up with comments to the best of their ability and will eventually get to yours.
- Go through the feature requests and ‘thumbs up’ the ones that you like so we can make sure they are prioritized!
What About Attending Core Team Meetings?
Currently, there are no open meetings for Angular, and prioritization meetings are limited to Google employees on the Angular Team and those who receive special invitations. However, anyone can look at the roadmap to find out what the team and other contributors are working on.
-Consider hosting your own meetup, event, or creating content for the Angular community.
Angular Success Stories
Before Minko Gechev became a Googler, he was contributing to Angular. His passion for Angular led to his career at Angular, and he is now the team lead for developer relations.
Will your story be next?
Ready to Begin?
You can find the Angular Github repository here.