On 2017-06-27 12:45, Richard Hartmann wrote: >> We should definitely install nageru onto one (or more) of the machines, >> and test it out during off hours. But only during off hours; for this >> year, we should prioritize recording on voctomix, not nageru. > I agree with prioritizating vocto for DC17; the intention of this > email was to try and build consensus if it would be possible to have > Nageru run in parallel. If it's tested in the off hours, that's also a > lot better than having the video team in one place and not testing > this. Especially built-in monitoring should be a given no matter what > system is used, long-term. Being able to quickly and automagically > make at least basic statements about things not being on fire is > incredibly valuable. > > The results would also be valuable for FOSDEM, I am sure. > > To me this is still a waste of time. We know vocto works and we know it works well. We know a lot of people are also using it, making it a good choice for at least the next few years. It indeed has shortcomings in term of hardware, but to me that's not a big deal: we can always buy more stuff if we really need it. More than anything else, our time is the most precious resource we have. If we have energy to dev and test during DebConf17, we should work on areas where we are actually having problems: * We still don't have any good audio kit that we own and can ship * Our reviewing system is less that ideal (wouter worked on something, but we still need to actually test it and see it for ourselves) * Our steaming system is also problematic (olasd working on it, but I'm sure he would welcome some more help) * We want to ship all of our stuff in all-in-one travel cases, but we are nowhere near that And I could name another 10 things that we should streamline wayyyy before even thinking about testing a replacement for our perfectly good and working Vocto setup. I know I may sound a bit pissed, but we hardly have time to train and manage our volunteers during DebConf... It would be nice to continue going forward and build something coherent instead of going back on technical decisions we already made a while ago. -- pollo
Attachment:
signature.asc
Description: OpenPGP digital signature