Welcome to HAAG-Code-Base-Template Discussions!

[KaileyCozart]

Welcome to Code Base Discussions

The code base requirements are the following:

• The instructor has to clearly be able to see the code you wrote each week. For example, a personal folders section that is designed solely for grading purposes. For the first week, we copied or linked our code in a separate repository.
  *** Currently, I think it is okay to simply use your project repo and then link to the specific files you worked on that week in your report.
• Each project needs to have its own repo that is (1) public and (2) part of this organization.
• Code contributions need to be tracked for publication attributions.
  *** Currently, each project should have a single repo. This means that the insights tab of each project repo can be used for attribution.
• Code needs to be marked as either: in-progress, tested and documented, or abandoned.
  *** Currently, code can be marked in each section or in each file, it just has to be clearly marked. Code marked as tested and documented should be tested by someone other than the person who wrote it. Suggestions for the best way to do this would be appreciated. This does not have to be done weekly, it just has to be done by the end of the semester.

Please comment below to suggest strategies that are efficient for researchers and fulfill the goals of the organization.