Page 3 of 3
Re:the HakwareOS project
Posted: Tue Jul 08, 2003 8:18 am
by nullify
Personally, I think gathering recruits for your own OS development project here is not an appropriate place to do so. In a forum like this, people intend to discuss the actual development of operating systems, *not* to look for an OS project to join. While you may find some willing to do so, a majority will probably turn away, with an attitude of "why should I join his project? I've got my own OS, and he's talking about his OS as if it was the most important one on the planet." It doesn't help either that your project is [mostly] vaporware at this point. I'm not saying that you shouldn't try to organize a group project, but there are other more appropriate places (and probably more effective, too) to ask people to join. For example, it appears that the members currently part of your team were from IRC.
P.S. If this comment sounds a bit harsh, I apologize, but I couldn't figure out a nicer way to word it so that still makes the point.
Re: Groups/Project
Posted: Mon Sep 29, 2003 10:32 pm
by kmcguire_l
Yeah, i had this guy once who started working with me. He only worked on some keyboard code that my kernel would use, i didn't really even need it, and he jumped from helping me back to his own OS. I guess he figured his ideas were better. Every now and then i check back at his site - he isn't getting very far - but the point is..
Working with multiple people can be hard because:
A. Each has their own opion.
At early stages they each think they know best. The best time to recruit people if after you have things going when they have to say, "Damn. It works. It works good. I can not say anything about it. It looks better than mine." Then they listen and respect you and want the project to get better.
B. No detication.
Alot of bullcrap about im making this and i almost got it working. Yep, we all do this even me, but it makes it difficult when you are working in a team and you have to keep the detication to a maximum and bullcrap to a minimal.
C. No Plan. No framework.
How are you going to get someone working on something when you can not tell them the general framework they need or what interfaces and exactly how they have to be. I mean, they are writting code now and code is exact its hard to compile with ???? markers all over the code and actually test it.
Im working alone on the kernel for now.
[email protected]
http://hf-mos.rfje.org