transcribers team mailing list archive

[Dave Walker <davewalker@xxxxxxxxxx>]

Steve Cook wrote:
> Alan Pope wrote:
>> On Thu, 2008-07-03 at 19:42 +0100, Steve Cook wrote:
>>> Who (Alan, I assume) declares an episode complete.
>> Good question. I guess there's declaring it's all transcribed, and
>> declaring it's perfect. I'd say ep1 is the former but not the latter.

Once we come up with a decent layout scheme, i'm not a fan of the
standard html export from transcriber - I'll set a cronjob to
automatically create updated web pages* from the transcriber files,
possibly every night.  This will mean that any further commits to the
branch will be automagically reflected the next day.  So a transcription
never really needs to be declared /finished/ per se, as some fixes could
still be made well into the future.

* hosted on http://podcast.ubuntu-uk.org

<SNIP>
> I've not really used Bazaar (or any version control), I'll have to have
>  a read of things to see what it can do.  Is there a way of having two
> versions of something for people to compare the two?  Rather than over
> write a file with a new version.

Well Bazaar generally handles merges quite well for code, it will warn
if there is a conflict, and show both in the native transcriber save
file (xml format), so it can be quite easily resolved.  If someone isn't
quite sure how to resolve this, I would think it's best to email here a
'diff' (changes from your tree to the original) using:
	$ bzr diff > diff.txt

This will produce the patch file (diff.txt), and can be emailed to this
list and allow someone else to apply the patch you have produced.

Keep up the good awesome work chaps!

Kind Regards,
Dave Walker