Hi Dean,
I'm probably one of the latest additional developers who has write been
given access to the SVN repostory and server.
But I'll try answer your questions as best as I know
Dean Edmonds wrote:
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?
diff's is typically the way, (I use diff -Nuar )
If it is an enhancement / bug you could make a bug-report, and then
attach the patch to it.
After a few patches, I assume you will be given access..//
//
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?
No, it should be all SVN..
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?
IRC channel, and the mailing list are a good place.
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?
Hold off.
I offered to help j6t with the latest merge, and he was able to organise
a means by which I could help him put the 2.0 -> 2.1 differences into
smaller patches. It may be possible to add more people to this effort,
but I am waiting on j6t's return (he's on a 1 week internet break).
5) How often do the Heroine merges occur?
See the wikipedia entry for cinelerra to see how often they occur.
(Typicall twice a year)
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?
We are always in that danger. Looking at the latest merger, I would say
HV does a lot more feature additions than we do, and it is very
important to make it as easy to do the merger as possible. To this end,
all the patches we make should be clear, and understandable, without
changing the formatting of the code too much. HV often pulls our
patches upstream, and in one respect, I see it as a good goal to aim for.
begin:vcard
fn:Pierre Dumuid
n:Dumuid;Pierre
org:The University of Adelaide;Mechanical Engineering
adr:;;;Adelaide;South Australia;5005;Australia
email;internet:[EMAIL PROTECTED]
title:Postgraduate Student
tel;work:8303 3847
tel;home:8388 5727
tel;cell:0407570263
note:CRICOS Provider Number 00123M
x-mozilla-html:TRUE
url:http://www.adelaide.edu.au
version:2.1
end:vcard
