Source tree structure

[Bill-Kunj]

@w2vy @jimscarver @dckc
The current source tree has all the rholang class files at the top level.
This is like fingernails on a chalkboard to me. I always think of the top-level directory having (mostly) subdirectories that organize everything.
For that matter, deploy-all currently hardcodes the names of the rholang files it deploys. Things could be genericized with a more structured source tree. Then localhost dev environment need not be specific to RGOV.

Let's discuss.

[dckc]

I agree that the number of files at the top level is uncomfortable. But git blame doesn't work very well across renames/moves (especially via github), and I rely heavily on the history. So it's a tricky balance.

[Bill-Kunj]

@dckc @jimscarver @David405 @w2vy I think we should consider creating a rholang or RGOV-src directory somewhere. Perhaps under src, but that might affect the webpack deployment and -also- be confused with the rholang actions.

[dckc]

I have considered it... a few times now. On balance, I don't think moving things around is cost-effective at this point. Perhaps it's a lesson for future projects.

[Bill-Kunj]

I believe this discussion is complete now that the rholang directory exists.
@dckc @jimscarver @David405 Someone please confirm by approving an answer so we can close this down.

[dckc]

I guess this discussion moved on without me. I'm mildly disappointed that the annotated version of rholang/core/CrowdFund.rho no longer shows my contribution at all. Sigh.

[Bill-Kunj]

Staff meetings.... Such a bother. :)
Add your name inside CrowdFund.rho in a PR if you feel it is required.