Congratulations, Nathan!

It's not unusual for module peers to be experts in only part of a module,
so that part sounds fine to me.

Nick

On Tue, Dec 13, 2016 at 6:17 AM, Gregory Szorc <g...@mozilla.com> wrote:

> Nathan Froyd has been doing a lot of great work at the periphery of the
> build system for years, especially around toolchain configuration and
> management. Recently, he's been improving our integration with Rust!
>
> I've been trying to cajole Nathan into being a build peer for a while.
> After half-jokingly asking him again after a few beers last Thursday, we
> talked about it a bit more on Friday. And, I'm pleased to report that
> Nathan has agreed to become a build peer!
>
> But there is a catch.
>
> The "deal" we brokered is Nathan would focus on parts of the build system
> most relevant to his day job - namely things strongly coupled with the
> development of Gecko and overlap with the C++ module. This includes
> toolchain management, Rust integration, etc. This should allow these
> aspects of the build module to move faster while not violating the modules
> system.
>
> Like all build peers, Nathan's expertise in some areas of the build system
> is not deep. Given this and Nathan's desire to focus on certain aspects of
> the build system, please exercise discretion before sending reviews for
> random parts of the build system his way, as there's a good chance the
> review may get deflected to another build peer. In effect, Nathan is a peer
> of a sub-module dealing with specific topics. However, I'm not yet sure
> what to name/describe that sub-module, so I'm stopping short of creating
> one. If anyone has ideas, please let me know.
>
> Please send your congratulations and/or condolences to Nathan!
>
> _______________________________________________
> dev-builds mailing list
> dev-builds@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-builds
>
>
_______________________________________________
dev-builds mailing list
dev-builds@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-builds

Reply via email to