How to become on a Apache Hadoop committer | Diary of a Data-Driven Product Manager
Do they have good technical skills in general, and also demonstrate good understanding of some part of our specific codebase? (in other words, can they effectively review and commit new contributor's work without introducing bad code or bugs) Do they know their limitations? (eg knowing when it's better to let another committer review a patch because they don't know the possible ramifications of the change well enough) Are they a team player who can compromise even if it means some extra work for them? (eg adding additional unit tests when asked, changing a design based on some feedback even if they have to throw away some code, etc)Read full article from How to become on a Apache Hadoop committer | Diary of a Data-Driven Product Manager
No comments:
Post a Comment