Using github in a more efficient way

[pcineverdies]

So far Dynamatic hasn't fully exploited github's features. I think there's still some room of improvement.

For instance, while it's great to have a roadmap for the students' project (and I would never push in a different direction), the Issue section is getting difficult to manage, as real bugs are overlapped with discussions/rfc/...

My suggestion is to move all of these into this Discussions section, and keep the Issue only for bugs and problems that should someday fixed to obtain a reliable system. While at the moment this is nothing but a cosmetic change, it might be relevant the more people and students get involved in the project (as this also means that more bugs are discovered).
Sometime the line between a discussion and an issue is quite vague, but that's just a minority of the cases.

I already moved some issues, so that you can have an idea of how it looks like.
In case you feel this causes more problems than it solves, we can just revert to the current system - otherwise I can go for the migration of others.

Also, I plan to (slowly, throughout the next weeks) address #89, by having a wiki for the project in the appropriate section.
That will contain a high-level view of the core parts of the project, without going too much into details (mostly to avoid the wiki getting obsolete in three days). This should serve to have a shared space where we can collect information, guidelines for future students and overview of the project (similar to what docs/ currently is).
As I already mentioned, the main problem with such a mechanism is obsolescence. However, while discussing about this feature with Lana and Paolo, we realized that, from an high-level perspective, the information do not change. For instance, fpga20 can be implemented with Gurobi or Google-OR, but it still replicates the algorithm of the correspondent paper.