Re: Editor module proposal

+1 and huzzah! -- Eric Shepherd Senior Technical Writer Mozilla Developer Network Blog: https://www.bitstampede.com/ Twitter: http://twitter.com/sheppy Doodle: http://doodle.com/the.sheppy On Aug 2, 2016, 11:23 PM -0400, Jet Villegas , wrote: > masayuki++ > > \o/ > > I suggest we defer the decisi

Re: Proposed Update for Email Communications

There are a number of isues with these changes aside from the minor typo I pointed out privately. :) I have to agree with my compatriots here that there are significant questions about the purpose and usefulness of these changes, with regards to both effectiveness of email campaigns and their impa

Re: Proposed Update for Email Communications

Those changes help a lot. Thanks for making them! -- Eric Shepherd Senior Technical Writer Mozilla Developer Network https://developer.mozilla.org/ Blog: http://www bitstampede.com/ Twitter: https://twitter.com/sheppy On September 29, 2017 at 12:30:37 PM, Gervase Markham via governance ( governa

Re: How Firefox violates the term "Free and Open Source"

On Wed, Dec 13, 2017 at 7:52 PM Joe Smith via governance < governance@lists.mozilla.org> wrote: > Hi Gervase, > > There are plenty of Open Source messaging apps such as Signal that don't > restrict users from using the servers based on age. Not all countries > restrict people under 13 to use the I

Re: Open communication and Slack

On Thu, Aug 16, 2018 at 10:38 AM Dão Gottwald via governance < governance@lists.mozilla.org> wrote: > AFAIK Slack is only available to Mozilla staff and volunteers who've signed > our NDA. It's my understanding that communication at Mozilla should be open > by default, and the rest is sufficiently

Re: Open communication and Slack

Certainly the issue is more than just "Slack vs. IRC," but it is definitely a substantial symptom of the larger issue. Artificial fragmentation of our community where it isn't necessary helps nobody. If we need a chat-style tool similar to IRC for a variety of reasons (and it seems clear that we do

Re: Re[2]: Updating (or deprecating?) the modules wiki page

I agree with Nick; this is an important resource and if it’s not up-to-date, it needs to be fixed, not deleted. The MDN Web Docs team relies on it to help track down potential sources of information, or people who might be able to provide needed technical reviews for new content. -- Eric Sheph

Re: The master password debacle: What is behind it?

I am curious if it’s possible that as we integrate Lockbox (and, I hope, totally replace our existing password manager with it), if we can simply have a totally new password storage locking mechanism through that. On April 5, 2019 at 10:46:20 AM, Honza Bambas via governance ( governance@lists.mozi