When we first started MakeDrive, we wanted to go fast, and not have to deal with dependencies spread across submodules or package versions. Now that the code has stabilized it's time to make things more modular. We're already seeing fallout from the monolithic nature of the repo, e.g., #457 where clients are having to deal with server deps.
The most obvious starting point would be to do something like the following (names TBD):
server/* becomes the makedrive repo
client/* becomes the makedrive-client repo
demo/* becomes the makedrive-demo repo
lib/rsync becomes the filer-rsync repo
shared code between server and client in lib/* becomes separate stand-alone modules/repos.
We'll have to figure out how to do tests for the client vs. server, since both will require each other in order to function. We'll also need an in-browser way to test the client vs. what we do now, which is using the client code in node.
One thing I'm not sure about is how to best manage these repos so that they appear as a set. We could put them all under github.com/mozilla/*, but that is a sea of a million repos at this point, and it's hard to find anything. Another option would be to create a github.com/makedrive/* Githug Organization, and host all the sub-repos under that.
When we first started MakeDrive, we wanted to go fast, and not have to deal with dependencies spread across submodules or package versions. Now that the code has stabilized it's time to make things more modular. We're already seeing fallout from the monolithic nature of the repo, e.g., #457 where clients are having to deal with server deps.
The most obvious starting point would be to do something like the following (names TBD):
server/*becomes themakedriverepoclient/*becomes themakedrive-clientrepodemo/*becomes themakedrive-demorepolib/rsyncbecomes thefiler-rsyncrepolib/*becomes separate stand-alone modules/repos.We'll have to figure out how to do tests for the client vs. server, since both will require each other in order to function. We'll also need an in-browser way to test the client vs. what we do now, which is using the client code in node.
One thing I'm not sure about is how to best manage these repos so that they appear as a set. We could put them all under
github.com/mozilla/*, but that is a sea of a million repos at this point, and it's hard to find anything. Another option would be to create agithub.com/makedrive/*Githug Organization, and host all the sub-repos under that./cc @simonwex, @thisandagain, @brianloveswords