We are here to build, learn and grow together and it happens when 

  • More users join the community, report bugs/issues and get sufficient help to adopt Apache Hudi to their production needs
  • Users can learn the code, design, operations over time, become contributors to the project and advocates for its use
  • Strong contributors can become committers on the project and in fuse new ideas 
  • Ultimately, the most deserving committers join the PMC as well to take active part in shaping its roadmap/vision 

Roles

Given all of us have limited time and resources, it's important to organize yourself into roles - which are merely personas - members of the community can adopt at any given time, such that we are always trying to guide more users through the steps above. This will result in a virtuous growth circle that will be rewarding for all of us involved. We have outlined some of these roles below. Note that these merely serve as guidelines and there are no hard-fast rules here. One can assume any number of roles from below or help the community in ways not outlined below, at any given time.  


Under Discussion

Main idea here is to provide contributors/users to target their efforts more and for PMC/Committers to organize themselves such that we are evenly resourced. This is still being discussed on the mailing list




RolesResponsibilities

PMC/Committer
Shepherds

R1User Engagement : You are the face of the project in many ways, also its lifeline. First responders to user issues, doing the best to unblock them asap.
  • Answer user questions on Slack
  • Answer simple GH issues
  • Answer simple questions on users@
  • Keep FAQ/Troubleshooting guides upto date
  • Handoff anything that might need a closer look/confirmation to R2

Bhavani Sudha

Vinoth Chandar

R2

Community Management : You are the pillar of strength for the project, taking on the context switching, connecting the dots for everyone 

  • Triage handed-off R1 issues and help users with tuning, configs, alternate workarounds
  • Tag GH issues with the right label for tracking
  • Once an issue is triaged to a real bug/feature request, file a JIRA against the right release
  • If fixes are simple/small, deliver fixes on master to help users make progress
  • Fix any small docs issues, take up administrative tasks.
  • Answer simple questions on dev@ from contributors

Balaji Varadarajan

sivabalan narayanan

Nishith Agarwal

R3User Success : You go the extra mile to help users understand the project and remove adoption hurdles.
  • Spend more hands-on interactive time with user' issue over any conferencing tool/slack to help them get to production sooner.
  • Many users may be new to data processing/Spark/Hadoop as well. You also provide them with architectural help along the way

 sivabalan narayanan

Nishith Agarwal

R4 Evangelization : You get the word out. You are the growth team, thinking constantly about how to bring new people/ideas to the project.
  • You tweet, post, write, share things in and around Apache Hudi
  • You deliver conference talks, meetups and get the word out
  • You also author some strong technical blogs on hudi.apache.org/blog
  • You are constantly thinking about aspects that are less explained, and how to make them easier for the users

Vinoth Chandar

R5Code Reviews: You are moving the needle by providing great, kind and constructive code reviews. Code can be written, but has to be landed for it to matter.
  • You prowl the PRs, with the intent of making quick forward progress along with high quality
  • You contribute small fixes yourself and are constantly thinking of making the process more efficiently
  • You contribute towards making our code style, tests, test infrastructure more complete, robust and standardized 

Nishith Agarwal

sivabalan narayanan

R6Design Reviews : You actively engage on DISCUSS threads and review RFCs and unlock great new features
  • You chime in on RFC reviews with insightful comments, helping the design make steady progress 
  • You also follow through and review large RFCs

Vinoth Chandar

Nishith Agarwal

Shaofeng Li

R7Engineering : You are the "engine" (pun intended). Ultimately, Apache Hudi will be widely adopted for the technical merits and its beautiful set of features. You author them.
  • You are constantly working on the committed work for the next release, with an eye for what's best for the project
  • You are authoring RFCs, with due process that describe new features/improvements to Hudi
  • You are in general, a strong engineer, who wants to ship Hudi code.

Vinoth Chandar


  • No labels