abathur has quit [Read error: Connection reset by peer]
abathur has joined #nixos-dev
<Profpatsch>
It feels to me like blaggacao desperately wants to help, but mostly just ties up contributors in very extensive discussions that are not super useful https://github.com/NixOS/rfcs/pull/77
<{^_^}>
rfcs#77 (by blaggacao, 2 days ago, open): [RFC 0077] Stale Issues Amendement
<Profpatsch>
Like holy hell, this is a discussion about making stale bot hit after 90 instead of 180 days, and it’s been going on for a million pages
<Profpatsch>
who is producing all that text, why, and what could they be doing instead
evanjs- has joined #nixos-dev
cransom has quit [Quit: WeeChat 2.7.1]
evanjs has quit [Ping timeout: 256 seconds]
cransom has joined #nixos-dev
<niksnut>
Profpatsch: so you're not volunteering to be a shepherd? :p
<Profpatsch>
Okay, I want to say I think it’s fantastic that this NixCon is done with a free software stack
<Profpatsch>
Super cool!
<Profpatsch>
worldofpeace++
<{^_^}>
worldofpeace's karma got increased to 202
<niksnut>
yeah very cool
<Raito_Bezarius>
worldofpeace++
<{^_^}>
worldofpeace's karma got increased to 203
<Raito_Bezarius>
and also is using somewhat Nix :p
bhipple has joined #nixos-dev
<ryantm>
Agreeing strongly with Profpatsch about blaggacao.
niksnut has quit [Quit: Lost terminal]
niksnut has joined #nixos-dev
<abathur>
I've had this thought as well
saschagrunert has quit [Quit: Leaving]
alp has joined #nixos-dev
tv has quit [Ping timeout: 260 seconds]
cole-h has joined #nixos-dev
tv has joined #nixos-dev
<zimbatm>
same here, but I have seen code contributions as well so it's not just talk
ris has joined #nixos-dev
jonringer_ has joined #nixos-dev
<abathur>
<3 zimbatm
<{^_^}>
zimbatm's karma got increased to 19
<srhb>
We've had great luck with mavenix in our (admittedly) small projects.
<srhb>
Oops, wrong channel
vcunat has quit [Ping timeout: 272 seconds]
vcunat has joined #nixos-dev
tilpner has quit [Ping timeout: 264 seconds]
orivej has joined #nixos-dev
<ajs124>
if a package (multiple versions in nixpkgs) reached EOL a year ago, but wasn't dropped, is it ok to backport the commit that dropped it to a release?
alp has quit [Remote host closed the connection]
alp_ has joined #nixos-dev
<gchristensen>
imo no but maybe mark it as insecure
<jonringer_>
generally no, if there's known CVEs, just mark it as insecure
<jonringer_>
oh
<jonringer_>
gchristensen++
<{^_^}>
gchristensen's karma got increased to 351
<gchristensen>
jonringer_++ :)
<{^_^}>
jonringer_'s karma got increased to 0x1
orivej_ has joined #nixos-dev
orivej has quit [Ping timeout: 272 seconds]
jonringer_ has quit [Quit: Leaving]
<ajs124>
so #100159 should only be merged without dropping asterisk_15, then…
rajivr has quit [Quit: Connection closed for inactivity]
abathur has quit [Read error: Connection reset by peer]
abathur has joined #nixos-dev
__monty__ has joined #nixos-dev
alp_ has quit [Ping timeout: 258 seconds]
alp_ has joined #nixos-dev
<das_j>
heck
orivej_ has quit [Ping timeout: 272 seconds]
<maralorn>
Are there any plans to change the way the manuals are structured and rendered, soon? Because peti is really annoyed, that the Haskell section has no table of contents anymore (and that links to it got broken in june).
<maralorn>
So what he is proposing now is moving all of the Haskell documentation out of the nixpkgs manual and put it on read the docs.
<maralorn>
cole-h: Yes. His comment was the last one. That's mainly the reason why he wants to move away. "people broke our manual and they don‘t care."
<arianvp>
opened a ticket
<arianvp>
lets see
<cole-h>
maralorn: Does he have examples of broken links?
<cole-h>
And is updating them not a possibility?
<cole-h>
Ah, I see. You can't link to sub-sub-headers (e.g. "15.9.2.3. How to install a compiler with libraries, hoogle and documentation indexes")
<cole-h>
maralorn: If he can't be persuaded away from using read the docs, at least ensure he doesn't remove the docs from Nixpkgs entirely (and maybe only adds a link to the new docs) to keep git history intact.
<maralorn>
cole-h: Yeah, that's a good idea.
tilpner has joined #nixos-dev
cole-h has quit [Ping timeout: 272 seconds]
<maralorn>
cole-h: Well, we talked about that. I have revised my opinion.
<maralorn>
I think having two documentations in different states would be more harmful.
<maralorn>
People would probably find out-dated information in the nixpkgs manual without seeing the warning at the beginn of the large section.
FRidh has quit [Quit: Konversation terminated!]
alp_ has quit [Ping timeout: 272 seconds]
<andi->
arianvp: thats a know issue. I've reported it multiple times to them... They are aware but not on the roadmpa...
<samueldr>
to me it smells like those unicorns (from taking too much time) are a bad optimization so that queries "always return in less than X seconds"
tv has quit [Read error: Connection reset by peer]
<samueldr>
see, our graph is all green, all answered under 15 seconds! (not pointed out: time outs in 15s)
alp_ has joined #nixos-dev
<abathur>
I think you're saying general AI won't be invented by AI researchers, but will be an emergent property of someone dogfooding their own APM?
<arianvp>
andi-: what exactly is not on the roadmap?
<arianvp>
search not working?
tv has joined #nixos-dev
__Sander__ has quit [Quit: Konversation terminated!]
<gchristensen>
samueldr: on the other hand, aggressively killing things at 15s is a useful way to limit damage
<gchristensen>
s/is/may be/
justanotheruser has quit [Ping timeout: 272 seconds]
<samueldr>
it's all a balance act, but timeouts these days are veering into the unhelpful too short way too often
<gchristensen>
yeah.
vcunat has quit [Ping timeout: 272 seconds]
vcunat has joined #nixos-dev
bhipple has quit [Remote host closed the connection]
vcunat has quit [Quit: Leaving.]
__monty__ has quit [Quit: leaving]
orivej has joined #nixos-dev
justanotheruser has joined #nixos-dev
avn has quit [Read error: Connection reset by peer]