<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jul 29, 2016 at 11:15 PM, Holger Levsen <span dir="ltr"><<a href="mailto:holger@layer-acht.org" target="_blank">holger@layer-acht.org</a>></span> wrote:<br><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">Hi alberto,<br>
<span><br>
On Thu, Jul 28, 2016 at 01:48:51PM +0200, alberto fuentes wrote:<br>
> petition #1:<br>
> Can I have the subtitles sync with debian-meetings?<br>
<br>
</span>what does this mean in practice, what needs to be done?<br>
<span><br></span></blockquote><div><br>manually erase any reminds of subs since the latest version with new name schema (mostly remove subtitles folders):<br></div><div><br> find -name '*srt' and remove those folders<br></div><div><br>copy files. Roughly:<br> git clone subtitles; cd subtitles; for i in */; do for j in $i*/; do cp $i$j/* ../$i$j/subs; done; done<br><br>Some doubts come to mind tho:<br>- I wonder if there is a way for me to trigger this copy without bothering anybody<br></div><div>- versioning of the subs files are implied on the file name. That means, every new version the file name changes and old version needs to be removed. I asking about the better way to fix this. Some rsync with -delete? hardlinks to the name without version? Keep the versioning in a separate metadata file altogether?<br></div><div><br><br><br></div><div> </div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote"><span>
> petition #2:<br>
> Can I have some consistency in <a rel="noreferrer" href="http://video.debian.org" target="_blank">video.debian.org</a>?<br>
<br>
</span>I don't think it's useful to move files of historic events around, as<br>
this will break links.<br></blockquote><div><br></div><div>I see why this could be troublesome. hardlinks to the legacy video names? >:)<br><br>I guess some metada file about whats on <a href="http://video.debian.net">video.debian.net</a> would be the best solution. Some json and start maintaining it every time something gets added. I can make the first of such file if this is indeed a good idea<br><br></div><div> <br></div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">
So even DebConf16 I already wouldn't change anymore. But in future,<br>
consistancy can surely be improved, could you please indicate what we<br>
can improve?<br></blockquote><div><br></div><div>Since you are asking just about ideas, I would recode everything and start anew to remove the cruft... although this is very unlikely to happen x)<br><br></div><div>I guess a metadata file would fix mostly every wacky decision past or future on the video tree. High/medium/low quality videos is the tag im thinking for the json file... there are old different formats not necessarily high/low quality. I will shoehorn this somehow :P<br></div><span><font color="#888888">
</font></span></div><br></div></div>