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.
