Actualities for the purpose of publication

Documentation
1

I was tempted by a pun to contribute to the docs site.

Of course, I understand the difficulty (in the sense of boring drudge work, not complexity in the abstract) of processing issues and pull requests.

But is it especially unusual or unfortunate for the docs site to have 44 open PRs and 100 open issues?

I think it’s OK for (let’s say) the compiler project to get bogged down in complex (and perhaps unhelpful!) PRs.

But docs are just words.

Sometimes the words are in a language one hasn’t studied in school, let alone grown up with.

Mostly, though, one must trust the person wielding the words.

Of course, sometimes the words are unwieldy.

I would expect a docs project to ingest words readily (or lightly edited) and produce them selectively based on queries.

For the record, the requirement that my topic title, “Actualities”, have at least 15 characters is offensive to any sense of natural language and taste. I don’t deny that my revised title, “Actualities for the purpose of publication”, might, perversely, be an improvement.

1 Like
2

Unfortunate, definitely. Unusual, somewhat. It’s always been somewhat slow in the website repos since it’s never been anyone’s primary responsibility, but even so, the current numbers are unusually high.

The good news is that hugely reducing that backlog will be a top priority in the Sovereign Tech Agency work. (Reference: Scala documentation, web sites: What should be improved?)

1 Like
3

Ah, thanks. I didn’t intend to complain, I must have had a few minutes on my hands in which to wonder will A.I. help.

I don’t know who the “sovereign” is in “sovereign tech”, but please thank them.

Here in the U.S., we have no kings and queens, but only BDFL.

The B is for billionaire, obviously.

2 Likes