Looking for volunteers to help with NetDOS/32

[clementttttttttt]

Currently I'm developing it alone, so volunteering will be greatly appreciated.

Name: NetDOS/32
Contact: [email protected]
Description: Another OS I have been developing for fun. Is the successor of my earlier NetDOS project.
Git: https://github.com/clementtttttttt/NetDOS-32

Status: Heavily under development.
Features implemented:
- keyboard input
- protected mode
- kernel heap(copied some code)
- paging
- ring 0 multitasking

Features implementing:
- ring 3 multitasking
- vfs
- kernel libc

[bloodline]

Currently I'm developing it alone, so volunteering will be greatly appreciated.

Name: NetDOS/32
Contact: [email protected]
Description: Another OS I have been developing for fun. Is the successor of my earlier NetDOS project.
Git: https://github.com/clementtttttttt/NetDOS-32

Status: Heavily under development.
Features implemented:
- keyboard input
- protected mode
- kernel heap(copied some code)
- paging
- ring 0 multitasking

Features implementing:
- ring 3 multitasking
- vfs
- kernel libc

Your project is less advanced than mine... why don’t you join my project?

[ComputerFido]

Please read https://wiki.osdev.org/Beginner_Mistakes#Teamwork, most of us have our own projects to work on and its a fairly common mistake to assume that we will invest time and effort into a new OS.

[iansjack]

If you are looking for collaborators you obviously need a detailed design document for them to work from (and to give some idea of why they should donate time to the project). Could you give us a link to your design plans please.

Do you have previous experience of managing a collaborative project?

[clementttttttttt]

no, I've never worked on a collab project before, so yeah if I did anything wrong please tell me.

[nexos]

I am working on an OS which I want to be advanced. So, eventually I am going to look for volunteers. But I am going to wait until I have something to show (i.e., able to run GCC and Binutils and Bash on a microkernel, support most modern peripherals, support SMP and NUMA, and so on). People want to know what they are joining. They want to help with something structured. My personal opinion is that you should make the architecture of your kernel, and create the base, and then have people help you after that. Linus Torvalds had GCC and Bash running before people joined Linux. So it is possible to create a hobby and be successful and almost change the OS world. Keep up the good work though . P.S., one thing me, and perhaps other OS developers would be willing to do is test your OS on their machines. All machines are different, so doing lots and lots of tests is important.

[iansjack]

I think what you are doing wrong is asking people to join your project when there is really no project to join. At the very least you need a decent written specification so that people know what the aims of the project are.

Unless there is something special about your project, some unique selling point, I can't see what would convince a competent programmer to join you.

[xeyes]

Currently I'm developing it alone, so volunteering will be greatly appreciated.

Name: NetDOS/32
Contact: [email protected]
Description: Another OS I have been developing for fun. Is the successor of my earlier NetDOS project.
Git: https://github.com/clementtttttttt/NetDOS-32

Status: Heavily under development.
Features implemented:
- keyboard input
- protected mode
- kernel heap(copied some code)
- paging
- ring 0 multitasking

Features implementing:
- ring 3 multitasking
- vfs
- kernel libc

No offense and half joking response below

Nowadays a coder can expect $100 (quite a bit more for good ones, maybe $150 or even $200) an hour before tax.

To attract the good coders, and at a bare minimal. You likely need to make it crystal clear how is volunteering (also known as, working without pay) for you more interesting than pocketing $200 an hour.

FWIW, implementing (more like doing throwaway work on) vfs before getting ring3 task switch working doesn't seem to convey that point too well.