Setup litmus-devel mailing list

RESOLVED WONTFIX

Status

mozilla.org Graveyard
Server Operations
RESOLVED WONTFIX
12 years ago
3 years ago

People

(Reporter: coop, Assigned: justdave)

Tracking

Details

(Reporter)

Description

12 years ago
Can I please get a mailing list setup that I can use for discussing development issues surrounding Litmus (litmus-devel)?

The list should be open to the general public. I don't know what policy is for list administrators, but I would like to be on the administrators list if possible.

Initial membership (if I won't have admin access):
* myself (ccooper@deadsquid.com)
* zach@zachlipton.com
* jay@mozilla.com

Thanks
Assignee: server-ops → aravind
Is Litmus considered part of the mozilla webtools?  (Isn't that where it lives in CVS?)

How about dev-apps-webtools@lists.mozilla.org?  I'd be happy to let you co-moderate it.


From the list description:

"This list is for development discussion about the various products that make up the Mozilla Webtools Suite, which includes Bonsai, Tinderbox, LXR, Mozbot, Doctor, and anything else checked out from the mozilla/webtools directory in CVS, except for Bugzilla, which has its own list (dev-apps-bugzilla)."

And since Bugzilla now has its own list, the webtools one is going to be a little bit dead if nobody chimes in there to liven it up. ;)
(Reporter)

Comment 2

12 years ago
It took me a while to convince myself that I wanted to use the existing list, but I did eventually reach that conclusion. Rather than walling Litmus off from the other tools, we should be encouraging any cross-pollination that may result from using the common list. Besides, if the traffic is currently minimal, we'll just dominate the dicussion anyway. :)

I would like to co-moderate the existing list, if possible.

Assignee: aravind → justdave
OK, done.  moderator password mailed separately.
Status: NEW → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → WONTFIX
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.