Create Remark organization on Azure DevOps

[asbjornu]

Subject of the feature

As suggested in remarkjs/remark#508 (comment) we need a remark organization in Azure DevOps under which we can publish new versions of this extension. Here's a recipe for the entire publishing process.

As soon as the personal access token and everything else is set up as secrets in this repository, I can get to work on automating the publishing process.

[asbjornu]

@ChristianMurphy, can you please assist with this? 🙏

[wooorm]

This project seems to average about 1 release per year (5 releases since 2016). I’m generally a fan of cutting releases by hand. What benefits do you see by automating releases?

[asbjornu]

Regardless of the automation, we need an organization on Azure DevOps, which by the lack of access to this repository and the remark organization I can't create.

Regarding the automation, I can't think of a good reason to not publish on every git tag preformed in the repository. How often that has happened in the past is not indicative of how often it's going to happen in the future, with a new maintainer. Also, if the release process happens seldom, it's even more important to automate it, as there's little I hate more than having to re-read documentation on how to perform a release on a platform because it's so long since I last did it I have forgotten how to do it. Baking it in to a simple GitHub workflow is the simplest way to ensure that releases stay consistent over time, imho.

[ChristianMurphy]

/cc @JounQin from https://github.com/mdx-js/vscode-mdx
I notice the mdx vscode plugin is running off the JounQin namespace https://marketplace.visualstudio.com/items?itemName=JounQin.vscode-mdx
Is it easier to run off a personal namespace, or would there be value in creating an organization?

[wooorm]

@ChristianMurphy See also the previous discussion about downsides of personal namespaces: remarkjs/remark#508 (comment)

[asbjornu]

Creating an organization is simple enough and makes the published extensions independent of one single person, reducing the bus factor. If you have several projects underneath the Remark umbrella published on the Visual Studio Marketplace, I think that argues even more strongly for creating a Remark organization on there.

[asbjornu]

@ChristianMurphy, @wooorm, is it anything I can do to assist in the creation of a RemarkJS organization?

[asbjornu]

@ChristianMurphy @wooorm Ping?

[JounQin]

+1 for official organization personally

[wooorm]

Sorry, @asbjornu, thanks for the ping!

@asbjornu @JounQin As we’re talking vscode-remark and vscode-mdx, which fall under different organisations, does unified (or unifiedjs) or so sound good?

[JounQin]

@wooorm I'm in favor of unifiedjs which is also the GitHub organization name.

[asbjornu]

Sounds good to me!

[wooorm]

cool cool! @asbjornu, I believe you volunteered to set it up, right? I’d appreciate that. Otherwise I can try my hands at it!

[asbjornu]

Sure, I've now created the Unified.js publisher on the VS Marketplace. Let me know your Microsoft Account e-mails so I can add you to it. I'll close this issue and will create a new one for publishing to the VS Marketplace.

[wooorm]

Thanks @asbjornu. I’m using my gmail listed here: https://github.com/wooorm.
Also, @ChristianMurphy, @JounQin?

[ChristianMurphy]

My email is listed here: https://github.com/ChristianMurphy

[asbjornu]

Sorry, neither of those addresses seem to work. Are they registered Microsoft Accounts?

[edited by wooorm to remove slightly sensitive information]

[JounQin]

@asbjornu https://github.com/JounQin

[asbjornu]

Seems like there's a bug. I'll see whether I can circumvent it somehow.

[asbjornu]

Maybe you can try [edited by christianmurphy to remove slightly sensitive information]

Sorry, that didn't work either.

[edited by christianmurphy to remove slightly sensitive information]

This is a bug and the only way around seems to be to send Microsoft the ID of your Microsoft Accounts. To retrieve your Microsoft Account ID please do the following:

1. Login to the Marketplace with the email address that has to be added to the publisher.
2. After getting logged in, from the same browser window, open this API URL.
3. In the JSON, please find the value of authenticatedUser.id and paste it here.

[wooorm]

I’m: ccb650b3-241b-6d93-b0c6-bc7b7568509a

[JounQin]

Mine: 20db3b81-ae57-4f71-b57a-dec769d2bbac

[ChristianMurphy]

f39e7fd2-43fe-45dc-8eb7-9eed90da28db