[fpc-other] Fork

[Adem]

On 2010-10-22 11:53, Florian Klaempfl wrote:
> Am 22.10.2010 10:31, schrieb Adem:
>> Let's suppose that we have agreed that it would be much more fun and
>> more useful to turn FPC itself into a kind of component/module which
>> itself is composed of components/modules so that people can use FPC as
>> an engine for their projects more directly, while other people tinker
>> and experiment with modules within the FPC.
> Of course, if somebody pops up who we trust that he can handle this, his
> patches will be integrated. Throwing half-baken patches into the bug
> tracker, giving up at the first obstacle or reporting own trivial coding
> mistakes as bugs surely doesn't increase the trust that somebody can
> handle such a huge task.
I'd like to ask you, if I may, how you would go about it.

Suppose you're the one wanting to do that work.

First, how would you prove you're worthy of the task?

Second, could you really do it in small steps?

Third, how would you feel if the /masters/ kept referring to your 
efforts as 'half-baked'?

Fourth, how would you react if your attempts are belittled on the 
grounds of them not being comliant with coding style --of all things?

Fifth, how would you feel if you're considered to be a 
wet-behind-the-ears noob?

Finally, how do you suggest an understanding conducive to co-operation 
can be established.
> The sad thing about all this is: if we integrate all patches without
> quality controll, people will also cry about the decreasing quality of FPC.
Too True.

Quality control must, definitely, be applied before releasing the code 
for production use.

But, "quality control of what?" is the more immediate question.

We need a roadmap (more like an arhitect's design/specification) so that 
everyone has good enough an idea what is expected at what stage etc.

DoDi has written up some; other people and I have written some (consider 
them wishlist, if you like).

I'd bet you already didn't have a more detailed plan in your head.

At this poit, let me quote Machiavelli (I think it was him): "A prince 
isn't accountable for what he did; but for what he didn't".

If he is right --which, he often is-- the onus is on you :)

You need to make the plan against which quality control will be performed.

-- 
Cheers,

Adem