<domenkozar>
could I ask you to add a comment on PR and add 1-2 sentances that you think summarize the content?>
<timokau[m]>
domenkozar: sure
<domenkozar>
I'm thinking to have a predicate for sending weekly for minimal 10 posts
<domenkozar>
thoughts?
<domenkozar>
posts == entries
<timokau[m]>
Personally I'd prefer regularity, even if some issues are very light
<srhb>
It was suggested earlier to have a ~maximum per week to avoid running into a minimum, I think that was a good idea. :)
<domenkozar>
that's hard to balance
<domenkozar>
what if we get one week 30 posts?
<domenkozar>
and max is 10?
<timokau[m]>
And if we're lacking content, we could include features major software updates (in a section at the end)
<domenkozar>
we might get a queue that gets longer and longer
<domenkozar>
yeah I was also for light issues
<domenkozar>
but then it's quite some work to push one out
<domenkozar>
maybe I should focus more effort to make it easier to publish
<domenkozar>
and then we just push 3 entries
<timokau[m]>
Why is it a lot of effort?
<domenkozar>
it's not automated yet
<domenkozar>
I think if everyone wrote the entries in given format
<domenkozar>
with summary
<domenkozar>
that would remove half of the work
<LnL>
yeah, decoding was broken for a bit
<LnL>
err, scrollback
<domenkozar>
:D
<srhb>
LnL: Welcome to the present! :-)
<domenkozar>
at least I have documented step by step workflow now
<domenkozar>
so each issue should be easier :)
<timokau[m]>
Nice :) Maybe in the long run we can further automate it or distribute the work
<domenkozar>
I don't think it scales with people :)
<domenkozar>
if we get formatting right and some automation, I think it's going to be ~30min per week
<domenkozar>
which is really good :)
<ekleog>
domenkozar: fwiw, I'm in favor of regularity over quantity too, even if some day that means sending a NixOS Weekly empty with just “don't forget to send your news to NixOS Weekly!”
<domenkozar>
aight :)
<ekleog>
and +1 to automation :) ideally we could just PR the additions to a repo, you click on “merge” for all good ones, have the CI auto-deploy as a website on each merge, and finally just have to click a button to send a notice to the discourse / add a RSS entry :)
<domenkozar>
yeah that's all there, but most people don't send PRs :)
<timokau[m]>
domenkozar: an easy way to scale would be to just take turns
<domenkozar>
I think I'll phrase to prefer PRs over issue comments
<timokau[m]>
Lots of PRs on a couple of lines of markdown might introduce a lot of conflicts though
<domenkozar>
timokau[m]: garbas tried that but it's kind of hard, I think routines are easier to build as a single person than collectively
<ekleog>
oh, it's possible to send a PR right now? I thought we were supposed to only comment on the grouping PR
<timokau[m]>
domenkozar: True, maybe when its more mature (and if its necessary)
<ekleog>
timokau[m]: if the file is split into 1 file per news, it's OK (and I'm not sure the order matters much apart from categories, that could be handled by prefixing the file names)
<timokau[m]>
ekleog: you're right, if the order doesn't matter it is easy(er)
<infinisil>
I'll argue again for including interesting PR's, even if they're no RFC or merged yet
<garbas>
domenkozar: timokau[m]: i also thought rotating ppl would work, but for some reason it doesnt. since you then need somebody to remind that it is a day to send weekly out. then it is easier to just send the weekly out :)
<garbas>
domenkozar: also +1 on having weekly news be regular
<garbas>
it would be also nice to automate some of the "news" via scripts
<garbas>
eg.
<garbas>
(1) welcome new contributors since last weekly news
<garbas>
(2) questions asked on stackover flow and discourse
<garbas>
(3) since RFCs are become a thing now, it would be nice to have a "Status of RFCs" section
<garbas>
i guess all of the above should be scriptable
<domenkozar>
right now I need to automate existing stuff
<domenkozar>
rather than add more things
<domenkozar>
and get more word around :)
<domenkozar>
the last thing I'd like to do is summarize status of RFCs :P
<domenkozar>
happy to publish those that need attention
<garbas>
+1 feel you there. i guess you can include what you need help automating in weekly :)
<domenkozar>
infinisil: oh I never intended to say that's discouraged
<domenkozar>
ok so seems like everyone is for making weekly regular
<domenkozar>
I'll work then on getting automation in place
<domenkozar>
and then we can add things
<ekleog>
<domenkozar> the last thing I'd like to do is summarize status of RFCs :P <-- it's time to push for https://github.com/NixOS/rfcs/pull/18 to land :D
<Dezgeg>
same thing with 'clang -o test.ast test.c'
<layus>
Ouch, i cheched and it indeed appears that the mechanism our project relies on does not work...
<layus>
We were just lucky that precompiled headers and ast files are the same for clang
<layus>
Dezgeg, thanks for checking
<Dezgeg>
hah :D
<layus>
My issue remains however because now I want the wrapper to understand -emit-ast. Should be fairly easy to PR however :-)
pie_ has quit [Ping timeout: 240 seconds]
<makefu>
ekleog: wow i really went deep into the rabbit hole today ... found out my reader is only supported by libnfc, hat to package ifdnfc for this. now at least pcsc_scan works. lets see if i can get gp working
<ekleog>
wow :) g'luck! I could get gp to recognize and list my card, but I'm currently having issues figuring out the keys to use to access the card, so past the point where `gp -l` detects your card I won't be able to help you much :/