Community OS Questions

[KieranFoot]

Hey guys,

I was just reading the topic about starting a Mega Tokyo Community OS, I think its a really good idea and i would gladly help with any C / C++ programming...

Forgive me if these questions were answered in the topic, i diddnt read it all, but how would you guys share files, how would versioning be done, would there need to be some kind of protection against unauthorised code changes???

I was working with a group on a small OS, however development stopped because people could not agree on actions to be taken so each made there own modifications and in the end the OS started to fracture and nobody new how systems were working anymore, which made problem solving a nightmare...

Sorry im ranting!

I think its a really good idea, but it will take alot of planning before the actual codeing can begin...

I hate planning

----
Thanx for reading
Kioran Foot

[Kemp]

If you want to talk about that then maybe you should have read the thread and then posted in there?

[kataklinger]

I hate planning

??? The planning is most important thing if you want to do something bigger then "Hello World!" program.

And you should read all of the posts in thread and then send your comment there. ::)

[Brendan]

Hi,

I was just reading the topic about starting a Mega Tokyo Community OS, I think its a really good idea and i would gladly help with any C / C++ programming...

Unfortunately, it'd probably take 6 months or so before a micro-kernel is ready and before modules can be written in high level languages...

Forgive me if these questions were answered in the topic, i diddnt read it all, but how would you guys share files, how would versioning be done, would there need to be some kind of protection against unauthorised code changes???

The way I see it is that "system level" work would be sent to me. I'd check it for bugs and consistancy and then merge it into the main source for everyone to download.

For versioning, there's already a versioning system for binaries that is built into the boot manager and will also be built into the kernel itself (to make sure that all modules are compatibile at run time). The idea is that users will be able to create their own custom OS out of different modules without compatibility problems.

I was working with a group on a small OS, however development stopped because people could not agree on actions to be taken so each made there own modifications and in the end the OS started to fracture and nobody new how systems were working anymore, which made problem solving a nightmare...

I've seen it happen many times. The first time for me was with a project called "Jolt OS", where a group of about 20 people spent ages arguing about little details. After many months with no code at all people were getting annoyed at the lack of progress, so the leader decided to start with an existing OS (MMURTL, from the "Developing Your Own 32-Bit OS" book) despite a few experienced developers pointing out major flaws in the OS itself and with the copyright of it's original author. I'm not sure what happened to the project after that - AFAIK it evapourated quickly after that.


Cheers,

Brendan