On 1/10/14, 3:15 PM, Tim Abraldes wrote:
On our various modules pages (the largest of which is at [1]), we provide
contact information for module owners and peers in the form of email addresses.
Given the recent efforts surrounding mozillians.org, should we switch to
providing links to Mozilli
On 1/16/14, 8:01 AM, Mike Hoye wrote:
On 1/16/2014, 12:25 AM, Gregory Szorc wrote:
Can we just store the modules membership in LDAP or some other machine
readable location (if not inside mozilla-central for relevant modules)
and have a web page pull from that? Yes, it introduces process and
On 2/11/14, 9:01 AM, Ehsan Akhgari wrote:
On 2/11/2014, 5:27 AM, Reuben Morais wrote:
On Feb 11, 2014, at 4:51, Byron Jones wrote:
Kyle Huey wrote:
We could copy the Chromium OWNERS file thing.
that wouldn't work for modules which are not code (such as tree
sherifs, governance/policy, reps,
:25, Ehsan Akhgari wrote:
> On 2/11/2014, 12:42 PM, Gregory Szorc wrote:
>> On 2/11/14, 9:01 AM, Ehsan Akhgari wrote:
>>> On 2/11/2014, 5:27 AM, Reuben Morais wrote:
>>>> On Feb 11, 2014, at 4:51, Byron Jones wrote:
>>>>> Kyle Huey wrote:
>>>>
At one time there were a few modules with "emeritus" peers: these were
essentially formerly active peers that don't do much any more. I liked that
label because it gave people a "badge" of accomplishment, without burdening
them with daily responsibility. But I can't find any references to this any
On Sat, Oct 17, 2015 at 11:59 AM, Mitchell Baker
wrote:
> Hello
>
> Benjamin Smedberg pinged me to say that he would find it useful if I were
> to implement the idea of Emeritus Module Owners. I also suspect this
> would help existing module owners feel recognized and thus better about
> passing
My initial reaction was I could make a case for owning this, as I'm heavily
involved with build system and version control foo and changes to the
directory hierarchy can have significant implications for both.
However, I feel like it would be appropriate for someone more senior to be
the owner, as
On Wed, Mar 9, 2016 at 1:20 PM, Nathan Froyd wrote:
> Hi all,
>
> Several of us have been talking about having a module that covers various
> aspects of how we use C++, including, but not necessarily limited to:
>
> - language feature usage
> - standard library versions/usage
> - compiler/toolcha
On Wed, Jul 13, 2016 at 11:23 AM, Benjamin Smedberg
wrote:
> I would like to propose a code module "Firefox Telemetry" which covers the
> core infrastructure in the Firefox client to send back telemetry and FHR
> data. This will include the common mechanism to submit histograms and the
> telemet
On Wed, Aug 3, 2016 at 8:20 PM, Mitchell Baker wrote:
> ideal followup is governance ... cross posting to reach those likely to be
> interested
>
> I'm currently the owner of the Commit Access Policy module. That's
> because I wrote the original policy and did what was necessary to get it
> impl
ease Management and they tend to
not get involved until close to ship time).
> I agree that acting as if this policy governs code it doesn't is not
> helpful. And by being clear what it does cover, it also makes it clear
> where we are making a different risk / convenience / reward
There is currently a sub-module of the Build Config module governing the
Fennec build system. The peers are all the Build Config peers plus Nick
Alexander. I am the current owner.
The sub-module was created to allow Fennec's build system to have some
autonomy from the overall build system and to h
On Thu, Mar 9, 2017 at 1:53 PM, Mike Connor wrote:
> (please direct followups to dev-planning, cross-posting to governance,
> firefox-dev, dev-platform)
>
>
> Nearly 19 years after the creation of the Mozilla Project, commit access
> remains essentially the same as it has always been. We've evol
On Fri, Jul 28, 2017 at 9:54 AM, Gijs Kruitbosch via governance <
governance@lists.mozilla.org> wrote:
> (x-post platform + governance + bmo, please followup-to governance)
>
> Today I was asked for super-review. Although I've been around a while, I
> am not a super-reviewer. I can't remember the
Historically, the code that controls how Firefox CI runs has lived outside
of the Firefox repo and has been managed by Release Engineering. Over the
past few years, more and more of that code has moved into the Firefox
repository. And with the transition to Taskcluster to power Firefox CI,
that cod
I have been the module owner for the Core :: Build Config module since
2013. I am no longer a Mozilla employee and am effectively dormant in The
Project.
The build system module requires someone who is active in The Project and
has experience with its vast scope and impact.
I am honored to announ
16 matches
Mail list logo
