I'd be happy to contribute some of my time to fixing problems in
Cinelerra, particularly those which bother me the most. ;-)
To that end, I have a few questions:
1) Presumably I should not be granted write access to the repository
until I've had a chance to prove that I know what I'm doing. In the
meantime, what's the procedure for submitting changes? Do I email
patches to this list (yuk!)? Do I email one of the other developers?
If so, who? What format should the patches be in?
2) The documentation seems confused as to whether the repository is CVS
or SVN. Am I correct in assuming that it used to be CVS and is now
SVN? Or is there some odd mix of the two in place?
3) Being new to Cinelerra, I might few as a problem something which
experienced users consider a feature. As such, I should really
discuss potential changes before wasting my time inside the code. Do
I do that here on this mailing list, or elsewhere?
4) During these massive multi-week merges of Heroine code, should other
developers just hold off on changes until the merge is finished, or
are they free to continue with commits?
5) How often do the Heroine merges occur? As Cinelerra CVS acquires
more features and changes which are not in the Heroine code base, the
merge effort will presumably grow. Are we in danger of ending up in
a situation where the developers spend all of their time doing merges
and never any new development?
===========================================================================
- deane Gooroos Software: Plugging you into Maya
Visit http://www.gooroos.com for more information
_______________________________________________
Cinelerra mailing list
[email protected]
https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
