2010/10/22 Adem <listmem...@letterboxes.org>: > 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.
Let me answer as someone who wrote several patches, and only one or two of them were accepted. > Suppose you're the one wanting to do that work. > > First, how would you prove you're worthy of the task? Firstly, you need to understand how FPC development works, and to accept that. Secondly, you need to show other FPC developers that you are willing to work (continuous task) and work as part of team. > Second, could you really do it in small steps? If you really want it - yes. > Third, how would you feel if the /masters/ kept referring to your efforts as > 'half-baked'? How would you feel if someone came and change lot of your code? Would you just blindly accept those changes? > Fourth, how would you react if your attempts are belittled on the grounds of > them not being comliant with coding style --of all things? I would give more importance to coding style. Personally, I change coding style every few months, for two reasons: first, I adopt coding style of the code I use (engines, libraries, ...), and second, I respect my co-worker's coding style (unless it is horrible in which case I talk to them about it). > Fifth, how would you feel if you're considered to be a wet-behind-the-ears > noob? I actually feel like "wet-behind-the-ears noob" every time I start working with new library/technology/problem area. But that's what we are until we learn something :) > Finally, how do you suggest an understanding conducive to co-operation can > be established. It's psychological question - how to you establish trust or love? This is open-source project, and it's developed based on the free will to do so. If you want to be part of that, you need to be team-worker, and that requires not only knowledge but also team working skills. At least, that's how I understand it. Regards, Aleksa _______________________________________________ fpc-other maillist - fpc-other@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-other
