I understand. I wanted to make a place for out-of-band patches to be announced within the larger umbrella of Transcode resources to assist in keeping track of them. I realise that in this case the patch is on track for going into the core.
The stabilization module is very interesting, btw. I wonder whether it can be applied to correct the "bobbing" artifacts common to many "restored" videos? There are a number of dvd's originating from China which have wildly bobbing credits that I think would be appropriate candidates. Georg Martius wrote: > Hi Phil, > > thanks for the wiki page. There was one misunderstanding. Francesco already > added my code to the CVS some time back and we had also some very > constructive conversation and I also send a larger patch to fix the major > coding style things which also went in smoothly. I just thought after that > the stuff is going to be included in the upcoming release candidates, that's > all. I really did not want to make a big fuss. > > Regards! > Georg > > On Sunday 07 December 2008, Phil Ehrens wrote: > > Georg Martius wrote: > > > > If you would like to make your patch available > > > > via the wiki, please feel free to link to it > > > > from a wiki page. That is probably the best way > > > > to make it available to the people who want it. > > > > > > Okay, I will provide a patch myself. I was just wondering what general > > > policy is followed to include stuff. If things are held back because of > > > minor style issues I believe that it is not the way to go, because new > > > developers get quickly bored. > > > > I am not a transcode developer myself. I only host and > > maintain the wiki. At one time I wrote a wrapper script > > that was used by thousands of people to make dvd's using > > Transcode, but that script fell out of general use several > > years ago. > > > > The actual development of Transcode is handled by a VERY > > small number of contributors at any given time. The > > strictness about coding style is necessary to avoid > > overwhelming the core development staff with the task of > > understanding other peoples code. > > > > Contributions are always welcome. Relieving the burden > > of the core developers by making the patches available > > via the wiki, and keeping track of bug fixes to the > > patches casually via the wiki is a good way of getting > > feedback for the code. But there is no guarantee that > > the core developers will even look at the patches. > > > > I have created a tentative template for you to use to > > present the Stabilization Patch via the wiki: > > > > http://www.transcoding.org/cgi-bin/transcode?Patches > > > > Please feel free to change the format of the example > > to suit your needs. > > > > I will be adding upload capability to the wiki soon, > > which will require per-user passwords. There's plenty > > of disk space but very little bandwidth, however. > > > > -- > ---- Georg Martius, Tel: +49 177 6413311 ----- > ------- http://www.flexman.homeip.net ---------- > > -- Phil Ehrens <[EMAIL PROTECTED]> | Fun stuff: The SilverLake Linux Users Group | http://www.ralphmag.org 3428 Winslow Drive | http://www.tokyotosho.com Silverlake, CA 90026 | http://www.slug.org
