Content services: Difference between revisions

Jump to navigation Jump to search

Content services (view source)

Revision as of 00:02, 24 February 2015

3,019 bytes removed ,  24 February 2015
Removed 2014 content, updated vision and mission
(Removed 2014 content, updated vision and mission)
Line 3: Line 3:
The Content Services Team was formed in late 2013 to explore opportunities that will provide additional value to our users, strongly align with our mission, and over time, generate new sources of diversified revenue.
The Content Services Team was formed in late 2013 to explore opportunities that will provide additional value to our users, strongly align with our mission, and over time, generate new sources of diversified revenue.


We are particularly fascinated by the content ecosystem online – which is one of the primary currencies of the web.   How does content get distributed? How does content get monetized? How can we create better content experiences for our users?  All questions we continue to ask ourselves.
The team works to make the web economically and socially sustainable.  We want to sustain it economically, to ensure that the Web remains a place of economic opportunity for content creators. And we wish to make is socially sustainable, meaning that we wish to address the "maladies" that the advertising-supported content ecosystem has engendered on the Web, including:
* poor use experience
* widespread use of proprietary technology on the Web
* ad fraud
* lack of user control over data resulting in a loss of privacy


A group of Mozillians from the Steering Committee and Firefox team evaluated more than two dozen revenue related proposals in late 2013. Each idea we considered was closely evaluated on whether it resulted in incremental value to our users, aligned with our mission and values, and had the potential to significantly impact our sustainability over time.
Our current mission is to provide in-browser promoted content experiences for advertisers who want better, higher-quality relationships with their audience
 
and who choose Mozilla Content Services in order to have a future-facing, ethical partner with scale.
Below are the initial projects we decided to test..




Line 14: Line 17:
===Directory Tiles===
===Directory Tiles===
:Every time a user opens up a new tab in Firefox, the browser displays Tiles. Frequent Firefox users see screenshots of the websites they visit most often in their Tiles. We look to leverage the Tiles on our New Tab pages and make them a source of revenue for Mozilla. There are a few opportunities that we will test in market (first in pre-release channels) within 2014 and the first of which is to provide sponsored content on First-Run-Tiles known as Directory Tiles. This should begin testing in Q2/3 and we will then work on additional Tile enhancements outside of First-Run.
:Every time a user opens up a new tab in Firefox, the browser displays Tiles. Frequent Firefox users see screenshots of the websites they visit most often in their Tiles. We look to leverage the Tiles on our New Tab pages and make them a source of revenue for Mozilla. There are a few opportunities that we will test in market (first in pre-release channels) within 2014 and the first of which is to provide sponsored content on First-Run-Tiles known as Directory Tiles. This should begin testing in Q2/3 and we will then work on additional Tile enhancements outside of First-Run.
===[https://wiki.mozilla.org/Mozilla_Voices Mozilla Voices]===
:[https://wiki.mozilla.org/Mozilla_Voices Mozilla Voices] will be a world class editorial platform showcasing the ideas, organizations, communities, movements and individuals who best exemplify how open systems empower people to reach their fullest potential.
:We advocate that Open Systems create healthier communities and more successful societies overall. We will cover everything from open source to open government and the need for transparency; privacy and security, the "Internet of Things" vs. "pervasive computing", to education and if it's keeping up with the technological changes. The bottom line? Open is better.
:When complete, Voices will have a full-time editorial news-gathering staff and a global set of contributors – both paid and volunteer – to contribute stories, as well as offer news ideas (leads) for the editorial staff and recommend the best expert sources.
:At its best, Voices will start conversations and settle argument.


===[https://intranet.mozilla.org/UP UP/Intent Engine]===
===[https://intranet.mozilla.org/UP UP/Intent Engine]===
:[https://intranet.mozilla.org/UP UP] is our Intent Engine for across Mozilla that helps us deliver personalization platforms for all of our products and services. Our 2014 strategy is to keep building our UP platform to make it available to the desktop, OS, services, and other products and have the bridges built this year that each product team has the ability to read/write to it. We will do limited tests in Q2/3/4 of this year to test different Intent Engine modules (such as tasks, discovery, personalization, ads).  Within UP, we have a particular focus around Intentcasting and VRM.
:[https://intranet.mozilla.org/UP UP] is our Intent Engine for across Mozilla that helps us deliver personalization platforms for all of our products and services. Our 2014 strategy is to keep building our UP platform to make it available to the desktop, OS, services, and other products and have the bridges built this year that each product team has the ability to read/write to it. We will do limited tests in Q2/3/4 of this year to test different Intent Engine modules (such as tasks, discovery, personalization, ads).  Within UP, we have a particular focus around Intentcasting and VRM.


===[https://intranet.mozilla.org/Subscribe2Web Subscribe2Web]===
:[https://intranet.mozilla.org/Subscribe2Web Subscribe2Web] is a program within the Content Services group that is working on ways for users to support content creators they love without having to resort to advertising. Our first pilot, in Sweden and Poland, intends to test how much users are willing to spend on an ad free experience, and how that might work.
:Pilot1 is planned for Q4 2014 in Poland and Sweden
==Content Services Roadmap==
<b>Q1 2014:</b> Grow Team - We’ll start by hiring a small team of paid staff who can dedicate the majority of their time thinking about how to develop and execute these initiatives. We’ll also look to grow support within the Mozillian community by exploring opportunities for participation and through regular dialog.
<b>Q2 2014:</b> Directory Tiles Initial Testing & Grow Team<br>
June 16-20 will be a Work Week in New York City for Content Services.  We'll be spending time thinking about the product roadmap and working with the community and partners to achieve our goals.
<b>Q3 2014:</b> Voices Soft Initial Testing, Grow Team, Tiles (to Beta, redefine UI/UX), and UP's Personal Interest Dashboard
<b>Q4 2014:</b> UP Content Recommendation Testing, Voices Testing, and scale Tiles


== Content Services Resources==
== Content Services Resources==
Line 49: Line 28:
Check out our [https://blog.mozilla.org/advancingcontent/ Official Content Services Blog.]
Check out our [https://blog.mozilla.org/advancingcontent/ Official Content Services Blog.]


Watch the Directory Tiles Town Hall on [https://air.mozilla.org/town-hall-directory-tiles/ AirMozilla.]
Join our Interest mailing list [https://mail.mozilla.org/listinfo/contentservices-distro ContentServices Distro]
 
== Get Involved/Share Ideas & Feedback==
 
If you’re interested in what we are doing,  we’d love for you to subscribe to our group and contribute to the discussions. We are also actively hiring, so if you’re interested in joining our team, check out Mozilla’s careers page for opportunities. We have lots to talk about in the coming weeks and months!
 
In the meantime, if you have anything to add, feel free to reach out to [mailto:contentservices@mozilla.com?Subject=Your%20Subject%20Here the Content Services Team]
 
== IRC Channel ==


You can also ping us at #mozcontent
Reach out on email to [mailto:contentservices@mozilla.com?Subject=Your%20Subject%20Here the Content Services Team]


=June 2014 Work Week=
Find us on IRC #mozcontent
From June 16-20, 40+ Mozillians came to the Manhattan, NY based Content Services office to discuss Content Services. The schedule was packed with presentations from each Product Manager (Tiles, UP, Subscribe2Web, Voices, DirectPay & Notifications), community, outside speakers (The Media Kitchen, Wired), and many others.
Pfinch
173

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/1057723"

Navigation menu