#179 Updates to Initiatives page, including removal of failing ref to attributes.adoc file
Closed a year ago by karl0sfandang0. Opened a year ago by karl0sfandang0.
Fedora-Council/ karl0sfandang0/council-docs main  into  main

@@ -1,24 +1,28 @@ 

- include::ROOT:partial$attributes.adoc[]

- 

- = Current 12-18 Month Community Initiatives

+ = What are Community Initiatives?

  :page-aliases: objectives.adoc

  

- The primary role of the xref:council::index.adoc[Fedora Council] is to identify the short-, medium-, and long-term goals of the Fedora community and to organize and enable the project to best achieve them.

- This section documents the **medium-term** targets we've highlighted (as explained in the Council charter).

- Each Community Initiative has a designated Community Initiative Lead who is responsible for coordinating efforts to reach the Community Initiative's goals, for evaluating and reporting on progress, and for working regularly with all relevant groups in Fedora to ensure that progress is made.

+ Fedora Community Intitiatives (formerly "Objectives") contain projects which do not fall neatly into the 6 monthly Fedora release-cycle. Typically they require longer to complete. 12-18, or even up to 24 months. Community Initiatives typically are not engineering projects - although they can be - and are not necessarily aligned with a release. 

I wouldn't say "typically aren't" here. The idea mix would be 50% engineering, 50% from the rest of the project. We rarely hit that ideal mix, but that's dream.

+ 

+ The primary role of the xref:council::index.adoc[Fedora Council] is to identify the short-, medium-, and long-term goals of the Fedora community and to organize and enable the project to best achieve them. Anyone can propose a Community Initiative to the Council. To be accepted it should to align with Fedora's https://docs.fedoraproject.org/en-US/project/#_our_mission[mission statement] and long-term goals. 

+ 

+ This section documents the **medium-term** targets we, the Council, have highlighted (as explained in the Council charter). Each Community Initiative has a designated Community Initiative Lead who is responsible for coordinating efforts to reach the Community Initiative's goals, for evaluating and reporting on progress, and for working regularly with all relevant groups in Fedora to ensure that progress is made.

"this section" is no longer valid. Probably replace with an xref to the "Current Initiatives" section below and word accordingly.

I'd also explicitly mention that the Lead sits on the Council.

  

  

  [[proposing]]

  == Proposing a Community Initiative

  

- Any community member can propose a Community Initiative to the Council.

- First, discuss on the https://discussion.fedoraproject.org/tag/council[#council tag on Fedora Discussion].

- Next, if well-received, file a https://pagure.io/Fedora-Council/tickets/[ticket].

+ To propose a Community Initiative to the Council. First, discuss on the https://discussion.fedoraproject.org/tag/council[#council tag on Fedora Discussion]. Next, if well-received, file a https://pagure.io/Fedora-Council/tickets/[ticket].

This paragraph starts with a sentence fragment.

  Of course, people need to be ready to do the actual work required — a Community Initiative with no passionate bottom-liners won't get far.

  

+ To succeed, Community Initiatives ideally require a leadership team. The Council can assist a proposer in finding the right people to work on the project if required. Additionally, new Community Initiatives will be assigned an executive sponsor from amongst the Council members, to assist with raising and maintaining the visibility of the Initiative in the community.

It might be good to explicitly discuss the separation from technical leadership and organizational/project management leadership like we discussed. We could also mention that the Council will assign an existing member as an Executive Sponsor (and describe that role), but I'm not sure if it belongs here or elsewhere.

+ 

+ [[completing]]

+ == How are Community Initiatives Finalized?

+ 

+ At the end of the expected duration of the Initiative (as specified at the proposal / acceptance stage), the Council will assess the progress of the Initiative. If the all of the aims, or all of the most significant of them have been achieved the Initiative will be terminated. If the aims are close to complete and further work will substantially increase the impact it may be allowed to continue for a further agreed period, after which it will be terminated. Initiatives will not be allowed to run indefinitely.

  

  [[current]]

- == Current Community Initiatives

+ == Current 12-18 Month Community Initiatives

  

  [[websites-apps]]

  === Websites & Apps Revamp

I've made some first edits to the Initiatives page. Stopping here and creating this PR to check it's on the right track.
Signed-off-by: Karl Stevens karlosfandango64@gmail.com

I wouldn't say "typically aren't" here. The idea mix would be 50% engineering, 50% from the rest of the project. We rarely hit that ideal mix, but that's dream.

"this section" is no longer valid. Probably replace with an xref to the "Current Initiatives" section below and word accordingly.

I'd also explicitly mention that the Lead sits on the Council.

This paragraph starts with a sentence fragment.

It might be good to explicitly discuss the separation from technical leadership and organizational/project management leadership like we discussed. We could also mention that the Council will assign an existing member as an Executive Sponsor (and describe that role), but I'm not sure if it belongs here or elsewhere.

Good work @karl0sfandang0! I've left some specific comments above.

Generally, it would be better to format it one sentence per line (or SemBr...see below). AsciiDoc works like Markdown in that a single newline will not create a new paragraph. This makes changes much easier to review,

I also notice you kept a lot of the existing wording. That's fine if you like it. But also, if you think some of the wording is bad, now's a great time to propose improvements!

A note on Semantic Line Breaks (SemBr): Matthew is a big fan of Semantic Line Breaks (SemBr). This concept inserts line breaks at semantic boundaries. This makes diffs evern more useful to understand the meaning. Personally, I see the appeal, but I can't make myself write that way. Also, I think SemBr has an unintended side effect of enabling far-too-long sentences. So if you want to use SemBr, go for it! If not, I understand. It's not the official style, just a windmill mattdm tilts at from time to time. :wink:

As discussed with @bcotton. Closing this PR and opening a fresh one against a specific branch for Issue44, incorporating new edits based on comments above.

Pull-Request has been closed by karl0sfandang0

a year ago
Metadata