Branch strategy needs clarification

[fadc80]

What is the purpose of dev-root branch? Master is the default branch, but has no code. I think the intention was to have a development branch and a stable master branch. In this case, shouldn't the master branch be updated with dev-root content after a development task (code improvements, bug fixes, etc) is completed? What about to describe in a README or CONTRIBUTING file your branch strategy?

[pcmnac]

That's the idea. There's nothing on master because we don't have (maybe we should have) a release version yet. Feel free to describe this strategy ;)