Re: Report your development frustrations via `mach rage`

[Gervase Markham]

On 09/08/16 08:57, Chris Mills wrote:
> mach issue
> mach complain
> mach complaint
> mach feedback? (does it have to be negative, necessarily?)

mach itbetter ?
mach animprovement ?

:-)

Gerv


___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Re: Report your development frustrations via `mach rage`

[Chris Mills]

Yeah, gripe is a bit idiomatic.

How about 

mach issue
mach complain
mach complaint
mach feedback? (does it have to be negative, necessarily?)


Chris Mills
 Senior tech writer || Mozilla
developer.mozilla.org || MDN
 cmi...@mozilla.com || @chrisdavidmills

> On 9 Aug 2016, at 01:57, Gregory Szorc  wrote:
> 
> I agree: "rage" is a bit aggressive. And as mconnor said on IRC, "rage" can
> have an alternate meaning in the brogrammer lexicon.
> 
> Speaking of bikeshedding, I was looking at a thesaurus and one of the
> synonyms for "complain" is "yammer." As much as I want to rename it to
> `mach yammer`, I think I'll hold off :)
> 
> I think "gripe" conveys the right attitude. My only concern is it may not
> be friendly towards those who don't speak English as their primary
> language. I think verbs that describes a concrete human (re)action would be
> more understood. Something like "groan" or "sigh."
> 
> Anyway, we can continue the bikeshed in bug 1293493.
> 
> On Mon, Aug 8, 2016 at 1:25 PM, Jim Blandy  wrote:
> 
>> LOL, but honestly, one of the ways I get myself to treat people better is
>> to avoid the whole rage / tableflip / flame vocabulary when thinking about
>> what I want to do. Could we publicize this as "mach gripe", and leave
>> "rage" as an alias?
>> 
>> On Mon, Aug 8, 2016 at 10:51 AM, Gregory Szorc  wrote:
>> 
>>> Sometimes when hacking on Firefox/Gecko you experience something that irks
>>> you. But filing a bug isn't appropriate or could be time consuming. You
>>> instead vent frustrations on IRC, with others around the figurative water
>>> cooler, or - even worse - you don't tell anyone.
>>> 
>>> The Developer Productivity Team would like to know when you have a bad
>>> experience hacking on Firefox/Gecko so we can target what to improve to
>>> make your work experience better and more productive.
>>> 
>>> If you update to the latest commit on mozilla-central, you'll find a new
>>> mach command: `mach rage`.
>>> 
>>> `mach rage` opens a small web form where you can quickly express
>>> frustration about anything related to developing Firefox/Gecko. It asks a
>>> few simple questions:
>>> 
>>> * Where did you encounter a problem
>>> * How severe was it
>>> * What was it
>>> * (optional) How can we fix it
>>> 
>>> If you don't want to use `mach rage`, just load
>>> https://docs.google.com/forms/d/e/1FAIpQLSeDVC3IXJu5d33Hp_ZT
>>> COw06xEUiYH1pBjAqJ1g_y63sO2vvA/viewform
>>> 
>>> I encourage developers to vent as many frustrations as possible. Think of
>>> each form submission as a vote. The more times we see a particular pain
>>> point mentioned, the higher the chances something will be done about it.
>>> 
>>> This form is brand new, so if you have suggestions for improving it, we'd
>>> love to hear them. Send feedback to g...@mozilla.com and/or
>>> jgrif...@mozilla.com.
>>> 
>>> Happy raging.
>>> ___
>>> dev-platform mailing list
>>> dev-platform@lists.mozilla.org
>>> https://lists.mozilla.org/listinfo/dev-platform
>>> 
>> 
>> 
> ___
> dev-platform mailing list
> dev-platform@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-platform

___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Re: Rust code in mozilla-central now builds via cargo

[Henri Sivonen]

On Aug 8, 2016 1:06 AM, "Nathan Froyd"  wrote:
>
> TL; DR: Bug 1231764 has landed on mozilla-central; the build system
> now invokes cargo to build all the Rust code in m-c.  This should
> result in a better Rust developer experience, as well as making it
> easier to import Rust libraries into m-c.

\o/

> The e10s crate must also be checked into the tree at the appropriate
> path.

Are there technical constraints (upcoming arising from the behavior of
cargo vendor maybe?) or guidelines that one should be aware of when
choosing a location for a crate in m-c?
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform