[openbeos] Re: BeAPI++

Axel Dörfler wrote: 
Adi Oanca <adioanca@xxxxxxxxxxxxxx> wrote:

Stefano Ceccherini wrote:

What about code reviews ? Fixing bugs ? 

    I won't say this isn't necessary. But I will say that for a new-
comer, this sucks.


Well, but isn't that how you usually come in touch with an open source project? You fix a bug that's annoying you, and all of a sudden you're the maintainer for that thing.
If you want to do any useful work for us, you would have to do something like code reviews anyway - in order to understand what's already there. 

    Yes, already agreed.

OK, let's say this happens. In time there will be too much people doing one task and they will start stepping on each other's toes. As that happens, with no direct


There cannot be enough people doing code reviews and fixing bugs - it's hard to step on other's toes with that kind of work, really.

You did not understood what I said. you have 3 developers working at something. There come another 3 to fix some bugs. Now we have a total of 6 people fixing bugs, 3 of which are not that familiar with the code. These 3 modify some things as they see fit, and because they didn't participate from beginning they will screw up some things. Then comes one of the original 3 and has to fix what one thought was right. Auch, that is my feet!
Suppose all 6 are good enough. There were 3 people at the beginning because 3 was enough. Why I say that? Because otherwise at least one of the 3 new comers would made it: 4 original developers. Now, what do you think will happen in a(n open source) project with a module that needs only 3 people to develop but instead has 6 willing to do some work? Auuuuuch!

        ... from where do you think I know this?

But sure, those people would soon like to do something else and we may not find something for everyone - hey, that would be a great position to be in. Having too many people to do the job :) 

    I... don't think so. Having the appropriate amount is the best!

leadership and free will at hand, a fork or a leave will happen.

People come in and leave open source projects as they feel like. There is no reason to stop them doing that. 

    Indeed. But we have to avoid them from doing that.

And to start a fork of a project in development would be a huge undertaking that you don't pull off that easily. Nor would it make a lot of sense, either (at least I can't see much sense in this). 

    I didn't said/meant a fork of the whole project... just an application, 
a module, a kit or server.

[Believe me - that's what I'm doing/feeling at work (money is the glue holding us here - oh yeah, there are a few of us sharing this feeling)]

I think open source projects are fundamentally different to almost any workplace :)

You're right here. I too like working to what I want, when I want. But where's the money from that? Can you live without them?

There is nothing than my free will that keeps me developing for Haiku. I really want to have what we're about to create. 

    Seconding you.


Adi.

Other related posts: