On 6 September 2016 at 10:00, Stephen Gallagher <sgallagh(a)redhat.com> wrote:
On 08/23/2016 12:14 PM, Stephen Gallagher wrote:
> We need to discuss our new plans going forward for the Fedora Server Edition.
> Fedora has started adopting the Kellogg Logic Model for planning purposes. At
> this year's Flock in Kraków, Poland, we started this process with the people who
> were present.
> I put together a Kanban board as an imperfect visualization of this
> discussion so we can use that. In a proper visualization of the model, all of
> the cards would have arrows pointing to the column to their right to indicate
> which card they were implementing.
> I'd like to continue this exercise with the larger Server SIG audience on this
> mailing list. We will go through five unique phases, each corresponding to the
> five columns in the Kellogg Logic Model from right to left (so we will start at
> the rightmost column, "Impact" and then proceed through
> "Activities", and "Resources in order).
> This thread will begin with "Impact". In the Kellogg Logic Model, this is
> high-level change we want to effect in the world. An analogue to this in our
> original PRD would be our Mission and Vision statements.
> At Flock, we summarized (and shortened) the Vision and Mission as follows:
> * Vision: Admins default to choosing Fedora Server as a deployment platform for
> apps and services
> * Mission: Produce common base and server roles (best practices in a can)
> So let's start by discussing these. Do we like these as our long-term end goals?
> Should they be more specific or more vague?
Sorry folks, I meant to send a follow-up about this last Wednesday and it
completely slipped my mind. We had a very lively discussion at the last meeting
as we tried to decide on a Vision Statement for the Server Edition.
I won't attempt to recreate the complete discussion here (the logs are
available if you want to read through them). I'll summarize approximately
where we left off though.
We were attempting to work from this draft:
"Anyone should be able to confidently obtain, configure and deploy software
services that address their needs using readily-available and trustworthy recipes."
There was concern that this is too long. Stephen Smoogen noted that it wouldn't
fit within a tweet, which is *probably* a decent metric for a sound-bite like
this needs to be.
A number of attempts were made to shorten it up a little, but as Vinny pointed
out, we were rapidly approaching "Anyone should address their needs" levels of
For the most part, people seemed generally in favor of the message this was
offering, so now we're basically down to painting the bikeshed of the exact
wording. Help welcome from all corners.
We should also start working on the Mission Statement in parallel. Where a
Vision is "a declaration of an organization's objectives, ideally based on
economic foresight, intended to guide its internal decision-making.", a Mission
is "a statement which is used as a way of communicating the purpose of the
organization." So our Vision shows us the change we want to see in the world and
our Mission should describe what the purpose of Server Edition is in
Our previous mission statement does not really accomplish that in any meaningful
way: "Fedora Server is a common base platform with "featured server roles"
on top of it. We commit to produce, test, and distribute these server roles."
I'd like to suggest a starting point (or straw-man, if you prefer):
Fedora Server's Mission is "To be the platform of innovation for building the
services of the next era in computing."
I have a hard time seeing the difference between most mission and
vision statements. The previous mission statement seemed something
that could be clearly accomplished and measured against. The straw man
seems to be something that could both always be met and never be met.
[My autistic filters are very high today so if I am seeing something
obvious I apologize.] Here is my straw man which I can better parse
but realize it needs a lot of work or can be thrown away.
Fedora Server is the common base platform for tested service roles
meeting the needs of old and cutting edge computing.
The goal of this is to say that we realize that our customer base for
services are wanting things that fit older technologies but also
cutting edge paradigms. They may want a print server (old technology)
but working with newer style printers and configurations (docker for
some reason) that a slower enterprise Linux isn't hitting. They may
want an email server but also a microservice controller for IOT
Stephen J Smoogen.