952790 - Adding Mozilla extensions bugs under an ADDONS component

Status: RESOLVED WONTFIX

(bugzilla.mozilla.org :: Administration, task)

Description

[Axel Grude [:realRaven]]

I have 5 major extensions, that I cannot host at mozdev.org anymore due to frequent outaged. 3 are Mail specific, 2 are across Browser+Mail; all are also Seamonkey compatible:
1-QuickFolders
2-quickFilters
3-smartTemplate4
4-QuickPasswords
5-Zombie Keys
the documentation is hosted at mozdev.org, which unforuntatly seems to be down permanently since last Monday
http://quickfolders.mozdev.org/
http://quickfilters.mozdev.org/
http://quickpasswords.mozdev.org/
http://zombiekeys.mozdev.org/
http://smarttemplate4.mozdev.org/

All 5 addons are fully reviewed and have been hosted at addons.mozilla.org for a long time.

Can any or all of these be added? There is a considerable amount of bugs that were entered in bugzilla.mozdev.org so I would like to import these bugs if that is a possibility (provided the information can still be restored).

Comment 1

[:glob ✱]

sorry, but bugzilla.mozilla.org isn't the right place for hosting bugs relating to extensions.
see http://www.mozdev.org/faq.html#mozilla

mozdev.org is the right place for that, and it's mostly working for me currently.

unfortunately i don't know the right point of contacts to see what's going on at mozdev. the drupal database is missing, and i suspect the default assignee for mozdev bugs is several years out of date.

[e-mail] is bouncing too:
> <[e-mail]>: host mozdev.mozdev.org[140.211.166.81] said: 550 5.1.1
>     <[e-mail]>: Recipient address rejected: User unknown in local
>     recipient table (in reply to RCPT TO command)

david, do you know who the right person is to contact about this, or what's going on with mozdev?

Comment 2

[Axel Grude [:realRaven]]

(In reply to Byron Jones ‹:glob› (unavailable until Jan 12th) from comment #1)
> sorry, but bugzilla.mozilla.org isn't the right place for hosting bugs
> relating to extensions.
> see http://www.mozdev.org/faq.html#mozilla
> 
> mozdev.org is the right place for that, and it's mostly working for me
> currently.

Good for you. Let me tell you that I was lobbying very very hard for the 10 days outage over the Christmas holidays, which probably cost me several 100 Dollars in lost donation revenues and a good bit of good will on side of my users who were presented with empty pages when trying to look up help pages, version history or donate.

It turned out that ALL mozdev web sites (including the one you mention above) and its bugzilla database are hosted on a 10 years old box which is probably a good while past its end of life. We are trying to get the hosting crowd (Oregon State University Open Source Lab) to move it to their VM clusters - I will send out an email to publicmozdev.project_owners to show that those Mozdev project owners who still _actively_ use mozdev.org back up this decision.

> 
> unfortunately i don't know the right point of contacts to see what's going
> on at mozdev. the drupal database is missing, and i suspect the default
> assignee for mozdev bugs is several years out of date.

that was my problem as well. I think we should probably take ownership of this more actively as a group to avoid this happening again. unfortunately there is a very prevalent opinion on most forums and contributors circles "I thought mozdev was dead", which made me consider migrating a large amount of work to a different host. People also seem to believe that it is just a trifle to migrate bugs from Bugzilla to a ticketing system or other systems (github was one suggestion) and I somehow doubt this. Personally I am highly invested in the "bugzilla way" of doing things, so if I was forced to migrate I would look at hosting my own Bugzilla base.

Any way I would prefer to stay with the old system as it was working nicely on the days that it was online (even with short intermittent outages) - I just dread the next extended blackout and the snide comments from non-mozdev users.

Comment 3

[David Boswell]

(In reply to Byron Jones ‹:glob› (unavailable until Jan 12th) from comment #1)
> david, do you know who the right person is to contact about this, or what's
> going on with mozdev?

mozdev.org is currently up right now but there is very little support these days in terms of either time or money available to keep it going.  Pete Collins is doing some work, but he has had to turn off parts of the site, like Drupal and most mailing lists, to make the core services maintainable.  I think there either needs to be more support coming from the remaining users of the site or the remaining users should migrate to other options.

Comment 4

[Axel Grude [:realRaven]]

(In reply to David Boswell from comment #3)
> (In reply to Byron Jones ‹:glob› (unavailable until Jan 12th) from comment
> #1)
> > david, do you know who the right person is to contact about this, or what's
> > going on with mozdev?
> 
> I think there either needs to be more support coming from the remaining
> users of the site or the remaining users should migrate to other options.

I am all for help Mozdev along for the next 5 years, if we can somehow secure the financing of moving on to the virtual cloud on osuosl.org as the server admins there suggested. I am not too concerned about the missing drupal support as long as the web sites and our bug tracking system can stay online. Philip Chee also reached out and would be in favor of migrating to VMs while staying on mozdev.org, the general consensus so far is that it should only increase reliability of the site without introducing much change.

I suggest I post a message to publicmozdev.project_owners to ask what the general consensus is, while finding out about cost (if we stay with current host + migrate to VM).

I have also tried to look at alternative hosting with similar feature set, but believe it or not, it is actually very difficult to find something reasonably priced that has CVS / SVN support for checking in web sites plus Bugzilla. In my eyes these 2 features are the key for a quick turnaround of bugs and web site updates and my main reason for staying with mozdev.org

Is it okay if I attach this bug for the discussion, or should I open a new one?

Comment 5

[Axel Grude [:realRaven]]

(In reply to Byron Jones ‹:glob› (unavailable until Jan 12th) from comment #1)
> sorry, but bugzilla.mozilla.org isn't the right place for hosting bugs
> relating to extensions.
> see http://www.mozdev.org/faq.html#mozilla
> 
> mozdev.org is the right place for that, and it's mostly working for me
> currently.
> 
> unfortunately i don't know the right point of contacts to see what's going
> on at mozdev. the drupal database is missing, and i suspect the default
> assignee for mozdev bugs is several years out of date.
> 
> [e-mail] is bouncing too:
> > <[e-mail]>: host mozdev.mozdev.org[140.211.166.81] said: 550 5.1.1
> >     <[e-mail]>: Recipient address rejected: User unknown in local
> >     recipient table (in reply to RCPT TO command)
> 
> david, do you know who the right person is to contact about this, or what's
> going on with mozdev?

Another thing - assuming mozdev,org would remain volatile, wouldn't it be possible to add an ADDONS component and then allow addons authors to host their (mozilla) addons here? I don't quite understand why it is allowed for things like calendar but not for addons with several ten thousand users?

If we had an "Addons" component and a special vetting process would it be possible to change this policy? (If it is a policy)

Comment 6

[David Boswell]

(In reply to Axel Grude [:realRaven] from comment #4)
> I suggest I post a message to publicmozdev.project_owners to ask what the
> general consensus is, while finding out about cost (if we stay with current
> host + migrate to VM).

That would be great to see what sort of interest you can find from existing mozdev users to help with this.

In terms of cost, there probably isn't any.  OSUOSL provides free hosting to mozdev and I suppose that applies to their VMs as well as for hosting physical servers.

(In reply to Axel Grude [:realRaven] from comment #5)
> If we had an "Addons" component and a special vetting process would it be
> possible to change this policy? (If it is a policy)

You might want to talk to Amy Tsay, the AMO Community Manager, about the policy of using bugzilla.mozilla.org to support add-on developers.