EclipseFdn / EclipseFdn/open-vsx.org

Claiming namespace pacmon

Closed Beginner friendly
#13,163 1 comment 0 reactions 0 assignees View on GitHub
namespace operations
Dominant language
TypeScript
Stars
395
Forks
145
Avg merge
2d 19h
Merged PRs (30d)
3

Description

### Namespace

pacmon

### 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

### 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.

### VS Code Publisher without Repo

- [ ] 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.

### Not a VS Code Marketplace Publisher

- [x] The namespace is not a publisher account on the VS Code Marketplace

### All Other Cases

- [ ] You are unable to provide the inputs required in the three options above. This option will take the longest to process.

### Claim evidence

- Open VSX namespace: pacmon — created by @yavuzatlas-kontra, currently unowned.
- Domain: pacmon.dev, registered and operated by Kontra Siber Savunma Teknoloji
Ltd. Sti. (https://kontra.com.tr).
- I will add a TXT record on pacmon.dev containing the URL of this issue and
comment here once it has propagated.
- Context: Pacmon is our VS Code extension, published on the VS Code Marketplace
as Kontra.pacmon (https://marketplace.visualstudio.com/items?itemName=Kontra.pacmon),
with source at https://github.com/kontratek/pacmon and the npm package "pacmon"
(https://www.npmjs.com/package/pacmon). The extension itself is published under
the "kontra" namespace; we are claiming the matching "pacmon" namespace only to
prevent a confusing duplicate from appearing under our product name.

Contributor guide

No contributing guide indexed for this repository

Research direction

Check the pacmon namespace on open-vsx.org and review the linked VS Code Marketplace and GitHub repository evidence. Verify the pacmon.dev TXT record once it propagates; the work is done when ownership is confirmed and the namespace is claimed.

Written by the indexing model from the issue text.

Assessment

Tech stack
vscode
Domain
tooling
Issue type
Feature
Difficulty
1/5
Estimated time
1-3 hours
Activity status
Active
Clarity
Clearly specified
Newbie friendliness
75/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.