deploy: albertlauncher/documentation@9445ca0

Author: ManuelSchneid3r

assets/js/search-data.json

@@ -57,7 +57,7 @@
   },"8": {
     "doc": "Contributing",
     "title": "Code",
-    "content": "The place for official plugin repositories is the Albert launcher organization. Distributed native plugins are submodules in the Albert repository plugins directory. Python plugins in the Python repository plugins directory respectively. The main branch of a plugin repository represents the latest version that is or will be distributed with the application and therefore has to be protected. Contributions have to pass peer reviewing via pull request. As such contributors have to work on their own fork and send a PR. The rationale is to ensure . | Safety. For users and developers. | Simplicity. Upstream main branch is reviewed and distributable. | Tidiness. git status is clean or contains approved plugin changes. | . Fixes and Features . Before putting a lot of effort into a contribution, open an issue and discuss your planned changes. This is important, because there is a chance that your changes may be rejected. Contributing to existing plugins is straightforward. | Fork the repository. | Work on the fork. | Send a pull request. | Go through the review process. | . New plugins . We highly appreciate new plugin additions, however to be shipped there should be a demand for its use case. If you want your plugin to be added to the official repositories, put it to the list of candidates in the organization readme and promote it in the community chat. Once your plugin has some users, you can request its addition to the official repositories. For a plugin to be accepted it has to satisfy the following requirements: . | The project is licensed under a permissive open source license (e.g. MIT, Apache, BSD). | The project has an active maintainer. | The repository content is essential to the functionality of the plugin. Keep in mind that in future somebody else may want to maintain the plugin and for distribution the size of the repository should be minimal. | Icons are vector graphics or 128x128 raster images. | . Having a concise README.md summarizing features, requirements, limitations, supported platforms and implementation details is recommended. ",
+    "content": "The place for official plugin repositories is the Albert launcher organization. Distributed native plugins are submodules in the Albert repository plugins directory. Python plugins in the Python repository plugins directory respectively. The main branch of a plugin repository represents the latest version that is or will be distributed with the application and therefore has to be protected. Contributions have to pass peer reviewing via pull request. As such contributors have to work on their own fork and send a PR. The rationale is to ensure . | Safety. For users and developers. | Simplicity. Upstream main branch is reviewed and distributable. | Tidiness. git status is clean or contains approved plugin changes. | . Fixes and Features . Before putting a lot of effort into a contribution, open an issue and discuss your planned changes. This is important, because there is a chance that your changes may be rejected. Contributing to existing plugins is straightforward. | Fork the repository. | Work on the fork. | Send a pull request. | Go through the review process. | . New plugins . We highly appreciate new plugin additions, however to be shipped there should be a demand for its use case. If you want your plugin to be added to the official repositories, put it to the list of candidates in the organization readme and promote it in the community chat. Once your plugin has some users, you can request its addition to the official repositories. For a plugin to be accepted it has to satisfy the following requirements: . | The project is licensed under a permissive open source license (e.g. MIT, Apache, BSD). | The project has an active maintainer. | The repository content is essential to the functionality of the plugin. Keep in mind that in future somebody else may want to maintain the plugin and for distribution the size of the repository should be minimal. | Icons are vector graphics or 128x128 raster images. | Git history has to be linear | Git commits have to be Conventional Commit Spec compliant (automated versioning and changelogs) | . Having a concise README.md summarizing features, requirements, limitations, supported platforms and implementation details is recommended. ",
     "url": "/gettingstarted/contributing/#code",
 
     "relUrl": "/gettingstarted/contributing/#code"