EclipseFdn / EclipseFdn/open-vsx.org

Claiming namespace openany

Open
#13,150 1 comment 0 reactions 0 assignees View on GitHub
namespace operations
Dominant language
TypeScript
Stars
394
Forks
145
Avg merge
2d 19h
Merged PRs (30d)
3

Description

### Namespace

openany

### Ownership

- [x] The namespace is not currently owned on Open VSX (verify by a search on [open-vsx.org](https://open-vsx.org))

### Account Age

- [x] The GitHub ID making this request has at least 12 months of public history

***
### Option 1

### VS Code Publisher with Repo

- [ ] The namespace is also a publisher account on the VS Code Marketplace (check by browsing https://marketplace.visualstudio.com/publishers/{publisher}) and has an extension published there with a repo specified in its package.json file.

***
### Option 2

### VS Code Publisher without Repo

- [x] The namespace is also a publisher account on the VS Code Marketplace and does not have published extensions or has published extensions with no GitHub repos.

__Chose one of the following:__
- [ ] Provide Open VSX administrator ID (`46461f8e-a0a8-6de8-9186-8ac72e28656d`) temporary reader access to the VS Code Marketplace Publisher Account.
- [x] If the namespace matches your domain name, define a TXT record in your DNS, listing the URL to this issue and provide the domain/subdomain of the TXT record

### Claim Evidence

- VS Code Marketplace publisher: https://marketplace.visualstudio.com/publishers/openany (extension `openany.openany-har` 1.0.0, published today; its package.json has no repository field because the source repo is private).
- The namespace matches our domain: https://openany.dev (the domain on the VS Code Marketplace publisher profile; Microsoft's DNS token check for it has passed).
- The same extension is published on Open VSX under this namespace: https://open-vsx.org/extension/openany/openany-har
- A TXT record `openvsx.openany.dev` listing the URL of this issue will be added right after this issue is created; I will comment with the record once it resolves.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by verifying the openany namespace on open-vsx.org and the VS Code Marketplace publisher evidence linked in the issue. Check that the DNS TXT record at openvsx.openany.dev lists this issue URL and resolves, then confirm that the namespace claim can be completed.

Written by the indexing model from the issue text.

Assessment

Tech stack
github, vscode
Domain
authorization
Issue type
Feature
Difficulty
1/5
Estimated time
Under an hour
Activity status
Active
Clarity
Clearly specified
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.