qyliss changed the topic of #spectrum to: A compartmentalized operating system | https://spectrum-os.org/ | Logs: https://logs.spectrum-os.org/spectrum/
klltkr has quit [Ping timeout: 265 seconds]
andi- has quit [*.net *.split]
vladimir-lu[m] has quit [*.net *.split]
manveru has quit [*.net *.split]
leah2 has quit [*.net *.split]
andi- has joined #spectrum
leah2 has joined #spectrum
manveru has joined #spectrum
vladimir-lu[m] has joined #spectrum
leah2 has quit [Max SendQ exceeded]
leah2 has joined #spectrum
cole-h has quit [Quit: Goodbye]
cole-h has joined #spectrum
ghavil has quit [Ping timeout: 256 seconds]
ghavil has joined #spectrum
klltkr has joined #spectrum
klltkr has quit [Read error: Connection reset by peer]
<Profpatsch> qyliss: As a casual lurker I liked the status report very much, especially the high level technical overview of what was done.
klltkr has joined #spectrum
<Profpatsch> I can see a funder liking the format very much as well, because it’s a small time investment and gives a concise overview that is really quite impressive
<Profpatsch> Small time investment for the (potential) funder, which is something worth optimizing for.
<Profpatsch> Pretty certain a weekly status update would only be read by potential contributors, not investors.
<samueldr> talking from my experience, weekly could be too short to have enough material to write about, but I personally think having a periodic scheduled post really helps
<samueldr> because I know that, personally, without a schedule I just wait until "I have enough to write about" and end up with too much to write about and declare post backruptcy
<samueldr> while if there is a scheduled periodicity, it also helps me see in restrospect what I did, and realize I didn't do "nothing" as sometimes it feels :)
<qyliss> samueldr: the weekly one for last week was like 1800 words lol
<MichaelRaskin> You seemed quite happy not having to compress it
<qyliss> but I will try to keep collating them into higher level status updates occasionally
<qyliss> yeah it was nice to be able to just write and send in a single pass
<qyliss> But I'm also fine with weekly status updates where I say "I accomplished very little this week"
<qyliss> (Which this week's might be, the way it's going...)
<Profpatsch> Which is never true tho, is it
<MichaelRaskin> «I accomplished very little this week.» — qyliss started. One thousand words and one thousand lines of corresponding crosvm diffs later…
<Profpatsch> some people are modest like that
<samueldr> I think it also helps and matters what the audience and tone here
<MichaelRaskin> I guess the problem is when one needs to read a few thousands of other people's diffs and extract what the hell is going on — it is easy to underestimate the amount of achievement there
<qyliss> Yeah, the audience for the weekly updates is rather different
<qyliss> (Which is why I post them to the mailing list and not my blog)
<qyliss> And that's true, MichaelRaskin. I have spent most of this week so far reading various kernel mailing list threads.
<Profpatsch> that’s why LWN is so awesome
<qyliss> Yeah LWN is great
<qyliss> (When there's an appropriate article)
<qyliss> I'm a very happy subscriber
<Profpatsch> same
<qyliss> My hit rate there with the stuff I'm currently looking at is fairly low, sadly
<qyliss> Most recently I had to figure out how to use the udmabuf API (not the external module with the same name you'll find through a web search) largely by just reading the kernel tests
<qyliss> There's a mailing list thread I eventually found with a tiny amount of documentation, but that patch was never applied for some reason.
klltkr has quit [Ping timeout: 256 seconds]
<MichaelRaskin> The nice part of tests is that it is usually easier to check for bitrot than with other kinds of usage examples…
Madars has joined #spectrum