(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 evolved the
vouching process a number of times, CVS has long since
On Fri, 2 Mar 2018 at 16:29 Justin Dolske via governance <
governance@lists.mozilla.org> wrote:
> Overall, +1 on filling this gap in the module system.
>
> One comment/question...
>
> IME a significant number of possible-escalation grumbles have been less
> about the _technical_ aspects, and more
With that open issue resolved, I think you're good to go. Thanks for all
of your hard work on sorting this out!
On Tue, Jul 9, 2019 at 8:25 AM James Graham via governance <
governance@lists.mozilla.org> wrote:
> On 19/06/2019 14:58, Andrew McCreight wrote:
> >
> >
> > On Thu, Jun 13, 2019 at 8:5
Hi folks,
As a step to remove unnecessary overhead, we are proposing that we amend
the Commit Access Policy for Level 1 commit access to remove the vouching
requirement for Mozilla employees. Level 1 access allows users to access
the Try Server as well as creating user repositories. It does not a
