Adventures in mozilla red tape.
Posted Sat, 02 Jun 2007
To publish, you need to submit it to the addons review system. Submitting it puts it in the "sandbox". To leave the sandbox and go public it must be nominated. To pass nomination it must meet a large set of criteria, all of which make some amount of sense with respect to quality assurance, etc.
I've submitted it 3 times. Every time it's been denied for different reasons. The first time was half reasonable, because one of the reasons was "Remove those debugging statmenets". Other reasons have been:
- "Document your preferences"
- tabsearch doesn't have any options, preferences, or tweakables
- "Your extension must have atleast one review from one of your users"
- Do I have a QA team who can review this for me? I thought the reason I was publishing it on mozilla addons was to get users. Seems like an awkward bootstrapping problem I'm not going to bother solving.
- "Make the key binding configurable"
- That's what keyconfig is for :(
Benjamin Franklin wrote a blurb about perfection, '"Yes," said the man, "but I think I like a speckled axe best."'. Most of the time, perfection isn't worth the effort when something is already good enough.
I don't mean to discourage people from submitting to mozilla addons, but after 3 attempts it's really not worth it. Basically, the fine, nearly-unwritten print in the policy is that you need real people to have submitted very detailed reviews of your extension before it'll be approved.