<whitequark>
josuah: what is "the doc" here? there's many different documents, some of which I'm actively working on
<whitequark>
ah, I see from the context now
<whitequark>
I'm going to bring the level of documentation to where it should be in the coming months; and Chipflow is in the process of hiring another person who will be assisting me in that
<whitequark>
byteit101: I think it's better to give a direct "no" than to have someone write a PR that's not going to be merged
<whitequark>
ultimately, development (including documentation development) has stalled for a long time due to my chronic illness, and this is not something I see open-source contributors respect in any meaningful way
<whitequark>
writing code demands time, reviews demand time, anything others want demands time, and time wasn't the resource I had.
<byteit101>
Even some basic javadoc/doxygen style api documentation is good for finding what exists
<whitequark>
there's docstrings in the source code as josuah mentioned. unfortunately a lot of them are out of date and sometimes flat out wrong
<byteit101>
Sure, and people (like me) were happy to help document what they have touched
<byteit101>
If you don't have time, why not let others who do have time help?
<whitequark>
the thing people don't understand is that accepting help always demands resources
<whitequark>
because that's not how anything works.
<byteit101>
sure, but it usually requires less time than doing it yourself
<whitequark>
please understand that for several years I had no time at all because I spent all day, every day, in extremely intense chronic pain to the point of barely being able to feed myself
<whitequark>
does this make things more clear?
<whitequark>
oh, and then a war started, and _while in that state_ I spent a year working on emigration, in order to, among other things, be able to continue working on open-source
<whitequark>
this wasn't me being bored of this project or something like that. this was me being *barely able to survive*. and people would still demand I put additional time (no matter how little) into whatever it is they got focused on
<byteit101>
Oh yikes that's intense! I hope things are better now
<whitequark>
yes, I got treatment that actually works, live in a country that's not mired in a pointless suicidal war, and Chipflow is employing me to work on the gosh darn documentation that you want to see improved
<whitequark>
but it didn't happen overnight
<byteit101>
horray!
<whitequark>
it's not that I don't understand your frustration. (I do! I'm probably more frustrated because I'm acutely aware of every single missing piece of docs.)
<whitequark>
it's more that I'm frankly shocked I survived to see 2023.
<whitequark>
anyway, every new piece of code, by policy, now gets merged with good docs covering it
<whitequark>
it'll take some time to go through the backlog of everything that needs updating but it will be done and done soon
<tpw_rules>
i actually might have a candidate project for it soon
<whitequark>
now that my brain doesn't float in a vat of cortisol i think i should be able to finish the design in an elegant way
<whitequark>
might or might not need a revision, idk, should actually measure the flop count first
<tpw_rules>
not sure what you mean by resurrect. idk if i can take on additional documented responsibilities but i saw some snippets recently used for the new amaranth features
<whitequark>
there hasn't been much activity on it for... a while, and iirc some of it was gated on me
<whitequark>
resurrect as in make something stationary move again
<cr1901>
Maybe I should un-bit-rot the simulator if the arch is finalized
<whitequark>
yes, there's a bunch of features in boneless (enums, mostly) that would be much nicer on newer amaranth
<whitequark>
i think i'll find out whether i can put more time into it and then ping you, tpw_rules ? and then you can decide how much if any time you want to put into it yourself
<whitequark>
I think boneless would be a cool demo design
<tpw_rules>
yeah it already was cool
<whitequark>
oh i mean like officially linked from amaranth pages
<whitequark>
or just under amaranth namespace, dunno. i want to highlight a number of cool projects, at some point
<tpw_rules>
i mean i was pretty satisfied the last time i used it. i think the official assembler needs improevement
<tpw_rules>
i wasn't depending on your contributions for it but yeah if you want to sync up later that could be cool
<whitequark>
ah gotcha, yeah
<whitequark>
i have barely any memory of that timeframe
<whitequark>
adamgreig: btw have you figured out that the github actions build docs for you in your fork?
<whitequark>
I think you need to actually enable actions and/or pages
<cr1901>
Well ~130 lines of Python generates 731 lines of Verilog. I have a 33-state Glorified Sequence Detector. Will test tomorrow to see if it works
_whitenotifier-f has quit [Ping timeout: 250 seconds]