--
Remy DeCausemaker
<decause(a)redhat.com>
Fedora Community Lead & Council Member
http://whatcanidoforfedora.org
308C A504 0B47 1503 C9D9 E670 E633 A79B 0BB0 F6D9
----- Original Message -----
From: "Matthew Miller" <mattdm(a)fedoraproject.org>
To: marketing(a)lists.fedoraproject.org
Sent: Monday, October 12, 2015 2:56:04 PM
Subject: working on f23 final release announcement
Thanks to everyone who helped pull together the F23 beta annoucement.
I'd like us to give ourselves a little more time for the final
annoucement. :)
The beta annoucement is usually targeted at a fairly technical
audience, and that makes sense, but when that hits the mainstream press
— even the mainstream tech press — that tends to lead to reporting
like this sarcastic gem:
http://www.theinquirer.net/inquirer/news/2427241/red-hat-releases-fedora-...
For the final release annoucement, I'd like to refer to release notes
(or package lists, or whatever) for the details, and focus more on The
Exciting Story of Fedora 23.
Please help me write that story. What have we got to work with?
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader
--
marketing mailing list
marketing(a)lists.fedoraproject.org
List info or to change your subscription:
https://admin.fedoraproject.org/mailman/listinfo/marketing
All,
This is a task that the CommOps team wants to help tackle. It makes sense for CommOps to
help it because it is a community effort that spans across many teams and subprojects. I
have added Release notes to our wiki page here:
https://fedoraproject.org/wiki/CommOps#Things_that_the_Fedora_Community_O...:
I, however, have never created a Final release announcement, and am not entirely sure what
all goes into officially making one, other than this list of general tasks here:
https://fedorapeople.org/groups/schedule/f-23/f-23-marketing-tasks.html
According to this list, we're on the final four steps calendar-wise, but task wise,
I'm not sure where we are at (other than we we did release Beta Release Notes.)
Is there a trac instance or some other document somewhere that we're using to track
progress on these items? If not, then we should start creating tickets somewhere to be
assigned in the very near future.
Any other information or resource pages would be super helpful. Even more useful than
static content would be a list of the folks who typically contribute or create the release
notes, so that we can open a loop with them, and get filled in on all the institutional
wisdom. I know the folks who have done the heavy lifting in the past include jzb and
mattdm for sure, who are already stretched pretty thin, so any additional suggestions
would be super helpful.
I'll be keeping an eye on this thread, as this is something that needs to get done in
the very short-term.
--RemyD.