While it's not true that this is finalized,
there is a current change proposal to drop Alpha releases from the
release cycles of Fedora starting in Fedora 27. You can read more
information at the Change wiki page.(jwf,
14:05:49)
Fedora Infrastructure officially migrated our
old pastebin service to a more modern and clean paste site. You can
read more info in the article on the Fedora Magazine.(jwf,
14:10:00)
How This Works: We look at past #action items
from the last meeting for quick follow-up. If a task is completed,
we move on to the next one. If it isn't, we get an update and
re-action it if needed. If no status, we'll try to get a quick
update and move forward.(jwf,
14:11:53)
=== [COMPLETE] jwf Start mailing list thread
about using a git forge for maintaining and creating a press kit for
our release cycle activities ===(jwf,
14:12:02)
Left off with discussion about git forge and
what should be included in the press kit. Can make a quick decision
on where we want to host this, then focus more on the content that
we wanted to put in there and how we want to start building
it.(jwf,
14:12:50)
AGREED: Marketing
team will host press kit in Pagure (which *does* have a web editor!)
and use Markdown as default markup language, which will also fit
into our existing workflow with other repos we have on Pagure(jwf,
14:31:29)
What's in a press kit? We suggested: one-page
release notes, background modules (general Fedora info), feature
modules (specific to releases), past press coverage, targeted
brochures / flyers(jwf,
14:32:48)
ACTION: FranciscoD /
bkp Discuss and draft a short proposal of what one-page release
announcements looks like for the press kit, with (1) timeline for
when they should be created during the release, (2) type of content
to include in the announcement, and (3) how it should be
delivered(jwf,
14:50:03)
ACTION: jwf Draft a
simple proposal for what background modules / past press coverage
should be in the press kit, add comment to ticket #242 for
discussion at next meeting(jwf,
14:51:31)
Talking points officially start today, now that
the change window is closed for Fedora 26. We're still awaiting
feedback from the Council, but we try starting with the raw data
that is on the existing talking points page and try to organize that
in a way that we can work with? We can also try to task outreach to
different WGs / SIGs, but this depends on if we want to collect
information by technical grouping or by audience.(jwf,
14:52:03)
FranciscoD / bkp Discuss and draft a short proposal of what one-page release announcements looks like for the press kit, with (1) timeline for when they should be created during the release, (2) type of content to include in the announcement, and (3) how it should be delivered
jwf Draft a simple proposal for what background modules / past press coverage should be in the press kit, add comment to ticket #242 for discussion at next meeting
Action items, by person
bkp
FranciscoD / bkp Discuss and draft a short proposal of what one-page release announcements looks like for the press kit, with (1) timeline for when they should be created during the release, (2) type of content to include in the announcement, and (3) how it should be delivered
FranciscoD
FranciscoD / bkp Discuss and draft a short proposal of what one-page release announcements looks like for the press kit, with (1) timeline for when they should be created during the release, (2) type of content to include in the announcement, and (3) how it should be delivered
jwf
jwf Draft a simple proposal for what background modules / past press coverage should be in the press kit, add comment to ticket #242 for discussion at next meeting