right, but that's independent of the tech we use.
right, but that's independent of the tech we use.
Pyou have to babysit the people that are gonna want to do that stuff anyway.
Tgiven i will daily drive bazzite when my new PC comes in, i guess i would have no problem contributing to docs
Ttrue
Jlike, no one is reading nor writing the docs no matter what we pick except nickname and me lol
Pnext time somebody does offer
Ti like reading my own docs
Plike this kind person above
Pgotta take them under your wing a bit
IYou’d be surprised
Pmake sure they're happy with putting that effort in
Tstill trying to find the justfile that involves "configure-nvidia" where i wanted to add additional kargs as i wrote in #bazzite-dev haha
Pmost people don't stick around for nothing
IA lot of people updated the stuff I was responsible for when I was at aws, and that was just “click button, make change, submit Pr
WRebasing to :testing. Got this:
Jyeah but this is nothing like our day jobs, haha
Pdocs really is a hard one and if people want to contribute they're probably gonna write the stuff up-front with little regard for how it gets hosted in the end
WCan't seem to rebase with this python error. Something weird I need to fix?
Pyou just have to be a facilitator where you can :v
JI mean, I freaking wish it was just like contributing to the k8s docs, but it's a totally different crowd
Krpm-ostree status
Tye, i wouldnt mind anything in particular, really
IThen be the half of the equation you’re missing.
Pwhat we do for the NZ:P docs is just API mirror the content from github to a server
Pand we also accept submissions from people up-front because it's not like they all use github
IU2F.garden has had a handful of people submit fixes and updates over time
Jhah. This would be like the 4th time. But I'm down if you are, if you two wanna grab what we have and make it look awesome, and it's all in github and actioned up, I'd +1 that.
Ti dont really have a problem with the lack of contributors with the docs tbh
Tthe bazzite buzz newsletter stuff on the other hand lol
Toh boy newsletter
i would really love to help, but in that regards im really bad haha
i would really love to help, but in that regards im really bad haha
Tbut docs are fine
Pi think it's better having a handful of contributors because you want your docs to be really strictly written
WIWhat’s the history on docs with bazzite/ublue?
Ptrying to bring in as many people as possible will just end up with low quality / AI submissions all over the place
Panyway
WI actually might finally be able to get rid of libldm after eliminating my windows dynamic disk.
Tthe ublue-os/website repo :dinobones:
Jreadmes first, then there was a short time of just a docs directory with markdown files, no rendering, then we had /website repo with mkdocs-material, then moved to discourse once we were large enough to qualify for their OSS plan
Tdocumenting is hard when the target audience is split down the middle. tons of new linux users here but then there's like a good chunk of users who have been using linux for a long time and want a tiling window manager image
II have a hierarchy of durability/usability of different formats, and forums and discord are all the way at the bottom of both for various reasons.
Searching discord is bad at best. Forums become… toxic if not carefully moderated.
Searching discord is bad at best. Forums become… toxic if not carefully moderated.
Tand mostly i just explain what fedora atomic desktop already does and linux gaming lol
IThat’s perfectly doable. I’ve done it many a time.
Tstuff that is kind of already documented elsewhere im sure
ISomething on the order of LineageOS’ device page would be a good reference to start with honestly
Jmoderation of the forums isn't an issue, discourse is pretty great for that. Agree with discord, but bazzite using it for user support isn't up to me. 
IFor support it’s fine so long as you don’t go “did you search first?”
JWe have a whole spiel somewhere about github being the source of truth
JDunno, I don't do support in discord, I concentrate on github and discourse, I have to be async
Iyeah.
The tl;dr of my hierarchy of documentation is
wiki > static site > text files in a git repo > bug tracker > PDFs/Docxs in a git repo > source code in a repo > Forums/Chat
The tl;dr of my hierarchy of documentation is
wiki > static site > text files in a git repo > bug tracker > PDFs/Docxs in a git repo > source code in a repo > Forums/Chat
IWiki and static site are 50/50 at the top, have tradeoffs.
