Summer internships are just about to start on May 14th!
One thing I'd like to have clarity on before then is a repository policy for new standalone tools. @dexter21's peer-to-peer sync tool is a good example of that. It's likely that by the end of the summer it will be adopted as a full ODK tool. There's also some possibility that the functionality will be rolled into Collect depending on user feedback. @dexter21 and @Shobhit_Agarwal, have you already discussed where on Github you think the work should happen?
I'd like to propose introducing a
opendatakit/skunkworks repository on GitHub. The term "skunkworks project" was first used by Lockheed and refers to innovative, exploratory projects led by small teams. We could have folders within that repository for different projects. Some of those might eventually be moved to their own repos, get absorbed into existing projects or so on. This is a model others have used: https://github.com/gitcoinco/skunkworks, https://github.com/boundlessgeo/skunkworks, etc. If we wanted to be a little more literal (boring?!), we could go with "experimental" instead of "skunkworks".
Another model used by larger organizations such as Netflix is to have a dedicated skunkworks organization with sub-repos: https://github.com/Netflix-Skunkworks. I don't think that's necessary in this case.