Remark: Move vscode-remark to the remarkjs organization

[asbjornu]

This isn't exactly a feature request, but I thought this would be the best way to bring your attention to the topic, so please bear with me.

vscode-remark is a plugin to Visual Studio Code that uses remark-lint to automatically lint documents. The plugin has ~7.000 downloads on the Visual Studio Marketplace and is currently looking for a new maintainer (see mrmlnc/vscode-remark#22). I thought the best solution would be to have the repository moved from @mrmlnc to @remarkjs.

If no one else comes forth with a strong desire to maintain the plugin, I'll volunteer as an administrator of the repository after the move. To perform the move, an administrator in the @remarkjs organization needs to be added as an administrator of the vscode-remark repository to initiate the move.

Thoughts?

[wooorm]

Hi Asbjørn, Denis,

That’s possible indeed! The process we use for such things is documented here: https://github.com/unifiedjs/collective/blob/main/organizations.md#motion-to-grant-governance.

I’m not a VSCode user though, so would prefer some other remark member or you to be the “owner” of the project, as I lack the knowledge or interest.

@asbjornu, are you also interested in other remark / unified projects?

[asbjornu]

Thanks, @wooorm! Much appreciated. We'll follow through with our commitments according to your governance process soon, I hope.

I'm happy to become an owner of the repository after it's moved.

are you also interested in other remark / unified projects?

What did you have in mind?

[mrmlnc]

I agree to transfer my project to your organization.

JFYI: I can't give you the rights for the extension in the store. As I understand from the instruction — I can grant rights to all extensions, but not to one specific one. So in this case we can deprecate the existing extension and point users to the next extension.

[asbjornu]

@wooorm, do you need anything else in order to start the transfer?

[wooorm]

Heyy sorry about the wait.

@mrmlnc Are you saying that, going with step 1, would give @asbjornu or me or so, access to publish all your extensions? 😞

[asbjornu]

@wooorm, isn't a much better solution to create a remark or remarkjs organization/user on the Visual Studio Marketplace under which we can publish an entirely new extension and then deprecate and redirect the old extension to the new one?

[mrmlnc]

I think that the option suggested by @asbjornu suits us better. This does not require any investment (money) other than time (a little). Also VS Code has a great instruction.

[wooorm]

Sorry for dropping the ball again and being slow, was busy focussing on micromark!

That idea sounds fine! Want to do that, @asbjornu?

[wooorm]

And, @asbjornu, as you said “I'm happy to become an owner of the repository after it's moved.”, we can do that where you are an “outside maintainer” in the remark org, for that repo specifically, or a “normal” maintainer, with write and review rights to the whole remarkjs org. Which would you prefer?

[asbjornu]

I'm fine with both, @wooorm! I'm not ready to take on more responsibility than vscode-remark for the moment, though.

[asbjornu]

micromark looks awesome, btw!

[wooorm]

Alright, @mrmlnc can you add me to the project? See Granting for more on the next steps, which I’ll take

[asbjornu]

@mrmlnc, ping?

[wooorm]

@mrmlnc can you give me more access rights? I can’t see the settings tab yet?

[mrmlnc]

I couldn't find any buttons to give more rights (already collaborator). So, I chose transfer ownership to @wooorm.

[wooorm]

I keep forgetting how to best transfer haha, this works, thanks!

[asbjornu]

@wooorm, awesome to see the repository moved. Could you please promote me to admin as well? 🙏