Being in the toolkit directory I guess this feature is currently nominally part of the general Toolkit module. As owner of that I'm perfectly fine with this getting its own module, most of the folks who work day to day on Toolkit likely do not have the expertise required for working on the crash reporter code. It may also make sense to move this out of the toolkit directory to make the separation here more clear but I don't think that that is required.
On Wed, Mar 20, 2019 at 5:19 PM Eric Rahm via governance < governance@lists.mozilla.org> wrote: > Hi all- > > It recently came to my attention that we don't have a module for our > 'Toolkit :: Crash Reporting' code base. Whereas the existing Socorro module > [1] focuses on the server side ingestion and presentation of crash reports, > this module would focus on the client-side generation of crash reports and > supporting utilities and libraries used to interpret them. I'd like to > propose the formal creation of the 'Core :: Crash Reporting' modules, > please let me know if you have any objections or questions. Given that > Gabriele Svelto is the primary contributor and maintainer of crash > reporting I'd like to nominate him as module owner. > > Proposed details: > > Name: Crash Reporting > Description: Client-side crash reporting libraries and tools > Owner: Gabriele Svelto > Peers: tbd > Source dir(s): toolkit/crashreporter > Bugzilla Component(s): Toolkit::Crash Reporting > Discussion group: dev-platform > > -e > > [1] https://wiki.mozilla.org/Modules/All#Socorro > _______________________________________________ > governance mailing list > governance@lists.mozilla.org > https://lists.mozilla.org/listinfo/governance > _______________________________________________ governance mailing list governance@lists.mozilla.org https://lists.mozilla.org/listinfo/governance