council/docs
council/docs
12
1
Fork 5
Code Issues 6 Pull requests 2 Projects Activity Actions

Updates to Initiatives page. #180

Merged
jflory7 merged 4 commits from issue44-initiatives into main 2026-06-09 01:55:41 +00:00
Conversation 24 Commits 4 Files changed 3 +47 -26
karl0sfandang0 commented 2023-02-20 09:58:24 +00:00
Contributor
Copy link

Removal of failing ref to attributes.adoc file.
Change side menu to "Initiatives"
Change reference "Objectives" to "Community Initiatives" on "Get Involved" page

Signed-off-by: Karl Stevens karlosfandango64@gmail.com

Removal of failing ref to attributes.adoc file. Change side menu to "Initiatives" Change reference "Objectives" to "Community Initiatives" on "Get Involved" page Signed-off-by: Karl Stevens <karlosfandango64@gmail.com>
bcotton commented 2023-02-21 21:00:46 +00:00
Contributor
Copy link

I'd like to find a better way to phrase "engineering projects and those from the wider…" but we've long struggled for a good vocabulary here. I won't block on it, but if anyone has suggestions, let's hear them!

I'd like to find a better way to phrase "engineering projects and those from the wider…" but we've long struggled for a good vocabulary here. I won't block on it, but if anyone has suggestions, let's hear them!
bcotton commented 2023-02-21 21:05:10 +00:00
Contributor
Copy link

Looks good overall, but there's a conflict that prevents merging. Looking at it locally, it seems trivial to fix. In the meantime, let's see if anyone else has feedback.

Looks good overall, but there's a conflict that prevents merging. Looking at it locally, it seems trivial to fix. In the meantime, let's see if anyone else has feedback.
jflory7 commented 2023-02-22 13:12:43 +00:00
Owner
Copy link

This should probably be xref:initiatives.adoc?

This should probably be `xref:initiatives.adoc`?
jflory7 commented 2023-02-22 13:14:12 +00:00
Owner
Copy link

"6 monthly" is somewhat confusing to me. Maybe instead, "twice annually" or "biannual"?

"6 monthly" is somewhat confusing to me. Maybe instead, "twice annually" or "biannual"?
jflory7 commented 2023-02-22 13:15:24 +00:00
Owner
Copy link

@bcotton I think we could lean into the vocabulary we have as "Mindshare projects"? I don't think it is perfect, but I think there is at least some greater recognition that this is the other "half" of the community than the things that are more strictly engineering-focused?

@bcotton I think we could lean into the vocabulary we have as "Mindshare projects"? I don't think it is perfect, but I think there is at least some greater recognition that this is the other "half" of the community than the things that are more strictly engineering-focused?
jflory7 commented 2023-02-22 13:15:58 +00:00
Owner
Copy link

Could this keep to the one sentence per line convention?

Could this keep to the [one sentence per line convention](https://asciidoctor.org/docs/asciidoc-recommended-practices/#one-sentence-per-line)?
jflory7 commented 2023-02-22 13:17:10 +00:00
Owner
Copy link

Two catches:

  • s/it should to align with/it should align with/
  • This can be expressed as a xref: xref:project.adoc#_our_mission[mission statement]
Two catches: * s/it should to align with/it should align with/ * This can be expressed as a xref: `xref:project.adoc#_our_mission[mission statement]`
jflory7 commented 2023-02-22 13:17:22 +00:00
Owner
Copy link

Metadata Update from @jflory7:

  • Pull-request tagged with: type - existing docs
**Metadata Update from @jflory7**: - Pull-request tagged with: type - existing docs
jflory7 commented 2023-02-22 13:18:20 +00:00
Owner
Copy link

Two catches:

  • Typo: s/Communitiy Initiatives/Community Initiatives/
  • Perhaps we could make this a xref while we are at it? xref:initiatives.adoc[Community Initiatives]?
Two catches: * Typo: s/Communitiy Initiatives/Community Initiatives/ * Perhaps we could make this a `xref` while we are at it? `xref:initiatives.adoc[Community Initiatives]`?
jflory7 commented 2023-02-22 13:19:07 +00:00
Owner
Copy link

This should also be one sentence per line.

This should also be [one sentence per line](https://asciidoctor.org/docs/asciidoc-recommended-practices/#one-sentence-per-line).
jflory7 commented 2023-02-22 13:19:39 +00:00
Owner
Copy link

One sentence per line here too.

[One sentence per line](https://asciidoctor.org/docs/asciidoc-recommended-practices/#one-sentence-per-line) here too.
jflory7 commented 2023-02-22 13:20:23 +00:00
Owner
Copy link

One sentence per line

[One sentence per line](https://asciidoctor.org/docs/asciidoc-recommended-practices/#one-sentence-per-line)
jflory7 commented 2023-02-22 13:20:52 +00:00
Owner
Copy link

One sentence per line

[One sentence per line](https://asciidoctor.org/docs/asciidoc-recommended-practices/#one-sentence-per-line)
bcotton commented 2023-02-22 13:23:49 +00:00
Contributor
Copy link

@bcotton I think we could lean into the vocabulary we have as "Mindshare projects"? I don't think it is perfect, but I think there is at least some greater recognition that this is the other "half" of the community than the things that are more strictly engineering-focused?

Yeah, I suppose that's the best we have.

> @bcotton I think we could lean into the vocabulary we have as "Mindshare projects"? I don't think it is perfect, but I think there is at least some greater recognition that this is the other "half" of the community than the things that are more strictly engineering-focused? Yeah, I suppose that's the best we have.
karl0sfandang0 commented 2023-02-23 13:45:22 +00:00
Author
Contributor
Copy link

rebased onto 1ce6cea9e2

rebased onto 1ce6cea9e2fb06a1341d29c0348b7051e115a7da
karl0sfandang0 commented 2023-02-24 08:06:46 +00:00
Author
Contributor
Copy link

1 new commit added

  • Amendments as per comments on PR#180
**1 new commit added** * ``Amendments as per comments on PR#180``
karl0sfandang0 commented 2023-02-24 08:11:10 +00:00
Author
Contributor
Copy link

1 new commit added

  • Missed the change needed to nav.adoc from jflory7's comment on PR #180. Fixed that here.
**1 new commit added** * ``Missed the change needed to nav.adoc from jflory7's comment on PR #180. Fixed that here.``
bcotton commented 2023-02-27 14:50:43 +00:00
Contributor
Copy link

We should probably say "Fedora Linux release cycle" here to be consistent with our messaging.

We should probably say "Fedora Linux release cycle" here to be consistent with our messaging.
bcotton commented 2023-02-27 14:51:44 +00:00
Contributor
Copy link

"Council" should be capitalized here.

"Council" should be capitalized here.
karl0sfandang0 commented 2023-02-27 21:09:59 +00:00
Author
Contributor
Copy link

1 new commit added

  • Fixing for comments on lines 14 and 26 in PR#180
**1 new commit added** * ``Fixing for comments on lines 14 and 26 in PR#180``
karl0sfandang0 commented 2023-02-27 21:10:50 +00:00
Author
Contributor
Copy link

Thanks @bcotton I've fixed for those last 2 comments now.

Thanks @bcotton I've fixed for those last 2 comments now.
bcotton commented 2023-03-02 13:11:35 +00:00
Contributor
Copy link

Merging, thanks @karl0sfandang0!

Merging, thanks @karl0sfandang0!
bcotton commented 2023-03-02 13:11:45 +00:00
Contributor
Copy link

Pull-Request has been merged by bcotton

Pull-Request has been merged by bcotton
jflory7 commented 2023-03-03 19:48:54 +00:00
Owner
Copy link

@karl0sfandang0 Thanks again for your work here!

@karl0sfandang0 Thanks again for your work here!
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
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

  
good first issue
Good tickets to begin with (if you want to get involved, try working on one of these!)

  
help wanted
Tickets where we need help or need feedback from the wider Fedora community

  
needs
changes
 Needs changes or fixes before closing

  
needs
reporter feedback
 Additional feedback or information from the reporter is needed to advance

  
needs
triage
 A repository maintainer is needed to triage this further

  
needs
vote
 A vote is required from Fedora Council members in order to advance

  
role
engineering
 Needs attention from the Council FESCo Representative

  
role
fca
 Needs attention from the Fedora Community Architect

  
role
foa
 Needs attention from the Fedora Operations Architect

  
role
fpl
 Needs attention from the Fedora Project Leader

  
role
initiative lead
 Needs attention from a Community Initiative (Co-)Lead

  
role
mindshare
 Needs attention from the Council Mindshare Committee Representative

  
scope
bug
 Something isn't working

  
scope
improvement
 Requests for something we are either repeating or improving

  
scope
new
 Requests for a new task or project

  
state
approved
 Tickets that received approval by the Fedora Council

  
state
blocked
 Cannot move forward: blocked by feedback, other tickets, etc.

  
state
duplicate
 This issue or pull request already exists

  
state
invalid
 This doesn't seem right

  
state
wontfix
 This will not be worked on

No labels
type
dev tools
type
existing docs
type
new docs
good first issue
help wanted
needs
changes
needs
reporter feedback
needs
triage
needs
vote
role
engineering
role
fca
role
foa
role
fpl
role
initiative lead
role
mindshare
scope
bug
scope
improvement
scope
new
state
approved
state
blocked
state
duplicate
state
invalid
state
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 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/docs!180
No description provided.