Code repository reorganization

NOTE This proposal is a WIP and may be subject to change at any time

This is a proposal to move reorganize the riak_cs code to be organized in a more modular fashion. The impetus for this is twofold. The code may soon be open-sourced and there may be holdback features that we wish keep separate and these changes should facilitate that. Additionally, but perhaps more important is to remove the unreliable use of cut-and-paste code between riak_cs, velvet, and stanchion.

The top-level riak_cs repo becomes mostly a container for other dependency repos much like the riak or riak_ee top-level repos.

The list of dependency repos is as follows (naming subject to debate):

• riak_cs_lfs (large file support)
• riak_cs_web
• riak_cs_auth
• riak_cs_acl
• riak_cs_report

Other thoughts

• I think gc goes in with the lfs, but maybe not. Need to consider that more.
• Maybe the API stuff should be broken out into individual repos. e.g. riak_cs_s3, riak_cs_oos
• In case of riak_cs_web, what if any other interface not using http, such as NFS, AFP - or is it odd?