Thanks / Idea for a Spin Lab
by Rodrigo de Araujo
Hi Gabriele,
Thanks for the welcome and the explanations. I'll look at the tickets
you told me.
Unfortunately I could not attend the last meeting, but I intend to
become active in #fedora-mktg and in the meeting channel.
I did a quick search this afternoon and I realized that in Brazil there
are more than 63,000 active / legalized radio amateurs. Only in my
region are 4,531 people. The same applies to other amateurs worldwide.
This is a very segmented target so that we can act together, since we
have several applications packaged to the needs of these people.
I can also cite Scout groups who also deal with amateur radio, another
interesting audience to be worked in that sense. It would be interesting
that we could make Fedora a popular distro between them.
Fedora offers some spin labs and l think it would be nice for the
project to offer a spin lab called Fedora Amateurs or Fedora Hams. This
would facilitate us to reach that audience, but I'll start thinking
about other tactics as well.
I'm not sure how such thing could be done, but I can make a current list
of interesting software to this public already available in the system -
our wiki "Applications for Amateur Radio" doesn't seem 100% up to date.
Cheers,
Rodrigo
Em 10-01-2017 10:27, marketing-request(a)lists.fedoraproject.org escreveu:
> Send Fedora Marketing mailing list submissions to
> marketing(a)lists.fedoraproject.org
>
> To subscribe or unsubscribe via email, send a message with subject or
> body 'help' to
> marketing-request(a)lists.fedoraproject.org
>
> You can reach the person managing the list at
> marketing-owner(a)lists.fedoraproject.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Fedora Marketing digest..."
>
>
> Today's Topics:
>
> 1. Re: Self-Introduction: rodrigodearaujo (Gabriele Trombini)
> 2. Re: Finished questionnaire (Sylvia Sánchez)
> 3. Re: Finished questionnaire (Gabriele Trombini)
> 4. Re: Finished questionnaire (Jan Kurik)
>
>
> _______________________________________________
> Fedora Marketing mailing list -- marketing(a)lists.fedoraproject.org
> To unsubscribe send an email to marketing-leave(a)lists.fedoraproject.org
7 years, 1 month
[fedora-marketing] Issue #242 `Update release activity steps / process on the wiki`
by Justin W. Flory
jflory7 added a new comment to an issue you are following:
``
**Discussed in [2017-02-21 meeting](https://meetbot.fedoraproject.org/fedora-meeting/2017-02-21/mark...
## Summary
Using a public git forge or public platform for the press kit is a good way to promote our content and encourage community contributions, while also making sure our work and content is easily findable and revisable.
## Git forge
One general part of our discussion was about using a public git forge for our marketing activities to hold our content. The benefit of this is that:
1. It has one place to find everything (i.e. not across multiple wiki pages that might not be well-linked together)
* Most beneficial for communicating with press about where to find things (?)
2. It invites community collaboration and participation
## What is a press kit?
More verbose discussion in the meeting minutes, but here's a bulletpoint list of what we did discuss.
* **One-page release notes**: We are creating release notes, but a one-page deliverable (adapted from FPL's release announcement? something more unique / targeted?) to share with Ambassadors could improve communication of info to Ambassadors and better equip them for events to talk about a new release
* **Background modules**: Pulling info about Fedora itself, similar to FPL's "State of Fedora" talk data about project metrics for approximate growth, both technical and community?
* **Feature modules**: Individually crafted PDFs based off of release notes / meta points / other things we want to highlight to wider press audience (jwf, 14:35:52)
* **Past press coverage**: Currently happening in meeting announcements as "In the news", but could be extracted to the press kit in a file that is maintained during the release and kept current
* **Integrating targeted brochures / flyers into the press kit** especially as a deliverable for Ambassadors to use at events (see: [SXSW brochures targeted to specific audiences](https://fedoraproject.org/wiki/Design/SXSW_Materials#Brochures))
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-marketing/issue/242
7 years, 1 month
[Minutes] [2017-02-21] Updating our release process, retooling Marketing
by Justin W. Flory
Hey everyone, our meeting just finished up a few minutes ago! Thanks all
who participated in today's meeting.
We only had time to really cover one ticket, but it was a quality
discussion. We focused on #245 with regards to using the press kit as a
primary way to refocus our release activities, how we might do that, and
what it would look like. There will be a follow-up email a little later
today about a finer detail of this that will let us move forward on
building an example to demo and consider as a final choice for where our
deliverables go.
More to come soon, but the minutes should be easy to follow and read!
Thanks all.
= = = = =
Meeting ended Tue Feb 21 14:59:51 2017 UTC.
Minutes:
https://meetbot.fedoraproject.org/fedora-meeting/2017-02-21/marketing.201...
Minutes (text):
https://meetbot.fedoraproject.org/fedora-meeting/2017-02-21/marketing.201...
Log:
https://meetbot.fedoraproject.org/fedora-meeting/2017-02-21/marketing.201...
* * * * *
======================================================
#fedora-meeting: Fedora Marketing meeting (2017-02-21)
======================================================
Meeting started by jwf at 13:59:03 UTC. The full logs are available at
https://meetbot.fedoraproject.org/fedora-meeting/2017-02-21/marketing.201...
.
Meeting summary
---------------
* Agenda (jwf, 13:59:05)
* LINK:
https://fedoraproject.org/wiki/Meeting:Marketing_meeting_2017-02-21
(jwf, 13:59:11)
* (1) Roll call (jwf, 13:59:16)
* (2) Announcements (jwf, 13:59:22)
* (3) Action items from last meeting (jwf, 13:59:27)
* (4) Tickets (jwf, 13:59:32)
* (5) Upcoming tasks (jwf, 13:59:37)
* (6) Open floor (jwf, 13:59:42)
* Roll call (jwf, 13:59:47)
* Name; Timezone; Other sub-projects / interest areas (jwf, 13:59:52)
* Justin W. Flory; UTC+1; Marketing, Magazine, CommOps, Ambassador,
Diversity Team, sysadmin-badges, etc. (jwf, 14:00:17)
* Brian Proffitt; UTC-5; marketing; social media (bkp, 14:00:56)
* Eduard Lucena; UTC-4; Marketing, Magazine, CommOps, Ambassador,
Hubs, Join, etc (x3mboy, 14:00:58)
* Announcements (jwf, 14:05:09)
* === In the news: "New Fedora 25 Live ISO Respins Now Available with
Linux Kernel 4.9.8, Bug Fixes" === (jwf, 14:05:15)
* LINK:
http://news.softpedia.com/news/new-fedora-25-live-iso-respins-now-availab...
(jwf, 14:05:20)
* New live respins of all the Fedora 25 desktop environments and
editions are now available. Softpedia covers where to find them and
details a little about what they are and who they're for. (jwf,
14:05:25)
* === "North America and Fedora: Year in Review" === (jwf, 14:05:31)
* LINK:
https://communityblog.fedoraproject.org/north-america-fedora-year-review/
(jwf, 14:05:37)
* A quick overview of the past year's events in North America by the
Ambassadors. (jwf, 14:05:44)
* Action items from last meetings (jwf, 14:07:13)
* LINK:
https://meetbot.fedoraproject.org/fedora-meeting/2017-02-14/marketing.201...
(jwf, 14:07:20)
* 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:07:26)
* === [COMPLETE] jwf / x3mboy Discuss possibility of using a bot to
sync social media platform (e.g. FB / Twitter / RSS) to Fedora
Projects News Telegram group === (jwf, 14:07:34)
* Bot was set up this morning in the Project News channel to sync with
Facebook – all Facebook posts should show up in the Telegram channel
within an hour of being posted ( x3mboy++ ) (jwf, 14:07:46)
* === [COMPLETE] jwf File new ticket for education-focused marketing
campaign, with end goal being to share with Fedora Council at March
22nd sub-project report meeting === (jwf, 14:07:53)
* LINK: https://pagure.io/fedora-marketing/issue/248 (jwf, 14:07:57)
* === bkp (1) Research what our old press kits were, (2) leave comment
in ticket #242 with that info, (3) all marketing team members
encouraged to discuss / give feedback for modernizing press kits ===
(jwf, 14:08:05)
* bkp and shantorn did some research and found a lot of info on the
wiki - bkp has a proposal and is putting it into #242 now (jwf,
14:10:17)
* === [COMPLETE] x3mboy Leave comment in ticket #245 for initial list
of "target audiences" based on Fedora Labs, cross-compared with
package categories, to be discussed at the next meeting === (jwf,
14:10:27)
* LINK: https://pagure.io/fedora-marketing/issue/245#comment-172225
(jwf, 14:10:32)
* Tickets (jwf, 14:10:44)
* LINK: https://pagure.io/fedora-marketing/issues?tags=meeting (jwf,
14:10:48)
* === Ticket #242: "Update release activity steps / process on the
wiki" === (jwf, 14:10:56)
* LINK: https://pagure.io/fedora-marketing/issue/242 (jwf, 14:11:00)
* IDEA: One-page release notes: We are creating release notes, but a
one-page deliverable (adapted from FPL's release announcement?
something more unique / targeted?) to share with Ambassadors could
improve communication of info to Ambassadors and better equip them
for events to talk about a new release (jwf, 14:24:12)
* IDEA: Background modules: Pulling info about Fedora itself, similar
to FPL's "State of Fedora" talk data about project metrics for
approximate growth, both technical and community? (jwf, 14:25:07)
* IDEA: Creating the press kit in a git forge to encourage community
participation and engagement to help expose the content (jwf,
14:33:10)
* IDEA: Feature modules: Individually crafted PDFs based off of
release notes / meta points / other things we want to highlight to
wider press audience (jwf, 14:35:52)
* IDEA: Past press coverage: Currently happening in meeting
announcements as "In the news", but could be extracted to the press
kit in a file that is maintained during the release and kept current
(jwf, 14:39:52)
* LINK: https://fedoraproject.org/wiki/Marketing/Python_brochure
(jwf, 14:40:53)
* LINK: https://fedoraproject.org/wiki/Design/SXSW_Materials#Brochures
(bkp, 14:41:24)
* IDEA: Integrating targeted brochures / flyers into the press kit
especially as a deliverable for Ambassadors to use at events (jwf,
14:43:12)
* ACTION: jwf Start mailing list thread about using a git forge for
maintaining and creating a press kit for our release cycle
activities (jwf, 14:49:31)
* AGREED: Stopping point: Creating a mock press kit repository to demo
the idea of where we create our release activities, with the
long-term intent to possibly adopt this as a permanent part of the
Marketing release cycle activities and updating our documentation to
reflect that (jwf, 14:50:50)
* === Ticket #245: "Create Fedora 26 talking points" === (jwf,
14:51:30)
* LINK: https://pagure.io/fedora-marketing/issue/245 (jwf, 14:51:34)
* Eduard put a full list of our Labs, Spins, and DNF repository
groups. He also proposed a small list of target audiences we could
start with, and try to filter down for how we want to approach this
release's talking points. (jwf, 14:51:39)
* AGREED: Will move the discussion about trimming the list to our
channel to free up the meeting channel (jwf, 14:58:16)
* === Ticket #248: " Create an education-focused marketing campaign"
=== (jwf, 14:58:27)
* LINK: https://pagure.io/fedora-marketing/issue/248 (jwf, 14:58:32)
* Not enough time in agenda, will revisit this next week (jwf,
14:58:41)
* Upcoming Tasks (jwf, 14:58:45)
* LINK:
https://fedorapeople.org/groups/schedule/f-26/f-26-marketing-tasks.html
(jwf, 14:58:51)
* (1) Change Checkpoint: Completion deadline (Tue 2017-02-28) (jwf,
14:58:56)
* (2) Create Talking Points (start: Tue 2017-02-28) (jwf, 14:59:02)
* (3) Proposed Changes Profiles (start: Tue 2017-03-07) (jwf,
14:59:07)
* (4) Email WGs to solicit bullet points for Alpha release
announcement (start: Thu 2017-03-09) (jwf, 14:59:13)
* Open Floor (jwf, 14:59:19)
Meeting ended at 14:59:51 UTC.
Action Items
------------
* jwf Start mailing list thread about using a git forge for maintaining
and creating a press kit for our release cycle activities
Action Items, by person
-----------------------
* jwf
* jwf Start mailing list thread about using a git forge for
maintaining and creating a press kit for our release cycle
activities
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* jwf (140)
* bkp (51)
* bexelbie (24)
* x3mboy (16)
* zodbot (12)
* Southern_Gentlem (7)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
--
Cheers,
Justin W. Flory
jflory7(a)gmail.com
7 years, 1 month
[fedora-marketing] Issue #242 `Update release activity steps / process on the wiki`
by Brian Proffitt
bproffit added a new comment to an issue you are following:
``
Press kits usually have the following materials within them. They are typically remixes of existing marketing materials/deliverables.
* One-page release notes, a short document intended to be printed on a one-page handout for distribution to users at events alongside LiveCDs, as well as within electronic press kits. They explain the Fedora Project, briefly highlight and summarize some of the new features in the release that may be especially relevant to user, cloud, and developer audiences, and are intended to answer the newcomer's question of "What is Fedora <Release Number>?" in a way that will make them want to try it out. Information can include:
* Background module with information on the project (if specific) and/or the Fedora Project itself
* Feature module listing specific features, statistics, etc. on the project or the current release
* Past press coverage. Lists of news coverage the project has recently gotten.
* Photos and images. People, logos, products, etc. (high resolution).
* Press release. Details the most recent news about which the media kit is sent in reference.
* Media contact information. Usually of a public relations department or spokesperson.
* Demo media (optional). A USB Stick, CD, DVD, software title, video, etc. as appropriate for the sender of the release.
Press kits were usually delivered in hard copy format. For efficiency and speed, it is suggested that PDF and ISO files be placed in a zip file that can either be emailed to press as needed, or placed on bootable USB sticks to be handed out at events.
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-marketing/issue/242
7 years, 1 month
[Minutes] [2017-02-14] Target audiences, press kits, a new education campaign
by Justin W. Flory
Hey everyone!
Today's weekly meeting just came to a close. We made some good progress
on advancing through some of the existing tickets we have open for
retooling Marketing but also identifying some new and exciting goals
too! This was an exciting meeting for me and we went right up to the
full hour for the meeting.
Full minutes and logs are all below. Keep an eye out for more soon –
thanks all!
= = = = =
Meeting ended Tue Feb 14 15:06:41 2017 UTC.
Minutes:
https://meetbot.fedoraproject.org/fedora-meeting/2017-02-14/marketing.201...
Minutes (text):
https://meetbot.fedoraproject.org/fedora-meeting/2017-02-14/marketing.201...
Log:
https://meetbot.fedoraproject.org/fedora-meeting/2017-02-14/marketing.201...
* * * * *
======================================================
#fedora-meeting: Fedora Marketing meeting (2017-02-14)
======================================================
Meeting started by jwf at 13:58:29 UTC. The full logs are available at
https://meetbot.fedoraproject.org/fedora-meeting/2017-02-14/marketing.201...
.
Meeting summary
---------------
* LINK:
https://fedoraproject.org/wiki/Meeting:Marketing_meeting_2017-02-14
(jwf, 13:58:39)
* (1) Roll call (jwf, 13:58:44)
* (2) Announcements (jwf, 13:58:48)
* (3) Action items from last meeting (jwf, 13:58:53)
* (4) Tickets (jwf, 13:58:57)
* (5) Upcoming tasks (jwf, 13:59:02)
* (6) Open floor (jwf, 13:59:07)
* Roll call (jwf, 13:59:11)
* Name; Timezone; Other sub-projects / interest areas (jwf, 13:59:18)
* Justin W. Flory; UTC+1; Marketing, CommOps, Magazine, Diversity
Team, Ambassadors, sysadmin-badges, social media, and more… (jwf,
13:59:59)
* Eduard Lucena; UTC-3; Marketing, Magazine, Ambassadors, L10N /
Social Media, Users Support, Classroom/University Project (x3mboy,
14:01:11)
* Brian Proffitt; UTC-5; Marketing, Social Media (bkp, 14:02:48)
* Charles Profitt; UTC-5; Marketing, Social Media, other stuff
(cprofitt, 14:03:36)
* Announcements (jwf, 14:05:33)
* === "Community Promotion Ads - 2017" === (jwf, 14:05:38)
* LINK:
http://meta.unix.stackexchange.com/questions/4337/community-promotion-ads...
(jwf, 14:05:43)
* mattdm submitted a series of community ads to the Unix StackExchange
site, featuring the Fedora Magazine and each Fedora edition. To be
featured on the site, ads need to have six or more votes. If you
have a StackExchange / StackOverflow account, please log in and add
your vote! (jwf, 14:05:48)
* HELP: Please help vote for the Fedora Community Ads on Unix
StackExchange!
http://meta.unix.stackexchange.com/questions/4337/community-promotion-ads...
(jwf, 14:06:05)
* It's been a quiet week across the media world for Fedora. No new
articles or coverage of anything this week, but we haven't hit an
exciting period yet as far as press coverage goes. The alpha is just
around the corner, though! (jwf, 14:06:14)
* Action items from last meetings (jwf, 14:09:00)
* LINK:
https://meetbot.fedoraproject.org/fedora-meeting/2017-02-07/marketing.201...
(jwf, 14:09:06)
* 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:09:11)
* === [IN PROGRESS] Amita / dhanesh95 Research the Mozilla marketing
team / efforts to see what kind of work and activities they do for
their release cycles, and then leave a comment in ticket #242 for
discussion at next meeting === (jwf, 14:09:16)
* LINK: https://pagure.io/fedora-marketing/issue/242#comment-75600
(jwf, 14:09:24)
* === [COMPLETE] mailga Prepare / create the Fedora 26 talking points
wiki page and update the link for it on the main Marketing wiki page
by next week's meeting, 2017-02-14 === (jwf, 14:09:35)
* LINK: https://fedoraproject.org/wiki/Fedora_26_talking_points
(jwf, 14:09:43)
* === [COMPLETE] jflory7 File a new ticket for Council sub-project
report in next month === (jwf, 14:09:51)
* === [IN PROGRESS] jflory7 / x3mboy Discuss possibility of using a
bot to sync social media platform (e.g. FB / Twitter / RSS) to
Fedora Projects News Telegram group === (jwf, 14:09:55)
* ACTION: jflory7 / x3mboy Discuss possibility of using a bot to sync
social media platform (e.g. FB / Twitter / RSS) to Fedora Projects
News Telegram group (jwf, 14:10:01)
* Tickets (jwf, 14:10:19)
* LINK: https://pagure.io/fedora-marketing/issues?tags=meeting (jwf,
14:10:26)
* === Ticket #242: "Update release activity steps / process on the
wiki" === (jwf, 14:10:32)
* LINK: https://pagure.io/fedora-marketing/issue/242 (jwf, 14:10:36)
* Picking up on past discussions with regards to retooling ourselves
to being a more effective and productive Marketing Team. New
insights from Mozilla courtesy of Amita and dhanesh95, as well as
OSAS from bkp. (jwf, 14:10:42)
* LINK: https://etherpad.net/p/EUYbfXuRGG (jwf, 14:11:56)
* IDEA: Revitalizing press kits: Once upon a time, we had press kits.
Could revisit old press kits, modernize it, and possibly split them
into "target audience" press kits, e.g. Python press kit, Rust press
kit, Design press kit (integrating closely with Labs, maybe???)
(jwf, 14:27:20)
* IDEA: Education approach: Finding a better way to make Fedora more
attractive to an education-minded audience (students, teachers,
professors, faculty, administrators) – maybe a good idea for our
next targeted campaign? (jwf, 14:28:01)
* LINK:
https://fedoraproject.org/wiki/Workstation/Workstation_PRD#Target_Audience
(nirik, 14:28:58)
* LINK:
https://fedoraproject.org/wiki/Server/Product_Requirements_Document#User_...
(nirik, 14:30:50)
* LINK:
https://fedoraproject.org/wiki/Cloud/Cloud_PRD#User_Profiles.2C_Goals.2C_...
(nirik, 14:31:34)
* IDEA: Fedora Labs are, more or less, already use cases for specific
target audiences of Fedora users - this might be something we can
spend more time looking at and cross-comparing with the user cases /
profiles from the above links (jwf, 14:31:53)
* ACTION: jwf File new ticket for education-focused marketing
campaign, with end goal being to share with Fedora Council at March
22nd sub-project report meeting (jwf, 14:39:34)
* ACTION: bkp (1) Research what our old press kits were, (2) leave
comment in ticket #242 with that info, (3) all marketing team
members encouraged to discuss / give feedback for modernizing press
kits (jwf, 14:40:16)
* === Ticket #245: "Create Fedora 26 talking points" === (jwf,
14:41:38)
* LINK: https://pagure.io/fedora-marketing/issue/245 (jwf, 14:41:43)
* mailga has created the Fedora 26 talking points wiki page, but it
has a lot of trimming and prettying to do, as we discussed. See
bex's comment in the ticket with regards to how we present this
talking points instead by audience instead of by edition. (jwf,
14:41:48)
* LINK: https://fedoraproject.org/wiki/Fedora_26_talking_points
(jwf, 14:41:53)
* IDEA: Separating talking points by AUDIENCE instead of by EDITION or
FEATURESET (jwf, 14:42:08)
* Why do we have talking points? Talking points are the key points we
want to communicate and share with our audience of users (current
and potential) whenever we cut a new Fedora release (jwf, 14:46:46)
* Current Fedora packaging categories: Development and Creative
Workstation, Web Server, Infrastructure Server, Basic Desktop, 3D
Printing, Administration Tools, Ansible node, Audio Production,
Authoring and Publishing, Books and Guides, C Development Tools and
Libraries, Cloud Infrastructure, Cloud Management Tools, Container
Management, D Development Tools and Libraries, Design Suite,
Development Tools, Domain Membership, Fedora Eclipse, (jwf,
14:54:56)
* Current Fedora packaging categories: Editors, Educational Software,
Electronic Lab, Engineering and Scientific, FreeIPA Server, Games
and Entertainment, Headless Management, LibreOffice, MATE
Applications, MATE Compiz, Medical Applications, Milkymist, Network
Servers, Office/Productivity, Robotics, RPM Development Tools,
Security Lab, Sound and Video, System Tools, Text-based Internet,
Window Managers (jwf, 14:55:13)
* IDEA: In the interest of time, will instead identify target
audiences by looking at Fedora Labs, then cross-comparing against
the packaging categories above to add more suggestions for audience
as they think is necessary – team can discuss and provide feedback
afterwards (jwf, 15:02:17)
* ACTION: x3mboy Leave comment in ticket #245 for initial list of
"target audiences" based on Fedora Labs, cross-compared with package
categories, to be discussed at the next meeting (jwf, 15:04:29)
* === Ticket #246: "Prepare report for Council sub-project report" ===
(jwf, 15:05:16)
* LINK: https://pagure.io/fedora-marketing/issue/246 (jwf, 15:05:20)
* Marketing is tentatively on the hook for a sub-project update in
March. We'll want to begin mapping out our current status, future
plans, and anything we'd like to request help from the Council on.
Also relevant, see our last sub-project report with croberts on
YouTube as a review. (jwf, 15:05:24)
* LINK: https://www.youtube.com/watch?v=VP6GXsjM7AA (jwf, 15:05:30)
* SKIPPED: Will revisit next meeting! (jwf, 15:05:35)
* Upcoming Tasks (jwf, 15:05:41)
* LINK:
https://fedorapeople.org/groups/schedule/f-26/f-26-marketing-tasks.html
(jwf, 15:05:45)
* (1) Change Checkpoint: Completion deadline (Tue 2017-02-28) (jwf,
15:05:50)
* (2) Create Talking Points (start: Tue 2017-02-28) (jwf, 15:05:55)
* (3) Proposed Changes Profiles (start: Tue 2017-03-07) (jwf,
15:06:01)
* (4) Email WGs to solicit bullet points for Alpha release
announcement (start: Thu 2017-03-09) (jwf, 15:06:06)
* Open Floor (jwf, 15:06:12)
Meeting ended at 15:06:41 UTC.
Action Items
------------
* jflory7 / x3mboy Discuss possibility of using a bot to sync social
media platform (e.g. FB / Twitter / RSS) to Fedora Projects News
Telegram group
* jwf File new ticket for education-focused marketing campaign, with end
goal being to share with Fedora Council at March 22nd sub-project
report meeting
* bkp (1) Research what our old press kits were, (2) leave comment in
ticket #242 with that info, (3) all marketing team members encouraged
to discuss / give feedback for modernizing press kits
* x3mboy Leave comment in ticket #245 for initial list of "target
audiences" based on Fedora Labs, cross-compared with package
categories, to be discussed at the next meeting
Action Items, by person
-----------------------
* bkp
* bkp (1) Research what our old press kits were, (2) leave comment in
ticket #242 with that info, (3) all marketing team members
encouraged to discuss / give feedback for modernizing press kits
* jwf
* jwf File new ticket for education-focused marketing campaign, with
end goal being to share with Fedora Council at March 22nd
sub-project report meeting
* x3mboy
* jflory7 / x3mboy Discuss possibility of using a bot to sync social
media platform (e.g. FB / Twitter / RSS) to Fedora Projects News
Telegram group
* x3mboy Leave comment in ticket #245 for initial list of "target
audiences" based on Fedora Labs, cross-compared with package
categories, to be discussed at the next meeting
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* jwf (187)
* bkp (48)
* cprofitt (27)
* x3mboy (26)
* shantorn (21)
* zodbot (15)
* nirik (11)
* dhanesh95 (11)
* mailga (7)
* bexelbie (6)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
--
Cheers,
Justin W. Flory
jflory7(a)gmail.com
7 years, 1 month
[fedora-marketing] Issue #242 `Update release activity steps / process on the wiki`
by Justin W. Flory
jflory7 added a new comment to an issue you are following:
``
@bproffit++ Thanks for this comment!! This is a lot of helpful info to have… we should try to get it into somewhere static. :thumbsup:
# Mozilla strategy
I talked with @amsharma before the meeting and got a quick update from here. The current Etherpad can be found [here](https://etherpad.net/p/EUYbfXuRGG) with the raw notes, since the Piratepad appears to have issues.
To summarize…
### Questions asked
1. What are general marketing strategies followed in Mozilla communities?
2. Can we have some example wiki pages and/or more from Mozilla to study their marketing process?
3. Are there specific marketing tasks done in Mozilla during every release cycle?
### Marketing strategies
* Mozilla has **paid staff _and_ volunteers working on marketing**: Community marketing not as clearly defined or organized*
* **Community _does_ help with social media content creation**: Community members encouraged to create content (e.g. infographics, posters, etc.) for personal accounts (?), then reshared by official accounts
* **Uses the STP (Segmentation, Targeting, Positioning) model**
* In general, uses model to give more clarity about where to see yourself in few years
* _Segmentation_: Identify potential users, have a background check of existing users. Then, differentiate different types of users into groups
* _Targeting_: Have desired plans for different groups as not everyone uses product for same reasons
* _Positioning_: Time to market why should someone use product and its benefits
### Example documents
* [Engagement/Integrated Marketing](https://wiki.mozilla.org/Engagement/Integrated_Marketing)
* [Contribute/Funnels/Process#Mozilla Marketing's Process](https://wiki.mozilla.org/Contribute/Funnels/Process#Mozilla_Mark...
* [Marketing plan - Mozilla Firefox](http://www.slideshare.net/jmarovt/mozilla-firefox-marketing-plan) (older, but still possibly helpful to understand how Mozilla works to build a marketing plan)
### Understanding Mozilla release cycle tasks
* [Past audio/video meetings](https://air.mozilla.org/?tag=product+marketing) (also dated, but still helpful)
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-marketing/issue/242
7 years, 1 month
[fedora-marketing] Issue #247 `Change to Changes (idea)`
by Brian Exelbierd (bex)
bex reported a new issue against the project: `fedora-marketing` that you are following:
``
I was doing some thinking about Fedora Marketing and wound up reading through some of the F26 Changes. I realized that out template doesn't seem to specifically call out some data would be helpful to the outreach teams (Marketing, Ambassadors, Magazine, etc.) in promoting our releases.
I'd like to consider expanding the "Benefits to Fedora" and "User Experience" sections of the Changes template. I am thinking of: (note all examples are hypothetical and possibly wrong)
1.5 Benefits to Fedora (complete all that apply)
1.5.1 Benefits to Fedora (technical)
Describe the technical benefits of this change. This is how the change makes the distribution technically better. For example:
* This change modifies a package to use a different language stack that reduces install size by removing dependencies
* This upgrade results in faster resolution of user requests from /etc/passwd
* This change causes 100% of proprietary programs to be Open Source
1.5.2 Benefits to Fedora (distribution)
Address the benefits of this change to the Fedora Distribution as a whole or the specific Editions/Spins/etc. it applies too. This section is for the benefits to the project. For example:
* This change modifies the default install of Fedora Workstation to be more in line with the base install of Fedora Server. Building for a more related package set will allow for greater reuse of OpenQA tests.
* This change ensures that a minimal set of tools required for contribution to Fedora are installed easing the onboarding of new contributors.
1.9 User Experience (complete all that apply)
1.9.1 User Experience (technical)
Describe the specific interactions that will change for the user. For example:
* Kerberos tickets that can be renewed will be automatically renewed and survive reboots.
* The user's home directory will automatically clean and file downloaded files, placing them in date specific folders after 30 days.
* The default installation of Firefox will be enabled for kerberos based SSO resulting in fewer login screens.
1.9.2 User Experience (beneficial)
Why is this change good for users? How does it help them be more productive? What is the benefit of this change? For example:
* Users will now have to authenticate less and become more productive. Credential management improvements mean a user can start their work day with a single sign on and not have to pause for reauthentication during their entire day.
* Libreoffice is one of the most commonly installed applications on Fedora and it is now available by default to help users "hit the ground running."
* Python developers will find the package separation between Python 3 and Python 2 makes it easier for them to know what is installed and being used by which version. Dependency auto-completion will cause executed code to automatically pull packaged pypi packages as needed by the Python interpreter. This will result in more successful executions of code during the development process.
* Green has been scientifically proven to be the most relaxing color. The move to a default background color of green with green text will result in Fedora users being the most relaxed users of any operating system.
I believe these sections will help drive our changes into a story for our users and show that we are making decisions for the distribution to benefit our users. We do that today but we aren't necessarily telling our users about it. I hope this data will help the outreach groups do even more in the way of sharing this story.
I'd appreciate your feedback on this. Will this actually help the outreach teams?
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-marketing/issue/247
7 years, 1 month