Best dev workflow to contribute to the project?

Hi!

I'm interested in contributing to this project. I've been looking through the codebase, and wanted to ask about what your general dev workflow is.

What I've been doing is:
1) Run mkdist.sh
2) Run configure
3) Do my changes
4) Run make
5) Run the samples to test my changes

Just wanted to ask if there was an easier way to (seems to produce a lot of files that are not checked into git?), or if this is the best way?

Thanks!
Jamie

Forums: 

We do not use mkdirs

We do not use mkdist/configure internally, but cloned (not commited) Makefile.devel

-- Alex Tutubalin @LibRaw LLC