<adisbladis[m]>
I don't know if that's applicable for us?
<makefu>
adisbladis[m]: i am not totally sure who is "they" but i guess the user, not the distributor
<makefu>
so my guess is that it is a nonfree license similar to the virtualbox oracle extensions
<makefu>
or more precise nonfree-redistributable
<makefu>
however i am not a lawyer, so i might be wrong
__Sander__ has joined #nixos-dev
ckauhaus has joined #nixos-dev
__Sander__ has quit [Read error: Connection timed out]
__Sander__ has joined #nixos-dev
__Sander__ has quit [Client Quit]
__Sander__ has joined #nixos-dev
tilpner has quit [Ping timeout: 264 seconds]
goibhniu has joined #nixos-dev
sphalerit has quit [Ping timeout: 245 seconds]
florianjacob has quit [Ping timeout: 245 seconds]
florianjacob has joined #nixos-dev
sphalerit has joined #nixos-dev
hiberno has quit [Quit: WeeChat 1.6]
goibhniu has quit [Ping timeout: 260 seconds]
goibhniu has joined #nixos-dev
vcunat has joined #nixos-dev
MichaelRaskin has quit [Quit: MichaelRaskin]
flokli has quit [Quit: WeeChat 2.0.1]
flokli has joined #nixos-dev
hiberno has joined #nixos-dev
<adisbladis[m]>
makefu: Yeah I'm very uncertain..
<makefu>
adisbladis[m]: according to the LICENSE file "TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION" - apache2 license
viric has quit [Read error: Connection reset by peer]
viric has joined #nixos-dev
<makefu>
the link to the licensing states "If you intend to use our technology on your Android smartphones and tablets, please access our website and check how to use it."
<adisbladis[m]>
Yeah I find it very confusing who actually needs to do that certification process
<srhb>
Is someone able to select timeout from builds where id = 73497724; ?
<niksnut>
can't wait to use -std=c++2a :p
<srhb>
Curious whether the meta change actually affects Hydra correctly.
<niksnut>
sure
<gchristensen>
whoa, hydra will read the timeout from the meta? cool :D
<srhb>
niksnut: Thanks! :)
<srhb>
gchristensen: Hopefully.
<niksnut>
timeout = 86400
<gchristensen>
for all its warts, Hydra is a beast to be reckoned with
<srhb>
We attempted to give chromium a buttload of extra time so we don't run into that annoyance again.
<srhb>
niksnut: Nice, at least the tables are updated correctly then. :)
<srhb>
gchristensen: Yes it is.
phreedom has quit [Ping timeout: 255 seconds]
<angerman>
so I'm still a bit confused. I am supposed to rebase my changes onto the unstable-channel, right? But I'm supposed to perform a PR against master, no? What's the usual workflow here?
<timokau[m]>
Ideally you develop, test and PR against master
<timokau[m]>
Practically rebuilding can take a long time, so you develop against unstable to use the binary cache
<sphalerite>
angerman: develop from your choice of unstable branches, PR against master (except for mass-rebuilds)
<gchristensen>
who wants to write up some docs? =)
<sphalerite>
angerman: most of the time you won't get any conflicting stuff between unstable and master.