Closed guidocalvano closed 13 years ago
Agreed.
Added a strategy label and a For Beginners label. This issue itself is neither a problem, nor a proposal (anymore now that we agree on it), so strategy is probably a good label. I'll add this to the wiki.
We should discuss how we communicate;
I say, let's use github issues, such as this to describe motives, make proposals and document problems. Goals are a nice type of issue to translate a motive into something concrete. Proposals can then be made to accomplish these goals. Proposals give rise to problems, a problem is a small task that must be solved.
We can use comments to document our discussion of issues.
I like how issues cluster stuff in manageable chunks. I also like how they make sure we don't forget things. Finally I like how it will help other people solve their problems, and thus help us solve them too.
Lets use the git wiki to cluster motives, goals, proposals and problems into requirement docs, designs, documentation. Not that I am overly fond of writing huge documents. Everything should be brief and only when its necessary. Motives and goals help stick to what is necessary.