Re: [Debconfsubs-team] Subtitles publishing workflow
Le 27/06/2019 à 21:52, Wouter Verhelst a écrit : > We'll also have to come up with a way to decide which sub goes into > which directory. I think the easiest way to do that is to ensure that > the files in the subs git repository match the files in the video > archive. That would mean it would not be possible to remove files, > however -- even if it is possible to tell rsync to only consider files > with a given extension, I don't want to miss an option or two after an > upgrade and start accidentally erasing the whole video archive. > I'm currently cleaning the master branch and will ensure at the same time that the folders match yours. Thomas signature.asc Description: OpenPGP digital signature
Re: [Debconfsubs-team] Subtitles publishing workflow
On Mon, Jun 24, 2019 at 12:02:04AM +0200, Thomas Vincent wrote: > Le 23/06/2019 à 21:17, Wouter Verhelst a écrit : > > On Sun, Jun 23, 2019 at 07:01:08PM +0200, Thomas Vincent wrote: > >> Being the one that pings the DebConf video team each time a subtitle is > >> ready, I would really love not being a SPOF anymore. > > > > :-) > > > > One way in which things could be done somewhat automatically would be to > > have a git checkout of the subs repository on vittoria which is updated > > by cron and for which some script rsyncs files to apu (which is the > > master for meetings-archive.d.n)... > > The subs repository can also be used to keep subs that are in progress. > With what you propose, I believe those unfinished subs would be > automatically published, right? > > I guess we would just have to update our current (non-)workflow to use > dedicated branches for WIP subs and keep master for the subs ready for > publication. That's probably easiest, yes. We'll also have to come up with a way to decide which sub goes into which directory. I think the easiest way to do that is to ensure that the files in the subs git repository match the files in the video archive. That would mean it would not be possible to remove files, however -- even if it is possible to tell rsync to only consider files with a given extension, I don't want to miss an option or two after an upgrade and start accidentally erasing the whole video archive. -- To the thief who stole my anti-depressants: I hope you're happy -- seen somewhere on the Internet on a photo of a billboard
Re: [Debconfsubs-team] Subtitles publishing workflow
Le 24/06/2019 à 03:24, Louis-Philippe Véronneau a écrit : > You could also add a KGB webhook to the subs repository to send messages > to the #debconf-video channel. It would really help us see the work you > do and keep up with the subs team! That's a great idea! > Our next IRC meeting is on Tuesday June 25th from 18:00 to 19:00 UTC. > I've added a point to our agenda [1] about this. Let's make it happen! > > If people from the substeam could be there (it's the first item on the > agenda) it'd be even better. I'll try to be there. Thomas signature.asc Description: OpenPGP digital signature
Re: [Debconfsubs-team] Subtitles publishing workflow
On 2019-06-23 6:02 p.m., Thomas Vincent wrote: > Le 23/06/2019 à 21:17, Wouter Verhelst a écrit : >> On Sun, Jun 23, 2019 at 07:01:08PM +0200, Thomas Vincent wrote: >>> Being the one that pings the DebConf video team each time a subtitle is >>> ready, I would really love not being a SPOF anymore. >> >> :-) >> >> One way in which things could be done somewhat automatically would be to >> have a git checkout of the subs repository on vittoria which is updated >> by cron and for which some script rsyncs files to apu (which is the >> master for meetings-archive.d.n)... > > The subs repository can also be used to keep subs that are in progress. > With what you propose, I believe those unfinished subs would be > automatically published, right? > > I guess we would just have to update our current (non-)workflow to use > dedicated branches for WIP subs and keep master for the subs ready for > publication. That'd be awesome! You could also add a KGB webhook to the subs repository to send messages to the #debconf-video channel. It would really help us see the work you do and keep up with the subs team! >> Then you'd only need to add a merge request to the archive-meta >> repository. > > That'd be great. > >> >>> Making the subs team a part of the video team (on Salsa) has already >>> been discussed last year but we never actually did it. >> >> Any idea why that is the case? > > Not really. The discussion happened off-lists and probably everyone > forgot (I know I did). Our next IRC meeting is on Tuesday June 25th from 18:00 to 19:00 UTC. I've added a point to our agenda [1] about this. Let's make it happen! If people from the substeam could be there (it's the first item on the agenda) it'd be even better. [1] http://deb.li/3aA7s | -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ signature.asc Description: OpenPGP digital signature
Re: [Debconfsubs-team] Subtitles publishing workflow
Le 23/06/2019 à 21:17, Wouter Verhelst a écrit : > On Sun, Jun 23, 2019 at 07:01:08PM +0200, Thomas Vincent wrote: >> Being the one that pings the DebConf video team each time a subtitle is >> ready, I would really love not being a SPOF anymore. > > :-) > > One way in which things could be done somewhat automatically would be to > have a git checkout of the subs repository on vittoria which is updated > by cron and for which some script rsyncs files to apu (which is the > master for meetings-archive.d.n)... The subs repository can also be used to keep subs that are in progress. With what you propose, I believe those unfinished subs would be automatically published, right? I guess we would just have to update our current (non-)workflow to use dedicated branches for WIP subs and keep master for the subs ready for publication. > > Then you'd only need to add a merge request to the archive-meta > repository. That'd be great. > >> Making the subs team a part of the video team (on Salsa) has already >> been discussed last year but we never actually did it. > > Any idea why that is the case? Not really. The discussion happened off-lists and probably everyone forgot (I know I did). Thomas signature.asc Description: OpenPGP digital signature
