Re: [CinCVS] WHERE CINELERRA IS GOING? ...anyone? proposal for CinelerraCV 2 maintenace

2007-08-16 Thread Martin Ellison
On 16/08/07, Herman Robak <[EMAIL PROTECTED]> wrote: > > > ... Adam would not be able to fix this in a reasonable timeframe, even if > he was given an exhaustive TODO list. Neither will we, unless a lot > of the underlying code is redone to support all the stuff that an NLE > and compositor of th

Re: [CinCVS] WHERE CINELERRA IS GOING? ...anyone? proposal for CinelerraCV 2 maintenace

2007-08-16 Thread Kevin Brosius
On 2007-08-16 00:49, Christian Thaeter wrote: > Kevin Brosius wrote: > > On 2007-08-15 17:36, Christian Thaeter wrote: ... > > I think you won't get much feedback from the older core developers since > > these goals are so large and you haven't tackled a smaller piece of Cin > > first. > I have d

Re: [CinCVS] WHERE CINELERRA IS GOING? ...anyone? proposal for CinelerraCV 2 maintenace

2007-08-16 Thread Herman Robak
On Thu, 16 Aug 2007 11:49:39 +0200, mark carter <[EMAIL PROTECTED]> wrote: On Thu, 2007-08-16 at 16:37 +0800, Martin Ellison wrote: Could you explain this more? svn allows branching, so why not just create as many development branches as required and work there? I do not know git, so could

Re: [CinCVS] WHERE CINELERRA IS GOING? ...anyone? proposal for CinelerraCV 2 maintenace

2007-08-16 Thread mark carter
On Thu, 2007-08-16 at 16:37 +0800, Martin Ellison wrote: > > Could you explain this more? svn allows branching, so why not just > create as many development branches as required and work there? git allows a project to be forked easily, whereas svn is geared towards central command. svn requires

Re: [CinCVS] WHERE CINELERRA IS GOING? ...anyone? proposal for CinelerraCV 2 maintenace

2007-08-16 Thread Martin Ellison
ok, I've found http://git.or.cz/course/svn.html. On 16/08/07, mark carter <[EMAIL PROTECTED]> wrote: > > On Thu, 2007-08-16 at 16:37 +0800, Martin Ellison wrote: > > > > Could you explain this more? svn allows branching, so why not just > > create as many development branches as required and work

Re: [CinCVS] WHERE CINELERRA IS GOING? ...anyone? proposal for CinelerraCV 2 maintenace

2007-08-16 Thread Christian Thaeter
Martin Ellison wrote: > > Could you explain this more? svn allows branching, so why not just > create as many development branches as required and work there? > > I do not know git, so could you please explain what git has over svn? > (Not intended as an attack). I am out of office today. In sh

Re: [CinCVS] WHERE CINELERRA IS GOING? ...anyone? proposal for CinelerraCV 2 maintenace

2007-08-16 Thread mark carter
On Thu, 2007-08-16 at 16:37 +0800, Martin Ellison wrote: > > Could you explain this more? svn allows branching, so why not just > create as many development branches as required and work there? > > I do not know git, so could you please explain what git has over svn? > (Not intended as an attack

Re: [CinCVS] WHERE CINELERRA IS GOING? ...anyone? proposal for CinelerraCV 2 maintenace

2007-08-16 Thread Martin Ellison
Could you explain this more? svn allows branching, so why not just create as many development branches as required and work there? I do not know git, so could you please explain what git has over svn? (Not intended as an attack). On 16/08/07, Christian Thaeter <[EMAIL PROTECTED]> wrote: > > ... >

Re: [CinCVS] WHERE CINELERRA IS GOING? ...anyone? proposal for CinelerraCV 2 maintenace

2007-08-15 Thread Christian Thaeter
Kevin Brosius wrote: > On 2007-08-15 17:36, Christian Thaeter wrote: >> This my maybe arguable view how to hive Cinelerra CV out of its >> develoment stall: >> >> 1) Change the focus of CinelerraCV >> 2) Stop using SVN >> 3) Make releases >> 4) Make tracking HV less important > > I've been pretty

Re: [CinCVS] WHERE CINELERRA IS GOING? ...anyone? proposal for CinelerraCV 2 maintenace

2007-08-15 Thread Christian Thaeter
mark carter wrote: > On Wed, 2007-08-15 at 19:36 +0200, Christian Thaeter wrote: >> 2) Stop using SVN > > I just saw a YouTube vid by Linus who is talking about git: > http://uk.youtube.com/watch?v=4XpnKHJAok8 > > >> Even if commit access is generously handled to people who ask, it's >> still a

Re: [CinCVS] WHERE CINELERRA IS GOING? ...anyone? proposal for CinelerraCV 2 maintenace

2007-08-15 Thread Kevin Brosius
On 2007-08-15 17:36, Christian Thaeter wrote: > This my maybe arguable view how to hive Cinelerra CV out of its > develoment stall: > > 1) Change the focus of CinelerraCV > 2) Stop using SVN > 3) Make releases > 4) Make tracking HV less important I've been pretty silent on these issues so far, no

Re: [CinCVS] WHERE CINELERRA IS GOING? ...anyone? proposal for CinelerraCV 2 maintenace

2007-08-15 Thread mark carter
On Wed, 2007-08-15 at 19:36 +0200, Christian Thaeter wrote: > 2) Stop using SVN I just saw a YouTube vid by Linus who is talking about git: http://uk.youtube.com/watch?v=4XpnKHJAok8 > Even if commit access is generously handled to people who ask, it's > still a big blocker as I explained earlier

Re: [CinCVS] WHERE CINELERRA IS GOING? ...anyone? proposal for CinelerraCV 2 maintenace

2007-08-15 Thread Fred Williams
On Wed, 2007-15-08 at 21:20 +0300, Mikko Huhtala wrote: > Christian Thaeter writes: > > This my maybe arguable view how to hive Cinelerra CV out of its > > develoment stall: > > > > 1) Change the focus of CinelerraCV > [ ... ] > > 2) Stop using SVN > [ ... ] > > 3) Make releases > [ ... ] >

Re: [CinCVS] WHERE CINELERRA IS GOING? ...anyone? proposal for CinelerraCV 2 maintenace

2007-08-15 Thread Mikko Huhtala
Christian Thaeter writes: > This my maybe arguable view how to hive Cinelerra CV out of its > develoment stall: > > 1) Change the focus of CinelerraCV [ ... ] > 2) Stop using SVN [ ... ] > 3) Make releases [ ... ] > 4) Make tracking HV less important Hear hear. I've been reading this threa

Re: [CinCVS] WHERE CINELERRA IS GOING? ...anyone? proposal for CinelerraCV 2 maintenace

2007-08-15 Thread Christian Thaeter
This my maybe arguable view how to hive Cinelerra CV out of its develoment stall: 1) Change the focus of CinelerraCV Currently CVs goal is repackaging the HV version and fixing bugs. But a real community version should acknowledge progress and new features which are contributed by the community.