New maintainer

[cmcaine]

I can take over maintenance of this project, if you like.

My npm username is cmcaine. I believe ownership can be transferred like so: slevithan/xregexp#11

I'm interested to know why you think Mozilla is compromising privacy for convenience. Is it the DRM issue?

[ghost]

Hi, I can definitely give you the appropriate rights here and on npm as well!

I was referring to the google analytics deployed on supposedly internal pages (That were in fact AMO pages), which came in the wake of the big browser is watching you ad campaign they led. But I understand that's a very personal opinion.

[ghost]

So, maintenance rights have been given, on npm and github. :)

[cmcaine]

I think Mozilla's response to the issue was good, though I'm disappointed that they were ignoring DNT beforehand: mozilla/addons#3145

When I try to commit to the repo, I get

remote: Resolving deltas: 100% (2/2), completed with 2 local objects.
remote: error: GH006: Protected branch update failed for refs/heads/master.
remote: error: Required status check "continuous-integration/travis-ci" is expected.
To github.com:michael-zapata/web-ext-types.git
 ! [remote rejected] master -> master (protected branch hook declined)
error: failed to push some refs to 'git@github.com:michael-zapata/web-ext-types.git'

I imagine I could push to another branch then merge. Do you have a strong preference for that style? Do you use a helper to make it easier?

Because this seems like a lot when I already know that the tests pass:

git checkout -b chore/change-maintainer
# edits, adds and commits
git push -u origin
git checkout master
git merge chore/change-maintainer
git branch -d chore/change-maintainer
git push -d origin chore/change-maintainer

[ghost]

That's because master is protected, I tend to rely on some level of CI to ensure master is always green, fool-proofing it against my tired/hasty/... self. You can always disable the check though.