Consider adding "Editions" wiki page to project docs #43
Labels
No labels
blocked
Closed As
complete
Closed As
duplicate
Closed As
insufficient data
Closed As
moved
Closed As
not possible
Closed As
out of scope
Closed As
stale
good first issue
help wanted
needs changes
needs feedback
needs testing
Priority
awaiting triage
Priority
needs review
Priority
next meeting
Priority
waiting on assignee
Priority
waiting on external
type - dev tools
type - existing docs
type - new docs
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Council/council-docs#43
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
There is a useful wiki page that defines what Fedora Editions are, names the current Editions, and gives a short history on them. This is a good candidate page for migrating to Fedora Docs.
My intended use case is to promote this in the organizer resource pack, which will include a section on Fedora Editions and Objectives.
I'd love to review a PR that adds this content and retains links to the working groups.
Metadata Update from @jflory7:
In a totally karmic way, this issue is still relevant nearly seven years after I originally opened it. 💀
It came up in a conversation on
#marketing:fedoraproject.orgwith @ngompa. The story itself around Editions is no longer clear to our community. We need to use this as an opportunity to modernize our story about Editions, how they are distinguished from other offerings like Spins and Labs, and most importantly, make Edition candidacy an accessible concept in the community. I think we should rightfully so have opinionated versions of Fedora that come with greater promise and reliability than a conventional Spin. I have helped build a Spin in Fedora; I could not build an Edition alone in Fedora. We should lean into making Editions a more accessible concept to our contributor community.Also, this is in direct contrast to the messaging that we originally adopted with Editions. We adopted Editions originally because the pool was getting crowded, both with high-quality and mid-quality solutions. This made Fedora easier to market in some senses, but now is an important moment to revisit whether this approach still makes sense for Fedora in 2025, and whether a modernized marketing strategy can lean into having multiple, high-quality, defined Editions in concert with each other.
I committed myself to spend time on this after Flock and DevConf CZ in June. I don't have much capacity to focus on anything else other than those two things right now. 😉
Metadata Update from @jflory7:
Metadata Update from @jflory7: