As the nim-communtiy is maturing, contributors come and go, efforts could be
streamlined by coordination and management (in a non-bossy way).
I think this is currently missing in nim-community (but i dont see all the
nim-stuff). And under this management falls:
* needs-list ("demand"). This is a list with requests-for-help (rfh) for
nim-changes, nim-libraries (or there upkeep), documentation etc.
* volunteer-list ("supply"). A list with people wanting to contribute in some
fashion; the volunteer should add the task-type (like programming/
documentation etc) and subject of interest.
* assignment-list; the list where volunteers are assigned (only voluntarily
of course) to a need.
* procedures; agreed ways of doing things.
(- evaluations?; do products / makings live up to expectations or not,
potentially feeding back to the needs. I put this between parentheses because
this is usually done on the nim-forum.)
My idea was to create special github-repos for that function. I mean this in a
non-commercial way of programmer-to-programmer-service. The above information
is written down in markdown-files in the same way as source-code. Communication
would happen thru the issues-section.
For procedures you could also work the same way as source-code with
pull-requests / merges etc.
Pros:
* inventorize needs of nim-makings and potential contributors.
* facilitate voluntary assignment.
* volunteer-names are allready present for github-contributors.
* issues-section can be used to communicate.
* share the glory :-)
Cons:
* somebody must maintain it.
* people may feel pressured to do stuff when they are assigned to something.
* there could be privacy-issues?
Unknowns:
* do we want/need something like this? Is there enough support for it?
* is the repo-format optimal for this use-case?
* how to determine priorities towards the needs? (votes, discussion, etc.)
* how do we accomodate for different levels of expertise?
* How many repos? I think one big one, and different files for the different
things. (needs, volunteers, assignments, procedures, [evaluations])
* who owns the repo?
* who maintain(s) it?
By the way i dont say i want to pull such a repo-project, I just throw it into
the arena.. (but i might want to contribute a little bit.. ;-))
