Fedora-Council/tickets

The Fedora Council uses this to record ongoing work and to track issues which need a specific resolution.  |  http://fedoraproject.org/wiki/Council

#114 Finalizing Fedora mission update

Created 2 months ago by mattdm
Modified a month ago

Hi everyone. After our FAD and and the discussion on the Fedora Council Discuss mailing list, it's time to finalize this.

See

https://lists.fedoraproject.org/archives/list/council-discuss@lists.fedoraproject.org/thread/RJQWWPGDVBXPNHP6KGISKYY74CZH47UQ/

for the discussion — and

https://lists.fedoraproject.org/archives/list/council-discuss@lists.fedoraproject.org/message/OH3MKWIVRETSOPL2FKSE6YK4YIF5SZAD/

for my thread wrap-up.


For reference, here's our initial 25-word draft:

Fedora creates an innovative platform that lights up hardware, clouds, and containers for software developers and community members to build tailored solutions for their users.

From the wrap-up, I think there are three big things we need to cover. (I'll just present them, and include my own opinions in a followup comment.) Note that I'm presenting each of these independently, without list


First: there was a strong push to include something about free software and/or open source in the mission statement directly. As I noted in my wrap-up, there was not agreement on what phrase exactly to use — and not complete agreement on having it there at all.

If we do include something, I think the phrase "free software and open source" is probably our best bet:

Fedora creates an innovative, open source and free software platform that lights up hardware, clouds, and containers for software developers and community members to build tailored solutions for their users.


Second: "lights up". Looks like people want to switch this to "enables", like this:

Fedora creates an innovative platform that enables hardware, clouds, and containers for software developers and community members to build tailored solutions for their users.


Third: ordering of the statement. I don't want to do one of the radical restructurings which changes the fundamental meaning. Something more lightweight would be:

Fedora creates an innovative platform for software developers and community members to build tailored hardware, container, and cloud solutions for their users.


Administrative note: to keep things in one place, let's keep this ticket to Council member comments and if there's more discussion, continue that on https://lists.fedoraproject.org/archives/list/council-discuss@lists.fedoraproject.org/

My comments:

  1. Software freedom. My preference is to instead present the foundations clearly in parallel with the mission statement, but I won't block including it if the rest of the council feels it is important. +0 to change draft.

  2. "Lights up". I'm still not keen on enables. I think "lights up things to build on" makes sense, while "enables things to build on" doesn't. I'd almost prefer "for" — except that we already use that preposition to say who this is for. I'm -1 to just dropping in "enables", but +0 (or could be even +1) to some other phrasing which includes it.

  3. Inverting the order. Actually, my "lightweight" reordering also significantly changes the meaning by scoping the solutions developers and community members are expected to build, rather than scoping the platform as intended.

Maybe

Fedora creates an innovative platform for software developers and community members to build tailored solutions for their users on hardware, in the cloud, and in containers.

... eh. I prefer the original order, because of the scope issue. I get the idea of putting the community first, but I'm not sure it works.

Fedora creates an innovative platform that enables hardware, clouds, and containers for software developers and community members to build tailored solutions for their users.

is my preference. Focus on the platform, get off the hill of "lights up".

Software freedom. My preference is to instead present the foundations clearly in parallel with the mission statement, but I won't block including it if the rest of the council feels it is important. +0 to change draft.

I think presentation with the Four-Fs is best. I think we could spend a lot of cycles debating this language and still not get it right.

"Lights up". I'm still not keen on enables. I think "lights up things to build on" makes sense, while "enables things to build on" doesn't. I'd almost prefer "for" — except that we already use that preposition to say who this is for. I'm -1 to just dropping in "enables", but +0 (or could be even +1) to some other phrasing which includes it.

I am also -1 to dropping the concept. I'd like to hear more from people who can't parse lights up or from localizers telling us why it is bad. I feel like a lot of the responses were worried it wouldn't parse for others. I have not read the responses again recently, so I may be misremembering.

Fedora creates an innovative platform that enables hardware, clouds, and containers for software developers and community members to build tailored solutions for their users.

is my preference. Focus on the platform, get off the hill of "lights up".

I am very in favor of this structure without reordering. See above re: enables.

Also, I think we should mock up the presentation page with the final draft so we can bring this conversation to a conclusion.

So, here's a phrasing that's been bouncing around in my head:

Fedora creates an innovative platform for hardware, clouds, and containers that enables software developers and community members to build tailored solutions for their users.

It keeps the general order and drops "lights up" in favor of enables (which I still find to be a weak word, but here it's the software developers and community members enabled, rather than clouds and such).

What do you think?

Sounds good to me.

Also, I think we should mock up the presentation page with the final draft so we can bring this conversation to a conclusion.

I will do this this week. I have 1255 messages in my inbox after a couple of weeks of conferences, so, we'll see exactly when this week. :)

+1 here too, I like it.

a month ago

Metadata Update from @bex:
- Issue assigned to mattdm

Login to comment on this ticket.