If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Request for mozilla.dev.ports.beos newsgroup / mailing list

RESOLVED FIXED

Status

mozilla.org Graveyard
Server Operations
P1
normal
RESOLVED FIXED
12 years ago
3 years ago

People

(Reporter: Jorge G. Mare (a.k.a. Koki), Assigned: justdave)

Tracking

Details

(Whiteboard: waiting for Giganews)

(Reporter)

Description

12 years ago
User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1)
Build Identifier: 

Hello,

I am a member of Bezilla, the project team that works on the BeOS/ZETA port of 
Mozilla & Firefox.

We are in the process of updating our pages on mozilla.org 
(http://www.mozilla.org/ports/beos/), and we would like to have an email 
address for general inquiries from those interested in helping out with our 
port.

To that effect, I am requesting an email account with the mozilla.org domain, 
preferably bezilla@mozilla.org.

Jorge G. Mare (a.k.a. Koki)
koki@aequus.net


Reproducible: Always

Steps to Reproduce:
N/A
Actual Results:  
N/A

Expected Results:  
N/A

Comment 1

12 years ago
Notice:
Jorge G. Mare already has webtree CVS account -
https://bugzilla.mozilla.org/show_bug.cgi?id=290537
Frank Hecker is in charge of mozilla.org domain usage now, I'll let him make the call on this.  I tend to suspect this wouldn't be allowed, though, unless we create it as a public mailing list.
Assignee: mitchell → hecker

Comment 3

12 years ago
I don't know if it's correct to say that I control the mozilla.org domain (to my mind it's a project-wide resource, not necessarily specific to the Mozilla Foundation), but personally I would prefer not to see more @mozilla.org addresses. I think @mozilla.org addresses should be reserved for people like mozilla.org staff, common addresses that are project-wide (e.g., security@mozilla.org), and aliases for public project mailing lists.
Gerv: I don't seen a spot in the new news hierarchy for these guys...  but that seems like the most logical place.
Dave: the correct place in the hierarchy is:

Ports                            
-----                            
mozilla.dev.ports.os2            n.p.m.os2

To which we should add mozilla.dev.ports.beos. That would then have an associated mailing list address, to which enquiries could be addressed.

I concur with Frank; @mozilla.org addresses have not been given out in the past for this sort of thing, and I don't see any reason to change.

Gerv
Jorge / Sergei: would creating such a newsgroup with a mailing list gateway for it satisfy what you needed?
(Reporter)

Comment 7

12 years ago
(In reply to comment #6)
> Jorge / Sergei: would creating such a newsgroup with a mailing list gateway for
> it satisfy what you needed?

Yes, I think that would work. Please advise if we need to do anything from our side to proceed with this.
Assignee: hecker → server-ops
Component: Miscellaneous → Server Operations
QA Contact: mitchell → justin
Summary: @mozilla.org mail account request → Request for mozilla.dev.ports.beos newsgroup / mailing list
Assignee: server-ops → justdave
Status: UNCONFIRMED → NEW
Ever confirmed: true
Priority: -- → P1
mailing list has been created with koki@aequus.net as the list moderator.
Ticket has been opened with Giganews to create the corresponding newsgroup.
Whiteboard: waiting for Giganews
Newsgroup has been created.
Status: NEW → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.