Thanks @zoom

I will read your thread aswell (these can be interesting but also read-heavy 
subjects). I assume it is relevant. As we say in Dutch sometimes I am walking a 
little behind the facts.

To decrease potential bossyness I would like to adjust the term "need" to 
"want", and assignment maybe to "attachment"?

So you would get a want-list, and an attachment-list. Volunteer seems OK to me.

Management sounds also a bit bossy so maybe attunement? Haha, thinking about 
these things makes me feel like a marketeer. Maybe keep it with coordination.

Also I think one should distinguish (two repos) between the subject: on the one 
hand nim-internal and libraries, an on the other hand applications. The latter, 
apps written in Nim are an entirely different but also important subject and 
they also attract different persons with different expectations, 
knowlegde-levels and focuses.

When the core-nim-devs are overloaded [ :-) ] a scenario could be also to start 
with such a repo-project for Nim-applications. People who want to present their 
app or app-idea as a cooperative project (a "want") can invite volunteers to 
attach to the project. Also wandering app-programmers without project-ideas or 
who just want to do a cooperative project can look there aswell.

It is important to keep low-knowlegde starters on-board and to give them some 
sub-forum to exchange stuff on their level and/or subject, otherwise they may 
feel neglected and may leave the language. We dont want that do we? I am 
inclined to keep everyone on board...

Reply via email to