Re: Fork of Octave Forge video package

On 9 October 2013 13:57, Yufei Yuan <address@hidden> wrote: 
> ----- Original Message ----- 
> 
> From: Carnë Draug 
> 
> Sent: 10/08/13 05:50 PM 
> 
> To: address@hidden 
> 
> Subject: Fork of Octave Forge video package 
> 
> 
> 
> Hi 
> 
> I just came across the fork you have recently started on github of 
> Octave's Forfe video package[1]. Would you consider to develop on the 
> package which is currently unmaintained, rather than forking it? We 
> have recently prepared a mercurial repo of it[2] in the hopes to ease 
> other users in developing it. 
> 
> You started your fork from the package version 1.0.2 which was 
> released more than 4 years ago. There has been more changes to the 
> package since to make up for the changing API of ffmpeg. 
> 
> Carnë 
> 
> [1] https://github.com/tufei/octave-forge-video 
> [2] https://sourceforge.net/p/octave/video/ 
> 
> Hi, 
> 
> Thanks for bringing the Hg repo to my attention. I am new to Octave and only 
> found the video package from octave-forge website. So why is that package 
> not updated yet if we've had an updated version in the repo? 

Because no one bothered to prepare a release. The package is 
unmaintained so while developers accumulate patchs on it, no one 
decided that the changes were good enough to actually release it (or 
not worth the effort). 

Well, I would think keeping abreast with FFmpeg API itself alone would justify a release, :) Since that release is not in a usable state right now. Otherwise, Octave newbies unaware of the Hg repo like me will take matters to their own hands and inevitably wasting time on issues already fixed. 

> I thought it's faster track to have something working out there rather than 
> waiting for it to be reviewed or having check-in privilege, especially since 
> it appears that there is no maintainer for the package at this point of 
> time. 
> 
> I would be more than happy to have the fork merged back to the official Hg 
> repo if I could be granted the permission. 

We changed from svn to hg exactly to avoid that. Could you host a 
clone of it with your changes on it somewhere (bitbucket for example 
since github is git only) where we could pull the changes from? Just 
create an entry in our patch tracker [3] asking for us to pull changes 
for you clones. If you can't host it somewhere, you can submit hg 
changesets as files. 

That sounds fine. I could certainly do that. 

Carnë 

[3] https://savannah.gnu.org/patch/?func=additem&group=octave
From:	Yufei Yuan
Subject:	Re: Fork of Octave Forge video package
Date:	Wed, 09 Oct 2013 12:14:31 -0400