Council/council-docs
1
0
Fork 0
Code Issues 8 Pull requests Projects Releases Packages Wiki Activity Actions

Include Fedora's place in the FOSS eco system somewhere in docs #84

New issue
Closed
opened 2020-08-12 12:07:55 +00:00 by ankursinha · 12 comments
ankursinha commented 2020-08-12 12:07:55 +00:00
Contributor
Copy link

We're seeing quite a few newcomers come in and ask "what can I code"? They're not clear on what it is the community really does---how we generate all our outputs.

So, we need to keep explaining to them how Fedora is a community that produces a downstream Linux distribution, and so we don't write all the software that we include in our deliverables---rather we take software from upstream developers and make it available to users; and the only software we write is to enable to community to pursue its projects.

Can this, Fedora's place in the FOSS eco system, be documented somewhere? The "project" docs would be the ideal place in my book.

https://fedoraproject.org/wiki/Staying_close_to_upstream_projects

We're seeing quite a few newcomers come in and ask "what can I code"? They're not clear on what it is the community really does---how we generate all our outputs. So, we need to keep explaining to them how Fedora is a community that produces a downstream Linux distribution, and so we don't write all the software that we include in our deliverables---rather we take software from upstream developers and make it available to users; and the only software we write is to enable to community to pursue its projects. Can this, Fedora's place in the FOSS eco system, be documented somewhere? The "project" docs would be the ideal place in my book. https://fedoraproject.org/wiki/Staying_close_to_upstream_projects
jflory7 commented 2020-08-12 12:11:42 +00:00
Contributor
Copy link

I am most focused on #67 and getting that figured out right now. But after that, I may have capacity to take on this ticket. I have personal motivations to see this get documented publicly too!

I am most focused on #67 and getting that figured out right now. But after that, I may have capacity to take on this ticket. I have personal motivations to see this get documented publicly too!
alciregi commented 2020-08-12 12:46:16 +00:00
Copy link

Just another point of view of the same issue.
I see (I imagine, I suppose) that there is a lack of newcomers interested in other aspect of the community. For the same reason, maybe.
People see a GNU/Linux distribution mainly as a stuff for IT folks. IT folks aka developers and sysadmins.

So a newcomer thinks that coding and sysadmin/sysop skills are needed in order to contribute.

In example:

  • persona A: proficient in language X, technology enthusiast
  • persona B: proficient in design & videomaking; they like GNU/Linux, simple user

Persona A: "I want to contribute to development (writing lines of code)". So, "I join the community looking to write code in my favourite programming language." Whoops, in order to write code there are more possibilities upstream.

Persona B: they are not aware that in the community there is room for design skills as well; they think that the Fedora Project is a place for technology experts only, devs, sysadmins and so on. They will never get in touch with the community.

Just another point of view of the same issue. I see (I imagine, I suppose) that there is a lack of newcomers interested in other aspect of the community. For the same reason, maybe. People see a GNU/Linux distribution mainly as a stuff for IT folks. IT folks aka developers and sysadmins. So a newcomer thinks that coding and sysadmin/sysop skills are needed in order to contribute. In example: - persona A: proficient in language X, technology enthusiast - persona B: proficient in design & videomaking; they like GNU/Linux, simple user Persona A: "I want to contribute to development (writing lines of code)". So, "I join the community looking to write code in my favourite programming language." Whoops, in order to write code there are more possibilities _upstream_. Persona B: they are not aware that in the community there is room for design skills as well; they think that the Fedora Project is a place for technology experts only, devs, sysadmins and so on. They will never get in touch with the community.
mattdm commented 2020-08-12 15:26:52 +00:00
Contributor
Copy link

Kind of a "what does fedora actually do" document, with an emphasis on places to get involved?

Kind of a "what does fedora actually do" document, with an emphasis on places to get involved?
mattdm commented 2020-08-12 15:33:04 +00:00
Contributor
Copy link

We have the Fedora Council's Guiding Policy, but it's a little ... abstract, and really more meant for internal guidance rather than as an explanation to new contributors.

We have [the Fedora Council's Guiding Policy](https://docs.fedoraproject.org/en-US/council/policy/guiding-policy/), but it's a little ... abstract, and really more meant for internal guidance rather than as an explanation to new contributors.
jflory7 commented 2021-02-10 20:43:55 +00:00
Contributor
Copy link

Metadata Update from @jflory7:

  • Issue assigned to jflory7
  • Issue priority set to: waiting on assignee
  • Issue tagged with: type - new docs
**Metadata Update from @jflory7**: - Issue assigned to jflory7 - Issue priority set to: waiting on assignee - Issue tagged with: type - new docs
jflory7 commented 2021-02-10 20:45:38 +00:00
Contributor
Copy link

I am seeing more reasons and situations where having this information documented is valuable. I will take this as my last major docs contribution in the D&I Advisor role before stepping down in Fedora 34.

I am seeing more reasons and situations where having this information documented is valuable. I will take this as my last major docs contribution in the D&I Advisor role before stepping down in Fedora 34.
jflory7 commented 2025-02-15 04:06:13 +00:00
Contributor
Copy link

Draft document of a Fedora Project docs page titled "Upstream First: A Core Fedora Principle". The page describes the concept of "upstream first" in open source development, Fedora's commitment to it, its benefits, and examples. It features a sidebar navigation menu and Fedora project branding.

[![Draft document of a Fedora Project docs page titled "Upstream First: A Core Fedora Principle". The page describes the concept of "upstream first" in open source development, Fedora's commitment to it, its benefits, and examples. It features a sidebar navigation menu and Fedora project branding.](/Fedora-Council/council-docs/issue/raw/files/fbf86b1225b4743884378d70feee4318ece2835cc427ac1afa2db52b7f9a213a-Screenshot_2025-02-14_at_23-04-31_Upstream_First_A_Core_Fedora_Principle_Local_Preview.png)](/Fedora-Council/council-docs/issue/raw/files/fbf86b1225b4743884378d70feee4318ece2835cc427ac1afa2db52b7f9a213a-Screenshot_2025-02-14_at_23-04-31_Upstream_First_A_Core_Fedora_Principle_Local_Preview.png "Draft document of a Fedora Project docs page titled \"Upstream First: A Core Fedora Principle\". The page describes the concept of \"upstream first\" in open source development, Fedora's commitment to it, its benefits, and examples. It features a sidebar navigation menu and Fedora project branding.")
jflory7 commented 2025-02-15 04:07:39 +00:00
Contributor
Copy link

Metadata Update from @jflory7:

  • Issue priority set to: next meeting (was: waiting on assignee)
**Metadata Update from @jflory7**: - Issue priority set to: next meeting (was: waiting on assignee)
jflory7 commented 2025-02-15 04:07:53 +00:00
Contributor
Copy link

Closed by #244.

Closed by #244.
jflory7 commented 2025-04-02 15:22:48 +00:00
Contributor
Copy link

#244 is merged. I am closing this issue as complete. Thanks everyone for the feedback over the last two months!

#244 is merged. I am closing this issue as `complete`. Thanks everyone for the feedback over the last two months!
jflory7 commented 2025-04-02 15:22:50 +00:00
Contributor
Copy link

Metadata Update from @jflory7:

  • Issue close_status updated to: complete
  • Issue status updated to: Closed (was: Open)
**Metadata Update from @jflory7**: - Issue close_status updated to: complete - Issue status updated to: Closed (was: Open)
jflory7 commented 2025-04-04 11:53:08 +00:00
Contributor
Copy link

https://docs.fedoraproject.org/en-US/project/upstream-first/

https://docs.fedoraproject.org/en-US/project/upstream-first/
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
edition_policy_change
youtube_proposal
stg
No results found.
Labels
Clear labels   
blocked

Progress blocked by another task or issue

  
Closed As
complete
Closed with the reason of complete

  
Closed As
duplicate
Closed with the reason of duplicate

  
Closed As
insufficient data
Closed with the reason of insufficient data

  
Closed As
moved
Closed with the reason of moved

  
Closed As
not possible
Closed with the reason of not possible

  
Closed As
out of scope
Closed with the reason of out of scope

  
Closed As
stale
Closed with the reason of stale

  
good first issue

Good for newcomers (if you want to get involved, try working on one of these!)

  
help wanted

Anyone is welcome to help us with this!

  
needs changes

Needs changes or fixes before closing

  
needs feedback

Extra attention or feedback needed

  
needs testing

Needs testing or QA before closing

  
Priority
awaiting triage
Priority of awaiting triage

  
Priority
needs review
Priority of needs review

  
Priority
next meeting
Priority of next meeting

  
Priority
waiting on assignee
Priority of waiting on assignee

  
Priority
waiting on external
Priority of waiting on external

  
type - dev tools

Related to developer tooling or build scripts

  
type - existing docs

Improves or changes existing documentation

  
type - new docs

Adds or creates new documentation

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
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
4 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Council/council-docs#84
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?