Code Contribution Guidelines

1. Code should note duplicate functionality. i.e. if there is already a function (code) in the repo that serves a function (purpose). You should try to merge them (without destroying backwards compatibility) - discuss your merge in the slack channel.
2. Code should follow the analysis function guidelines and assume data is stored/formatted following data formatting standards.
3. Before submission to this final repository, at least one other person in the lab should try it and have it work.
4. Should CERTAIN people have to approve submissions?
5. An open question is if we want code checks - via branches or via forks?