Closed pwalm closed 10 years ago
Here are some additional ones. Again, I think we can do some classifying here, into ideas that support editorial, support developers, involve localization, etc. I can work on a spreadsheet for this.
Editorial Support (helping Scott with Mozilla editorial)
Developer Support
User Support
Concern: many Editorial Support activities are less interesting than creating new materials.
As a contributor:
Editorial Support | Developer Support | User Support |
---|---|---|
Help localise editorial content that Mozilla came up with. For example: we’re launching 10 new collections in Brazil and 10 other collections in India. We have the English text already. | Supplement app listing page with functional, good-looking additional screenshots and videos – taken from a Firefox OS device | Abuse patrol. Look through Marketplace for reviews, apps, other content that is inappropriate. |
Review new apps - Give list of new apps in the Marketplace and encourage contributors to review them. X number of reviews could earn them recognition. Contributors could specialize in certain categories (games) and locales (Brazil). Recommendations passed on to Scott. | Localise app listing page. A lot of app landing page is only available in English. A lot of developers don’t, or can’t, localise. A contributor should be able to do this. The app might not be localised, but at least its description is. | |
Find apps for x. Have contributors find apps for a particular thing on the editorial calendar. For example, finding Christmas-related apps | Help make screenshots interactive. Let’s say that the app listing page has a screenshot of the app’s home screen. What are the parts, and what do they do? | |
Missing apps. Identifying gaps in content in locales and raising issue to editorial team. For example, identifying lack of newspapers in Macedonia. | Mark information in the app listing page as needing correction. Somebody else is notified and invited to correct it. | |
New and notable. Every so often, a great app comes along but is overlooked by the editors. A community member can be constantly on the lookout for these hidden gems: trying, testing, and recommending them for the editors. | Edit app listing page. Let’s say that you’ve found a typo or incorrect information in the app landing page. As a contributor, you have the power to correct this information. Corrections are sent to developers for approval. Contributors get credit. | |
Localise apps. This isn’t related to the app listing page. This is about localising the apps themselves, and helping developers to get their app strings translated into other languages using tools like Transifex. | ||
App promoters. Hook developers up with contributors who are passionate about their app. Have contributor work with developer to promote app via Facebook, Twitter, etc. |
Help localise editorial content Scott has been using an agency to localize editorial content to date. I think the turn around was too fast for the l10n community to translate the text. @pwalm localization might be a good topic to talk to Scott about on Friday.
I think your concern about why community would want to help the editorial team rather than do their own thing is valid. Advantages of helping the editorial team are the prestige of being an official board/team member, getting the inside scoop on the editorial calendar and what is happening on the Marketplace. Helping the editorial team might be less time consuming then creating their own content. They also might not be confident in their writing skills and would rather identify apps then write content.
Very alpha customer journey maps for three concepts.
Localise app description
Supplement app listing with additional screenshots
Suggest an edit to app information, and editing app information
These are a great first start. My only concern is how does a developer know that the new localization is appropriate? Like, if someone translated my app into Polish, I'd have no idea how "good" the translation is (other than running it through Google Translate). Do we just count on the community to spot that when published?
After conversation with stakeholders, we’ve decided to go ahead with these ideas:
We may return to this list again to brainstorm or get inspiration for more or related ideas.
Ideas discussed here have been logged and elabored on the spec page: http://pwalm.github.io/marketplace-community-editorial/contributionTypes.html
If more ideas are needed, you can either reopen this issue or create a new one.