EclipseFdn / EclipseFdn/open-vsx.org
Claiming namespace swobu
Closed
Beginner friendly
Nobody has claimed this yet.
namespace
operations
- Dominant language
- TypeScript
- Stars
- 395
- Forks
- 145
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 3
Description
Namespace
swobu
Ownership
- The namespace is not currently owned on Open VSX (verify by a search on open-vsx.org)
Account Age
- 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/swobu) 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
- You are unable to provide the inputs required in the three options above. This option will take the longest to process.
Claim evidence
Provide the requested information (commit URL or domain/subdomain) or a justification for granting ownership of the namespace.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by verifying that the swobu namespace is unowned on open-vsx.org and that swobu is a VS Code Marketplace publisher with an extension whose package.json specifies a repository. The request is complete when the required claim evidence, such as a commit URL or domain/subdomain, is provided and the ownership claim can be processed.
Written by the indexing model from the issue text.
Assessment
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100