|The normal OSS task distribution model
|generally works much better:
|1) Pick some task that you want to have done,
| and that you think you are able to do.
|2) Check with the developer list that there
| isn't someone else currently working on
| that, and tell the list that you start
| working on it.
|3) Do it.
|4) Test it.
|5) Submit it.
|During steps 3 and 4 you would monitor the
|developer list to ensure that nobody else
|starts working on the same thing.
thanks for putting it in words, it is exactly that.
I will try to put that online along with a small "todo" list...
|This is completely decentralized, freeing
|the board from a huge management task.
|
|There is still a slight change of
|duplicate work, but by using the
|developer list that can be minimized.
good point, it is very self relying.
|> Talk about heirarchy and superiority! I would have rather went to a
|> web site and grabbed a well defined task of my choosing with a known
|> date that I needed to accomplish it by (so no one else stepped in and
|> did it).
|
|I think we have no more "heirarchy and
|superiority" than we create for ourselves.
|And I don't think we should create it.
|
Well I mean let's not be hypocrites either. We do have a strongly
hierarchical system, all OSS groups have that. It is not just along the
lines of "coder/designer" these don't work in OSS. There are excellent
designers among our best and excellent coders too. I beware of the rest, it
"smells funny" to me. "Show me the money".
marc
|
|Best Regards,
|
|Ole Husgaard.
|
