Hi,
I would like to add two candidates for the "Outcome" column that could
be combined into one:
========
Summary: It is easy to download, configure and install Fedora Server for
[insert list of standard use cases here, e.g. LAMP, container image
registry].
Supports: Vision
How it supports: It needs to be easy to get Fedora Server and actually
install it.
How to measure: Number of steps required to go from nothing to a
complete installation (should be minimized), this includes finding the
right deliverable and configuring/installing. This very likely needs to
be minimized by avoiding wizard patterns and making sure the process is
streamlined as much as possible (reference: Cockpit design goals).
========
Similar to the above, but the other side of the coin: development
Summary: It is easy and quick to test and deliver changes to existing
software in Fedora Server. [pick specific use cases here to make it more
concrete?]
Supports: Mission
How it supports: Easier update process lowers contribution threshold and
overhead, testing is essential to minimize bugs and developer
frustration - build and maintain the ideal ecosystem!
How to measure: Number of steps required to take an upstream software
change, run integration tests and have it available to users.
========
Overarching goal: The other side of CD/CI, help devs from the distro side.
-Dominik
On 09/07/2016 08:38 PM, Stephen Gallagher wrote:
OK, at last week's meeting, we settled on our new Mission and
Vision statement,
which compromises the "Impact" portion of the Kellogg Logic Model. This is one
half of the "effects" side of the diagram (the set of things we indirectly
influence).
The other half of this is the "Outcomes" column. We need to describe a list of
outcomes that our efforts need to have in order to effect the Impact we decided on.
Outcomes *must* be measurable. We don't necessarily need to be able to measure
it today, or even a specific plan to create those measurements, but it must be
at least theoretically possible to do so.
========
(1)
Summary: A growing number of startups and other SMBs pick Fedora Server for apps
and services
Supports: Vision
How it supports: Greater participation in the ecosystem leads to better testing,
documentation and widespread knowledge availability.
How to measure: Download statistics, formal and informal polls, bugzilla reports
========
(2)
Summary: Admins are happy with default settings
Supports: Mission
How it supports: "Validated" service roles will be those conforming to default
settings.
How to measure: User surveys, news articles, bugzilla reports
========
(3)
Summary: Customers not frequently adding packages to base outside of roles
Supports: Mission
How it supports: "Validated" service roles will be those conforming to default
settings.
How to measure: Bugzilla reports, sosreport
========
(4)
Summary: Community of users contributing roles
Supports: Vision and Mission
How it supports: Greater participation in the ecosystem leads to better testing,
documentation and widespread knowledge availability. Community development will
increase number and quality of available roles as well as increased affinity to
the project.
How to measure: Number of participants involved and roles in the catalog.
========
(5)
Summary: We get buzz (Translation: increased media presence)
Supports: Vision
How it supports: The more positive reviews of Fedora Server, the more confident
that people will be in its ability to deliver what they need.
How to measure: News articles, social media analytics
These are just some starter examples; we can take or drop any of them. Other
examples of outcomes (in a similar format) are hereby solicited.
_______________________________________________
server mailing list
server(a)lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/server@lists.fedoraproject.org