Please don't put todo's in publicly visible files

[armandofox]

@mattwr18 can you please move the 'todo.md' file (currently committed to master) to be an appropriate set of issues or PRs? we'd really not rather have the todo's as part of the student-visible file, to minimize confusion. thanks.

[tansaku]

@armandofox I was hoping the todos would be visible to encourage input from those who might like to help us improve the assignments - is is the naming that's the problem? Should we call them roadmap.md or something? put them in a private _dev folder or something?

[armandofox]

any reason not just keep them as 'issues' in the repo and let people know that 'if you want to help, checkout the Issues section associated with each HW'?

[tansaku]

I guess it was that we were maintaining a running list of issues that came up in our mobs as we were reviewing the assignments, and so there was a need to have an open document to minimise the time that it took to add the issues as they came up. In principle there's no reason why they can't be issues - it's just a question of spending time to split them out like that - but then even the overview of ordering and prioritizing them is helpful - perhaps better off as an overview document in the wiki that points to issues where appropriate ...

and would be great to have CONTRIBUTING.md docs pointing out how to get involved, as you say ...