READ FIRST when you want to publish add-ons

Add-ons for Pale Moon and other applications
General discussion, compatibility, contributed extensions, themes, plugins, and more.

Moderators: FranklinDM, Lootyhoof

User avatar
Moonchild
Project founder
Project founder
Posts: 38678
Joined: 2011-08-28, 17:27
Location: Sweden

READ FIRST when you want to publish add-ons

Post by Moonchild » 2025-01-29, 13:44

It seems there has not been a clear procedure laid out for publishing add-ons on addons.palemoon.org (APMO), leading to several extensions being submitted but going unreviewed/flying under the radar of our Add-ons team.

In general, if you want to publish an add-on on APMO, it is requested that you first make a post on the forum about your intent to publish what you created. Our addons site is not an automatic self-publishing platform and we check/vet all extensions/themes before they are made available to the public. This is a manual/human process. If you don't let the team know you're planning to publish something, they don't know to check your work, and it may remain in limbo!

So, for clarity, here's what is expected:
  1. Create and above all test your extension/theme on the intended target browser/application.
  2. Read the developer site information. This way, you know what is expected of the add-ons you might want to submit (and requirements of the meta data in your extension for integration and proper listing of the add-on). Also, it will tell you how to notify our team of your (pending) extension and that way our team is informed about the pending extension to check, and nothing gets left in limbo.
  3. Optionally, make a topic in the add-ons board on the forum if you want to/need to discuss the extension with the community.
  4. Make sure your add-on's meta data is as requested, and follow the instructions on the developer site to submit your add-on (upload via the Phoebus panel).
  5. Be patient while the vetting takes place, keep an eye on the topic or your private messages as our team may have questions/requests for extension updates for you.
  6. Once it has been approved/vetted and it's published, make a topic in the "add-on releases/support" board on this forum, so users can contact you about the extension.
"There is no point in arguing with an idiot, because then you're both idiots." - Anonymous
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite

User avatar
moonbat
Knows the dark side
Knows the dark side
Posts: 5746
Joined: 2015-12-09, 15:45

Re: READ FIRST when you want to publish add-ons

Post by moonbat » 2025-01-30, 03:11

Should also add - the source code repository URL is a must, else the addons team can't be expected to extract your .xpi and go through each file separately. Host your sourcecode on Github or similar.
"One hosts to look them up, one DNS to find them and in the darkness BIND them."

Image
KDE Neon on a Slimbook Excalibur (Ryzen 7 8845HS, 64 GB RAM)
AutoPageColor|PermissionsPlus|PMPlayer|Pure URL|RecordRewind|TextFX
Jabber: moonbat@hot-chili.net