Hey Folks,

I'd like to get involved with the project from a development perspective
but I'm looking for some guidance on where/how best to start.

I've looked at the contribution guidelines, but rather than arbitrarily
picking a jira I was hoping that there was a more structured approach for
newbies documented that I might have missed. A few questions that I have
are:

   - Does the community have a light-weight style mentoring system to help
   contributors get up to speed?


   - Are there designated component owners/guardians e.g. C++ core, Flight,
   Gandiva, API's etc that could provide guidance if a developer had a
   specific focus/interest?


   - Is the Arrow roadmap documented somewhere that describes development
   priorities (this would help new folks on where to focus/add value)?


   - Looking at the Arrow jiras in bulk, I noticed that 'easyfix',
   'beginner' and 'newbie' labels have been defined. Do you think that it
   makes sense to pick one label and standardise on it for future backlog
   grooming efforts? It would make it easier to identify the pipeline of
   issues that future engineers can use to ramp up on the project.


Thanks for your patience!

Cheers,
Chris

Reply via email to