A "to-do" list for new Ceedling developers

ThrowTheSwitch / Ceedling

Ruby-based unit testing and build system for C projects

http://throwtheswitch.org

Other

567 stars 241 forks source link

A "to-do" list for new Ceedling developers #70

Open hmijail opened 8 years ago

hmijail commented 8 years ago

I have a couple of ideas about what I would like to improve in Ceedling, but I don't know whether those are things that would be accepted by the official developers, or whether I could scratch my particular itch while also indirectly advancing some larger goal. So some "to-do" list could be a great synchronization tool.

Letme commented 8 years ago

Why don't you just open issues here and they can decide?

hmijail commented 8 years ago

Short answer: scaling.

I have already opened issues, and asked in the forum. Now I might implement my own fix for my own problems, and I don't know whether

others already tried what I want but
- wasn't doable or practical,
- wasn't accepted into Ceedling,
is something that is being worked on, and so could be duplicate work
is something deemed desirable, and so I might even get help by the official developers

All of those could shape my decision to do something and how to do it. Asking is good, but having a document where one can quickly check the status of things is better.

mvandervoord commented 8 years ago

I like this idea, actually. Personally, I use Trello for all my personal todo lists. If I were to set up a public Trello for this project, would you see that as filling this need? Were you thinking something more wiki-like?

hmijail commented 8 years ago

A simple, bog-standard TODO text file in the root dir would be enough...

mvandervoord commented 8 years ago

Sounds easy enough. :)