EclipseFdn / EclipseFdn/open-vsx.org

Claiming namespace `chintanjoshi`

Open
#13,111 0 comments 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

chintanjoshi

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

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

### All Other Cases

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

### Claim evidence

I am requesting ownership of the Open VSX namespace `chintanjoshi`.

My GitHub account is:
https://github.com/chintanjoshi01

The extension published under this namespace is:
https://open-vsx.org/extension/chintanjoshi/conversation-recall

The extension's public source repository is:
https://github.com/chintanjoshi01/conversation-recall-vscode

I am the developer and maintainer of the `conversation-recall` extension. The extension was developed and published by me under the `chintanjoshi` Open VSX namespace.

Although my GitHub username is `chintanjoshi01`, the Open VSX namespace used for my extension is `chintanjoshi`. The public GitHub repository provides evidence of my ownership and development of the extension.

I am requesting ownership of the namespace so I can continue maintaining and publishing updates to the extension under this namespace.

I can provide additional commit or repository evidence if required.

Thank you.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reviewing the namespace entry on open-vsx.org and the linked conversation-recall repository. Check the referenced VS Code Marketplace publisher conditions and the provided ownership evidence. Done means the request has been verified and the chintanjoshi namespace ownership is updated.

Written by the indexing model from the issue text.

Assessment

Tech stack
vscode
Domain
developer-experience
Issue type
Feature
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.