[Project_owners] AMO vs. mozdev was: Awaiting extension upgrade approval
Michael Vincent van Rantwijk, MultiZilla
mv_van_rantwijk at yahoo.com
Mon Jul 14 12:34:19 PDT 2008
Onno Ekker wrote:
> On Mon, Jul 14, 2008 at 5:32 AM, John Woods <johnrw at gmail.com> wrote:
>
>>> From: Onno Ekker <o.e.ekker at gmail.com>
>>> Date: Fri, Jul 11, 2008 at 4:30 AM
>>> To: Mozdev Project Owners List <project_owners at mozdev.org>
>>>
>>>
>>> l+31
>>>
>>>
>> Huh?
>>
>> Well at any rate... if anyone wants to chime in on amo review
>> performance...
>> there may be a better bug than this one... but I didn't find it.
>> https://bugzilla.mozilla.org/show_bug.cgi?id=340287
>>
>
> Sorry, haven't got a clue as to where that l+31 came from...
>
> Another bug on the pending queue is the following:
> Proposal for a publicly accessible interface to the pending updates queue
> <https://bugzilla.mozilla.org/show_bug.cgi?id=427104>
>
> I think it's amazing that there is so little on this matter on bugzilla. Do
> all project owners think it's no use to file bugs of vote for existing
> bugs???
I don't vote because I don't think that works (it never worked before).
> Since anyone can start a new project on mozdev and projects aren't actively
> reviewed here, it would be a bad idea for amo (or even mozdev) to just trust
> all projects from mozdev.
The quality of reviews is key to success for both parties involved, but
education is the most important and sometimes failing factor here.
Sharing information, having good on-line documentation and possibly some
sort of scanning script for add-ons would top it off.
Why isn't there a real knowledge base (mozdev.org corner anyone?) with
real examples about the blunt errors made by developers. Not to point
fingers, no, but to help others. Each error I make can then be turned
into help for others. Wouldn't that be great?
> A better bet might be to become a trusted add-on. I don't think the concept
> of trusted add-ons is any safe, but since amo uses it, it is probably your
> best bet to prevent future update problems. Unfortunately there isn't too
> much info about trusted add-ons either, but I can imagine becoming trusted
> involves a lot of hanging around and begging on irc ;-)
Nobody, not even mozilla should be considered to be 'trusted'. At least
not blindly.
> You can find further reading on the review process on Justin Scott's blog:
> <http://blog.fligtar.com/2008/06/24/amo-add-on-review-status/>
> <http://blog.fligtar.com/2006/11/21/reviewing-the-review-process/>
Ouch man. That is exactly where the shoe fits, or not. These few good
people must have their hands full of work with these reviews. Good to
see 'our' Brian King to be one of them. Thank you Brian!
Now, the main question remains and that to me is: "Can we help this AMO
ecosystem amd if yes how?".
We might, but at what price? My vote goes out to a pool of 'trusted'
reviewers for projects hosted at mozdev.org That my firends should help
anyone (think examples here) including me.
Michael
More information about the Project_owners
mailing list