@@ -12,13 +12,10 @@ nav_order: 3
1212
1313## Code
1414
15- The ** place for official plugin repositories** is the [ Albert launcher organization] ( https://github.com/orgs/albertlauncher/repositories ) .
16- Distributed native plugins are submodules in the [ Albert repository plugins directory] ( https://github.com/albertlauncher/albert/tree/main/plugins ) .
17- Python plugins in the [ Python repository plugins directory] ( https://github.com/albertlauncher/albert-plugin-python/tree/main/plugins ) respectively.
18-
19- The ** main branch** of a plugin repository represents the latest version
15+ The place for official plugin repositories is the [ Albert launcher organization] ( https://github.com/orgs/albertlauncher/repositories ) .
16+ The main branch of a plugin repository represents the latest version
2017that is or will be distributed with the application and therefore has to be protected.
21- Contributions _ have to pass peer reviewing _ via pull request.
18+ Contributions have to pass peer reviewing via pull request.
2219As such contributors have to work on their own fork and send a PR.
2320The rationale is to ensure
2421
@@ -27,18 +24,6 @@ The rationale is to ensure
2724- Tidiness. ` git status ` is clean or contains approved plugin changes.
2825
2926
30- ### Fixes and Features
31-
32- Before putting a lot of effort into a contribution, open an issue and discuss your planned changes.
33- This is important, because there is a chance that your changes may be rejected.
34- Contributing to existing plugins is straightforward.
35-
36- 1 . Fork the repository.
37- 1 . Work on the fork.
38- 1 . Send a pull request.
39- 1 . Go through the review process.
40-
41-
4227### New plugins
4328
4429We highly appreciate new plugin additions, however to be shipped there should be a demand for its use case.
@@ -58,6 +43,18 @@ For a plugin to be accepted it has to satisfy the following **requirements**:
5843Having a _ concise_ ` README.md ` summarizing features, requirements, limitations, supported platforms and implementation details is recommended.
5944
6045
46+ ### Fixes and Features
47+
48+ Before putting a lot of effort into a contribution, open an issue and discuss your planned changes.
49+ This is important, because there is a chance that your changes may be rejected.
50+ Contributing to existing plugins is straightforward.
51+
52+ 1 . Fork the repository.
53+ 1 . Work on the fork.
54+ 1 . Send a pull request.
55+ 1 . Go through the review process.
56+
57+
6158## Maintenance
6259
6360You can always send features and fixes as outside collaborator.
0 commit comments