KO | EN

GitLite

Minimalist Open Source Repository Search Engine

gitlite — search

#dsh #dsh-plugin #developer-tools #ai-agent #claude-code #codex #typescript #ai-agents #deepseek-harness #mcp #cli #rust

cinnamon-spices-extensions

★ 154 Open GitHub ↗

Extensions for the Cinnamon desktop

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# cinnamon-spices-extensions

![Validate spices](https://github.com/linuxmint/cinnamon-spices-extensions/workflows/Validate%20spices/badge.svg)

This repository hosts all the extensions available for the Cinnamon desktop environment.

Users can install spices from https://cinnamon-spices.linuxmint.com, or directly from within Cinnamon -> System Settings.

# Definitions

## UUID

Each spice is given a name which uniquely identifies them.

That name is their UUID and it is unique.

## Author

Each spice has an author.

The github username of the author is specified in the spice's info.json file.

# File structure

A spice can contain many files, but it should have the following file structure:

- UUID/
- UUID/info.json
- UUID/screenshot.png
- UUID/README.md
- UUID/files/
- UUID/files/UUID
- UUID/files/UUID/metadata.json
- UUID/files/UUID/extension.js
- UUID/files/UUID/icon.png

There are two important directories:

- UUID/ is the root level directory, it includes files which are used by the website and on github.
- UUID/files/ represents the content of the ZIP archive which users can download from https://cinnamon-spices.linuxmint.com or which is sent to Cinnamon when installing the spice from System Settings. This is the content which is interpreted by Cinnamon itself.

As you can see, the content of the spice isn't placed inside UUID/files/ directly, but inside UUID/files/UUID/ instead. This guarantees files aren't extracted directly onto the file system, but placed in the proper UUID directory. The presence of this UUID directory, inside of files/ isn't actually needed by Cinnamon (as Cinnamon creates it if it's missing), but it is needed to guarantee a proper manual installation (i.e. when users download the ZIP from the Cinnamon Spices website).

Important note:

- The UUID/files/ directory has to be "empty", which means that it should contain ONLY the UUID directory. Else the spice won't be installable through System Settings.

At the root level:

- info.json contains information about the spice. For instance, this is the file which contains the github username of the spice's author.
- screenshot.png is a screenshot of the spice in action.
- README.md is optional and can be used to show instructions and information about the spice. It appears both in Github and on the website.

## Validation

To check if a spice with UUID satifies those requirements run the `validate-spice` script in this repo:
```
./validate-spice UUID
```

### AI-assisted coding

All submissions may be subject to AI code review as well as human review. If you are 'coding' using an AI tool, it is highly recommended you use [our review agent's instructions](.github/copilot-instructions.md) as a context guide and perform your own code review based on it prior to submission. You, the human, should read it as well.

## Development

To facilitate easier testing of Extensions locally, run the `test-spice` script in this repo:

Validate and then copy a Spice with UUID:

```bash
./test-spice UUID
```

Skip validation (not recommended) and then copy a Spice with UUID:

```bash
./test-spice -s UUID
```

Remove all locally installed development copies of Spices:

```bash
./test-spice -r
```

NOTE: Local copies of Spices for development/testing purposes will have a `devtest-` prefix attached for easier identification and cleanup.

# Rights and responsibility of the author

The author is in charge of the development of the spice.

Authors can modify their spice under the following conditions:

- They need to respect the file structure and workflow defined here
- They cannot introduce malicious code or code which would have a negative impact on the environment
- They cannot direct users to install code or functionality from outside the Spices ecosystem (see "Spices must be self-contained" below)
- They cannot ship pre-compiled blobs (besides icons and images), nor any code which is not open source, nor source code for binary compiled languages (other than something like GLSL).
- Settings should be maintained with Cinnamon's xlet settings interface. No GSettings schemas, no directly editing Cinnamon's JSON files.

Authors are able to accept or refuse changes from other people which modify the features or the look of their spice.

Authors may choose to pass on development of their extension to someone else. In that case, the "author" field in UUID/info.json will be changed to the new developer and the "original_author" field will be added to give credit to the original developer.

If an author abandons their extension, the Linux Mint team will take over maintenance of the extension or pass it on to someone else. Several factors are used to determine if an extension is abandoned, including prolonged activity, failure to respond to requests, and serious breakages that have occurred due to changes in API, etc. If you plan to abandon an extension, please notify us, so we don't have to guess as to whether it is abandoned or not.

# Spices must be self-contained

These repositories exist so that third-party developers can publish their spices and users can install them safely. When a spice is hosted here, it is reviewed when it is added and again on every update, and we are able to watch for security and safety problems in the code. This oversight is the whole reason the Spices repositories and the [Cinnamon Spices website](https://cinnamon-spices.linuxmint.com) exist — it's what lets users install spices with confidence.

For this to work, the version of a spice published here must be the complete, fully functional spice. Anything a user installs from outside these repositories is outside our review and outside our control: we can't check it for malicious or unsafe code, we can't vouch for it, and it puts users at risk. Accordingly, authors **may not**:

- Direct or encourage users to download or install additional code, plugins, add-ons, or an "enhanced"/"full"/"pro" version of the spice from anywhere outside the Spices ecosystem.
- Have the spice fetch and execute code from external sources at runtime.
- Withhold or disable features in the published spice in order to push users toward an externally-hosted version.
- Use the spice, its README, screenshots, or settings to advertise or link to such downloads.

This applies regardless of whether the external version is paid, free, or offered for any other reason. The point is not money — it's that everything a user runs should be the code we have reviewed and published here. Submissions that don't meet this requirement will not be accepted.

## System dependencies

Some spices rely on software that is already packaged for the user's distribution (for example `yad`, `sox`, or `nmcli`). It is fine for a spice to detect a missing dependency and offer to install it — or to prompt the user to install it — through the system's package manager: `apt`, or a distro-agnostic front-end such as PackageKit (`pkcon`/`pkgcli`), using the system's normal authentication (`pkexec`). These packages come from the distribution's own trusted repositories, not from the author. A spice must **not**, however, instruct users to manually download and install software from arbitrary websites.

## Supporting the author

None of this prevents authors from being supported for their work. You are welcome to include a donation or support link. That link must not interrupt the user — no nag screens, pop-ups, repeated prompts, or features held back behind it inside the spice itself.

# Pull requests from authors and workflow

To modify a spice, developers create a Pull Request.

Members of the cinnamon-spices-developers team review the pull request.

If the author of the pull request is the spice author (his github username matches the author field in UUID/info.json), the reviewer only has to perform the following checks:

- The changes only impact spices which belong to that author
- The changes respect the spices file structure
- The changes do not introduce malicious code or code which would negatively impact the desktop environment

If everything is fine, the PR is merged, the website is updated and users can see a spice update in System Settings.

# Pull requests from other people

In addition to the checks specified above, if the pull request comes from somebody other than the author, it will be held until the author reviews it or gives a thumbs-up, with the following exceptions:

- If it is a bug fix, the PR may be merged, though if the bug is minor, or the fix could potentially impact the way the extension works, we may wait for author approval before merging.
- If the pull request adds translations it will likewise be merged. These are not going to effect the functionality of the code, and will make the extension available to many users who couldn't use it before due to a language barrier. We view this a essentially a bugfix, but it is included here for clarification.
- If the author fails to respond in a reasonable time, we will assume the extension is abandoned (as mentioned above) and the pull request will be merged assuming it meets all other requirements.

If the changes represent a change in functionality, or in look and feel, or if their implementation could be questioned and/or discussed, the reviewer should leave the PR open and ask the author to review it.

If the author is happy with the PR, it can then be merged. If he's not, it can either be closed or updated to reflect any changes the author requested, at which point it will either be merged or the author may be asked to review the changes depending on whether it is clear the changes fully meet the author's requirements.

# Deletions

Authors are entitled to remove their spice.

The Cinnamon team is also entitled to do so. Common reasons are lack of maintenance, critical bugs, or if the features are already provided, either by Cinnamon itself, or by another spice which is more successful.

# Additions

New spices can be added by Pull Request.

The Cinnamon team can accept or reject the addition and should give justification in the PR comments section.

# Reporting Bugs and Creating Pull Requests

See the [Guidelines for Contributing](https://github.com/linuxmint/cinnamon-spices-extensions/blob/master/.github/CONTRIBUTING.md)

# Translations

The script `cinnamon-spices-makepot` in this repo was written to help authors to update their translation template (`.pot`) file and to help translators to test their translations.

Updating a translation template `.pot`:
```
./cinnamon-spices-makepot UUID
```

Test your translations `.po` locally before uploading to Spices:
```
./cinnamon-spices-makepot UUID --install
```

Ensure that the `.po` file you wish to install is located inside the `UUID/files/UUID/po/` directory.

More info:
```
./cinnamon-spices-makepot --help
```

# Translations Status Tables

The spices receive updates which sometimes contain new or updated strings that need to be translated. The translation status tables were created to give translators a better overview of the current state of translations and also to make it easier to track where new untranslated strings appear.

* [Translation Status Tables for Extensions](https://github.com/linuxmint/cinnamon-spices-extensions/blob/translation-status-tables/.translation-tables/tables/README.md)

To ensure that these tables are always up-to-date, they are automatically regenerated whenever a new commit is pushed to the master branch.

cinnamon-spices-extensions

Explore Similar Repositories

Was this content helpful?

Recent Feedback

Download README