|
4 | 4 |
|
5 | 5 | ## Contents
|
6 | 6 |
|
7 |
| -This branch is not used for public. Please use one of the other branches available for submitting add-ons. |
| 7 | +This branch contains a certain category of add-ons from which our back-end script creates .zip files which are made available to each Kodi client. |
| 8 | +* Language add-ons |
| 9 | +* Image resources |
| 10 | +* Controller profiles |
| 11 | + |
| 12 | +## How to submit your add-on and subsequent updates ## |
| 13 | + |
| 14 | +Your add-on must follow our strict repository rules to be considered for inclusion. Please consult the [Add-on rules] (http://kodi.wiki/view/Add-on_Rules) wiki page for further details. Please review these rules carefully before submitting your add-on. Should you have any questions regarding them please start a forum thread in one of the following locations |
| 15 | +* [Python add-ons] (http://forum.kodi.tv/forumdisplay.php?fid=26) |
| 16 | +* [Skins] (http://forum.kodi.tv/forumdisplay.php?fid=12) |
| 17 | + |
| 18 | +After you have read the repository guidelines and made sure your addon is compliant with them, you may begin the submission process. By forking this repository and creating a pull-request to the correct repository branch you are asking permission to include your add-on into the official Kodi repository. Subsequent updates can be done in a similar way by updating the code and creating a new pull-request again. Make sure that your local git clone is always rebased before sending a pull-request. |
| 19 | + |
| 20 | +* Fork this repository |
| 21 | +* Create a branch |
| 22 | +* Commit your new add-on or any subsequent update in a single commit |
| 23 | +* Push the branch to your own forked repository |
| 24 | +* Create pull request |
| 25 | +* Await commments if any changes are deemed necessary |
| 26 | + |
| 27 | +A short guide on forking and creating a pull request can be found here: [contributing] (https://github.com/xbmc/repo-resources/blob/master/CONTRIBUTING.md). |
| 28 | + |
| 29 | +Keep in mind that add-ons in the official repository should be considered stable. This means that they should be well-tested before you submit them for inclusion. Because they are for stable users, they should avoid being updated too often. Too often is of course subjective. If your add-on is in rapid development, and features are constantly being added, hold off until you have hit a good stopping point and tested the current version. |
| 30 | +This means that you should not submit a request every time you change your code. If you are submitting updates more than once per week something is wrong. Once or twice per month is probably a better goal, barring unforeseen conditions (like a content source changing its paths). With good reasons provided we will of course make exceptions as we strive to provide the best user experience. |
| 31 | + |
| 32 | +## Compatibility |
| 33 | + |
| 34 | +This branch is used for add-ons that are designed for Kodi v21 Omega builds and higher only. From these code repositories and branches our back-end uploads .zip files of the compatible add-ons to our main mirror server. |
| 35 | +* [Mirror of Kodi v21 Omega compatible add-ons] (http://mirrors.kodi.tv/addons/omega/) |
| 36 | + |
| 37 | +## Status |
| 38 | + |
| 39 | +* New add-on additions: **Accepted** |
| 40 | +* Updating already present add-ons: **Accepted** |
| 41 | + |
| 42 | +## Disclaimer ## |
| 43 | + |
| 44 | +The contents of this repository mainly consist of add-ons created by third party developers. Team Kodi holds no responsibility for it's contents. |
| 45 | +Team Kodi reserves the right to update or remove add-ons at any time as we deem necessary. |
8 | 46 |
|
9 | 47 | ## Quick Kodi development links
|
10 | 48 |
|
|
0 commit comments