Rust docs team is no more
blog.rust-lang.org
Rust docs team is no more
1–10 of 46 posts
Re: Rust docs team is no more
#2An example of a project that is "done?"
Re: Rust docs team is no more
#3An example of a project that is "done?"
"done" in what sense? I don't think documentation of a living project is ever finished.
Re: Rust docs team is no more
#4Rust is an amazing language, and I'm glad to see they are transparent too.
Re: Rust docs team is no more
#5Good work, docs team.
Re: Rust docs team is no more
#6Begs the question: Why isn't Mozilla funding this?
> At this point, the only person really writing docs is me, and I haven't had a ton of time lately either. So we haven't had a docs team meeting since August of 2018. There also aren't really docs RFCs these days. As such, this blog post isn't really announcing the end of the docs team as much as it is describing what is already true today.
Re: Rust docs team is no more
#7An example of a project that is "done?"
"done" in what sense? I don't think documentation of a living project is ever finished.
Sure, but it sounds like docs are now updated by the relevant developers. The "docs team" sounds more like a project team to overhaul the state of docs at the time, which is now complete.
Re: Rust docs team is no more
#8The headline sounds scary, but the actual change sounds like it's merely an organizational reshuffling formality.
Re: Rust docs team is no more
#9no engineer gets hired for writing docs; engineers performance is not measured by docs; even if some do get hired, they won't get paid that well;
Re: Rust docs team is no more
#10&tldr; The docs team created filled in the gaps where they were needed when it was created. Now, the teams making the code changes handle their own docs and doc changes. There is no longer a need for a docs only team.
So, instead of having a dedicated team for docs the load has shifted to the teams responsible for the code. Sounds like a reorg more than anything.