Browse files

added developer FAQ page (bug 719978)

  • Loading branch information...
1 parent 349b3bc commit ae9986e292069efa5cdd1e277fed10b6e2fab144 @potch potch committed Jan 26, 2012
Showing with 705 additions and 0 deletions.
  1. +703 −0 apps/pages/templates/pages/dev_faq.html
  2. +2 −0 apps/pages/urls.py
View
703 apps/pages/templates/pages/dev_faq.html
@@ -0,0 +1,703 @@
+{% extends "impala/base_shared.html" %}
+
+{% block title %}
+ {{ page_title(_('Developer FAQ')) }}
+{% endblock %}
+
+{% block extrahead %}
+ <style>
+ .faq {
+ font-size: 1.1em;
+ }
+ .faq h2 {
+ font-size: 1.5em;
+ margin: 1em 0;
+ }
+ .faq h3 {
+ font-weight: bold;
+ margin: 1em 0;
+ }
+ .fq p
+ .faq ul {
+ margin-bottom: 1em;
+ }
+ .faq ul li {
+ margin-bottom: 0;
+ }
+ </style>
+{% endblock %}
+
+{% block content %}
+ <aside class="secondary">
+ <h2>{{ _('Sections') }}</h2>
+ <ul>
+ <li><a href="#developing">{{ _('Developing an Add-on') }}</a></li>
+ <li><a href="#support-resources">{{ _('Support Resources') }}</a></li>
+ <li><a href="#contributing">{{ _('Contributing your Addon') }}</a></li>
+ <li><a href="#review-process">{{ _('Add-on Review Process') }}</a></li>
+ <li><a href="#managing">{{ _('Managing Your Add-on') }}</a></li>
+ <li><a href="#recommended-status">{{ _('Recommended Status') }}</a></li>
+ <li><a href="#user-reviews">{{ _('User Reviews') }}</a></li>
+ <li><a href="#license">{{ _('References for Open Source Licenses') }}</a></li>
+ </ul>
+ </aside>
+ <section class="prose faq primary">
+ <h1>{{ _('Add-on Developer FAQ') }}</h1>
+
+ <h2 id="developing">{{ _('Developing an Add-on') }}</h2>
+
+ {% trans url='https://developer.mozilla.org/En/Building_an_Extension' %}
+ <h3>How do I build an Add-on?</h3>
+ <p>
+ Mozilla provides documentation on how to build an add-on via the
+ Mozilla Developer Center. The tutorial, <a href="{{ url }}">Building
+ an Extension</a>, will help explain how to setup your work environment
+ and move forward with creating an add-on.
+ </p>
+ {% endtrans %}
+
+ <p>{{ _('Other resources include:') }}</p>
+ <ul>
+ {# L10n: update the links to point to the proper locales if available #}
+ {% trans %}
+ <li>
+ <a href="https://developer.mozilla.org/En/Firefox_addons_dev_guide">
+ Firefox Add-ons Developer Guide</a>
+ </li>
+ <li>
+ <a href="http://blog.mozilla.com/addons/2009/01/28/how-to-develop-a-firefox-extension/">
+ Robert Nyman's article "How to develop a Firefox extension"</a>
+ </li>
+ <li>
+ <a href="http://blog.mozilla.com/addons/2009/03/18/video-tutorial-extensions-bootcamp-zero-to-hello-world-in-45-minutes/">
+ Myk Melez's video tutorial "Video Tutorial - Extensions Bootcamp:
+ Zero to “Hello World” in 45 Minutes"</a>
+ </li>
+ {% endtrans %}
+ </ul>
+
+ <h3>{{ _('What tools do I need to be able to build an Add-on?') }}</h3>
+ <p>
+ {% trans %}
+ You will need to have a version the Mozilla software that you're
+ building the add-on for and a code editor of your choice. Add-ons
+ can be built for almost all Mozilla software but are primarily
+ targeted for:
+ {% endtrans %}
+ </p>
+
+ <ul>
+ {# L10n: update the links to point to the proper locales if available #}
+ {% trans %}
+ <li><a href="http://www.mozilla.com/en-US/firefox/">Firefox</a></li>
+ <li><a href="http://www.mozillamessaging.com/en-US/thunderbird/">Thunderbird</a></li>
+ <li><a href="http://www.seamonkey-project.org/">SeaMonkey</a></li>
+ <li><a href="http://www.mozilla.org/projects/calendar/sunbird/">Sunbird</a></li>
+ {% endtrans %}
+ </ul>
+
+ <p>{{ _('Popular code editors include:') }}</p>
+ <ul>
+ {# L10n: update the links to point to the proper locales if available #}
+ {% trans %}
+ <li><a href="http://www.activestate.com/komodo_edit/">Komodo Edit</a></li>
+ <li><a href="http://macromates.com/">TextMate</a></li>
+ <li><a href="http://notepad-plus.sourceforge.net/uk/site.htm">Notepad++</a></li>
+ <li><a href="http://www.eclipse.org/">Eclipse IDE</a></li>
+ {% endtrans %}
+ </ul>
+
+ <p>
+ {# L10n: update the link to point to your locale on MDN if available #}
+ {% trans %}
+ You can also learn more about setting up your development environment
+ via the MDC article
+ <a href="https://developer.mozilla.org/en/Setting_up_extension_development_environment">Setting up extension development environment</a>
+ {% endtrans %}
+ </p>
+
+ <h3>{{ _('Where can I find documentation on building add-ons?') }}</h3>
+ {# L10n: update the links to point to your locale if available #}
+ {% trans %}
+ <p>
+ All Mozilla documentation on add-on development including tutorials
+ and APIs can be found via the <a href="https://developer.mozilla.org/En">Mozilla Developer Center</a>.
+ {% endtrans %}
+
+ <h3>{{ _('What is a ".xpi" file?') }}</h3>
+ <p>
+ {% trans %}
+ Extensions are packaged and distributed in ZIP files or Bundles, with
+ the XPI (pronounced “zippy”) file extension.
+ {% endtrans %}
+ </p>
+
+ <h3>{{ _('What is XUL?') }}</h3>
+ <p>
+ {% trans %}
+ XUL (XML User Interface Language) is Mozilla's XML-based language
+ that lets you build feature-rich cross platform applications. It
+ provides user interface widgets like buttons, menus, toolbars,
+ trees, etc that can be used to enhance add-ons by modifying parts
+ of the browser UI.
+ {% endtrans %}
+ </p>
+
+ <h3>{{ _('What is the "install.rdf" file used for?') }}</h3>
+ <p>
+ {% trans %}
+ This file, called an <a href="https://developer.mozilla.org/en/Install_Manifests">Install Manifest</a>,
+ is used by Add-on Manager-enabled XUL applications to determine
+ information about an add-on as it is being installed. It contains
+ metadata identifying the add-on, providing information about who
+ created it, where more information can be found about it, which
+ versions of what applications it is compatible with, how it should
+ be updated, and so on. The format of the Install Manifest is RDF/XML.
+ {% endtrans %}
+ </p>
+
+ <h3>{{ _('What does "maxVersion" mean?') }}</h3>
+ <p>
+ {% trans %}
+ This determines the maximum version of Firefox you're saying this
+ extension will work with. Set this to be no newer than the newest
+ currently available version!
+ {% endtrans %}
+ </p>
+
+ <h3>{{ _('Can my add-on contain binary components?') }}</h3>
+ <p>
+ {% trans %}
+ Yes. You can use Mozilla's
+ <a href="https://developer.mozilla.org/en/XPCOM">XPCOM component object model</a>
+ to enhance your add-ons. XPCOM components be used and implemented in
+ JavaScript, Java, and Python in addition to C++.
+ {% endtrans %}
+ </p>
+
+ <h3>{{ _('Can I use a JavaScript library like jQuery, MooTools or Prototype to build my add-on?') }}</h3>
+ <p>
+ {% trans %}
+ Yes. It's possible, but some of the functionality provided by these
+ libraries are available through XPCOM, XUL, and JS 1.8. In addition,
+ authors should take care if libraries modify primitive object
+ prototypes (String.prototype, Date.prototype, etc.) and/or define
+ global functions (eg. the $ function). These are prone to cause
+ conflict with other add-ons, in particular if different add-ons use
+ different versions of libraries and so on. Developers need to be
+ very, very careful with using them. Mozilla does not offer
+ documentation on using them to build add-ons.
+ {% endtrans %}
+ </p>
+
+ <h3>{{ _('How do I test my add-on?') }}</h3>
+ <p>
+ {# L10n: update the links to point to your locale if available #}
+ {% trans %}
+ Details on testing your add-on are provided in the
+ <a href="https://developer.mozilla.org/en/Building_an_Extension#Test">Testing</a> &amp;
+ <a href="https://developer.mozilla.org/en/Building_an_Extension#Debugging_Extensions">Debugging Extensions</a> sections of the
+ <a href="https://developer.mozilla.org/en/Building_an_Extension">Building an Extension tutorial</a>.
+ {% endtrans %}
+ </p>
+
+ <h3>{{ _('How do I test for compatibility with the latest version of Mozilla software?') }}</h3>
+ <p>
+ {# L10n: update the links to point to your locale if available #}
+ {% trans %}
+ To ensure compatibility with the latest Mozilla software, it's
+ important to download updates as they become available and test your
+ add-on to ensure that it is still functioning as expected. It's best
+ to follow the steps outlined in the
+ <a href="https://developer.mozilla.org/en/Building_an_Extension">Building an Extension</a>
+ tutorial for <a href="https://developer.mozilla.org/en/Building_an_Extension#Test">testing your add-on</a>.
+ In many cases, the latest version of Mozilla
+ software may be a beta release. Since these releases at times
+ introduce architectural changes that may impact the functionality of
+ your add-on, it's important to be actively involved in the beta
+ process to ensure that you're add-on users are not negatively
+ impacted upon final release of Mozilla software.
+ {% endtrans %}
+ </p>
+
+ <h3>{{ _('What is leak testing?') }}</h3>
+ <p>
+ {% trans %}
+ Memory leaks are typically bugs in the source code used to build
+ applications which consume system memory without properly releasing
+ it once the application has finished. Leak testing allows you to
+ pinpoint which bit of code is causing the memory leak. The following
+ is a good <a href="https://wiki.mozilla.org/Performance:Leak_Tools">guide to
+ finding tools and strategies</a> that help manage leak testing.
+ Mozilla's Carsten Book has also written an excellent HOW-TO article
+ on the subject of <a href="https://wiki.mozilla.org/QA:Home_Page:Firefox_3.0_TestPlan:Leaks:LeakTesting-How-To">leak
+ testing in Firefox</a>.
+ {% endtrans %}
+ </p>
+
+ <h3>{{ _('Can my add-on support multiple locales?') }}</h3>
+ <p>
+ {# L10n: update the links to point to your locale if available #}
+ {% trans %}
+ Yes. Details on localizing your add-on can be found in the
+ <a href="https://developer.mozilla.org/en/Building_an_Extension#Localization">Building an Extension</a>
+ tutorial as well as the
+ <a href="https://developer.mozilla.org/en/Localization">Mozilla Developer Center Localization page</a>.
+ <a href="http://www.babelzilla.org/">The BabelZilla project</a>
+ is also a great resource for learning about localization and
+ volunteering to help translate add-ons.
+ {% endtrans %}
+ </p>
+
+
+ {# L10n: Heading for a list of resources for developers #}
+ <h2 id="support-resources">{{ _('Support Resources') }}</h2>
+
+ <h3>{{ _('I need some advice building my add-on. Where can I find help?') }}</h3>
+ <p>{{ _('Mozilla offers the following support options for add-on developers:') }}</p>
+ <ul>
+ <li>
+ irc://irc.mozilla.org/
+ <ul>
+ <li>{{ _('#extdev (for add-on development discussions)') }}</li>
+ <li>{{ _('#amo (for support relating to hosting your add-on on AMO)') }}</li>
+ </ul>
+ </li>
+ <li><a href="https://lists.mozilla.org/listinfo/dev-extensions">
+ {# L10n: Label for a link to the extension developers mailing list #}
+ {{ _('Mailing List') }}
+ </a></li>
+ <li><a href="news://news.mozilla.org/mozilla.dev.extensions">
+ {# L10n: Label for a link to the extension developers newsgroup #}
+ {{ _('Newsgroup') }}
+ </a></li>
+ <li><a href="http://groups.google.com/group/mozilla.dev.extensions">
+ {# L10n: Label for a link to the extension developers Google Group #}
+ {{ _('Google Group') }}
+ </a></li>
+ </ul>
+
+ <h3>{{ _('Does Mozilla offer development services?') }}</h3>
+ {{ _('No.') }}
+
+ <h3>{{ _('Are there 3rd party developers that I can hire to build my add-on?') }}</h3>
+ <p>
+ {% trans %}
+ Yes. You may find 3rd party developers via the <a href="http://www.mozilla.org/community/developer-forums.html#projectwide-forums">mozilla.jobs
+ list</a>, <a href="http://forums.mozillazine.org/">mozillaZine
+ forums</a> or <a href="http://consultants.mozdev.org/">MozDev</a>.
+ Please note that Mozilla does not offer developer recommendations
+ {% endtrans %}
+ </p>
+
+ <h2 id="contributing">Contributing your Addon</h2>
+
+ <h3>{{ _('Can I host my own add-on?') }}</h3>
+ <p>
+ {% trans %}
+ Yes. Many developers choose to host their own add-ons. Choosing to
+ host your add-on on Mozilla's AMO (<a href="https://addons.mozilla.org">https://addons.mozilla.org</a>),
+ though, allows for much greater exposure to your add-on due to the
+ large volume of visitors to the site. The <a href="http://mozdev.org/">mozdev.org</a> site offers free project
+ hosting for Mozilla applications and extensions providing developers
+ with tools to help manage source code, version control, bug tracking
+ and documentation.
+ {% endtrans %}
+ </p>
+
+ <h3>{{ _('Can Mozilla host my add-on?') }}</h3>
+ <p>
+ {% trans %}
+ Yes. You can host your add-on on Mozilla's AMO
+ (<a href="https://addons.mozilla.org">https://addons.mozilla.org</a>)
+ website.
+ {% endtrans %}
+ </p>
+
+ <h3>{{ _('What is AMO?') }}</h3>
+ <p>
+ {% trans %}
+ Mozilla's AMO (<a href="https://addons.mozilla.org">https://addons.mozilla.org</a>) is
+ the incubator that helps developers build, distribute, and support
+ fantastic consumer products powered by Mozilla. It provides you the
+ tools and infrastructure necessary to manage, host and expose your
+ add-on to a massive base of Mozilla users.
+ {% endtrans %}
+ </p>
+
+ <h3>{{ _('Does Mozilla keep my account information private?') }}</h3>
+ Yes. Our <a href="https://addons.mozilla.org/en-US/firefox/pages/privacy">Privacy Policy</a> describes how your information is managed by Mozilla.
+
+ <h3>{{ _('What are the "developer tools" listed on AMO?') }}</h3>
+ <p>
+ {% trans %}
+ The "Developer Tools" dashboard is the area that provides you the
+ tools to successfully manage your add-ons. It provides the
+ functionality necessary to submit your add-ons to AMO, manage add-on
+ information, and review statistics.
+ {% endtrans %}
+ </p>
+
+ <h3>{{ _('Does Mozilla have a policy in place as to what is an acceptable submission?') }}</h3>
+ <p>
+ {% trans %}
+ Yes. Mozilla's <a href="https://addons.mozilla.org/en-US/firefox/pages/policy">Add-on
+ Policy</a> describes what is an acceptable submission. This policy is
+ subject to change without notice. In addition, the AMO editorial
+ team uses the <a href="https://wiki.mozilla.org/AMO:Editors/ReviewingGuide">Editors
+ Reviewing Guide</a> to ensure that your add-on meets specific
+ guidelines for functionality and security.
+ {% endtrans %}
+ </p>
+
+ <h3>{{ _('How do I submit my add-on for review?') }}</h3>
+ <p>
+ {% trans %}
+ The Developer Tools dashboard will allow you to upload and submit
+ add-ons to AMO. You must be a registered AMO users before you can
+ submit an add-on. Before submitting your add-on be sure to you have
+ read the AMO <a href="https://wiki.mozilla.org/AMO:Editors/ReviewingGuide">Editors
+ Reviewing Guide</a> to ensure that your add-on has met the guidelines
+ used by editors to review add-ons
+
+ {% endtrans %}
+ </p>
+
+ <h3>{{ _('What operating system do I choose for my add-on?') }}</h3>
+ <p>
+ {% trans %}
+ You must choose the operating systems on which your add-on will
+ successfully function.
+ {% endtrans %}
+ </p>
+
+ <h3>{{ _('What category do I choose for my add-on?') }}</h3>
+ <p>
+ {% trans %}
+ The choice of category is dependent on what type of audience you are
+ targeting and the functionality of your add-on. If you're unsure of
+ which category your add-on falls into, please choose "Other". The AMO
+ team may re-categorize your add-on if it's determined that it's
+ better suited in a different category
+ {% endtrans %}
+ </p>
+
+ <h3>{{ _('What does "nominating" my add-on mean?') }}</h3>
+ <p>
+ {% trans %}
+ Nominated add-ons are new add-ons that the author has nominated to
+ become public via the Developer Tools.
+ {% endtrans %}
+ </p>
+
+ <h3>{{ _('Can I specify a license agreement for using my add-on?') }}</h3>
+ <p>
+ {% trans %}
+ Yes. You can specify a license agreement when submitting your add-on.
+ You can also add or update a license agreement via the Developer
+ Tools dashboard after your add-on has been submitted.
+ {% endtrans %}
+ </p>
+
+ <h3>{{ _('Can I include a privacy policy for my add-on?') }}</h3>
+ <p>
+ {% trans %}
+ Yes. You can specify a privacy policy when submitting your add-on.
+ You can also add or update a privacy policy via the Developer Tools
+ dashboard after your add-on has been submitted.
+ {% endtrans %}
+ </p>
+
+ <h2 id="review-process">{{ _('Add-on Review Process') }}</h2>
+
+ <h3>{{ _('Why must my add-on be reviewed?') }}</h3>
+ <p>
+ {% trans %}
+ All add-ons submitted, whether new or updated, are reviewed to ensure
+ that Mozilla users have a stable and safe experience. All add-ons
+ submissions are reviewed using the guidelines outlined in the
+ <a href="https://wiki.mozilla.org/AMO:Editors/ReviewingGuide">Editors
+ Reviewing Guide</a>.
+ {% endtrans %}
+ </p>
+
+ <h3>{{ _('Who reviews my add-on?') }}</h3>
+ <p>
+ {% trans %}
+ Add-ons are reviewed by the AMO Editors, a group of talented
+ developers that volunteer to help the Mozilla project by reviewing
+ add-ons to ensure a stable and safe experience for Mozilla users.
+ When communicating with editors, please be courteous, patient and
+ respectful as they are working hard to ensure that you're add-on is
+ setup correctly and follows the guidelines outlined in the <a href="https://wiki.mozilla.org/AMO:Editors/ReviewingGuide">Editors
+ Reviewing Guide</a>
+ {% endtrans %}
+ </p>
+
+ <h3>{{ _('What is the sandbox?') }}</h3>
+ <p>
+ {% trans %}
+ A complete explanation of the <a href="https://addons.mozilla.org/en-US/firefox/pages/sandbox">AMO
+ Sandbox</a> can be found <a href="https://addons.mozilla.org/en-US/firefox/pages/sandbox">here</a>
+ {% endtrans %}
+ </p>
+
+ <h3>{{ _('Why is my add-on marked as "experimental"?') }}</h3>
+ <p>
+ {% trans %}
+ Newly submitted and nominated add-ons are listed as "experimental"
+ until they have been properly reviewed by a member of the editorial
+ team. This ensures that users are aware of the add-on's status before
+ choosing to install an add-on that has not been fully reviewed
+ {% endtrans %}
+ </p>
+
+ <h3>{{ _('What are the guidelines used to review my add-on?') }}</h3>
+ <p>
+ {% trans %}
+ The Mozilla editorial team follows the <a href="https://wiki.mozilla.org/AMO:Editors/ReviewingGuide">Editors
+ Reviewing Guide</a> when testing an add-on for acceptance onto AMO.
+ It is important that add-on developers review this guide to ensure
+ that common problem areas are addressed prior to submitting their
+ add-on for review. This will greatly assist in expediting the review
+ process
+ {% endtrans %}
+ </p>
+
+ <h3>{{ _('How long will it take for my add-on to be reviewed?') }}</h3>
+ <p>
+ {% trans %}
+ We cannot give a time estimate as to how long it will take before an
+ add-on is reviewed. Many factors affect the time including the:
+ {% endtrans %}
+ </p>
+ <ul>
+ <li>{{ _('number of add-on submissions') }}</li>
+ <li>{{ _('complexity of an add-on’s code') }}</li>
+ <li>{{ _('number of problem areas discovered') }}</li>
+ </ul>
+ <p>
+ {% trans %}
+ This is why it's very important to read the <a
+ href="https://wiki.mozilla.org/AMO:Editors/ReviewingGuide">Editors
+ Reviewing Guide</a> to ensure that your add-on is setup as expected.
+ It's also a good idea to read the blog post, <a
+ href="http://blog.mozilla.com/addons/2009/01/14/successfully-getting-your-addon-reviewed/">Successfully
+ Getting your Addon Reviewed</a> which provides excellent insight into
+ ensuring a smooth review of your add-on.
+ {% endtrans %}
+ </p>
+
+ <h2 id="managing">{{ _('Managing Your Add-on') }}</h2>
+
+ <h3>{{ _('How can I see how many times my add-on has been downloaded?') }}</h3>
+ <p>
+ {% trans %}
+ The Statistics Dashboard found in the Developer Tools dashboard
+ provides information that can help you determine your add-on
+ downloads since you've submitted it to AMO.
+ {% endtrans %}
+ </p>
+
+ <h3>{{ _('How can I see how many active users are using my add-on?') }}</h3>
+ <p>
+ {% trans %}
+ The Statistics Dashboard found in the Developer Tools dashboard
+ provides information that can help you determine how many users have
+ been actively using your add-on since you've submitted it to AMO.
+ {% endtrans %}
+ </p>
+
+ <h3>{{ _('How do I submit an update for my add-on?') }}</h3>
+ <p>
+ {% trans %}
+ You can submit an update for your add-on via the Developer Tools
+ dashboard by choosing the option "Upload a new version" and uploading
+ a new .xpi file for your add-on.
+ {% endtrans %}
+ </p>
+
+ <h3>{{ _('Does my update need to be reviewed by editors?') }}</h3>
+ <p>
+ {% trans %}
+ That depends. If you are simply changing a description of your add-on
+ or updating a "maxVersion" to ensure compatibility with a new Mozilla
+ software update, then your add-on does not need to be reviewed again.
+ If, however, you submit a new updated file, then your add-on update
+ will need to be reviewed by an editor.
+ {% endtrans %}
+ </p>
+
+ <h2 id="recommended-status">{{ _('Recommended Status') }}</h2>
+
+ <h3>{{ _('What are the Recommended Lists?') }}</h3>
+ <p>
+ {% trans %}
+ The Recommended lists are an important part of exposing AMO visitors
+ to useful and compelling add-ons within a small &amp; focused list.
+ It allows us to feature add-ons that have done a good job of creating
+ a unique and/or exciting enhancement to Mozilla software and
+ increasing awareness of the thousands of add-ons hosted on AMO. The
+ lists are broken down into two categories; Recommended and Category
+ Recommended. The former is shown on the home page of AMO and is
+ typically limited to 40 featured add-ons. The latter are lists of
+ add-ons that are recommended at the category level. The only
+ distinction between the two lists is that Category Recommended
+ add-ons are not featured on the home page. Apart from that, both
+ lists are meant to recognize the achievements of individual add-on
+ authors and the work they’ve produced.
+ {% endtrans %}
+ </p>
+
+ <h3>{{ _('What is a Featured add-on?') }}</h3>
+ <p>
+ {% trans %}
+ The main page of AMO as well as the main page for each category
+ contain three slots which are used to display a set of Featured
+ Add-Ons. These add-ons are pulled from the Recommended and Category
+ Recommended lists respectively and periodically rotated as described
+ in the <a
+ href="https://wiki.mozilla.org/AMO:Editors/Featured_and_Recommended#Featured_Add-Ons">Featured
+ Add-ons FAQ</a> to allow recommended add-ons a chance for increased
+ visibility to users. Featured add-ons are rotated regularly to
+ prevent staleness.
+ {% endtrans %}
+ </p>
+
+ <h3>{{ _('How can my add-on be listed as Recommended?') }}</h3>
+ <p>
+ {% trans %}
+ The <a
+ href="http://blog.mozilla.com/addons/2009/03/10/the-hows-whys-of-the-amo-recommended-rotation/">following
+ blog post</a> describes the process by which the Recommended lists
+ are managed.
+ {% endtrans %}
+ </p>
+
+ <h3>{{ _('Can I pay to have my add-on listed as Recommended?') }}</h3>
+ <p>{{ _('No.') }}</p>
+
+ <h3>{{ _('Why is my add-on no longer listed as Recommended?') }}</h3>
+ <p>
+ {% trans %}
+ The <a
+ href="http://blog.mozilla.com/addons/2009/03/10/the-hows-whys-of-the-amo-recommended-rotation/">following
+ blog post</a> describes the process by which the Recommended lists
+ are managed.
+ {% endtrans %}
+ </p>
+
+ <h2 id="user-reviews">{{ _('User Reviews') }}</h2>
+
+ <h3>{{ _('How do I reply to a user who has posted a negative review of my add-on?') }}</h3>
+ <p>
+ {% trans %}
+ A developer may reply to any review posted to their add-on as long as
+ they are logged into AMO. In addition, any user can flag a review as:
+ {% endtrans %}
+ </p>
+ <ul>
+ <li>{{ _('Spam or otherwise non-review content') }}</li>
+ <li>{{ _('Inappropriate language/dialog') }}</li>
+ <li>{{ _('Misplaced bug report or support request') }}</li>
+ <li>{{ _('Other (provides a pop-up prompt for information)') }}</li>
+ </ul>
+ <p>
+ {% trans %}
+ Currently, AMO does not provide a mechanism to directly communicate
+ with a reviewer but this feature is being investigated and considered
+ for a future update.
+ {% endtrans %}
+ </p>
+
+ <h3>{{ _('Can I request that a review be removed if the review is negative?') }}</h3>
+ <p>
+ {% trans %}
+ No. We do not remove negative reviews from add-ons unless they are
+ found to be false.
+ {% endtrans %}
+ </p>
+
+ <h3>{{ _('Can I request that a review be removed if the review is inaccurate?') }}</h3>
+ <p>
+ {% trans %}
+ If an author contacts us and asks for a review containing false or
+ inaccurate information to be removed, we will review the post and
+ consider removing it.
+ {% endtrans %}
+ </p>
+
+ <h2 id="license">{{ _('References for Open Source Licenses') }}</h2>
+ <p>
+ {% trans %}
+ Do you need more information about the various open source licenses? Are you
+ confused as to which license you should select? What rights does a specific
+ license grant? While nothing replaces reading the full terms of a license,
+ below are some sites that contain information about some of the key open
+ source licenses that may help you sort out the differences between them. These
+ sites are being provided solely for your convenience and as a reference for
+ your personal use. These resources do not constitute legal advice nor should
+ they be used in lieu of such advice. Mozilla neither guarantees nor is
+ responsible for the content of these sites or your reliance on such content.
+ {% endtrans %}
+ </p>
+
+ <h3><a href="http://www.mozilla.org/MPL/">http://www.mozilla.org/MPL/</a></h3>
+ <p>
+ {% trans %}
+ In addition to the full text of the Mozilla Public
+ License(&#8220;MPL&#8221;), this also provides an annotated version
+ of the MPL and an <abbr title="Frequently Asked Questions">FAQ</abbr>
+ to help you if you want to use or distribute code licensed under it.
+ {% endtrans %}
+ </p>
+
+ <h3>
+ <a href="http://developer.kde.org/documentation/licensing/licenses_summary.html">
+ http://developer.kde.org/documentation/licensing/licenses_summary.html
+ </a>
+ </h3>
+ <p>
+ {% trans %}
+ A table summarizing and comparing how some of the key open source
+ licenses treat distributions, proprietary software linking, and
+ redistribution of code with changes.
+ {% endtrans %}
+ </p>
+
+ <h3>
+ <a href="http://www.fsf.org/licensing/licenses/">
+ http://www.fsf.org/licensing/licenses/
+ </a>
+ </h3>
+ <p>
+ {% trans %}
+ Free Software Foundation provides short summaries of the key open
+ source licenses, including whether the license qualifies as a free
+ software license or a copyleft license. Also includes a discussion
+ of what constitutes a free software license or a copyleft license
+ (e.g., a Copyleft license is a general method for making a program
+ or other work free, and requiring all modified and extended versions
+ of the program to be free as well.)
+ {% endtrans %}
+ </p>
+
+ <h3>
+ <a href="http://www.opensource.org/licenses/category">
+ http://www.opensource.org/licenses/category
+ </a>
+ </h3>
+ <p>
+ {% trans %}
+ Open Source Initiative provides the terms of some of the key open
+ source licenses.
+ {% endtrans %}
+ </p>
+ <h3>
+ <a href="http://en.wikipedia.org/wiki/Open_source_license">
+ http://en.wikipedia.org/wiki/Open_source_license
+ </a>
+ </h3>
+ <p>{{ _('Wikipedia listing of known open source licenses.') }}</p>
+</section>
+{% endblock %}
View
2 apps/pages/urls.py
@@ -10,4 +10,6 @@
name='pages.faq'),
url('^compatibility_firstrun$', direct_to_template,
{'template': 'pages/acr_firstrun.html'}, name='pages.acr_firstrun'),
+ url('^developer_faq$', direct_to_template,
+ {'template': 'pages/dev_faq.html'}, name='pages.dev_faq'),
)

0 comments on commit ae9986e

Please sign in to comment.