So, my main question/concern is that you're combining the server and the client code. Can either of the Ryans review Gecko code? (They're smart people I like, I just don't know if this makes sense.)
Is this two modules, or should there be an overall module to cover stuff like protocol/API changes, but the code is in submodules? On 9 July 2015 at 10:05, Gian-Carlo Pascutto <[email protected]> wrote: > Hi all, > > currently SafeBrowsing is wedged into the (DOM) Content Security module, > even though the relevant code is unrelated and the relevant peers and > owners can't review each others' code. We also have a "Tracking > Protection" module, which is separate even though a lot of client side > code is shared with SafeBrowsing and the server-side code is essentially > a SafeBrowsing server. The module owner no longer works on it and the > peers are two managers which AFAIK aren't reviewing anything. > > So, we'd like to pull SafeBrowsing out of Content Security and merge it > with Tracking Protection into a new module, URL Classifier, and set the > owners/peers to the people actually working on it. > > Name: URL Classifier > Description: Database and list-based classification of URL resources, > such as Tracking Protection and SafeBrowsing. > Owner: Gian-Carlo Pascutto, Ryan Tilder > Peer(s): Francois Marier, Ryan Kelly > Source Dir(s): > toolkit/components/url-classifier > netwerk/base/src/nsChannelClassifier > https://github.com/mozilla-services/shavar > URL: > https://wiki.mozilla.org/Phishing_Protection > https://wiki.mozilla.org/Privacy/Roadmap/Tracking > https://wiki.mozilla.org/Security/Features/Application_Reputation > Discussion Group: mozilla.dev.platform > > -- > GCP > _______________________________________________ > governance mailing list > [email protected] > https://lists.mozilla.org/listinfo/governance > _______________________________________________ governance mailing list [email protected] https://lists.mozilla.org/listinfo/governance
