RFC: Marketing collateral plan
by Ankur Sinha
Hi everyone,
A while back I'd written to the ambassadors list to collect some
feedback on what marketing collateral would be most useful on a per
release basis for use at events and so on. The information gathered is
summarised here:
https://fedoraproject.org/wiki/User:Ankursinha/Marketing_Collateral_Ide
as
The idea is to decide on a set of collateral that can be used at events
and at the same time generated every release without burdening any team
too much - so that they can continue working on other release critical
tasks.
Here's what I've come up with. I'd like to collect some feedback from
the marketing team first, and then the design team, after which I can
present the plan to the ambassadors.
------------------
== Target audience ==
1. Level 1 - Non Fedora users:
This set of users do not use Fedora yet. They are not aware of the
products that Fedora offers - editions + spins + labs. They may also
not be aware of the free software philosophy, the foundations and so
on.
2. Level 2 - Fedora end users:
Fedora users that are not developers and admins. They care about what
Fedora offers, but are not very interested in the lower level details
on what changes a release brings and so on. They are concerned about
higher level changes, such as changes to desktops, new tools, better
upgrades, quicker boots and so on.
3. Level 3 - Advanced Fedora users:
Fedora users that are developers, upstreams, system admins, and so on.
They care about lower level changes - what's changed in systemd,
yum/dnf and so on.
== Collateral ==
1. Timeless Fedora flyer:
This flyer would have a short summary of the different products Fedora
offers - the three editions + labs + spins. It would also contain a
summary of the Fedora mission statement - foundations, commitment to
free software and so on.
The target audience of this flyer is level 1.
The current implementation idea is to request the design team to
provide a design using scribus and I can follow that up with a scribus
script that can populate the flyer from text provided in simple text
files. This method will also ensure that we can have translations for
the text making the flyer available to a wider audience. The marketing
team can maintain a repository of translations and so on too.
2. Release details flyer or one page release notes:
The target audience for this is mainly levels 2 and 3.
This flyer/print will be about the newest release. It'll contain
important changes - both high and low level. This will also aid
ambassadors and community members. It'll pick up stuff from here:
http://fedoraproject.org/wiki/Releases/23/ChangeSet
I think a two sided "one page release notes" would be better than a
flyer - it'll contain more info.
3. Goodies - pens, bracelets, shirts, stickers, badges, case badges and
so on:
This can be used by all levels of the target audience.
I think event owners can decide what they'd like at the event and
produce them. This doesn't require any work from other teams unless
something needs to be updated and so on.
---------------------
Work wise, it's not too much extra. We already do release notes and the
flyers can come from there. The docs team also does beats and changes,
so we can use stuff from there too.
So, what do you think? :)
--
Thanks,
Regards,
Ankur Sinha "FranciscoD"
http://fedoraproject.org/wiki/User:Ankursinha
8 years, 6 months
Magazine articles.
by Gabriele Trombini
Hello guys,
in the discussion I followed after both jzb and croberts talks at
Flock, came out a couple of indications about writing another kind of
magazine articles:
1) seems that short articles are more attractive than the long ones and
they have to arouse the curiosity, so people reading may deepen the
topic in a second time and more carefully.
2) there's the need to have more user/contributor focused articles
instead of technical explanation. People need to be part of the Project
and there's nothing better than writing for them.
Do I have understood correctly?
Of course the magazine needs also the same kind of articles we always
have had.
Thanks.
Gabri
8 years, 7 months
Magazine Editorial recap 2015-08-27
by Paul W. Frields
Minutes: http://meetbot.fedoraproject.org/fedora-meeting/2015-08-27/magazine.2015-...
Minutes (text): http://meetbot.fedoraproject.org/fedora-meeting/2015-08-27/magazine.2015-...
Log: http://meetbot.fedoraproject.org/fedora-meeting/2015-08-27/magazine.2015-...
* * *
================================
#fedora-meeting: Fedora Magazine
================================
Meeting started by stickster at 21:00:18 UTC. The full logs are
available at
http://meetbot.fedoraproject.org/fedora-meeting/2015-08-27/magazine.2015-...
.
Meeting summary
---------------
* Roll call! (stickster, 21:00:23)
* Agenda review (stickster, 21:03:43)
* LINK: https://fedoraproject.org/wiki/Magazine/Editorial_meetings
(stickster, 21:03:47)
* LINK: http://bit.ly/1hizpuC (stickster, 21:08:08)
* LINK: http://opensource.com (decause_otg, 21:10:43)
* ACTION: decause open a loop with Rikki/Shibby for Editorial best
practices braindumping (decause_otg, 21:14:19)
* ACTION: ryanlerch flesh out post scheduling on the Magazine Wiki
Page (decause_otg, 21:18:25)
* ACTION: decause reach out to misc about adding Fedora Magazine to
Piwik instance in OSAS (decause_otg, 21:19:20)
* ACTION: decause_otg Talk to misc to see if we can get F-Mag on the
OSAS piwik instance (stickster, 21:25:31)
* LINK: https://wordpress.org/plugins/wp-piwik/ (jzb, 21:27:37)
* LINK: https://wordpress.org/plugins/wp-piwik/ -- embedding Piwik
stats + code for WP (stickster, 21:28:29)
* AGREED: Let's get Piwik functionality on board, pending OSAS
assistance via their instance (+5, 0, 0) (stickster, 21:32:23)
* Quick retrospective! (stickster, 21:34:59)
* 3 posts this week -- Major's firewall howto, Paul's Flock 2015 video
news, and Ryan's Wayland update for F23 story (stickster, 21:35:39)
* Pitch votes (stickster, 21:36:07)
* LINK:
http://fedoramagazine.org/wp-admin/edit.php?post_status=pitch&post_type=post
(stickster, 21:45:27)
* AGREED: Yes on fpaste (stickster, 21:50:26)
* IDEA: Let's ask Gerd (the pitch author) if he wants to provide a
couple brief bullet points on what he intends the reader to learn
with a fuller article (stickster, 21:56:30)
* ACTION: stickster Email Gerd to ask for clarification on point of
article by 2015-09-03 (stickster, 21:59:06)
* AGREED: NEEDINFO on pitch author (stickster, 22:00:07)
* for those who are not looking at the dashboard in wordpress, trash
means "go into another queue" not "delete from the site forever"
(decause-otg, 22:01:39)
* ACTION: stickster Add point to wiki page about critical update or
other urgent posts (stickster, 22:07:29)
* ACTION: ryanlerch draft Firefox article for publication tomorrow
(stickster, 22:14:19)
* AGREED: ryanlerch can go ahead and publish when ready (stickster,
22:15:07)
* Awesome first meeting! (stickster, 22:18:58)
Meeting ended at 22:19:09 UTC.
Action Items
------------
* decause open a loop with Rikki/Shibby for Editorial best practices
braindumping
* ryanlerch flesh out post scheduling on the Magazine Wiki Page
* decause reach out to misc about adding Fedora Magazine to Piwik
instance in OSAS
* decause_otg Talk to misc to see if we can get F-Mag on the OSAS piwik
instance
* stickster Email Gerd to ask for clarification on point of article by
2015-09-03
* stickster Add point to wiki page about critical update or other urgent
posts
* ryanlerch draft Firefox article for publication tomorrow
Action Items, by person
-----------------------
* decause_otg
* decause_otg Talk to misc to see if we can get F-Mag on the OSAS
piwik instance
* ryanlerch
* ryanlerch flesh out post scheduling on the Magazine Wiki Page
* ryanlerch draft Firefox article for publication tomorrow
* stickster
* stickster Email Gerd to ask for clarification on point of article by
2015-09-03
* stickster Add point to wiki page about critical update or other
urgent posts
* **UNASSIGNED**
* decause open a loop with Rikki/Shibby for Editorial best practices
braindumping
* decause reach out to misc about adding Fedora Magazine to Piwik
instance in OSAS
People Present (lines said)
---------------------------
* stickster (153)
* ryanlerch (61)
* roshi (43)
* jzb (32)
* decause_otg (25)
* decause-otg (16)
* zodbot (14)
* mitzie (13)
* mailga (10)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
The open source story continues to grow: http://opensource.com
8 years, 7 months
Help us rebrand rawhide
by Matthew Miller
So, here at Flock, we're talking about improving Rawhide so it's much
less likely to break (it will, for example, be always installable and
always updatable).
We took the "Rawhide eats babies" readme file away a long time ago,
but it still has that reputation. So, the consensus in the room here is
that we'd like a new name for a new, less scary devel tree.
What should it be?
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader
8 years, 7 months
Re: Help us rebrand rawhide
by Matthew Miller
On Sat, Aug 15, 2015 at 01:21:40PM -0600, Jonathan Corbet wrote:
> OK, I have to respond to this one. Rawhide was once a great distribution
> for staying at the leading edge of things; I was an enthusiastic user.
> But then developers stopped caring whether it broke, and, when I reported
> bugs, I was told that I shouldn't be running Rawhide at all. After a bit
> of that, I moved on. So did lots of others, I think.
> So now we're going to fix it and the first thing to do is to ... change
> the name?
Hi Jonathan. In short, no. :) This is the marketing list, and that's
the first thing around this for the marketing team to do. But this
isn't just a rebranding, and any name change would come _after_ actual
technical changes. The plan involves taking some lessons from our
friends over at openSUSE, and implementing gating, so that packages are
put in side-tags until they pass basic tests (initially, very basic
tests like dependency closure, and then "did this break booting", and
up from there").
The message of a name change is as much for those developers who told
you you shouldn't be running Rawhide at all as it is for users -- this
is something unlike what Rawhide has ever been, even in the days when
it was in better shape overall.
> I'd say forget about the name; it's one with some good history and name
> recognition. Instead, rehabilitate it. Show the world that developers
> *do* care about whether Rawhide actually works and that they actually
> want to see bug reports. Then people might actually start coming back.
All of the above said, I'm cautiously open to this possibility, if if
there's agreement that we can make it work.
> P.S. I wrote an article (https://lwn.net/Articles/506831/) about why I
> left Rawhide.
I remember. And I'm pretty sure you remember that I'm quoted. :)
> If the project is now actively trying to make Rawhide
> usable, I might be interested in doing something about the real steps
> that have been taken to make that happen...
More details to come. Although possibly after a quite a large amount of
post-Flock sleep. :)
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader
8 years, 7 months
Marketing coilateral, new presskit, and reviewers guide
by Zoltan Hoppar
Hi,
I have talked over here in the Flock with many people to get as many
as possible feedbacks around new marketing collateral, and presskit,
and reviewers guide (aka one page release notes, talking points) - and
I would like to be the volunteer for this who actually making and
updating them.
All what is need that some guiding that what should be included, and
where can I find them. Can you help in this?
Thank you in advance.
--
PGP: 06853DF7
8 years, 7 months