Hi Jörn,

I still have the HG repository here (including a few occasional fixes I've
made more recently, like support for newer FFmpeg versions).  I can upload
that to Bitbucket if you like.

  --Andrew Church
    http://achurch.org/

>
>Hi David,
>
>thanks for your response. I just changed my mind ;) I gave reactivating
>the Wiki a quick try by installing a static build of an older Perl
>version and yes: it runs.
>
>In fact I did this mainly because I wanted to check if the source code
>is hosted there at all. And the bad news are: no, there a just links to
>the dead berlios site.
>
>So we don't have any "official" tarball yet I could place on github.
>
>Probably I should clarify at that point that I am no transcode
>developer. Some years ago I just took over the services to my host, to
>keep the project alive. So I am not in the first line of responsibility
>to put any code on github. But of course I would do so, if no one of the
>"true" transcode developers rise their hands here ;)
>
>Of course the transcode source is out there. For example we could use
>the Debian source tarballs or ask the Debian mantainers what's best to
>do here e.g. what's their source. So we have some options.
>
>For now I keep the Wiki up and let's see what happens. Of course we
>should find a final solution, because the current state is  unsatisfactory.
>
>Regards,
>
>Jörn
>
>Am 14.11.2015 um 17:21 schrieb David Liontooth:
>> 
>> Hi Jörn,
>> 
>> Thank you for keeping us posted. I see the source tarballs and cvs are
>> hosted on transcode.org. The linked "support site" at
>> http://tcforge.berlios.de/ is down or gone.
>> 
>> Would you be open to putting the code on github? It would be nice to see
>> it in your name to vouch for the continuity of the project.
>> 
>> I still use transcode in production; it does a better job on some tasks
>> than anything else available.
>> 
>> Cheers,
>> David
>> 
>> 
>>     News
>> 
>> *September 24, 2008*
>> 
>> 
>>     New *Transcode* Support Site Launched
>>     on <http://tcforge.berlios.de/>http://tcforge.berlios.de
>> 
>>     For the full announcement see [1]
>>     <http://www.mail-archive.com/transcode-devel%40exit1.org/msg00691.html>.
>> 
>> *January 18 (Sunday), 2009*
>> 
>> 
>>     **Transcode* 1.1.0 released!*
>>     <http://transcoding.org/transcode?Download>
>> 
>>     **Transcode* 1.0.7 released!*
>>     <http://transcoding.org/transcode?Download>
>> 
>>     **Transcode* 1.0.6 released!*
>>     <http://transcoding.org/transcode?Download>
>> 
>>     **Transcode* 1.0.5 released!*
>>     <http://transcoding.org/transcode?Download>
>> 
>>     **Transcode* 1.0.4 released!*
>>     <http://transcoding.org/transcode?Download>
>> 
>>     **Transcode* 1.0.3 released!*
>>     <http://transcoding.org/transcode?Download>
>> 
>>     **Transcode* 1.0.2 released!*
>>     <http://transcoding.org/transcode?Download>
>> 
>>     **Transcode*-htdocs 1.0.0 released!*
>>     <http://transcoding.org/transcode?Download>
>> 
>> ------------------------------------------------------------------------
>> 
>> 
>>     Download
>> 
>> *Latest Source Tarballs /and/ CVS Access*
>> <http://transcoding.org/transcode?Download>
>> 
>> 
>> On 11/14/15 5:10 PM, Jörn Reder wrote:
>>> Hi folks,
>>>
>>> long time no see ;)
>>>
>>> Today I upgraded the server which runs the transcode Wiki and
>>> unfortunately it stopped working due to incompatiblities with a newer
>>> Perl version shipped with Debian Jessie.
>>>
>>> Currently I am not planning to invest time into fixing this issue since
>>> this project is somewhat "dead".
>>>
>>> If there is anyone here interested in hosting the Wiki and the other
>>> services (e.g. this mailing list), please contact me. Otherwise I will
>>> switch off them at some time in the future completely, including the
>>> transcoding.org domain.
>>>
>>> Regards,
>>>
>>> Jörn
>>>
>> 
>

Reply via email to