Closed Bug 958143 Opened 12 years ago Closed 9 years ago

[Tracker] MWC Workstream 1 - Content Partners

Categories

(Tracking :: User Story, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: cgalimidi, Assigned: mellis)

References

Details

Please create bugs for each project in this workstream, and block this bug. Workstream 1 (external): Content Partners - lead Michael Ellis - we now have a pretty good idea of the opportunities we can offer to key content partners Opportunity 1: demo their app on one of our 2 presentation pods next to the coffee area on the Mozilla stand Opportunity 2: 45-minute session in the Fox Den Opportunity 3: partner app pre-installed on demo devices and part of the Marketplace demo script (more on this in workstream 2) Opportunity 4: partner invited to Sunday Press Event Opportunity 5: partner highlighted on printed handout Opportunity 6: partner highlighted on website Opportunity 7: invitation to BD event (24 Feb, 150-200 partners invited including some content partners) and/or invitation to on-stand networking drinks (26 Feb, general show attendees) - Michael Ellis is putting together 1) a presentation listing these opportunities and 2) a spreadsheet to track which partners get what (including schedules for presentation pods and fox den) - call set up with the BD content team to agree which content partners we want to offer these opportunities to. Clearly these will only be content partners that help reinforce our messages around the strength of the html5 ecosystem. - call to be set up with Erica to agree partners we'd like to have at our Sunday press event - in parallel on the long-tail side, Mark Coggins is inviting 5 indie developers who have built great html5 apps for FxOS (more detail in his email below). These 5 developers will be included in the rota for the presentation pods (opportunity 1).
Summary: [Tracker] Content Partner Demos → [Tracker] MWC Workstream 1 - Content Partners
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.