Marketing-trac: #126: Create a wiki page for magazine covermount information
by Marketing Team
#126: Create a wiki page for magazine covermount information
----------------------+-----------------------------------------------------
Reporter: pfrields | Owner:
Type: task | Status: new
Priority: major | Milestone: F14a: Pre-alpha
Component: other | Severity: urgent
Keywords: |
----------------------+-----------------------------------------------------
We often get inquiries from magazines asking for permission to bundle one
or more Fedora discs with a future issue. This is a fairly routine
process as long as the disc is an unmodified copy of Fedora media (i.e. an
official release). Some interaction with Red Hat Legal is required to
send out an agreement to the magazine.
We can speed up that interaction and the overall process if we have a page
that tells magazines what they need to provide, and to whom, for a
covermount agreement. Generally we need the following information, sent
to the ''press(a)fp.o'' address:
* The name (d/b/a) and address of the company producing the magazine
* The exact disc(s) that are to be bundled
* Contact information for the person making the request
--
Ticket URL: <https://fedorahosted.org/marketing-team/ticket/126>
marketing-team <https://fedoraproject.org/wiki/Marketing>
Marketing team for the Fedora project.
10 years, 8 months
Marketing-trac: #125: SSSD F13 feature -- press blog entry
by Marketing Team
#125: SSSD F13 feature -- press blog entry
-----------------------------+----------------------------------------------
Reporter: pfrields | Owner: pfrields
Type: task | Status: new
Priority: major | Milestone: F14a: Pre-alpha
Component: Feature Stories | Severity: urgent
Keywords: meeting |
-----------------------------+----------------------------------------------
I had suggested this earlier to Robyn -- a press blog entry for Red Hat's
PR channel (http://press.redhat.com) that would synopsize and point to our
interview on the wiki. However, Robyn's pretty busy right now. Kara
Schiltz from Red Hat's PR department is willing to publish something next
week.
I'm going to pick this up and drive it forward, my way of helping this
week on something Marketing related!
--
Ticket URL: <https://fedorahosted.org/marketing-team/ticket/125>
marketing-team <https://fedoraproject.org/wiki/Marketing>
Marketing team for the Fedora project.
10 years, 8 months
Marketing-trac: #128: Press Release for FUDCon KL 2012
by Marketing Team
#128: Press Release for FUDCon KL 2012
--------------------+------------------------------
Reporter: izhar | Owner:
Type: task | Status: new
Priority: major | Milestone: Future releases
Component: FUDCon | Severity: urgent
Keywords: | Blocked By:
Blocking: |
--------------------+------------------------------
Hi,
Could we have a press-release for FUDCon KL 2012 which is happening this
May?. We are planning to distribute it to local newspapers and news sites.
We are originally planning to produce our own but FPL said that marketing
might want to do and approve it.
In term of dateline, .. erm .. is 27th March too short?, or more than
enough?. The earlier the better of course
Thanks.
--
Ticket URL: <https://fedorahosted.org/marketing-team/ticket/128>
marketing-team <https://fedoraproject.org/wiki/Marketing>
Marketing team for the Fedora project.
10 years, 8 months
release announcements, talking points, release notes, and how we group features into audiences or stories
by Robyn Bergeron
Hi,
(Sorry for evil double-posting :D)
I was taking a look at the oft-neglected Talking Points, which were
originally designed as a handy list of "new shiny" for each release
that could be handed off to Ambassadors as a quick reference list of
features to talk about, and have also at times served as a starting
point for choosing features to be highlighted in release videos,
interview stories / articles, blog posts, etc. It's entirely possible
that they have also been a reference point for writing release
announcements as well. Talking points tend to be very focused on
*totally new* things, and not generally on incremental improvements.
And so I figured I'd take a crack at it again - see
https://fedoraproject.org/wiki/Fedora_19_talking_points - though the
mail to mktg list is still yet-to-be-written (the content of this mail
sort of got in the way, ha). (For those unfamiliar, it's sort of an
iterative process, wherein a number of features are proposed, and
marketing whittles them down into a list, which is likely shorter than
perhaps the feature-related content in a release announcement might
be.)
A few things stood out as I was going through the list:
1: We have bucketized items into a handful of groups over time, in the
talking points as well as release announcements, as well as for docs
beats and eventually, release notes - User, Developer, Sysadmin (and
Cloud/Virt have popped up here and there in more recent releases for
announcements). Those lines seem to be increasingly blurry - there are
tools/apps that cross the dev and sysadmin roles, user and sysadmin
roles, etc. - and while these groups are probably good for
beats/release notes, esp. since content can just be duplicated /
retailored if absolutely necessary, I'm wondering the following:
Is bucketizing a bunch of stuff into "User, Sysadmin, Developer" the
best answer for marketing highlights of the release? It seems like...
well, a listing of car parts, but not really telling a story about the
car, for lack of a better metaphor. And it seems a lot like "we made
a bunch of improvements here and there" isn't as compelling as "we
have improved overall state of ($experience, $usecase, etc) and here's
how."
Looking at the list of features it seems like there are a few main
themes, for which I've suggested some marketing-i-fied
names/groupings, though (as you can see in the Talking Points link)
it's certainly open to other suggestions (or the option of leaving
as-is):
Develop and Distribute: Languages, compilers, and tools for developing
software, and tools for packaging software. (Could also be: Create,
develop, and distribute?)
Start and Recover: Enabling a variety of options for improving boot
times, as well as quicker recovery from system or software failure.
(Boot and Recover? Launch and Recover?)
Monitor and Manage: Systems and resource management, and tools for
diagnosis, monitoring, and logging.
2. Note that I'm not advocating for the "user, sysadmin, dev"
categories to change in docs-land; I think that these stories/themes
are likely to change with each release. But, given the intertwinement
of docs and marketing when it comes to the release announcement, it
seems like (if docs is crafting the tech-bits of the release
announcement) if we were to bucketize by stories, that we'd need to
get marketing to figure out what those stories are. And I don't just
mean the overarching stories, but also the individual feature stories,
in some cases; I can't tell you how many times I look at a feature and
say, wow, I wish I spoke that language, I wonder what the bigger
picture is, what this effectively enables? Maybe the talking points is
a launch point for that as well, in additoin to being the list that
gets handed off to ambassadors, and then can drive the story
collections in a release announcement, or in one-page release notes;
I'm not sure. Thoughts? The workflow, as often seems to be the case
between docs & mktg, is key.
Basically: Seeking feedback? Thoughts, anyone? :D
-Robyn
11 years
Vote for meeting times
by Ruth Suehle
For some of us, Daylight Savings Time recently changed. For others, it
didn't. We've had a good number of new people join. And it's been a
while since we discussed the meeting time. So it seemed like a good time
to bring it up again! Please take a moment this week to vote for times
that would work for you for marketing team meetings here:
http://whenisgood.net/2kmdy9w
Thanks!
Ruth
11 years, 1 month
Talking Points - call for participation / feedback / "should we do this, or can it permanently"
by Robyn Bergeron
Hello marketing pals,
The talking points have been on the schedule since, well, a long time
ago, and we haven't really done them for several releases now. These
were originally, AFAIK, designed as a point of reference for
Ambassadors for release highlights to discuss - basically paring down
the Feature List into some key enhancements, and making them
human-readable and to-the-point.
Over time, I think they may have been useful as (a) a starting point
for choosing features to write stories (feature profiles) about for an
upcoming release; I think they could also serve as a useful point of
reference for the press, or perhaps as a starting point for crafting a
list of feature information for the press, without pointing the press
folks directly to the feature list immediately.
Anyway: Despite my thoughts that I'm unsure of the usefulness of them
*in their current form* (I have no idea if, when they were created in
past releases, if Ambassadors really ever used them) - I think that
some of the process behind them, including figuring out which features
are story-worthy, and the content created as a result (not skipping
all over a feature page trying to get the bottom-line explanation of
what it does and why it's useful), is helpful.
And to echo Christoph's earlier mail to the marketing list, re: Jos's
efforts for marketing opensuse generally, and to the press - I think
that having a decent, well-written list of features / stories would be
useful for press folks, rather than pointing to the FeatureList as the
primary point of getting info, and perhaps this is part of that
process.
Moving along:
I sent a mail not long ago about the categories / buckets of User,
Developer, Sysadmin that we have typically used in Marketing for
announcements, etc. and whether or not we could think about optimizing
that to tell bigger stories about groups of features/improvements, vs.
"bullet point of new things for someone in a role," esp. since those
lines continue to blur as we move into the FUTURE!. Thoughts welcomed
- the suggestions I have are merely that, more are welcome, we could
also say "that's totally stupid, why would we change that" as well. :)
But I think it's a worthwhile idea perhaps to try out - I think it
drives home bigger-picture thoughts about areas of improvement, and
different stories tend to appeal to folks with different problem
spaces / areas of interest.
Finally:
https://fedoraproject.org/wiki/Fedora_19_talking_points <-- I created
this. This is really a starting point (plz read the Talking Points
SOP referenced on the page) - a way to collaboratively identify the
features we think should get highlighted (typically *new* things, not
incremental improvements) - people can take features and add their
reasoning as to why they think something should be a talking point. I
figured we could cross-reference different possible categories for
each feature, so you're welcome to do that as well. Once we have a
list whittled down (we can do that in email, or an IRC meeting) - we
turn those chosen items into content that looks more like this:
https://fedoraproject.org/wiki/Fedora_14_talking_points
Thoughts? Ideally, according to the schedule, the talking points would
be done by Tuesday (4/26), and then serve as a starting-point for
picking deeper-dive stories to tell as we approach release, but I'm
99.9% sure that not being done Tuesday isn't going to kill us. We
could also choose to keep talking points at a process level that is
just a "list of agreed-upon things to market" without turning it into
a formal document, but it seems like it wouldn't be significantly more
work to do so.
Anyway: Like I said - visit
https://fedoraproject.org/wiki/Fedora_19_talking_points and feel free
to note features that you think have great stories or should be
featured, and we can run from there? Yes? :D
-Robyn
11 years, 1 month
[Call to Arms] Fedora 19 Test Days starts this week
by Martin Holec
Hi Fedora users, developers and friends!
today Fedora 19 was branched from Rawhide. That means testing season begins now and will continue till Fedora 19 Final Release, which may be (or may not be) on 2013-06-25. Please, fasten your seatbelts, fire up your virtual or baremetal machines and enjoy this crash testing ride with us.
Remember: https://is0.4sqi.net/userpix/D1Y3XKHJVN4GIMRW.jpg
Before Alpha will (or won't) be ready on 2013-04-16, we have prepared some Test Days[0] for you. Starting this Thursday with KDE 4.10 [1] with one major innovation. You are invited to try how new KDE 4.10 [2] stuff not only using Fedora 19 Live test images, but also from updates-testing repository on your current Fedora stable installation, including both Fedora 18 and Fedora 17 releases. For first time, you can test new version of whole KDE platform before it rolls up and in as an stable update for your Fedora!
[0] https://fedoraproject.org/wiki/QA/Fedora_19_test_days
[1] https://fedoraproject.org/wiki/Test_Day:2013-03-14_KDE_4.10
[2] http://www.kde.org/announcements/4.10/
Well, you may already know about and use Bodhi[3] with karma voting process. But Test Day provides an opportunity to actually talk to developers before KDE 4.10 reaches stable updates and interactively report, explore, debug and fix your issues (or at least find workarounds for the time being). Together we can make this update less painful for everyday Fedora KDE users.
[3] https://admin.fedoraproject.org/updates/
Join IRC #fedora-test-day on FreeNode and ask QA or developers for help, if you get into trouble. We can try to find workarounds and help you with debugging. Please report all bugs under appropriate component preferably at upstream bugzilla https://bugs.kde.org/ regarding common KDE 4.10 issues or Red Hat bugzilla http://bugzilla.redhat.com/ if you have problems with Fedora distribution integration. You can also report other Fedora bugs not related to this Test Day. Feel free to ask on IRC, if you don't know against which component or on what bugzilla you should fill the report.
See you in Bugzilla!
Best Regards,
Martin Holec
Desktop QE, Red Hat Brno
Freenode nick: Martix
Your self-appointed Fedora 19 Test Day Wrangler.
11 years, 1 month
Self-Introduction: Bryan Sutherland
by Bryan Sutherland
Hi, my name is Bryan Sutherland, I am located in the deeply rural
Alberta community of Veteran. You can find my on FAS and IRC as
iambryan.
At present I am a bit of a marketing noob, though I do have
documentation and training experience. Currently I am working with the
Documentation team as a beat writer and a Guide author/editor.
I will also be working on the fedoramagazine.org project to provide
content and to help edit submissions.
Some of my skills that I hope to utilize are:
Technical and End User Documentation and End User Training
I would like to learn more about c
11 years, 1 month
