Fedora Release Tools Demo (Canceled) - Written Status
by Amanda Carter
Hi folks, due to travel and various obstacles, we're not able to host a recorded demo this month. Instead we've put together a status report that includes some additional highlights we think you might be interested in. If you have feedback and/or think this works well, I'd love to know b/c I think this vehicle covers more information than a demo alone so I might do both in the future if it's worth it.
Apologies for missing the actual show and tell - if there's anything you'd like to see specifically, I'm sure we can arrange something.
https://fedoraproject.org/wiki/ReleaseEngineering/StatusReport#13SEP2016
--
Amanda Carter
7 years
PRD Discussion: Kellogg Logic Model (Phase 2: Outcomes)
by Stephen Gallagher
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.
Back at Flock, we had a short brainstorming session and came up with a few
ideas. I'm going to try to capture them here (in a slightly more structured
approach than we had in the notes).
========
(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.
7 years, 1 month
USB writing changes: wiki instructions, tests
by Adam Williamson
Hey folks! Wanted to send a heads-up that I've made some fairly
significant changes to the wiki regarding writing Fedora to USB.
I've done (yet another) revision of the main wiki instructions for
writing USB sticks:
https://fedoraproject.org/wiki/How_to_create_and_use_Live_USB
since the Fedora Media Writer tool - the rewrite (of the rewrite?) of
LiveUSB Creator - now looks to be working well in testing, and is
available on all our target platforms, the page now heavily promotes it
as the best tool to use in almost all cases. Some other methods have
been entirely removed - FMW should be a better choice for Windows and
macOS than the tools that were listed before.
I retained sections for:
* livecd-iso-to-disk, as it's now the only tool that supports non-
destructive write and data persistence
* gnome-disk-utility, for non-Fedora *nix without Flatpak support
* dd, for non-Fedora *nix without Flatpak or GNOME and people who just
like dd
* unetbootin, because the section basically exists to explicitly state
that we don't support it (maybe we should add a similar section for
Rufus...)
Please do tell me about any problems you note, or if you think I
removed something wrongly, or anything. Note that as of right now the
best version of mediawriter for F23 and F24 is in updates-testing, so I
had the instructions to install it include `--enablerepo=updates-
testing`; I'm expecting the updates will go stable soon and we can
remove that.
For validation testing folks, I have also revised the USB validation
test cases. I really kinda hated the way the Installation matrix was
set up with test names that didn't match the test case page names for
no good reason, and also didn't think we really needed all the
different test cases, so I've consolidated them into three
consistently-named test cases with more result columns:
https://fedoraproject.org/wiki/QA:Testcase_USB_dd
https://fedoraproject.org/wiki/QA:Testcase_USB_fmw
https://fedoraproject.org/wiki/QA:Testcase_USB_litd
The effect is pretty much the same as before - except that we now
include the FMW test instead of the LiveUSB Creator test - we test all
three methods for both BIOS and UEFI and for both live and DVD images,
but it's just arranged a little differently (and, I hope, better). I
combined the separate 'live' and 'dvd' versions of the dd and litd test
cases (which were barely different at all) into single test cases, and
consolidated common wording between all the test cases using templates.
I've put this change live on the current Installation validation page -
https://fedoraproject.org/wiki/Test_Results:Fedora_25_Branched_20160930.n...
again, please let me know of any problems you see with this change :)
Thanks everyone!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
7 years, 2 months
Server SIG Meeting Minutes (2016-09-27)
by Stephen Gallagher
===================================================================
#fedora-meeting-1: Server Working Group Weekly Meeting (2016-09-27)
===================================================================
Meeting started by sgallagh at 20:00:33 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/fedora-meeting-1/2016-09-27/serversig.2...
.
Meeting summary
---------------
* Roll Call (sgallagh, 20:00:33)
* Agenda (sgallagh, 20:06:56)
* Agenda Item: Cloud/Server positioning (sgallagh, 20:07:09)
* Review the Kellogg Logic Model and discuss prioritization/assignment
(sgallagh, 20:07:17)
* Agenda Item: Beta Freeze and Testing (sgallagh, 20:07:48)
* Beta Freeze and Testing (sgallagh, 20:10:14)
* ACTION: adamw to figure out who volunteered to test AD support and
politely encourage them to do so (sgallagh, 20:13:09)
* adamw requests that anyone available should review the openQA tests
for Server and confirm they are testing a right and sufficient
amount of the required functionality (sgallagh, 20:18:49)
* Kellogg Logic Model Discussion (sgallagh, 20:24:14)
* LINK: http://kolinahr.herokuapp.com/edit/57d05a6984338834000515c9
(sgallagh, 20:26:32)
* ACTION: cmurf to start a discussion around concrete plans for cloud
images et. al. on devel@ (sgallagh, 20:53:30)
* ACTION: nirik and smooge to email server@ with additional
Activities, Outputs and Outcomes related to cloud images and SMTP.
(sgallagh, 20:54:15)
* Next week we plan to finalize the logic model. sgallagh will then
create a draft of a PRD from it (sgallagh, 20:54:45)
* Open Floor (sgallagh, 20:56:21)
Meeting ended at 21:01:45 UTC.
Action Items
------------
* adamw to figure out who volunteered to test AD support and politely
encourage them to do so
* cmurf to start a discussion around concrete plans for cloud images et.
al. on devel@
* nirik and smooge to email server@ with additional Activities, Outputs
and Outcomes related to cloud images and SMTP.
Action Items, by person
-----------------------
* adamw
* adamw to figure out who volunteered to test AD support and politely
encourage them to do so
* cmurf
* cmurf to start a discussion around concrete plans for cloud images
et. al. on devel@
* nirik
* nirik and smooge to email server@ with additional Activities,
Outputs and Outcomes related to cloud images and SMTP.
* smooge
* nirik and smooge to email server@ with additional Activities,
Outputs and Outcomes related to cloud images and SMTP.
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* sgallagh (96)
* adamw (27)
* nirik (23)
* smooge (15)
* jds2001 (14)
* zodbot (12)
* cmurf (7)
* mhayden (2)
* ssmoogen (1)
* dperpeet (0)
* mjwolf (0)
* vvaldez (0)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
7 years, 2 months
Cloud Atomic Server WGs
by Chris Murphy
Couldn't make the Cloud meeting but just skimmed the log;
cross-posting to server@ list.
How about combine Cloud and Server WGs into a new WG with three new sub groups:
hardware, cloud, atomic?
That way you get the benefit of one WG working on the big picture
stuff that enables integration among the outputs. And you get
collaboration that isn't possible by just cross posting emails on two
lists. Curation of the outputs is enhanced so they're optimal when the
products are used together, while not being exclusive to each other.
The differences are minor tweaks in terms of payload, but e.g.
cloud-init is not something most people in the Server WG probably know
much about. So most of Cloud + Server overlaps with really vertical
knowledge base needed to do the small tweaks that cause substantial
product differentiation.
On the issue of membership, anyone unavailable in the next 30 days
should be dropped. There will be another time for their participation
when they're available. I'd look into making it easy to rotate out WG
members to avoid long periods of inactivity which inhibits others'
ability to get stuff done, and avoid burn out when they've been on the
WG too long.
Maybe some WG seats should be ~18 months, and twice as many of those
would be 1 release cycle. i.e. 1/3 of the seats are longer term, and
2/3 are short term. There's sufficient stability in FESCo to make
frequent WG turnover a plus.
--
Chris Murphy
7 years, 2 months
Need someone to run 2016-09-20 meeting
by Stephen Gallagher
I am going to be in all day meetings tomorrow and won't be available to run the meeting. Would someone else mind volunteering to run the meeting and a brainstorming session on Outcomes?
7 years, 2 months
Server SIG Weekly Meeting Minutes (2016-09-20)
by Robyn Bergeron
===================================================================
#fedora-meeting-1: Server Working Group Weekly Meeting (2016-09-20)
===================================================================
Meeting started by rbergeron at 20:00:11 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting-1/2016-09-20/serversig.2...
.
Meeting summary
---------------
* Roll Call (rbergeron, 20:01:10)
* present: jds2001 smooge dperpeet mjwolf nirik (rbergeron, 20:04:11)
* Outcomes (rbergeron, 20:04:20)
* LINK:
https://meetbot.fedoraproject.org/fedora-meeting-1/2016-09-13/serversig.2...
(rbergeron, 20:04:38)
* Brainstorm Outcomes that we expect to be able to have an effect on
within one year (targeted at Flock 2017) (rbergeron, 20:05:56)
* Vision: Anyone should be able to confidently obtain, configure and
deploy software services that address their needs using
readily-available and trustworthy recipes. (rbergeron, 20:07:27)
* Mission: Fedora Server Edition is an ecosystem ideal for creating
and operating validated service roles addressing most computing
needs. (rbergeron, 20:07:38)
* LINK: https://fedoraproject.org/wiki/Server/Personas (nirik,
20:16:16)
* IDEA: Andy wants to run a file server in the office to share files
between himself and his colleagues (dperpeet, 20:18:18)
* IDEA: those files should be accessible via multiple operating
systems. (jds2001, 20:19:51)
* IDEA: It is easy to download, configure and install Fedora Server
for [role, e.g. setting up a fileserver] (dperpeet, 20:21:26)
* IDEA: the role should be usable immediately upon installation of
Fedora Server (jds2001, 20:22:17)
* IDEA: Sage needs to send and receive emails for a small group.
(smooge, 20:22:38)
* IDEA: the roles should probably be deployable via kickstart???????
(jds2001, 20:22:39)
* IDEA: have "helper tools" for maintenance / health that go hand in
hand with the thing being easily installed / deployed / etc.
(rbergeron, 20:26:31)
Meeting ended at 21:01:59 UTC.
Action Items
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* rbergeron (74)
* jds2001 (61)
* dperpeet (32)
* smooge (18)
* zodbot (8)
* nirik (5)
* mjwolf (1)
* adamw (0)
* sgallagh (0)
* #chair (0)
* vvaldez (0)
* mhayden (0)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
7 years, 2 months
Request for review of blocking deliverables for Fedora 25
by Jan Kurik
Hi Server WG,
I would like to request review of the WG deliverables for Fedora 25
release. The list of deliverables is available on wiki:
https://fedoraproject.org/wiki/Fedora_Program_Management/ReleaseBlocking/...
Please let me know, or edit the wiki page, in case there are missing
deliverables or the current one have wrong blocking status.
There is going to be overall review done by FESCo, probably on
2016-Sep-30 for all the blocking deliverables.
Thanks and Best Regards,
Jan
--
Jan Kuřík
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
7 years, 2 months
Server SIG Weekly Meeting Minutes (2016-09-13)
by Stephen Gallagher
===================================================================
#fedora-meeting-1: Server Working Group Weekly Meeting (2016-09-13)
===================================================================
Meeting started by sgallagh at 20:00:45 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/fedora-meeting-1/2016-09-13/serversig.2...
.
Meeting summary
---------------
* Roll Call (sgallagh, 20:00:45)
* Agenda (sgallagh, 20:03:00)
* Agenda Item: Release-blocking media (sgallagh, 20:03:10)
* Agenda Item: PRD Discussion (sgallagh, 20:03:18)
* Release-blocking media (sgallagh, 20:07:44)
* LINK:
https://fedoraproject.org/wiki/Fedora_Program_Management/ReleaseBlocking/...
(sgallagh, 20:07:49)
* ACTION: vvaldez to investigate creating a Fedora Server vagrant
image for Fedora 26 (sgallagh, 20:11:52)
* AGREED: The list as it currently stands is fine for Fedora 25. The
getfedora.org website should not offer 32-bit x86 media for Server.
(+6, 0, -0) (sgallagh, 20:28:52)
* PRD Discussion (sgallagh, 20:29:52)
* ACTION: Server SIG members should start brainstorming actively on
the server mailing list (sgallagh, 20:32:58)
* We will focus on Outcomes that we expect to be able to have an
effect on within one year (targeted at Flock 2017) (sgallagh,
20:44:39)
* The best way to have a good idea is to have lots of ideas
(sgallagh, 20:45:12)
* Outcome brainstorming will happen on the Server mailing list. All
are encouraged to participate. (sgallagh, 20:46:13)
* Open Floor (sgallagh, 20:46:40)
Meeting ended at 20:48:08 UTC.
Action Items
------------
* vvaldez to investigate creating a Fedora Server vagrant image for
Fedora 26
* Server SIG members should start brainstorming actively on the server
mailing list
Action Items, by person
-----------------------
* vvaldez
* vvaldez to investigate creating a Fedora Server vagrant image for
Fedora 26
* **UNASSIGNED**
* Server SIG members should start brainstorming actively on the server
mailing list
People Present (lines said)
---------------------------
* sgallagh (74)
* smooge (26)
* dgilmore (24)
* zodbot (16)
* jds2001 (16)
* adamw (15)
* danofsatx (13)
* vvaldez (11)
* nirik (8)
* mhayden (5)
* dperpeet (0)
* mjwolf (0)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
7 years, 2 months
