Hi Otto,
On Thu, Nov 25, 2021 at 2:27 AM Otto Urpelainen <oturpe@xxxxxx> wrote:
Blaise Pabon kirjoitti 25.11.2021 klo 5.43:
<snip>
When the docs were migrated, the intent was, of course, to make them
better, not worse. If things have regressed in some way, I would like to
fix them. Could you be more specific, in what ways the new docs less
useful? Is there some particular content in the retired wiki pages that
is not available at docs.fp.o, or what is the problem?
TL;DR: We could mitigate a pervasive "works-on-my-machine" anti-pattern with a few simple measures.
(Two years earlier....)
After 30 years at the fringe of Open Source, I decided to throw myself into the Fedora community and find ways to contribute. I observed a few common anti-patterns. "works-on-my-machine" happens when there is no distinction between internal and external behavior. So, a developer has no guidance on how to describe {{ process | artifact }} to an external stakeholder.
Looking at the current state, one thing I notice it that currently, the
"Joining the Package Maintainers" page barely mentions sponsorship. This
is fallout from trying to make that page sound less like you have to
submit a new package to join, previously it was discussed in the "Adding
a new package" section, which is now a separate page. I will add a note
with a link in the Joining page summary, so that part is clear from the
outset.
These links include examples.
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
