More Stories and Material Than We Can Publish
Good, original stories take time. They are like projects.
Today we took time to assess the amount of material we sat on last year compared to this year - material that ought to be published, eventually. We're gaining or have amassed material faster than we manage to publish. This means that sooner or later we might wish to increase publication speed and volume. We do not have to, but at the moment timing is important because of relevance and effect.
If Campinos becomes "King Of EPOnia" again (third term), it'll happen 2 years from now. So we're not particularly worried if some embarrassing stories about him are kept "in the bag" for a while longer. It's usually becoming evident when the tmke is right (in light of related events).
We recently saw people online (forums and articles) pleading for RMS to do something now that Linus Torvalds is a slop hypester. I asked an FSF contact about it, but there is no institutional message, at least not yet. If cohesive and resolute, it'll likely clarify that LLM slop isn't tolerated in GNU code/projects.
Today we thought about launching a canary subsite for suppressed material. We considered doing so some time before the twentieth anniversary, which is coming soon. There are pros and cons, but unless the pros vastly outweigh the cons, we are in no hurry.
One thing is for sure though; we can and probably should publish more (in quality, quantity, and frequency).
Sure, quantity is a very poor yardstick if it's repetition, chaff, or slop. But quantity can equally refer to exposure and changes resulting from publication. █
Image source: Newspaper Proprietor
