It is a design issue... when you say it will kill Cinelerra, do you mean she has such a monolithic design that no-one will work on her? a long-term developer will in time pick up a fair percentage of the code base, but to get developers in there in the first place, there needs to be problems of manageable size for them to work on, and in particular the amount of learning that they need to do of the existing codebase must be manageable. But is Cinelerra manageble in that state? Can she be put into that state?
On 14/11/2007, Z F <[EMAIL PROTECTED]> wrote: > > > --- Martin Ellison <[EMAIL PROTECTED]> wrote: > > > 1. Developers don't want to learn 100,000 lines of code before they > > contribute anything. > > Please, forgive me, but exactly this type of philosophy will kill > Cinelerra. > > This is a design isssue. Design of code should be such that it is not > necessary to learn huge amounts, but to contribute, one would most > likely > have to learn anyway... For this design problem to be solved there > should > be the "master" of the main development trunk and all > patches/contributions should conform to the requirements of the project > which should be spelled-out. Good intentions are not enough. broken > patches should not be acceptable even though someone else could fix > them. > > Well, this is my opinion. Unfortunatelly, I am at the stage of > reading design patterns books and learning how to use them... > > I would suggest that the leaders of the project get together and set > the > rules and ask everybody to follow them :) > > ZF > > > > > ____________________________________________________________________________________ > Get easy, one-click access to your favorites. > Make Yahoo! your homepage. > http://www.yahoo.com/r/hs > > _______________________________________________ > Cinelerra mailing list > [email protected] > https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra > -- Regards, Martin ([EMAIL PROTECTED]) IT: http://methodsupport.com Personal: http://thereisnoend.org
