EclipseFdn / EclipseFdn/open-vsx.org

Claiming namespace [laplace-lang]

Open
#13,092 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

laplace-lang

### 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 the sole author and maintainer of the laplace project, a
source-to-source preprocessor/compiler for the Stan probabilistic
programming language:

- Compiler: https://github.com/mlatinov/laplace
- Editor tooling (this extension): https://github.com/mlatinov/laplace_tools

The namespace "laplace-lang" corresponds to the project name
("laplace") with a "-lang" suffix, a common convention for
language-tooling namespaces (e.g. rust-lang, python-lang).

This project is not published on the VS Code Marketplace, and I do
not have a dedicated project domain.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the namespace claim in issue #13092, then verify laplace-lang on open-vsx.org and inspect the corresponding publisher page on the VS Code Marketplace. No repository files or tests are mentioned; done means the ownership evidence is verified and the namespace claim is processed.

Written by the indexing model from the issue text.

Assessment

Tech stack
vscode
Domain
tooling
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.