Developers can optionally create a PayPal ID for each of their Firefox Add-ons. We are working with PayPal on this pilot to provide a secure and international solution for facilitating payments.
We’ve also put together this brief FAQ on Contributions: Please let us know via the AMO newsgroup if you have ideas or thoughts to share. As always, we’ll be evaluating this pilot as we receive feedback and making changes based on that feedback. We’re incredibly excited about the potential of Contributions and hope it makes a meaningful difference in the lives of developers and users alike. We’ll be working with PayPal on this pilot to provide a secure and international solution for facilitating payments. We’re asking for feedback from our community to drive the future of this pilot and we look forward to learning as much as we can. Our aim with this pilot is to help support a growing ecosystem by providing our users with the opportunity to support their favorite add-on developers. Since this is the first time we’re presenting this opportunity, we’re treating this initial launch as a pilot. Since contributions are completely optional, users will have ample time to evaluate an add-on to determine whether or not they want to help a developer. Along with requesting this amount, we’re helping developers tell their stories with our new “About the Developer” pages, which explain to prospective contributors the motivations for creating an add-on and its future road map. This pilot allows developers to request an optional dollar amount for their Firefox Add-on. Today’s release includes a pilot of a feature we’re calling “Contributions”. Thousands of developers create add-ons that foreshadow the future of Web browsers, and until today, developers who wanted some sort of financial support for their development efforts had few options. The Contacts Page has the Roles and Responsibilities for Firefox teams, partner teams, and external partners.The Firefox Add-ons community is an amazing source of creativity and innovation for Firefox users all over the world.
Iterations are our two week long work periods, of which there are three in a Firefox release cycle.
This is not a commitment to the next projects - just our scratch area, but it is in order of relative priority. Firefox main release schedule is the master location for the dates when each Firefox version goes to Aurora, Beta, & Release.Īs we plan what's coming next, we're focused on the themes outlined here.Bi-Weekly Team Meeting: time and date TBD.Something here about what Team AddOns is responsible for with links to other key AddOns assets 1.1 Meetings, Status Reports, Communications.
0 kommentar(er)
