Free Software Directory:IceCat WebExtensions (proposed)/Dev
- IceCat WebExtensions (proposed)/About
- IceCat WebExtensions (proposed)/Add-on list
- IceCat WebExtensions (proposed)/Dev
- IceCat WebExtensions (proposed)/FAQ
- IceCat WebExtensions (proposed)/FSD bugs issue 1
- IceCat WebExtensions (proposed)/Issues
- IceCat WebExtensions (proposed)/License issues
- IceCat WebExtensions (proposed)/Resources
- Q: I cannot find any way to contact the author on the AMO page. How can I contact them?
- A: Mozilla answered: "You can also leave a review, which is email to them, normally. It will be deleted, most likely, but they will get notified" However, do not give low review rating, and never offer to increase the rating in exchange for something.
This list should not be confused with users with admin privileges of this wiki.
- David Hedlund - Project leader
- Author of licenseutils
How to become a contributor?
- Please read the participation guideline.
- Add your name/register to the project members if you decide to be active in this project.
- Decide if you are going to use IceCat: We recommend that you use the endorsed FSF distribution Trisquel GNU/Linux if you are going to evaluate add-ons for IceCat. This is not a requirement though, as you might just want to help solving license issues for which you can use any web browser. Gnu Icecat is developed by Rubén Rodriguez who work for the FSF, who is also the creator of GNU Trisquel. In case of a delayed icecat package you can always download the binary file for GNU/Linux x64 and run it out of the box.
- Subscribe to the bug-gnuzilla mailing list (gnuzilla-dev also found there is optional).
As neither I or Mangeurdenuage speak English natively someone else has to clean up after us.
- Please verify license for some of the 600 unapproved add-ons. Do _not_ add new entries as we are currently overloaded.
Verifying licenses is the first point that you must look at before even adding the add-on into the list of acceptable add-ons
Places you should observe for license are the following places
- Browse the addons.mozilla.org AMO page with IceCat and look for "Released under".
- The source code, look after a copyright file, or in the source files if you don't find such file.
The file generally has the name "COPYING" or simply "LICENSE" both a plain text you can open them with a text editor.
To download in IceCat you have to right-click on the green "Download now" button and select "Save as" (or "Copy Link Location" if you want to download with wget). You cannot simply click on the Download button: Cross-Platform Installer Module (XPI) is a ZIP file used to install packages, utilizing the XPInstall technology. XPI modules (so called "Bundles") are employed to install a wide variety of software, including Plugins, Extensions, Themes, and Thunderbird dictionaries. - https://developer.mozilla.org/en-US/docs/Mozilla/XPI Decompress the .xpi file or rename it to .zip if your file archiver require that.
- File an issue if the add-on do not qualify.
Example with GNU LibreJS
- https://addons.mozilla.org/en-US/firefox/addon/librejs/ says "Released under GNU General Public License, version 3.0"
- The source code - https://addons.mozilla.org/firefox/downloads/latest/librejs/addon-350590-latest.xpi
- The root directory carry a COPYING file.
- The source files carry license notices:
- Thus GNU LibreJS should remain approved, otherwise we would file an issue.
File license issues
- Search "License" submitted issues on GitHub for example. If no such issue exist, then please create it and label the message "License issues".
- For GitHub submitted issues make sure there is a separate comment with "[mylabel:AMO]" (including the square brackets but excluding the quotes) so we can it. The comment has to be new as GitHub do not re-index old comments, so you cannot edit old comments to track it.
You must copy and edit the Template before you send it to the add-on maintainer:
- Replace (including )
- [FULL_SOFTWARE_NAME] (not package name)
- [LICENSE LICENSE_VERSION]
- Delete unhelpful items
It is unhelpful to say, "has one or more of the issues listed below." If you want to succeed in motivating them to fix problems, you should always give them ALL the information THAT YOU HAVE about those problems.
So you should delete the items that are not pertinent to the case at hand.
- Send the message to the maintainer and wait for response.
- If a developer says, "I would install this but I don't have time to
work on this", please ask if you can you make the changes and send them to the developer, that will make for a lot more progress.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the page “GNU Free Documentation License”.
The copyright and license notices on this page only apply to the text on this page. Any software or copyright-licenses or other similar notices described in this text has its own copyright notice and license, which can usually be found in the distribution or license text itself.