Migration to firefox-devtools org

[digitarald]

Firefox DevTools wants to support the development of this extension. Joining forces with @hbenl, who will remain a maintainer, we'll continue with shared governance!

Apart from @hbenl and me, the Firefox DevTools team members that will be involved are @janodvarko and @jasonLaster.

How will shared governance help this project?

1. Keep the extension in sync with Firefox's debugger server, remote protocol changes and upcoming features (e.g. dfddc7a8134b3672fd9857f4c1d39a56a582ef02, 5f86bdbd2c27137e55f3bfd3352a95abb7a2cb6a, etc)
2. Simplify setup and integration with DevTools
3. Make this the official Firefox extension for VSCode, with proper branding (e.g. #81)
4. Do more joint outreach to spread the word about the extension and how to set up

What's next?

• [x] Transfer repo to https://github.com/firefox-devtools. Owner: @hbenl (moving the repo)
  • [x] Make @hbenl and @jasonLaster, @janodvarko & @digitarald maintainers of that repo. Owner: @digitarald (admin in firefox-devtools)
  • No need to update Copyright/License
• [x] Add Mozilla's contributing.md, CODE_OF_CONDUCT.md
• [x] Update references
  • [x] VSCode extension marketplace
• [x] Update branding
  • [x] New icon (@hbenl)
  • [x] Updated description (@digitarald)
• [x] Shared publishing access
  • [x] Create new publisher ID
  • [x] Update publisher ID for current extension with support from the VSCode team. Owner @digitarald
• [x] Ship a new release (@hbenl)
• [ ] Announcement
  • [ ] Blog post (@digitarald / @janodvarko)
  • [ ] Update MDN DevTools page (@digitarald)

[hbenl]

I have one more item for the TODO list: every maintainer should be able to publish new versions of the extension. There seem to be 2 options for this:

• move the extension to a new publisher account and add all maintainers to this publisher
• add other maintainers to the current publisher account

The big downside of the first approach is that this would change the extension ID in the VS Code Marketplace and hence all current users of the extension would have to reinstall it - it seems there is currently no way to automatically migrate them to the new extension ID. The downside of the second approach is that the current publisher account is also used for my other extensions and I would give you the ability to manage those extensions as well. But I'd trust you to not abuse this, so I'd be OK with that.

There doesn't seem to be any documentation on how to do this, all I could find so far are these issues: Transfer Publishers in Marketplace Guidance for transferring ownership of extension

[digitarald]

Good point @hbenl ! I have been in touch with the VSCode team and they offered to change the publisher ID. I will add those items to the list then.

[hbenl]

The migration of the extension to the firefox-devtools publisher was successful and I already made a bugfix release with the new publisher.