Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Deprecation of sumo-dev@mozilla.com
7 views
Skip to first unread message
Michael Cooper
Jan 13, 2015, 2:54:05 PM1/13/15
to dev-...@lists.mozilla.org, sumo...@mozilla.com
Hello all!
For a while we've had roughly a million mailing lists, groups, distribution
lists, forums, usenets, and carrier pigeons. As I understand it,
sumo...@mozilla.org was pretty cool, but with the new move to Google
services for our mail, it is now only available to Mozilla employees and a
few other people. Not a great situation.
dev-...@lists.mozilla.org on the other hand, is a Mailman mailing list. I
jumped through some hoops and got all the access I needed to manage
dev-sumo@, and I verified that it should be available to anyone, not only
employees.
So going forward, here is my proposal for how the mailing lists should be
used:
# dev-...@lists.mozilla.org
This should be used for discussion of SUMO development such as:
* "I'm having a problem with this code, can anyone help me?"
* Announcements of locked environments, like "I have a branch on -dev,
please don't deploy over it until ..."
* Announcements of development changes, such as peep or git practices.
* Discussion of code changes outside of bugs or pull requests. For example:
"Should we change to 99 characters per line?" or "Should we use Gulp or
Grunt for JS packaging?" Once a decision is reached, a bug should be filed.
Mailing lists are not bug trackers.
To subscribe to dev-...@lists.mozilla.org, you can visit it's mailman
page: https://lists.mozilla.org/listinfo/dev-sumo . You can also change
lots of settings there, like how you get emails and how often.
If you are subscribed already, but don't know your password, you can get
that by sending an email to dev-sumo...@lists.mozilla.org with the
subject "password". This password can be used on the mailman page.
# sumo...@mozilla.com
This should not be used at all.
# sumo...@mozilla.com
This still exists, and should be used for discussion of topics related
specifically to Mozilla employees who work on SUMO. This is not a public
list. If a topic could be posted on dev-...@lists.mozilla.org, it should.
This list should only be used when no other options are available. Which
shouldn't be often.
Does that sound good to everyone?
-mike
For a while we've had roughly a million mailing lists, groups, distribution
lists, forums, usenets, and carrier pigeons. As I understand it,
sumo...@mozilla.org was pretty cool, but with the new move to Google
services for our mail, it is now only available to Mozilla employees and a
few other people. Not a great situation.
dev-...@lists.mozilla.org on the other hand, is a Mailman mailing list. I
jumped through some hoops and got all the access I needed to manage
dev-sumo@, and I verified that it should be available to anyone, not only
employees.
So going forward, here is my proposal for how the mailing lists should be
used:
# dev-...@lists.mozilla.org
This should be used for discussion of SUMO development such as:
* "I'm having a problem with this code, can anyone help me?"
* Announcements of locked environments, like "I have a branch on -dev,
please don't deploy over it until ..."
* Announcements of development changes, such as peep or git practices.
* Discussion of code changes outside of bugs or pull requests. For example:
"Should we change to 99 characters per line?" or "Should we use Gulp or
Grunt for JS packaging?" Once a decision is reached, a bug should be filed.
Mailing lists are not bug trackers.
To subscribe to dev-...@lists.mozilla.org, you can visit it's mailman
page: https://lists.mozilla.org/listinfo/dev-sumo . You can also change
lots of settings there, like how you get emails and how often.
If you are subscribed already, but don't know your password, you can get
that by sending an email to dev-sumo...@lists.mozilla.org with the
subject "password". This password can be used on the mailman page.
# sumo...@mozilla.com
This should not be used at all.
# sumo...@mozilla.com
This still exists, and should be used for discussion of topics related
specifically to Mozilla employees who work on SUMO. This is not a public
list. If a topic could be posted on dev-...@lists.mozilla.org, it should.
This list should only be used when no other options are available. Which
shouldn't be often.
Does that sound good to everyone?
-mike
will kahn-greene
Jan 14, 2015, 9:36:57 AM1/14/15
to dev-...@lists.mozilla.org
+1 from me!
Long live dev-sumo!
On 01/13/2015 02:53 PM, Michael Cooper wrote:
> Hello all!
>
> For a while we've had roughly a million mailing lists, groups,
> distribution lists, forums, usenets, and carrier pigeons. As I
> understand it, sumo...@mozilla.org <mailto:sumo...@mozilla.org> was
Long live dev-sumo!
On 01/13/2015 02:53 PM, Michael Cooper wrote:
> Hello all!
>
> For a while we've had roughly a million mailing lists, groups,
> distribution lists, forums, usenets, and carrier pigeons. As I
> pretty cool, but with the new move to Google services for our mail, it
> is now only available to Mozilla employees and a few other people. Not a
> great situation.
>
> dev-...@lists.mozilla.org <mailto:dev-...@lists.mozilla.org> on the
> is now only available to Mozilla employees and a few other people. Not a
> great situation.
>
> other hand, is a Mailman mailing list. I jumped through some hoops and
> got all the access I needed to manage dev-sumo@, and I verified that it
> should be available to anyone, not only employees.
>
> So going forward, here is my proposal for how the mailing lists should
> be used:
>
> # dev-...@lists.mozilla.org <mailto:dev-...@lists.mozilla.org>
> got all the access I needed to manage dev-sumo@, and I verified that it
> should be available to anyone, not only employees.
>
> So going forward, here is my proposal for how the mailing lists should
> be used:
>
>
> This should be used for discussion of SUMO development such as:
>
> * "I'm having a problem with this code, can anyone help me?"
> * Announcements of locked environments, like "I have a branch on -dev,
> please don't deploy over it until ..."
> * Announcements of development changes, such as peep or git practices.
> * Discussion of code changes outside of bugs or pull requests. For
> example: "Should we change to 99 characters per line?" or "Should we use
> Gulp or Grunt for JS packaging?" Once a decision is reached, a bug
> should be filed. Mailing lists are not bug trackers.
>
> To subscribe to dev-...@lists.mozilla.org
> <mailto:dev-...@lists.mozilla.org>, you can visit it's mailman page:
> This should be used for discussion of SUMO development such as:
>
> * "I'm having a problem with this code, can anyone help me?"
> * Announcements of locked environments, like "I have a branch on -dev,
> please don't deploy over it until ..."
> * Announcements of development changes, such as peep or git practices.
> * Discussion of code changes outside of bugs or pull requests. For
> example: "Should we change to 99 characters per line?" or "Should we use
> Gulp or Grunt for JS packaging?" Once a decision is reached, a bug
> should be filed. Mailing lists are not bug trackers.
>
> To subscribe to dev-...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-sumo . You can also change lots
> of settings there, like how you get emails and how often.
>
> If you are subscribed already, but don't know your password, you can get
> that by sending an email to dev-sumo...@lists.mozilla.org
> <mailto:dev-sumo...@lists.mozilla.org> with the subject "password".
> of settings there, like how you get emails and how often.
>
> If you are subscribed already, but don't know your password, you can get
> that by sending an email to dev-sumo...@lists.mozilla.org
> This password can be used on the mailman page.
>
> # sumo...@mozilla.com <mailto:sumo...@mozilla.com>
>
>
> This should not be used at all.
>
> # sumo...@mozilla.com <mailto:sumo...@mozilla.com>
> This should not be used at all.
>
>
> This still exists, and should be used for discussion of topics related
> specifically to Mozilla employees who work on SUMO. This is not a public
> list. If a topic could be posted on dev-...@lists.mozilla.org
> <mailto:dev-...@lists.mozilla.org>, it should. This list should only be
> This still exists, and should be used for discussion of topics related
> specifically to Mozilla employees who work on SUMO. This is not a public
> list. If a topic could be posted on dev-...@lists.mozilla.org
Ricardo Rosario
Jan 14, 2015, 9:52:19 AM1/14/15
to dev-...@lists.mozilla.org
+1 from me too!
On Wed, Jan 14, 2015 at 9:36 AM, will kahn-greene <wkahn...@mozilla.com>
wrote:
>> _______________________________________________
> dev-sumo mailing list
> dev-...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-sumo
>
On Wed, Jan 14, 2015 at 9:36 AM, will kahn-greene <wkahn...@mozilla.com>
wrote:
> dev-sumo mailing list
> dev-...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-sumo
>
Rehan Dalal
Jan 14, 2015, 11:48:55 AM1/14/15
to Ricardo Rosario, dev-...@lists.mozilla.org
I'll join the +1 party.
On Wed, Jan 14, 2015 at 8:22 PM, Ricardo Rosario <rros...@mozilla.com>
wrote:
On Wed, Jan 14, 2015 at 8:22 PM, Ricardo Rosario <rros...@mozilla.com>
wrote:
0 new messages