Creating github project to manage common issues.

[kYc0o]

While checking some PRs I noticed that as they increase in number we start to loose the track of previous ones and issues that could be related.

Even if the github projects feature is quite new and most of the things are done manually, I'd like to propose the use of such feature to organise PRs and issues that share a common solution.

For example, I noticed some PRs and issues that could be solved by the introduction/optimisation/fix of the newlib/gcc for msp430 platforms. Namely, I can cite:

#5188
#4766
#6194
#6150
#4954
#4413

Among some others that surely I'm missing.

So, the goal is that if we choose a shepherd who can take care of getting this new feature/fix (newlib/gcc in this case) some (or all) of these PRs and issues would be solved at once.

What do you think? Maybe I should move this to the devel mailing list?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you want me to ignore this issue, please mark it with the "State: don't stale" label. Thank you for your contributions.