Step by step plan.

[M52]

So basically, we need to decide WHAT we are going to do and WHO is going to do it. The discussions within the other 'issues' are great but, we aren't really working as a team yet.

I think it would be best to tackle this step by step.

1. Let's first determine which components we need
2. Let's decide who is going to make them.
3. Devise a test-method so we can test the code we have written.
4. Test & Develop until the code is fully working.
5. Document the code and make yourself available for writing a new component.

^That is just a rough idea on how to go about it. Another way to do it would be to tackle it piece by piece. Meaning, we'd all start writing on the memory management, then we all work on the bootloader, then we all work on the filesystem etc...

This latter way is slower and might be difficult as a way of coding BUT, in this fashion everyone will comprehend the code...

EDIT: We might want to put someone in charge of assigning tasks to people. I personally think some sort of command would be needed especially if more developers start to contribute.

[Liraal]

I think assigning some sort of leader is a good idea. I'd also like to do it step by step, because that's (roughly) how it was, and piece by piece is not really appealing. Plus, some people can grasp certain things more easily, and having them all tied up to one issue doesn't seem like the way to go for me.

[dilbertfan]

^ dat post
Also, milestone are awesome and should be used verily

[M52]

I agree with @viccuad

[ColErr]

So milestones:

1. bootloader, mem management
2. program scheduler
3. Test suite
4. ???
5. Profit... I mean working Kernel/bug fixes/feature improvement.