You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Turning a private email discussion with @gvwilson into a public issue for followup:
Consider organizing the Managing Research Software Projects curriculum into time phases of the project: starting, mid-stream, and finishing/maintenance, with summary checklists of the issues to consider at each stage. e.g. starting a new project:
choose version control system and hosting
choose license
choose primary communication method (email, slack, tickets...)
choose programming language(s) and key technologies
document coding standards
setup template repo(s) with placeholder docs, code, unit tests, README, install methodology
(I'm more fuzzy about requirements gathering, a&e, etc. at start of project; that was a very useful section but I'm still digesting it...)
...
And a similar checklist for how to keep a mid-stream project on track and how to wrap up a project into "done" (or at least maintenance mode).
The text was updated successfully, but these errors were encountered:
Turning a private email discussion with @gvwilson into a public issue for followup:
Consider organizing the Managing Research Software Projects curriculum into time phases of the project: starting, mid-stream, and finishing/maintenance, with summary checklists of the issues to consider at each stage. e.g. starting a new project:
And a similar checklist for how to keep a mid-stream project on track and how to wrap up a project into "done" (or at least maintenance mode).
The text was updated successfully, but these errors were encountered: