Official Kodi Wiki - User contributions [en]

Kodi Foundation

2025-07-30T18:03:57Z

Yol:

{{mininav}}
<section begin=intro />The "'''Kodi Foundation'''" is the non-profit organization that oversees the [[Kodi|{{kodi}}]] project and is registered in the US.<section end=intro />

== Members ==
Membership of the Kodi Foundation is typically taken from members of Team Kodi, but may include non Team members.

== Board of Directors ==
{| class="infobox"
|-
|
<section begin=Foundation members />
* '''Keith Herrington (keith)''' - Board member - ''Term: 11/2016 - 11/2026''
* '''Markus Härer (neo1973)''' - Board member - ''Term: 11/2024 - 11/2026''
* '''Prof Yaffle (Prof Yaffle)''' - Board member - ''Term: 11/2023 - 11/2025''
* '''Yol (Yol)''' - Board member - ''Term: 11/2019 - 11/2025''
* '''Phunkyfish (Phunkyfish)''' - Board member - ''Term: 11/2023 - 11/2025''<section end=Foundation members />
|}
The Kodi Board of Directors are Foundation members that manages the Kodi Foundation. The Board consists of five seats that are chosen by vote from the Kodi Foundation members. The Board's responsibilities include management of funds, publicity, and all business related issues (taxes, communication with other businesses, maintaining non-profit status etc.)
{{-}}

== Board of Directors meetings ==
The Board meets about once a month (in addition to any special meetings as required) to discuss any business that needs to be handled by the foundation. Meetings are typically conducted via teleconference using a service such as Skype.

== Board of Directors elections ==
;Who can be a Kodi Board member?
:Any existing member of the foundation, as voted by the remaining members.

;How long does a board member hold office?
:Terms last for two years. We endeavor to have a staggered cycle so that not all board members are turned over at a single election. There are no term restrictions, so Board members may even run for consecutive terms. However, in the interests of sharing the load, any and all members are encouraged to participate.

;What is expected of a Kodi Board member?
:Board members are expected to attend all meetings or will otherwise be diligent in letting the other board members know if they won't be around. Further, they'll be expected to make decisions (as a group) in the best interests of the foundation. The Board accountable to the members, so should consider recommendations made by members during the decision making process, Though they ultimately must make the final decisions. Any and all discussion should be frankly communicated to members within a reasonable time frame.

;Who elects the officers (President, Secretary, Treasurer etc?)
:The board elects the officers. In doing so, they may choose to take advice from the membership, but the decision is theirs. The President must be from within the board itself, though Secretary, Treasurer, and any other officers the board wishes to appoint may be from outside the board (or outside the membership).

=== Election process ===

Board elections occur as follows:
# A member is nominated by the Board to oversee the election.
# Nominations for the open positions are taken from within the existing membership via email and/or via a forum thread. This lasts a minimum of 10 days.
# Confirmed nominees are placed on the ballot.
# A vote of the membership is then taken using a trusted internet voting service using a ranking system. (usually via the Condorcet Internet Voting Service, http://www.cs.cornell.edu/w8/~andru/civs ) and the candidates with the highest ranks take office. This lasts about two weeks.
#: ''In the event of a tie, it will be resolved with the existing board members discussing with the tied nominees. Tied nominees that do not go on the board may be nominated as officers of the Foundation, for example.''

=== Previous elections ===
* [[/Elections/2024|2024]]
* [[/Elections/2023|2023]]
* [[/Elections/2022|2022]]
* [[/Elections/2021|2021]]
* [[/Elections/2020|2020]]
* [[/Elections/2019|2019]]
* [[Archive:XBMC_Foundation/Elections/2018|2018]]
* [[Archive:XBMC_Foundation/Elections/2017|2017]]
* [[Archive:XBMC_Foundation/Elections/2016|2016]]
* [[Archive:XBMC_Foundation/Elections/2014|2014]]
* [[Archive:XBMC_Foundation/Elections/2013|2013]]
* [[Archive:XBMC_Foundation/Elections/2012|2012]]

== Foundation Bylaws and other important documents ==
* [[Media:ByLaws.pdf]]
* [[Media:Delaware Incorporation Notice.pdf]]
* [[Media:Delaware Notice Of Good Standing.pdf]]
* [[Media:KodiFoundationIncorporationNotice.pdf]]
* [[Media:Kodi_Foundation_exempt.jpg]]

== Trademarks ==
{{see|Official:Trademark Policy index}}

== Financial information ==

=== Financial status ===

* Form 990 2016 - http://www.guidestar.org/FinDocuments/2016/474/565/2016-474565769-0e36f6e3-9.pdf
* Income and expenses 2015 - https://drive.google.com/file/d/0BwsEEPRqIzELOVpUa0p4endrRWc/view?usp=sharing
* Income and expenses 2014 - https://drive.google.com/file/d/0BwsEEPRqIzELVW9rMkpPUWZRSHM/view?usp=sharing
* Income and expenses 2013 - https://docs.google.com/spreadsheet/ccc?key=0AtlJ3dnHcw46dHpmeXlIV0hGaC13Z3I3b25hZWhWRGc#gid=8

''note'': 2014 and 2015 expenses are US Foundation account only.

=== Account details ===

'''Unites States account'''

* Bank: Wells Fargo
* Beneficiary: Kodi Foundation

== Legal representation ==
The Kodi Foundation is legally represented by the [[w:Software Freedom Law Center|SFLC (Software Freedom Law Center)]].

In addition the Kodi Foundation is member of [[w:Open_Invention_Network|OIN (Open Invention Network)]] since 9 July 2010. OIN is a defensive patent pool and community of patent non-aggression which enables freedom of action in Linux.

== Contact ==
For contact information, please see http://kodi.tv/about/contact/

[[Category:Kodi_Foundation-Archived]]

Kodi Foundation/Elections/2024

2025-07-30T18:01:22Z

Yol: Created page with "{{mininav| Kodi Foundation | Elections }} ==Pre-election== yol was voting admin, as his seat was not up for re-election. ==Nomination notice== The following notice posted on the Team Kodi private forum, and linked to in an e-mail to all Foundation members, to give due notice about the election and to collect nominations. The Foundation bylaws state that at least ten days must be given for a notice about member decisions such as an elec..."

{{mininav| [[Kodi Foundation]] | [[Kodi Foundation/Elections|Elections]] }}

==Pre-election==
yol was voting admin, as his seat was not up for re-election.

==Nomination notice==
The following notice posted on the Team Kodi private forum, and linked to in an e-mail to all Foundation members, to give due notice about the election and to collect nominations. The Foundation bylaws state that at least ten days must be given for a notice about member decisions such as an election, which served as the nomination period.

:''Nominations for the XBMC Foundation Board Elections 2024", as written by yol''

:{| class="wikitable"
|-
|
It's time for the yearly Kodi Foundation board elections again!

This year board member seats up for election are: Keith and DarrenHill. Seats not up for election are: phunkyfish, Prof Yaffle and yol (me).

The rules are pretty simple:

Any team member can nominate, but the nominee must be a member of the Foundation*.
You're allowed to nominate multiple people if you wish.
The nominated member has the option to accept or decline their nomination.
Only foundation members will be able to vote. *
If a person has already been nominated, please don't nominate them again.

Please make sure to keep your nominations simple and clear. Eg:

Quote:
Nominate: <member> Motivation: I would like to nominate <member> for the Kodi Foundation Board because <motivation>

In case you're nominated, please reply with something like..

Quote:
Thank you. I accept my nomination. <motivation>

or

Quote:
No, thanks. I decline my nomination. <Optional motivation>

The second post in this thread will be updated with a list of members and the nomination status on a regular basis, so you don't have to crawl through all posts/pages to check.

The nomination period is 1 month starting today and will end on September 18th.
Actual voting will begin after that and will be closed a couple of weeks later (if a vote is required).
Once the voting is over, the results will be announced in this thread as well as through a team email.

The actual starting date for the new board seats will be in October or November, when we would like to have a joint online meeting with the old and new board members as a smooth hand-over and to welcome the new board members.

* If you'd like to vote in the election, you need to be accepted as a foundation member and affirm the by-laws of the foundation.
Details on applying to join the Foundation are at: Click here to join the foundation
A list of all foundation members can be found here: https://drive.google.com/open?id=1yy_gPb...Y0UJaJRPHE (Foundation member list - only accessible to Google accounts logged in using your Kodi address).
|}

The following text was later added: "EDIT September 17: The nomination period has been extended to October 18th."

==Voting==

;Final list of confirmed nominees:
* Keith
* neo1973

==Results==

As two nominations were accepted for two seats, no vote was held and all two nominees were accepted onto the board.

DevCon

2025-04-13T14:17:34Z

Yol:

{{mininav}}

The Kodi developers conference is where Team Kodi members gather to discuss and handle various Kodi related business. It is one of the few times where Team members meet up in real life.
{{-}}
<div class="nonumtoc">__TOC__</div>
{{-}}

== 2025 (Tirana) ==

[[File:2025 Tirana.webp|600px|thumb|right]]

'''Location:''' Tirana, Albania

'''Date:''' April 11-13

* https://kodi.tv/article/devcon-2025-tirana-part-i/
* https://kodi.tv/article/devcon-2025-tirana-part-ii/

{{-}}

== 2024 (Budapest) ==

[[File:2024 Budapest.webp|600px|thumb|right]]

'''Location:''' Budapest, Hungary

'''Date:''' March 22-24

* https://kodi.tv/article/devcon-2024-budapest-part-i/
* https://kodi.tv/article/devcon-2024-budapest-part-ii/
* https://kodi.tv/article/devcon-2024-budapest-part-iii/

{{-}}

== 2023 (Bergamo) ==

[[File:2023 Bergamo.webp|600px|thumb|right]]

'''Location:''' Costa Volpino near Bergamo, Italy

'''Date:''' March 31-April 02

* https://kodi.tv/article/devcon-2023-buongiorno-lombardia/

{{-}}

== 2022 (Barcelona) ==

[[File:2024 Barcelona.webp|600px|thumb|right]]

'''Location:''' Sitges near Barcelona, Spain

'''Date:''' April 01-03

* https://kodi.tv/article/devcon-2022-moltes-gr%C3%A0cies-catalunya/

{{-}}

== 2019 (Serbia) ==

[[File:2019 Belgrade.jpg|600px|thumb|right]]

'''Location:''' Belgrade, Serbia

'''Date:''' October 11-13

* https://kodi.tv/article/devcon-2019-belgrade-part-i/
* https://kodi.tv/article/devcon-2019-belgrade-part-ii/
* https://kodi.tv/article/devcon-2019-belgrade-part-iii/

{{-}}

== 2018 (Bulgaria) ==
[[File:Devcon 20180930 Sofia Bulgaria.jpg|600px|thumb|right]]

'''Location:''' Sofia, Bulgaria

'''Date:''' September 28-30

* https://kodi.tv/article/devcon-2018-sofia-part-i
* https://kodi.tv/article/devcon-2018-sofia-part-ii
* https://kodi.tv/article/devcon-2018-sofia-part-iii

{{-}}

== 2017 (Czech Republic) ==
[[File:DevCon2017IITeamPhoto.jpg|600px|right|thumb]]

'''Location:''' Prague, Czech Republic

'''Date:''' October 27-29

* https://kodi.tv/article/devcon-2017-part-ii-day-one
* https://kodi.tv/article/devcon-2017-part-ii-day-two
* https://kodi.tv/article/devcon-2017-part-ii-day-three

{{-}}

== 2017 (Portugal) ==
[[File:DevCon2017TeamPhoto.jpg|600px|right|thumb]]

'''Location:''' Porto, Portugal

'''Date:''' May 5th - 7th

* https://kodi.tv/article/devcon-2017-day-one
* https://kodi.tv/article/devcon-2017-day-two
* https://kodi.tv/article/devcon-2017-day-three
* https://kodi.tv/article/kodis-2017-developers-conference
* http://forum.kodi.tv/showthread.php?tid=311585

{{-}}

== 2016 (Hungary) ==
[[File:DevCon2016Teamfoto2.jpg|600px|right|thumb]]

'''Location:''' Budapest, Hungary

'''Date:''' October 10th - 12th

* https://kodi.tv/article/kodi-devcon-2016-live-blog

{{-}}

== 2015 (Czech Republic) ==
[[File:Devcon2015.jpg|600px|right|thumb|<section begin="2016 photo"/>Top: alwinus, jjd-uk, keith, razze, ksoo, zag<br/>Middle: ruuk, koying, montellese, mkortstiege, , phil65, martijn<br/>Bottom: natethomas, paxxi, garbear, ansii, wisler, negge, hitcher, bignoid, fkoch, kib<section end="2016 photo"/>]]
'''Location:''' Prague, Czech Republic

'''Date:''' October 7th - 9th

* https://kodi.tv/article/devcon-2015-liveblog

{{-}}

== 2014 (Portugal) ==
[[File:DevCon2014.jpg|500px|right|thumb]]

'''Location:''' Lisbon, Portugal

'''Date:''' October 10th - 12th

* https://kodi.tv/article/kodi-devcon-2014-live-blog/

{{-}}

== 2013 (Germany) ==
[[File:2013 DevCon.jpg|600px|right|thumb|<section begin="2013 photo"/>The team in Munich<section end="2012 photo"/>]]
'''Location:''' Munich, Germany

'''Date:''' October 11th - 13th

* https://kodi.tv/article/xbmc-devcon-2013/
* https://kodi.tv/article/xbmc-devcon-2013-liveblog/

{{-}}

== 2012 (Austria) ==
[[File:Devcon2012.JPG|right|600px|thumb|<section begin="2012 photo"/>From left to right: topfs2, da-anda, Martijn, fneufneu, sraue, benjee , Memphiz, Wiso, Montellese, chadoe, Davilla, jfcarrol, cptspiff, amet, vdrfan, olympia, anssi, alanwww1, jmarshall, TheUni, Clumsy, Freezy, natethomas<section end="2012 photo"/>]]
Vienna, sponsored by at-visions
'''Location:''' Vienna, Austria

'''Sponsored by:''' At-Visions

* https://kodi.tv/article/devcon-2012-user-meetup/
* http://www.at-visions.com/XBMC-conference-in-Vienna.html

Photos and videos:
* http://www.flickr.com/photos/23449328@N05/sets/72157631428716214/
* http://www.youtube.com/watch?v=jJBhe7arBlk

{{-}}

== 2010 (Austria) ==
[[File:2010 DevCon.png|right|frame|alt=Group photograph of DevCon 2010 attendees|<section begin="2010devcon"/>'''From left to right''' Amet (Zeljko), Andy (at-visions), freezy (Nico), clumsy (Thomas), topfs2 (Tobias), chadoe (Martin), jmarshall (Jonathan), ''BACK'':unknown ''FRONT'':elupus (Joakim), vdrfan (Matthias), prae5 (Paul), davilla (Scott), WiSo (Winfried), malloc (Sean), Malard (Martin), TheUni (Cory), Michael (at-visions), Olympia (Bence), Ronen (At-Visions' CEO), ''BACK'':lcapriotti (Luigi) ''FRONT'':spiff (Dr. Arne), Lucas (at-visions)<section end="2010devcon"/>]]
'''Location:''' [[w:Vienna|Vienna, Austria]]

'''Sponsored by:''' At-Visions

* [https://kodi.tv/article/devcon-2010/ Official Announcement]
* [https://kodi.tv/article/xbmc-devcon-2010-summary/ Event Summary]

{{-}}

== 2009 (Germany) ==
[[File:2009 DevCon.jpg|right|600px|thumb|From left to right: Erez, Pike, Yuvalt, WiSo, vulkanr, vdrfan, elupus, blittan, chadoe, MaestroDD]]
Berlin

{{-}}

== 2008 (Netherlands) ==
[[File:2008 DevCon.jpg|right|600px|thumb|]]
'''Location:''' Amsterdam, The Netherlands

'''Sponsored by:''' Boxee

* http://www.bunniestudios.com/blog/?p=251
* https://www.flickr.com/photos/27660056@N07/sets/72157605632155509/
{{-}}

[[Category:XBMC_Foundation]]

File:2025 Tirana.webp

2025-04-13T14:16:19Z

Yol:

2025 Tirana

File:2019 Belgrade.jpg

2025-04-13T14:14:02Z

Yol:

2019 Belgrade

DevCon

2025-04-13T14:10:49Z

Yol:

{{mininav}}

The Kodi developers conference is where Team Kodi members gather to discuss and handle various Kodi related business. It is one of the few times where Team members meet up in real life.
{{-}}
<div class="nonumtoc">__TOC__</div>
{{-}}

== 2025 (Tirana) ==

'''Location:''' Tirana, Albania

'''Date:''' April 11-13

* https://kodi.tv/article/devcon-2025-tirana-part-i/
* https://kodi.tv/article/devcon-2025-tirana-part-ii/

== 2024 (Budapest) ==

[[File:2024 Budapest.webp|600px|thumb|right]]

'''Location:''' Budapest, Hungary

'''Date:''' March 22-24

* https://kodi.tv/article/devcon-2024-budapest-part-i/
* https://kodi.tv/article/devcon-2024-budapest-part-ii/
* https://kodi.tv/article/devcon-2024-budapest-part-iii/

{{-}}

== 2023 (Bergamo) ==

[[File:2023 Bergamo.webp|600px|thumb|right]]

'''Location:''' Costa Volpino near Bergamo, Italy

'''Date:''' March 31-April 02

* https://kodi.tv/article/devcon-2023-buongiorno-lombardia/

{{-}}

== 2022 (Barcelona) ==

[[File:2024 Barcelona.webp|600px|thumb|right]]

'''Location:''' Sitges near Barcelona, Spain

'''Date:''' April 01-03

* https://kodi.tv/article/devcon-2022-moltes-gr%C3%A0cies-catalunya/

{{-}}

== 2019 (Serbia) ==
'''Location:''' Belgrade, Serbia

'''Date:''' October 11-13

* https://kodi.tv/article/devcon-2019-belgrade-part-i/
* https://kodi.tv/article/devcon-2019-belgrade-part-ii/
* https://kodi.tv/article/devcon-2019-belgrade-part-iii/

{{-}}

== 2018 (Bulgaria) ==
[[File:Devcon 20180930 Sofia Bulgaria.jpg|600px|thumb|right]]

'''Location:''' Sofia, Bulgaria

'''Date:''' September 28-30

* https://kodi.tv/article/devcon-2018-sofia-part-i
* https://kodi.tv/article/devcon-2018-sofia-part-ii
* https://kodi.tv/article/devcon-2018-sofia-part-iii

{{-}}

== 2017 (Czech Republic) ==
[[File:DevCon2017IITeamPhoto.jpg|600px|right|thumb]]

'''Location:''' Prague, Czech Republic

'''Date:''' October 27-29

* https://kodi.tv/article/devcon-2017-part-ii-day-one
* https://kodi.tv/article/devcon-2017-part-ii-day-two
* https://kodi.tv/article/devcon-2017-part-ii-day-three

{{-}}

== 2017 (Portugal) ==
[[File:DevCon2017TeamPhoto.jpg|600px|right|thumb]]

'''Location:''' Porto, Portugal

'''Date:''' May 5th - 7th

* https://kodi.tv/article/devcon-2017-day-one
* https://kodi.tv/article/devcon-2017-day-two
* https://kodi.tv/article/devcon-2017-day-three
* https://kodi.tv/article/kodis-2017-developers-conference
* http://forum.kodi.tv/showthread.php?tid=311585

{{-}}

== 2016 (Hungary) ==
[[File:DevCon2016Teamfoto2.jpg|600px|right|thumb]]

'''Location:''' Budapest, Hungary

'''Date:''' October 10th - 12th

* https://kodi.tv/article/kodi-devcon-2016-live-blog

{{-}}

== 2015 (Czech Republic) ==
[[File:Devcon2015.jpg|600px|right|thumb|<section begin="2016 photo"/>Top: alwinus, jjd-uk, keith, razze, ksoo, zag<br/>Middle: ruuk, koying, montellese, mkortstiege, , phil65, martijn<br/>Bottom: natethomas, paxxi, garbear, ansii, wisler, negge, hitcher, bignoid, fkoch, kib<section end="2016 photo"/>]]
'''Location:''' Prague, Czech Republic

'''Date:''' October 7th - 9th

* https://kodi.tv/article/devcon-2015-liveblog

{{-}}

== 2014 (Portugal) ==
[[File:DevCon2014.jpg|500px|right|thumb]]

'''Location:''' Lisbon, Portugal

'''Date:''' October 10th - 12th

* https://kodi.tv/article/kodi-devcon-2014-live-blog/

{{-}}

== 2013 (Germany) ==
[[File:2013 DevCon.jpg|600px|right|thumb|<section begin="2013 photo"/>The team in Munich<section end="2012 photo"/>]]
'''Location:''' Munich, Germany

'''Date:''' October 11th - 13th

* https://kodi.tv/article/xbmc-devcon-2013/
* https://kodi.tv/article/xbmc-devcon-2013-liveblog/

{{-}}

== 2012 (Austria) ==
[[File:Devcon2012.JPG|right|600px|thumb|<section begin="2012 photo"/>From left to right: topfs2, da-anda, Martijn, fneufneu, sraue, benjee , Memphiz, Wiso, Montellese, chadoe, Davilla, jfcarrol, cptspiff, amet, vdrfan, olympia, anssi, alanwww1, jmarshall, TheUni, Clumsy, Freezy, natethomas<section end="2012 photo"/>]]
Vienna, sponsored by at-visions
'''Location:''' Vienna, Austria

'''Sponsored by:''' At-Visions

* https://kodi.tv/article/devcon-2012-user-meetup/
* http://www.at-visions.com/XBMC-conference-in-Vienna.html

Photos and videos:
* http://www.flickr.com/photos/23449328@N05/sets/72157631428716214/
* http://www.youtube.com/watch?v=jJBhe7arBlk

{{-}}

== 2010 (Austria) ==
[[File:2010 DevCon.png|right|frame|alt=Group photograph of DevCon 2010 attendees|<section begin="2010devcon"/>'''From left to right''' Amet (Zeljko), Andy (at-visions), freezy (Nico), clumsy (Thomas), topfs2 (Tobias), chadoe (Martin), jmarshall (Jonathan), ''BACK'':unknown ''FRONT'':elupus (Joakim), vdrfan (Matthias), prae5 (Paul), davilla (Scott), WiSo (Winfried), malloc (Sean), Malard (Martin), TheUni (Cory), Michael (at-visions), Olympia (Bence), Ronen (At-Visions' CEO), ''BACK'':lcapriotti (Luigi) ''FRONT'':spiff (Dr. Arne), Lucas (at-visions)<section end="2010devcon"/>]]
'''Location:''' [[w:Vienna|Vienna, Austria]]

'''Sponsored by:''' At-Visions

* [https://kodi.tv/article/devcon-2010/ Official Announcement]
* [https://kodi.tv/article/xbmc-devcon-2010-summary/ Event Summary]

{{-}}

== 2009 (Germany) ==
[[File:2009 DevCon.jpg|right|600px|thumb|From left to right: Erez, Pike, Yuvalt, WiSo, vulkanr, vdrfan, elupus, blittan, chadoe, MaestroDD]]
Berlin

{{-}}

== 2008 (Netherlands) ==
[[File:2008 DevCon.jpg|right|600px|thumb|]]
'''Location:''' Amsterdam, The Netherlands

'''Sponsored by:''' Boxee

* http://www.bunniestudios.com/blog/?p=251
* https://www.flickr.com/photos/27660056@N07/sets/72157605632155509/
{{-}}

[[Category:XBMC_Foundation]]

File:2024 Budapest.webp

2025-04-13T14:09:46Z

Yol:

2024 Budapest

File:2023 Bergamo.webp

2025-04-13T14:07:40Z

Yol:

2023 Bergamo

File:2024 Barcelona.webp

2025-04-13T14:06:44Z

Yol:

2024 Barcelona

DevCon

2025-04-11T16:38:28Z

Yol:

{{mininav}}

The Kodi developers conference is where Team Kodi members gather to discuss and handle various Kodi related business. It is one of the few times where Team members meet up in real life.
{{-}}
<div class="nonumtoc">__TOC__</div>
{{-}}

== 2024 (Budapest) ==

'''Location:''' Budapest, Hungary

'''Date:''' March 22-24

* https://kodi.tv/article/devcon-2024-budapest-part-i/
* https://kodi.tv/article/devcon-2024-budapest-part-ii/
* https://kodi.tv/article/devcon-2024-budapest-part-iii/

{{-}}

== 2023 (Bergamo) ==

'''Location:''' Costa Volpino near Bergamo, Italy

'''Date:''' March 31-April 02

* https://kodi.tv/article/devcon-2023-buongiorno-lombardia/

{{-}}

== 2022 (Barcelona) ==

'''Location:''' Sitges near Barcelona, Spain

'''Date:''' April 01-03

* https://kodi.tv/article/devcon-2022-moltes-gr%C3%A0cies-catalunya/

{{-}}

== 2019 (Serbia) ==
'''Location:''' Belgrade, Serbia

'''Date:''' October 11-13

* https://kodi.tv/article/devcon-2019-belgrade-part-i/
* https://kodi.tv/article/devcon-2019-belgrade-part-ii/
* https://kodi.tv/article/devcon-2019-belgrade-part-iii/

{{-}}

== 2018 (Bulgaria) ==
[[File:Devcon 20180930 Sofia Bulgaria.jpg|600px|thumb|right]]

'''Location:''' Sofia, Bulgaria

'''Date:''' September 28-30

* https://kodi.tv/article/devcon-2018-sofia-part-i
* https://kodi.tv/article/devcon-2018-sofia-part-ii
* https://kodi.tv/article/devcon-2018-sofia-part-iii

{{-}}

== 2017 (Czech Republic) ==
[[File:DevCon2017IITeamPhoto.jpg|600px|right|thumb]]

'''Location:''' Prague, Czech Republic

'''Date:''' October 27-29

* https://kodi.tv/article/devcon-2017-part-ii-day-one
* https://kodi.tv/article/devcon-2017-part-ii-day-two
* https://kodi.tv/article/devcon-2017-part-ii-day-three

{{-}}

== 2017 (Portugal) ==
[[File:DevCon2017TeamPhoto.jpg|600px|right|thumb]]

'''Location:''' Porto, Portugal

'''Date:''' May 5th - 7th

* https://kodi.tv/article/devcon-2017-day-one
* https://kodi.tv/article/devcon-2017-day-two
* https://kodi.tv/article/devcon-2017-day-three
* https://kodi.tv/article/kodis-2017-developers-conference
* http://forum.kodi.tv/showthread.php?tid=311585

{{-}}

== 2016 (Hungary) ==
[[File:DevCon2016Teamfoto2.jpg|600px|right|thumb]]

'''Location:''' Budapest, Hungary

'''Date:''' October 10th - 12th

* https://kodi.tv/article/kodi-devcon-2016-live-blog

{{-}}

== 2015 (Czech Republic) ==
[[File:Devcon2015.jpg|600px|right|thumb|<section begin="2016 photo"/>Top: alwinus, jjd-uk, keith, razze, ksoo, zag<br/>Middle: ruuk, koying, montellese, mkortstiege, , phil65, martijn<br/>Bottom: natethomas, paxxi, garbear, ansii, wisler, negge, hitcher, bignoid, fkoch, kib<section end="2016 photo"/>]]
'''Location:''' Prague, Czech Republic

'''Date:''' October 7th - 9th

* https://kodi.tv/article/devcon-2015-liveblog

{{-}}

== 2014 (Portugal) ==
[[File:DevCon2014.jpg|500px|right|thumb]]

'''Location:''' Lisbon, Portugal

'''Date:''' October 10th - 12th

* https://kodi.tv/article/kodi-devcon-2014-live-blog/

{{-}}

== 2013 (Germany) ==
[[File:2013 DevCon.jpg|600px|right|thumb|<section begin="2013 photo"/>The team in Munich<section end="2012 photo"/>]]
'''Location:''' Munich, Germany

'''Date:''' October 11th - 13th

* https://kodi.tv/article/xbmc-devcon-2013/
* https://kodi.tv/article/xbmc-devcon-2013-liveblog/

{{-}}

== 2012 (Austria) ==
[[File:Devcon2012.JPG|right|600px|thumb|<section begin="2012 photo"/>From left to right: topfs2, da-anda, Martijn, fneufneu, sraue, benjee , Memphiz, Wiso, Montellese, chadoe, Davilla, jfcarrol, cptspiff, amet, vdrfan, olympia, anssi, alanwww1, jmarshall, TheUni, Clumsy, Freezy, natethomas<section end="2012 photo"/>]]
Vienna, sponsored by at-visions
'''Location:''' Vienna, Austria

'''Sponsored by:''' At-Visions

* https://kodi.tv/article/devcon-2012-user-meetup/
* http://www.at-visions.com/XBMC-conference-in-Vienna.html

Photos and videos:
* http://www.flickr.com/photos/23449328@N05/sets/72157631428716214/
* http://www.youtube.com/watch?v=jJBhe7arBlk

{{-}}

== 2010 (Austria) ==
[[File:2010 DevCon.png|right|frame|alt=Group photograph of DevCon 2010 attendees|<section begin="2010devcon"/>'''From left to right''' Amet (Zeljko), Andy (at-visions), freezy (Nico), clumsy (Thomas), topfs2 (Tobias), chadoe (Martin), jmarshall (Jonathan), ''BACK'':unknown ''FRONT'':elupus (Joakim), vdrfan (Matthias), prae5 (Paul), davilla (Scott), WiSo (Winfried), malloc (Sean), Malard (Martin), TheUni (Cory), Michael (at-visions), Olympia (Bence), Ronen (At-Visions' CEO), ''BACK'':lcapriotti (Luigi) ''FRONT'':spiff (Dr. Arne), Lucas (at-visions)<section end="2010devcon"/>]]
'''Location:''' [[w:Vienna|Vienna, Austria]]

'''Sponsored by:''' At-Visions

* [https://kodi.tv/article/devcon-2010/ Official Announcement]
* [https://kodi.tv/article/xbmc-devcon-2010-summary/ Event Summary]

{{-}}

== 2009 (Germany) ==
[[File:2009 DevCon.jpg|right|600px|thumb|From left to right: Erez, Pike, Yuvalt, WiSo, vulkanr, vdrfan, elupus, blittan, chadoe, MaestroDD]]
Berlin

{{-}}

== 2008 (Netherlands) ==
[[File:2008 DevCon.jpg|right|600px|thumb|]]
'''Location:''' Amsterdam, The Netherlands

'''Sponsored by:''' Boxee

* http://www.bunniestudios.com/blog/?p=251
* https://www.flickr.com/photos/27660056@N07/sets/72157605632155509/
{{-}}

[[Category:XBMC_Foundation]]

PulseAudio

2025-01-04T19:47:45Z

Yol: switch from deprecated KODI_AE_SINK to --audio-backend

{{mininav|[[Audio]]}}
<section begin="intro" />This page goes into detail on using PulseAudio on Linux systems. PulseAudio is used when Kodi is installed in a desktop-environment rather than a dedicated/direct boot setup. PulseAudio allows normal video & audio playback in XBMC while at the same time allowing the user to get audio in their browser or other applications. It also allows Kodi playback of video or audio to be paused in order to run a game, Skype or similar. Kodi is set to only use PulseAudio if you have installed it and running.<section end="intro" />

== History ==
In the past users have experienced problems with audio not working within Kodi, because they were running a full-blown Ubuntu desktop environment with PulseAudio installed. This happened because PulseAudio blocked the device Kodi required, and audio playback only worked reliably when using the virtual Pulse device.

Our workaround for those users has been to uninstall PulseAudio which completely broke desktop audio.

For XBMC 13 'Gotham' and later (named Kodi since 14 'Helix') we wanted this situation to change, so thanks to the new '''PulseAudio Sink''' users now can run a normal Ubuntu desktop.

== PulseAudio Output Configuration ==
PulseAudio will be automatically detected and selected in Kodi when it is running.

PulseAudio can be run in one of two modes these are:

<big>'''Passthrough Mode'''</big>
Used if you want to passthrough (bitstream) AC3, DTS, and EAC3 to an AVR or other device. In order to allow passthrough to work with PulseAudio then it '''MUST''' be set to use a 2.0 channel configuration, despite the 2.0 setting this will still allow 5.1 audio from AC3, DTS, and EAC3.

{{Note| PulseAudio does not currently allow TrueHD or DTS-MA passthrough, this is a PulseAudio limitation and not a limitation of the Kodi implementation, in order to get 7.1 audio Multichannel Mode must be used}}

<big>'''Multichannel Mode'''</big>

Used if you want Multichannel PCM out, in this mode you can configure PulseAudio for up to 7.1 channels. In this mode Kodi must decode all audio formats to PCM for passing onto the PulseAudio, this can have the advantage of improve audio/video sync. In the case of video with TrueHD/DTS-HD 7.1 audio this must be decoded by Kodi to Multichannel PCM by disabling passthrough, then Pulseaudio can handle the 7.1 channels of audio.

{{Note| Audio decoded to PCM and sent through PulseAudio the audio will not likely be "bit perfect". As Pulseaudio will always open the number of channels you have configured. You can stop it doing upmixing (see Known issues), but it will still open all configured channels which makes Dolby Pro Logic II of your AVR not usable.}}

<br />

== Setting up pavucontrol ==

=== Passthrough Mode ===
{{bluev|'''IMPORTANT:'''|Passthrough is always an exclusive mode. If you have another application hogging the device, e.g. Chrome or Skype, passthrough won't work. Even applications that simply monitor the device, such as SoundWireServer, will prevent passthrough from working.}}
{{greenv|'''REMEMBER:'''| To use passthrough you need to be using '''2.0''' channel configuration via '''pavucontrol''' (e.g. Digital Stereo (HDMI)}}

In order to activate passthrough codecs, setup pavucontrol as following:

<gallery widths=500px heights=313px>
File:Passthrough2.png|<big>'''Step 1:'''</big> ''pavucontrol'' '''Output Settings.'''
File:Passthrough1.png|<big>'''Step 2:'''</big> ''pavucontrol'' '''Configuration.'''
</gallery>

If you like to do this from the command line, first, first identify the correct sound card ID:
'''pacmd list-cards'''

Look at the output to find the id of the card and the name/format of the profile you want to use (in this case, card ID is '''0''' and profile is '''output:hdmi-stereo''')
Once you've identified this information, set your output profile to the one for hdmi-stereo:
'''pacmd set-card-profile 0 output:hdmi-stereo'''

Then, obtain the sink ID you want to set formats on by inspecting output of:
'''pactl list sinks'''

Then set the sink format for the sink you want, as below (in this case '''0'''):
'''pactl set-sink-formats 0 "pcm; ac3-iec61937; dts-iec61937; eac3-iec61937"'''

You can leave out the codecs your AVR does not support, always keep pcm.

{{bluev|'''IMPORTANT:'''| If you have for example 5.1 flacs or other multichannel files, you can play them as AC3 streams, check the AC3 Transcoding setting.}}

{{redv|'''IMPORTANT:'''| Enabling ''' Sync Playback to Display ''' will disable passthrough silently, as it makes zero sense to sync with a display clock while one cannot alter audio.}}

=== Multichannel Mode ===
{{greenv|'''REMEMBER:'''| When configuring pulse to use '''Multichannel configuration''' passthrough will be disabled}}
To configure instead Multi channel mode, do the following settings.

<gallery widths=500px heights=313px>
File:Lpcm2.png|<big>'''Step 1:'''</big> ''To alternatively configure Multi channel, check this:''.
File:Lpcm1.png|<big>'''Step 2:'''</big> The ''Add-on manager'', displaying four/five options (explained below).
</gallery>

=== Example setup in Kodi ===
{{orangev|'''GOOD TO KNOW:'''| Limit sample rate can be set to Fixed - between 48kHz ~ 192kHz or as Optimized and even Best match.}}

<gallery widths=500px heights=313px>
File:Xbmclpcm.png |<big>'''Step 1:'''</big> ''to be edited'' '''Output Settings.'''
File:Xbmcpaa1.png |<big>'''Step 2:'''</big> ''to be edited'' '''Configuration.'''
</gallery>

<gallery widths=500px heights=313px>
File:Xbmcpass2.png |<big>'''Step 1:'''</big> ''to be edited'' '''Output Settings.'''
File:Xbmcpass1.png |<big>'''Step 2:'''</big> ''to be edited'' '''Configuration.'''
</gallery>
{{-}}

=== Setup Guide ===
{{orangev|DEVICE ENUMERATION:| Kodi Enumerates Pulseaudio devices as SPDIF when you have '''Passthrough''' set. Otherwise its '''PCM Device'''. If '''Passthrough''' was not configured with pavucontrol - no '''Passthrough''' setting within Kodi will be available.}}
{{bluev|GOOD TO KNOW:|SPDIF has 2 pcm channels but can do virtual 5.1 formats like dts, ac3, eac3.}}
{{greenv|'''NOTICE'''|The following is meant to act as a guide to get you started, thus you may want to adjust things to suit your own particular set of equipment.}}
{| class="prettytable" style="text-align: center; color: black;"
!
! PC Speakers<br />2.0
! PC Speakers<br />5.1
! TV SPDIF<br />2.0
! TV SPDIF<br />AC3 ('''1''')
! AVR SPDIF<br />AC3/DTS ('''2''')
! AVR HDMI<br />PCM ('''3''')
! AVR HDMI<br />No HD Audio ('''4''')
! AVR HDMI<br />Decode HD Audio ('''5''')
|-
! colspan="9"|'''PulseAudio Mode'''
|-
|
|Multichannel
|Multichannel
|Multichannel
|Passthrough
|Passthrough
|Multichannel
|Passthrough
|Multichannel
|-
! colspan="9"|'''Pavucontrol - Output Devices'''
|-
|align="left"|'''Port'''
|Speakers
|Speakers
|Digital Output (S/PDIF)
|Digital Output (S/PDIF)
|Digital Output (S/PDIF)
|HDMI/Displayport
|HDMI/Displayport
|HDMI/Displayport
|-
|align="left"|'''AC3'''
|N/A
|N/A
|Disabled
|Enabled
|Enabled
|Disabled
|Enabled
|Disabled
|-
|align="left"|'''EAC3'''
|N/A
|N/A
|Disabled
|Disabled
|Disabled
|Disabled
|Enabled
|Disabled
|-
|align="left"|'''DTS'''
|N/A
|N/A
|Disabled
|Disabled
|Enabled
|Disabled
|Enabled
|Disabled
|-
! colspan="9"|'''Pavucontrol - Configuration'''
|-
|align="left"|'''Profile'''
|Analog Stereo Output
|Analog Surround 5.1 Output
|Digital Stereo <br />(IEC958) Output
|Digital Stereo <br />(IEC958) Output
|Digital Stereo <br />(IEC958) Output
|Digital Surround 5.1 <br />(HDMI) Output
|Digital Stereo <br />(HDMI) Output
|Digital Surround 7.1 <br />(HDMI) Output
|-
!Colspan="9"|Kodi Settings
|-
|align="left"|'''Audio Output Device'''
|Speakers
|Speakers
|SPDIF
|SPDIF
|SPDIF
|HDMI
|HDMI
|HDMI
|-
|align="left"|'''Number of channels'''
|2.0
|5.1
|N/A
|N/A
|N/A
|5.1
|2.0
|7.1
|-
|align="left"|'''Enabled passthrough'''
|Disabled
|Disabled
|Disabled
|Enabled
|Enabled
|Disabled
|Enabled
|Disabled
|-
|align="left"|'''Passthrough output device'''
|N/A
|N/A
|N/A
|SPDIF
|SPDIF
|N/A
|HDMI
|N/A
|-
|align="left"|'''Dolby Digital (AC3) capable receiver'''
|N/A
|N/A
|N/A
|Enabled
|Enabled
|Disabled
|Enabled
|Disabled
|-
|align="left"|'''Enabled Dolby Digital transcoding'''
|N/A
|N/A
|N/A
|Enabled
|Enabled
|Disabled
|Enabled
|Disabled
|-
|align="left"|'''DTS capable receiver'''
|N/A
|N/A
|N/A
|Disabled
|Enabled
|Disabled
|Enabled
|Disabled
|-
|align="left"|'''TrueHD capable receiver'''
|N/A
|N/A
|N/A
|Disabled
|Disabled
|Disabled
|Disabled
|Disabled
|-
|align="left"|'''DTS-HD capable receiver'''
|N/A
|N/A
|N/A
|Disabled
|Disabled
|Disabled
|Disabled
|Dsiabled
|}

'''(1)''' Where TV can decode 5.1 AC3.

'''(2)''' Where AVR only has SPDIF which will support 5.1 AC3 & DTS.

'''(3)''' Where AVR can do 5.1 PCM.

'''(4)''' Where AVR has HDMI inputs but can't decode TrueHD or DTS-HD but does support 5.1 Ac3 or DTS.

'''(5)''' Where AVR has full decode capabilities including 7.1 PCM.

{{orangev|'''IMPORTANT:'''| You can only have '''AC3''', '''DTS''', '''EAC3''' passthrough '''if your Receiver supports it'''. Most '''TV's''' only support '''AC3'''. If you have a '''HDMI''' connection to your TV and '''from this TV''' a '''SPDIF/Optical''' connection to an '''AVR''', passthrough might not work at all.}}

== Combined Output aka dual audio==
If you want to output to all your attached devices in parallel, e.g. HDMI out, analog out and USB sound card, it is enough to do as below:

'''Step 1:''' Edit <code>/etc/pulse/default.pa</code>

<pre>load-module module-combine-sink sink_name=combined</pre>
'''Step 2: '''Restart pulseaudio.
<pre>killall pulseaudio</pre>

Kodi will then pickup the device, it is named '''combined'''.

{{orangev|'''Downside:'''| The dual audio sink will only output decoded audio, you cannot use it to have one slave doing AC3/DTS and the other PCM. If you use the combined sink for normal music you will realize that direct passthrough output for your movies won't be working anymore, too. This is a pulseaudio bug, cause the combine sink is not deconstructed fast enough internally while the passthrough opening is always exclusive. It will work however if your passthrough device is not part of the device combination. }}

== Audiophile Pulse User ==
Pulseaudio resamples everything that does not match the underlaying sink, so if you are an audiophile user, you perhaps want to hear your 96 / 192 khz and 24 bit recordings as exact as possible. Therefore you need to tell pulseaudio to use a better resampler in general and second avoid resampling. Starting with version 11 of pulseaudio, it can reopen sinks with their native samplerate. Furthermore you need to take care, that your sink has a wide enough output format. To properly resample samperates that are not available with your sound card, e.g. 176000 or other exotic rates, we set pulseaudio to a default of 44100 khz, which is the default for every standard mp3. As alternate sample-rate we suggest 48000. That means that all non available samplerates are resampled with an exact integer division of src_rate / dst_rate.

To do this configuration systemwide (96 khz in that example), change /etc/pulse/daemon.conf to include (please replace already existing lines and also remove the commenting):

<pre>
default-sample-format = s24le
default-sample-rate = 44100
alternate-sample-rate = 48000
;new with pulseaudio 11
avoid-resampling = true
resample-method = speex-float-5
</pre>

Some remark: This will actively make '''passthrough non working''', as we need s16le format for adding ac3 / dts / etc. to the sink.

The last setting will increase the resample quality from pulse and therefore the CPU load quite a lot. Again: Resampling is only done, when the sink output does not match the data you throw onto it. But as most normal mp3s are in 44.1 khz, you need to take great care when upsampling them. The overwriting of the resample-method is for this use case.

{{orangev|'''Alternatively:'''| If you don't want any resampling outside Kodi, e.g. no resampling done extra by pulse, you need to configure the sink as told above and set Audio Engine to '''Fixed''' with the number of channels you configured pulseaudio via pavucontrol and samplerate of '''96 khz''' with resample quality high. In that combination Kodi will take care that files are resampled (e.g. 44.1 khz or 48 khz media) in the best possible quality. Already 96 khz files are not touched at all. }}

== FAQ ==

{| width="100%"
{{FAQ|1=When_would_I_want_Pulseaudio
| BGcolor=whitesmoke
| Question=When would I want PulseAudio?
| Answer=
You should use '''PulseAudio''' when:

* You use your Kodi computer mainly as your Desktop when you don't run XBMC.
* You want other applications audio like Skype, youtube, browser mail notification in parallel with Kodi.
* You use Kodi in windowed mode as Desktop player
* You use Pulseaudio as a network sink to stream Audio to other devices in your living room.
* Passthrough is nice to have for you, but to be honest - you don't really need it.
* Whenever you plugin your Bluetooth headset, Kodi audio will continue over this new device (when Default 'PULSE' device is chosen)
}}

{{FAQ|1=When_would_I_want_ALSA
| BGcolor=
| Question=When would I want ALSA?
| Answer=
You should use '''ALSA''' when:

* You use Kodi as your standalone media center.
* You are highly interested in bitperfect exclusive audio output.
* DTS-HD, TrueHD is something you use daily and is of high importance.
* You don't need other applications that would access audio in parallel.
}}

{{FAQ|1=Why_cant_I_have_both?
| BGcolor=whitesmoke
| Question=Why can't I have both?
| Answer=
* '''PulseAudio''' might hog your Audio device and you cannot open the '''ALSA''' device exclusively, therefore we decided for one or the other.
* Whenever '''PulseAudio''' is running your '''ALSA''' device that Kodi chooses, might be busy or even might vanish while you are using Kodi, when system sounds are playing and pulseaudio is trying to access the device again. Out of this reason we also won't implement a selection box to decide between '''ALSA''' and '''PULSE''', because it will actively harm users. Advanced Users can go with the workaround listed beneath.
}}

{{FAQ|1=Forcing_alsa
| BGcolor=
| Question=Can I force ALSA even with PulseAudio installed?
| Answer=
{{note|Doing so may cause problems!}}

Yes, you can - start Kodi from terminal with:
<pre>pasuspender -- kodi --audio-backend=alsa</pre>

'''pasuspender''' is a tool that can be used to tell a local PulseAudio sound server to temporarily suspend access to the audio devices, to allow other applications access them directly. pasuspender will suspend access to the audio devices, fork a child process, and when the child process terminates, resume access again.

You can also put the previous command in a custom .desktop-file.

Be warned as this will interfere with your Desktop sounds!
}}
|}
=== Known issues ===
When your audio is much too fast or crackles a lot or passthrough only produces noise, you might have a broken driver in use. If this is the case, try to add ''tsched=0'' to the udev loading section in /etc/pulse/default.pa to read like:

''load-module module-udev-detect tsched=0''

Audio devices are disappearing with pulseaudio 8.0 (Ubuntu 16.04, even later version are affected) especially while running kodi and while using ''Adjust Refreshrate to match video''. This is an issue with the module-switch-on-port-available module and will be fixed with pulseaudio 9.0, the fix sadly won't probably make it into Ubuntu 16.04. As a workaround please disable that feature by editing /etc/pulse/default.pa and commenting or removing ''load-module module-switch-on-port-available'' and reboot the system.

''' Kodi v16 '''

When Pulseaudio is configured to be multi-channel output, e.g. 5.1 profile from within pavucontrol, 2.0 streams are automatically upmixed, no matter what setting you have chosen in Kodi. This is default pulseaudio server behaviour. You can workaround that by disabling ''enable-remixing'' in /etc/pulse/daemon.conf

''enable-remixing = no''

Beware: This will also forbid PA to remix e.g. FL,FR, LFE, FC, BL, BR into FL, FR, LFE, FC, SL, SR - which means you might loose your rears if your speaker layout is non standard.

''' Kodi v17 '''

Starting with the upcoming kodi v17 Krypton the above behaviour is taken care within kodi. You don't have to disable remixing in pulseaudio anymore. That means content is output without further remixing by pulseaudio server if a sane mapping is possible. Basically that means if the audio is FL, FR, FC, LFE, SL, SR and your speaker-mapping is FL, FR, FC, LFE, BL, BR we will resolve that and output 6 channels accordingly. Whenever we cannot map all input channels to the output we ask pulseaudio to do the mixing for us.

''' Volume issues '''

Issue: Changing kodi's volume will change overall system volume, especially on song change this is an irritating behaviour. The effect you hear is not done by kodi, but by a systemwide pulseaudio (mis)configuration. Some distributions sadly still ship pulseaudio with '''flat-volumes = yes''' as the default, which produces this behaviour. In fact it will cause the hardware volume (or master volume) to go up and down for every pulseaudio stream that changes its own volume. As this effect is unexpected behaviour for users, distributions started to ship pulseaudio with '''flat-volumes = no''' by default (as time of writing this is Ubuntu, Arch-Linux and others). In order to change that setting, depending on your distribution edit ''/etc/pulse/daemon.conf'' and set '''flat-volumes = no'''. After a PA server restart, the volume handling is more intuitive. If you are at it, please inform your distribution about those issues, so that they can ship a more user-friendly default with next release. At the time of writing, affected distributions: Debian.

[[Category:Audio]]

Mirrors

2024-12-16T17:15:07Z

Yol:

{{mininav}}

This page contains information about our mirrors network setup.

== Download mirrors ==

To provide downloads we use a network of mirrors across the globe to provide the best possible location to download from. For actually distributing the downloads and making sure you will download from the best server available we have been using Mirrorbits, which has been operating since August 2015 and so far hasn't failed us yet. This is a great piece of software that constantly checks the status of the mirrors and dishes out files based on certain criteria, in an effort to ensure that downloads work as quickly and reliably as possible. Besides these builds it also hosts all the add-on which you can find in our official kodi.tv repository.

== Information ==

The actual mirror list is generated automatically and can be found by appending <code>?mirrorlist</code> to the URL of any mirrored file on mirrors.kodi.tv.
Example: http://mirrors.kodi.tv/demo-files/BBB/bbb_sunflower_2160p_60fps_normal.mp4?mirrorlist

So we would like to thank all these providers for helping us out on distributing Kodi throughout the world. If you are interested in being added to this list feel free to contact us. '''Do note that we will only accept offers from large institutions or companies to keep possible problems at a minimum.'''

Our main mirror address is: http://mirrors.kodi.tv

== rsync setup ==

We have two main rsync mirrors which are used by main Tier1 mirror hosts per continent.
All other hosts should use those hosts according to their location.

=== main ===

primary Tier1 USA server:
* Name: gatech.edu
* address: rsync://rsync.gtlib.gatech.edu/xbmc/
* Uses: rsync://rsync.kodi.tv/main/
** sync on half past the hour XX:30
* Notes:
** all other USA mirrors should sync from this host
** mirrors should sync at XX:00

=== euro ===

primary Tier1 Europe server:

'''The Tier1 Europe server has changed from Heanet (which closed down their FTP service) to RWTH Aaachen on 2024-12-16. Please only use RWTH Aachen from now on.
'''

* Name: RWTH Aachen
* address: rsync://ftp.halifax.rwth-aachen.de/xbmc/
* Uses: rsync://rsync.kodi.tv/euro/
** push sync
* Notes:
** all other non-USA mirrors pull from them
** mirrors should sync at XX:00

== Requirements ==
* Space needed: ~100GB
* Mirrors pull at various times, the mirrorbits database contains notes about these times.
* Every couple of hours. Max is every 24h.
* If mirrors ever move to a new server, the dns entry for rsync.xbmc.org or rsync.kodi.tv can be changed and there should theoretically be no interruption. In reality, it makes sense to be sure that no one is pulling by IP or has white-listed the current IP for our constant mirror status checks.
* hosts need to provide this information to have proper setup
** http:// location (mandatory)
** ftp:// location (currently not used at all)
** rsync:// access to the mirrors for scanning available files(mandatory)
** Network bandwidth (gives indication of probability factor for traffic redirecting)
** Host webpage
** Host description
** Redirect options: AS network only / Continent only/ Country only / Global
** Admin name (will not be made public)
** Admin e-mail (will not be made public)
* rsync server is split up in two sections for providing data
** Please choose one of the TIER server rsync locations

Extra information
* rsync data could range to ~400Mb a day (amount may vary up or down)
* We have no hard data on amount of data that we redirect. We try to expand our network to reduce the amount for each mirror. We can always reduce the redirection criteria to reduce traffic to your mirror. Please contact us if needed.

[[Category:XBMC_Foundation]]

Mirrors

2024-12-16T17:05:41Z

Yol:

{{mininav}}

This page contains information about our mirrors network setup.

== Download mirrors ==

To provide downloads we use a network of mirrors across the globe to provide the best possible location to download from. For actually distributing the downloads and making sure you will download from the best server available we have been using Mirrorbits, which has been operating since August 2015 and so far hasn't failed us yet. This is a great piece of software that constantly checks the status of the mirrors and dishes out files based on certain criteria, in an effort to ensure that downloads work as quickly and reliably as possible. Besides these builds it also hosts all the add-on which you can find in our official kodi.tv repository.

== Information ==

The actual mirror list is generated automatically and can be found by appending <code>?mirrorlist</code> to the URL of any mirrored file on mirrors.kodi.tv.
Example: http://mirrors.kodi.tv/demo-files/BBB/bbb_sunflower_2160p_60fps_normal.mp4?mirrorlist

So we would like to thank all these providers for helping us out on distributing Kodi throughout the world. If you are interested in being added to this list feel free to contact us. '''Do note that we will only accept offers from large institutions or companies to keep possible problems at a minimum.'''

Our main mirror address is: http://mirrors.kodi.tv

== rsync setup ==

We have two main rsync mirrors which are used by main Tier1 mirror hosts per continent.
All other hosts should use those hosts according to their location.

=== main ===

primary Tier1 USA server:
* Name: gatech.edu
* address: rsync://rsync.gtlib.gatech.edu/xbmc/
* Uses: rsync://rsync.kodi.tv/main/
** sync on half past the hour XX:30
* Notes:
** all other USA mirrors should sync from this host
** mirrors should sync at XX:00

=== euro ===

primary Tier1 Europe server:

'''The Tier1 Europe server has changed from Heanet (which closed down their FTP service) to RWTH Aaachen on 2024-12-16. Please only use RWTH Aachen from now on.
'''

* Name: RWTH Aachen
* address: rsync://ftp.halifax.rwth-aachen.de/xbmc/
* Uses: rsync://rsync.kodi.tv/euro/
** sync on the hour XX:00
* Notes:
** all other non-USA mirrors pull from them
** mirrors should sync at XX:00

== Requirements ==
* Space needed: ~100GB
* Mirrors pull at various times, the mirrorbits database contains notes about these times.
* Every couple of hours. Max is every 24h.
* If mirrors ever move to a new server, the dns entry for rsync.xbmc.org or rsync.kodi.tv can be changed and there should theoretically be no interruption. In reality, it makes sense to be sure that no one is pulling by IP or has white-listed the current IP for our constant mirror status checks.
* hosts need to provide this information to have proper setup
** http:// location (mandatory)
** ftp:// location (currently not used at all)
** rsync:// access to the mirrors for scanning available files(mandatory)
** Network bandwidth (gives indication of probability factor for traffic redirecting)
** Host webpage
** Host description
** Redirect options: AS network only / Continent only/ Country only / Global
** Admin name (will not be made public)
** Admin e-mail (will not be made public)
* rsync server is split up in two sections for providing data
** Please choose one of the TIER server rsync locations

Extra information
* rsync data could range to ~400Mb a day (amount may vary up or down)
* We have no hard data on amount of data that we redirect. We try to expand our network to reduce the amount for each mirror. We can always reduce the redirection criteria to reduce traffic to your mirror. Please contact us if needed.

[[Category:XBMC_Foundation]]

Mirrors

2024-12-15T08:45:32Z

Yol:

{{mininav}}

This page contains information about our mirrors network setup.

== Download mirrors ==

To provide downloads we use a network of mirrors across the globe to provide the best possible location to download from. For actually distributing the downloads and making sure you will download from the best server available we have been using Mirrorbits, which has been operating since August 2015 and so far hasn't failed us yet. This is a great piece of software that constantly checks the status of the mirrors and dishes out files based on certain criteria, in an effort to ensure that downloads work as quickly and reliably as possible. Besides these builds it also hosts all the add-on which you can find in our official kodi.tv repository.

== Information ==

The actual mirror list is generated automatically and can be found by appending <code>?mirrorlist</code> to the URL of any mirrored file on mirrors.kodi.tv.
Example: http://mirrors.kodi.tv/demo-files/BBB/bbb_sunflower_2160p_60fps_normal.mp4?mirrorlist

So we would like to thank all these providers for helping us out on distributing Kodi throughout the world. If you are interested in being added to this list feel free to contact us. '''Do note that we will only accept offers from large institutions or companies to keep possible problems at a minimum.'''

Our main mirror address is: http://mirrors.kodi.tv

== rsync setup ==

We have two main rsync mirrors which are used by main Tier1 mirror hosts per continent.
All other hosts should use those hosts according to their location.

=== main ===

primary Tier1 USA server:
* Name: gatech.edu
* address: rsync://rsync.gtlib.gatech.edu/xbmc/
* Uses: rsync://rsync.kodi.tv/main/
** sync on half past the hour XX:30
* Notes:
** all other USA mirrors should sync from this host
** mirrors should sync at XX:00

=== euro ===

primary Tier1 Europe server:

'''We are currently looking for a new Tier1 server after heanet has closed down. We will change this page and inform mirror administrators once we have something ready.
'''

* Name: heanet.ie
* address: rsync://ftp.heanet.ie/mirrors/xbmc/
* Uses: rsync://rsync.kodi.tv/euro/
** sync on the hour XX:00
* Notes:
** all other non-USA mirrors pull from them
** mirrors should sync at XX:00

== Requirements ==
* Space needed: ~100GB
* Mirrors pull at various times, the mirrorbits database contains notes about these times.
* Every couple of hours. Max is every 24h.
* If mirrors ever move to a new server, the dns entry for rsync.xbmc.org or rsync.kodi.tv can be changed and there should theoretically be no interruption. In reality, it makes sense to be sure that no one is pulling by IP or has white-listed the current IP for our constant mirror status checks.
* hosts need to provide this information to have proper setup
** http:// location (mandatory)
** ftp:// location (currently not used at all)
** rsync:// access to the mirrors for scanning available files(mandatory)
** Network bandwidth (gives indication of probability factor for traffic redirecting)
** Host webpage
** Host description
** Redirect options: AS network only / Continent only/ Country only / Global
** Admin name (will not be made public)
** Admin e-mail (will not be made public)
* rsync server is split up in two sections for providing data
** Please choose one of the TIER server rsync locations

Extra information
* rsync data could range to ~400Mb a day (amount may vary up or down)
* We have no hard data on amount of data that we redirect. We try to expand our network to reduce the amount for each mirror. We can always reduce the redirection criteria to reduce traffic to your mirror. Please contact us if needed.

[[Category:XBMC_Foundation]]

RSS ticker

2024-03-18T15:18:47Z

Yol: Remove defunct feeds

{{mininav|[[General topics]]|[[Basic controls]]}}
<section begin="intro" />Kodi can display an [[w:RSS|RSS]] feed on the home screen of the default skin/interface, as well as any other skin that supports RSS feeds. By default, the RSS news feed is taken from https://kodi.tv, but the feed can be changed to almost any RSS feed.<section end="intro" />

{{Note|Don't confuse the [[RSS ticker]] with '''[[RSS media source]]''', which allows access to video and/or audio RSS streams.}}

= RSS ticker settings =
The RSS ticker can be toggled on or off by going to {{highlight|bordered=yes|'''[[Settings/Interface/Skin#Show_RSS_news_feeds|Settings -> Interface -> Skin -> Show RSS news feeds]]''' }}

Below this setting one can also change the RSS news feed address. This will be done via the RSS Editor add-on, which you will prompted to download before the first usage.

= Kodi RSS Feeds =
The following addresses are the default RSS Feeds for Kodi:

https://kodi.tv/feed

= Technical documentation for skinners =
{{main|Skinning}}
<section begin="main content" />

== RSS control ==
The rss control is used for displaying scrolling RSS feeds from the internet in Kodi. You can choose the font, size, colour, location and the RSS feed to be displayed.

;Example
<syntaxhighlight lang=xml enclose="div">
<control type="rss" id="123">
<description>My First RSS control</description>
<left>80</left>
<top>60</top>
<width>500</width>
<visible>true</visible>
<font>font14</font>
<textcolor>FFB2D4F5</textcolor>
<urlset>1</urlset>
<headlinecolor>FFFFFFFF</headlinecolor>
<titlecolor>FF655656</titlecolor>
</control>
</syntaxhighlight>

== Available tags and attributes ==
In addition to the [[Default_control_tags|default control tags]], the following tags are available. Note that each tag is '''lower case only.''' This is important, as xml tags are case-sensitive.
{| class="prettytable"
! Tag !! Description
|-
| '''urlset'''
| This refers to the feedset to be displayed. This is the id reference to the <set> section in [[RssFeeds.xml]] (see below):
|-
| '''font'''
| Specifies the font to use from the font.xml file.
|-
| '''textcolor'''
| Specified the color the text should be. In hex AARRGGBB format, or a name from the [[Colour_themes|colour theme.]]
|-
| '''shadowcolor'''
| Specifies the color of the drop shadow on the text. In AARRGGBB format, or a name from the [[Colour_themes|colour theme.]]
|-
| '''headlinecolor'''
| Specified the color that any highlighted text should be. In hex AARRGGBB format, or a name from the [[Colour_themes|colour theme.]]
|-
| '''titlecolor'''
| Specified the color the titles of the feeds should be. In hex AARRGGBB format, or a name from the [[Colour_themes|colour theme.]]
|-
|-
| '''scrollspeed'''
| Scroll speed of text in pixels per second.
|}

== RssFeeds.xml ==
{{Main|RssFeeds.xml}}
The actual content of the RSS feed is defined in the [[RssFeeds.xml]] file stored in the user's profile. Here is an example :

<syntaxhighlight lang=xml enclose="div">
<rssfeeds>
<set id="1">
<feed updateinterval="30">http://feeds.feedburner.com/XboxScene</feed>
<feed updateinterval="30">http://feeds.wired.com/wired/topheadlines</feed>
</set>
<set id="2">
<feed updateinterval="30">http://www.cnet.co.uk/feeds/public/rss_news_10.htm</feed>
</set>
</rssfeeds>
</syntaxhighlight>

As can be seen, each feedset has an id attribute – this is what we are referencing in the <id> attribute of the control. There can be more than one <set> defined, and more than one <feed> per set. The <feed>'s must be escaped so that they're xml-safe <nowiki>(ie replace & with & etc.)</nowiki>. Each feed in the set runs through in the order they are defined.
<section end="main content" />

{{top}}

{{updated|18}}
[[Category:Manual]]
[[Category:Skin development]]

Google Summer of Code/2023

2023-02-05T11:24:44Z

Yol:

{{GSOC_nav}}
{{mininav| [[Google Summer of Code]] }}
[[File:GSOC_2016_logo.png|left|150px]]Welcome to the Kodi [http://summerofcode.withgoogle.com Google Summer of Code] ideas page.

'''This page is currently work in progress.'''
Kodi has applied as mentoring organization for GSoC 2023. Accepted organizations will be announced on February 22.





== About Us ==
As there may be many students who have landed here as a result of GSoC, but are unfamiliar with the project, here are a few resources that may help explain what we are about.

:Kodi (formerly known as XBMC) is an award-winning free and open source (GPL) software media player and entertainment hub for digital media, designed around the 10-foot interface (living room) environment. Created in 2003 by a group of like minded programmers, Kodi is a non-profit project run and developed by volunteers located around the world. More than 1000 software developers have contributed to Kodi, and 300-plus translators have worked to expand its reach, making it available in more than 70 languages. For more information, see the page '''[[Kodi]]'''.

<br />
To get an idea of what Kodi is truly capable of, it really must be seen. Check out a few other user-created videos:<br />
[http://www.youtube.com/watch?v=NcogPuSo-DU Kodi with the default Confluence skin]<br />
[http://www.youtube.com/watch?v=4asUCtE0ONU Kodi with Aeon Nox skin]<br />
[http://www.youtube.com/watch?v=4NR57ELY28s Kodi on Raspberry Pi]<br />
[http://www.youtube.com/watch?v=e_0PB5hfz_k Kodi's new PVR functionality]<br />
<br />

Kodi is written primarily in C++ and runs on a variety of platforms including Android, iOS, Linux, OS X, and Windows. It has been ported to work on several low-power platforms including the Raspberry Pi and Android.

Kodi was a mentoring organization in 2008, 2012, 2013, 2015, 2017, 2018, 2019, 2020, 2021, and 2022 and had team members involved in GSoC for other projects during 2011.

If Kodi is selected as a mentoring organization for 2023, students will need to review the Overview of a good project proposal, follow the outline for proposals when applying, and review the list of project ideas detailed below. Students are welcome to propose ideas outside the list and are encouraged to be as creative as they like.

=== Mentors ===
All mentors and backup mentors are extremely experienced in the Kodi codebase and will thus be able to assist students in getting to know the codebase and in quickly identifying projects that are both achievable for someone unfamiliar with the internal workings of Kodi and desirable to the wider Kodi community.

==Prerequisites==
Some coding skills, basic familiarity with Git, solid understanding and interest in programming. Ability to quickly understand existing code is beneficial.

== Project Proposals ==
=== Overview ===
Qualifications for a good Summer of Code proposal:
* Discrete, well-defined, modular
* Comprised of a series of measurable sub-goals
* Based on open specs that are available free of charge
* Based on complete specs
An example of a good proposal is the implementation of a new feature or function that is not yet available in Kodi.

An example of a less desirable proposal is one that's not as measurable, such as refactoring an existing API. Bad proposals tend to be ones that would require touching a lot of core code.

To re-iterate:
* Localized/isolated code projects = ''good''
* Global code refactoring = ''bad''
* A project should have a set of subgoals, so even if the end goal turns out to be too big some of the parts will be of benefit.
* Not too big! This is an important problem when choosing a project, while it is fun to think about solving a grand project its not always realistic. It's better to finish a smaller project than to start a grand one.

Projects should have a workload of 12 weeks with a possible extension of up to 22 weeks.

=== Where to submit proposals ===
In addition to submitting to the [https://g.go/gsoc Google Summer of Code] website, you are highly encouraged to submit your idea/proposal to the [https://forum.kodi.tv/forumdisplay.php?fid=317 Kodi forum] for discussion. Any proposal not submitted to the forum for discussion will likely not be considered.

=== Outline for proposals ===
{{divbox|blue||
PROJECT TITLE GOES HERE

* '''Name:'''
* '''forum/e-mail:'''
* '''Summary:''' A somewhat small but explanatory walk through of the project. It should not be overly detailed just enough to understand the problem trying to be fixed and how this project opt to solve it.
* '''How will I achieve this:''' Explain how the project will be done, what technologies are needed and how to implement them.
* '''What will the project focus on:''' Explain what the project will focus on, what is the important parts of the project.
* '''Benefits:''' Who will benefit and why from this project. Think about what a user or developer may need or do to benefit from it. Why does it benefit many users.
* '''Goals:''' What is the goal of the project, a project may not always solve the problem entirely as it may take to much time. Think hard about what can be accomplished during a summer with your skill and deduct that quite a bit. If the project can't be done after this perhaps its better to opt for a smaller one or one with subgoals.
* '''What does it touch in Kodi:''' Think about what parts of the code this may touch, Kodi is a big application and a lot of the code is spread out and very complex. If a project touches to much it may be impossible to complete.
* '''Requirements:''' What is needed to complete the project, what code language knowledge what hardware etc.
* '''Possible mentors:''' Place to add possible mentors (Team-Kodi will add this).

}}

== Team-Kodi proposal ideas up for discussion ==

=== Portal integration and Flatpak improvements in Kodi ===
'''Description:''' Integrate libPortal https://github.com/flatpak/libportal into Kodi, to handle fileaccess and other sandbox relevant factors as far as possible. We could also improve some other sandbox features like handling of binary addons, automatic flatpak build checks and build improvements.

'''Expected outcome:''' Integration of libPortal into Kodi and possibly other Flatpak improvements

'''Skills preferred:''' C++, libPortal

'''Possible mentors:'''

'''Difficulty:''' Risky/Exploratory

'''Type:''' Linux/Kodi Core

'''Workload:''' 350 hours

=== Explore building binary addons in rust ===
'''Description:''' While Kodi has python addons, it can also handle binary addons. But these need to be build one by one for each platform and also might fail on errors. Rust might help with both of those problems and more. The idea is to use the api we have but via rust ffi and see where that leads us.

'''Expected outcome:''' Documentation and templates on how to use rust with kodi. In the best case also one or two example addons.

'''Skills preferred:''' C++, Rust, C

'''Possible mentors:'''

'''Difficulty:''' Hard

'''Type:''' Binary addon development

'''Workload:''' 350 hours

=== Finish the new web interface ===
'''Description:''' Kodi has a in development webinterface by the name of elm-chorus (https://github.com/xbmc/elm-chorus) which is written in Elm and is still missing some features of Chorus2 (the old interface). So the idea would be to bring it up to speed and do some additional styling and packaging work.

'''Expected outcome:''' Finished shipable version of the webinterface

'''Skills preferred:''' HTML, CSS, Elm

'''Possible mentors:'''

'''Difficulty:''' Medium

'''Type:''' Webinterface development

'''Workload:''' 350 hours






===Other ideas===
These ideas still need expanding and/or assigned a potential mentor. If one of these ideas interests you, feel free to ask for more info in the GSoC 2022 forum area. We may be able to assign a mentor if enough interest is shown
*Improvements to Retroplayer (retro gaming integrated in Kodi core)
*Visual Studio Code addon to validate/syntax highlight Kodi Addons

*High quality scalers for OpenGL(GLSL). Scale Y and UV plane separately (possible mentors: velocity)


*Implementing a performance critical element of Kodi in Rust
*Add multiroom audio support where each Kodi instance can act as client or server. Maybe Snapcast could be used somehow.
*Implement IWYU into existing CI (Jenkins). Of note would be the requirement to create IWYU mappings for the Kodi codebase.

=== More ===
We feel it is important to note that, while we are interested in a focus on the listed ideas, we would like to stress passion, expertise, and creativity above all else. If you would like to do something completely different, definitely send in that proposal. The ideas listed above are, as always, merely suggestions. We will be interested in any idea, so long as you can communicate your interest, your background, and your solution the problem.

== Students project proposal ideas ==

Submit your own proposals on the '''[https://forum.kodi.tv/forumdisplay.php?fid=317 Kodi GSoC forum]'''. They can be as big or as small as you feel you can comfortably accomplish in the defined time (175 or 350 hours). In the end, it's better to have a smaller, completed project, rather than a larger, incomplete project.

To submit a proposal idea:
# Copy the text from '''[[#Outline for proposals]]'''.
# Create a new forum post '''[https://forum.kodi.tv/forumdisplay.php?fid=317 HERE]''' and paste the text.
# Fill out everything using your specific proposal.

[[Category:Google Summer of Code]]

Google Summer of Code/2023

2023-02-05T11:24:00Z

Yol:

{{GSOC_nav}}
{{mininav| [[Google Summer of Code]] }}
[[File:GSOC_2016_logo.png|left|150px]]Welcome to the Kodi [http://summerofcode.withgoogle.com Google Summer of Code] ideas page.

'''This page is currently work in progress.'''
Kodi has applied as mentoring organization for GSoC 2023. Accepted organizations will be announced on February 22.





== About Us ==
As there may be many students who have landed here as a result of GSoC, but are unfamiliar with the project, here are a few resources that may help explain what we are about.

:Kodi (formerly known as XBMC) is an award-winning free and open source (GPL) software media player and entertainment hub for digital media, designed around the 10-foot interface (living room) environment. Created in 2003 by a group of like minded programmers, Kodi is a non-profit project run and developed by volunteers located around the world. More than 1000 software developers have contributed to Kodi, and 300-plus translators have worked to expand its reach, making it available in more than 70 languages. For more information, see the page '''[[Kodi]]'''.

<br />
To get an idea of what Kodi is truly capable of, it really must be seen. Check out a few other user-created videos:<br />
[http://www.youtube.com/watch?v=NcogPuSo-DU Kodi with the default Confluence skin]<br />
[http://www.youtube.com/watch?v=4asUCtE0ONU Kodi with Aeon Nox skin]<br />
[http://www.youtube.com/watch?v=4NR57ELY28s Kodi on Raspberry Pi]<br />
[http://www.youtube.com/watch?v=e_0PB5hfz_k Kodi's new PVR functionality]<br />
<br />

Kodi is written primarily in C++ and runs on a variety of platforms including Android, iOS, Linux, OS X, and Windows. It has been ported to work on several low-power platforms including the Raspberry Pi and Android.

Kodi was a mentoring organization in 2008, 2012, 2013, 2015, 2017, 2018, 2019, 2020, 2021, and 2022 and had team members involved in GSoC for other projects during 2011.

If Kodi is selected as a mentoring organization for 2023, students will need to review the Overview of a good project proposal, follow the outline for proposals when applying, and review the list of project ideas detailed below. Students are welcome to propose ideas outside the list and are encouraged to be as creative as they like.

=== Mentors ===
All mentors and backup mentors are extremely experienced in the Kodi codebase and will thus be able to assist students in getting to know the codebase and in quickly identifying projects that are both achievable for someone unfamiliar with the internal workings of Kodi and desirable to the wider Kodi community.

==Prerequisites==
Some coding skills, basic familiarity with Git, solid understanding and interest in programming. Ability to quickly understand existing code is beneficial.

== Project Proposals ==
=== Overview ===
Qualifications for a good Summer of Code proposal:
* Discrete, well-defined, modular
* Comprised of a series of measurable sub-goals
* Based on open specs that are available free of charge
* Based on complete specs
An example of a good proposal is the implementation of a new feature or function that is not yet available in Kodi.

An example of a less desirable proposal is one that's not as measurable, such as refactoring an existing API. Bad proposals tend to be ones that would require touching a lot of core code.

To re-iterate:
* Localized/isolated code projects = ''good''
* Global code refactoring = ''bad''
* A project should have a set of subgoals, so even if the end goal turns out to be too big some of the parts will be of benefit.
* Not too big! This is an important problem when choosing a project, while it is fun to think about solving a grand project its not always realistic. It's better to finish a smaller project than to start a grand one.

Projects can have a workload of either 175 hours or 350 hours.

=== Where to submit proposals ===
In addition to submitting to the [https://g.go/gsoc Google Summer of Code] website, you are highly encouraged to submit your idea/proposal to the [https://forum.kodi.tv/forumdisplay.php?fid=317 Kodi forum] for discussion. Any proposal not submitted to the forum for discussion will likely not be considered.

=== Outline for proposals ===
{{divbox|blue||
PROJECT TITLE GOES HERE

* '''Name:'''
* '''forum/e-mail:'''
* '''Summary:''' A somewhat small but explanatory walk through of the project. It should not be overly detailed just enough to understand the problem trying to be fixed and how this project opt to solve it.
* '''How will I achieve this:''' Explain how the project will be done, what technologies are needed and how to implement them.
* '''What will the project focus on:''' Explain what the project will focus on, what is the important parts of the project.
* '''Benefits:''' Who will benefit and why from this project. Think about what a user or developer may need or do to benefit from it. Why does it benefit many users.
* '''Goals:''' What is the goal of the project, a project may not always solve the problem entirely as it may take to much time. Think hard about what can be accomplished during a summer with your skill and deduct that quite a bit. If the project can't be done after this perhaps its better to opt for a smaller one or one with subgoals.
* '''What does it touch in Kodi:''' Think about what parts of the code this may touch, Kodi is a big application and a lot of the code is spread out and very complex. If a project touches to much it may be impossible to complete.
* '''Requirements:''' What is needed to complete the project, what code language knowledge what hardware etc.
* '''Possible mentors:''' Place to add possible mentors (Team-Kodi will add this).

}}

== Team-Kodi proposal ideas up for discussion ==

=== Portal integration and Flatpak improvements in Kodi ===
'''Description:''' Integrate libPortal https://github.com/flatpak/libportal into Kodi, to handle fileaccess and other sandbox relevant factors as far as possible. We could also improve some other sandbox features like handling of binary addons, automatic flatpak build checks and build improvements.

'''Expected outcome:''' Integration of libPortal into Kodi and possibly other Flatpak improvements

'''Skills preferred:''' C++, libPortal

'''Possible mentors:'''

'''Difficulty:''' Risky/Exploratory

'''Type:''' Linux/Kodi Core

'''Workload:''' 350 hours

=== Explore building binary addons in rust ===
'''Description:''' While Kodi has python addons, it can also handle binary addons. But these need to be build one by one for each platform and also might fail on errors. Rust might help with both of those problems and more. The idea is to use the api we have but via rust ffi and see where that leads us.

'''Expected outcome:''' Documentation and templates on how to use rust with kodi. In the best case also one or two example addons.

'''Skills preferred:''' C++, Rust, C

'''Possible mentors:'''

'''Difficulty:''' Hard

'''Type:''' Binary addon development

'''Workload:''' 350 hours

=== Finish the new web interface ===
'''Description:''' Kodi has a in development webinterface by the name of elm-chorus (https://github.com/xbmc/elm-chorus) which is written in Elm and is still missing some features of Chorus2 (the old interface). So the idea would be to bring it up to speed and do some additional styling and packaging work.

'''Expected outcome:''' Finished shipable version of the webinterface

'''Skills preferred:''' HTML, CSS, Elm

'''Possible mentors:'''

'''Difficulty:''' Medium

'''Type:''' Webinterface development

'''Workload:''' 350 hours






===Other ideas===
These ideas still need expanding and/or assigned a potential mentor. If one of these ideas interests you, feel free to ask for more info in the GSoC 2022 forum area. We may be able to assign a mentor if enough interest is shown
*Improvements to Retroplayer (retro gaming integrated in Kodi core)
*Visual Studio Code addon to validate/syntax highlight Kodi Addons

*High quality scalers for OpenGL(GLSL). Scale Y and UV plane separately (possible mentors: velocity)


*Implementing a performance critical element of Kodi in Rust
*Add multiroom audio support where each Kodi instance can act as client or server. Maybe Snapcast could be used somehow.
*Implement IWYU into existing CI (Jenkins). Of note would be the requirement to create IWYU mappings for the Kodi codebase.

=== More ===
We feel it is important to note that, while we are interested in a focus on the listed ideas, we would like to stress passion, expertise, and creativity above all else. If you would like to do something completely different, definitely send in that proposal. The ideas listed above are, as always, merely suggestions. We will be interested in any idea, so long as you can communicate your interest, your background, and your solution the problem.

== Students project proposal ideas ==

Submit your own proposals on the '''[https://forum.kodi.tv/forumdisplay.php?fid=317 Kodi GSoC forum]'''. They can be as big or as small as you feel you can comfortably accomplish in the defined time (175 or 350 hours). In the end, it's better to have a smaller, completed project, rather than a larger, incomplete project.

To submit a proposal idea:
# Copy the text from '''[[#Outline for proposals]]'''.
# Create a new forum post '''[https://forum.kodi.tv/forumdisplay.php?fid=317 HERE]''' and paste the text.
# Fill out everything using your specific proposal.

[[Category:Google Summer of Code]]

Google Summer of Code/2022

2023-01-29T16:05:37Z

Yol:

{{GSOC_nav}}
{{mininav| [[Google Summer of Code]] }}
[[File:GSOC_2016_logo.png|left|150px]]Welcome to the Kodi [http://summerofcode.withgoogle.com Google Summer of Code] ideas page.

We encourage interested students of all ethnicities and genders to review some of the ideas on this page, and then feel free to provide input on any ideas you may have in the '''[https://forum.kodi.tv/forumdisplay.php?fid=317 Kodi GSoC 2022 forum]''' and chat about any project you’d love to cover. To propose a project, see '''[[#Students project proposal ideas]]'''.



== About Us ==
As there may be many students who have landed here as a result of GSoC, but are unfamiliar with the project, here are a few resources that may help explain what we are about.

:Kodi (formerly known as XBMC) is an award-winning free and open source (GPL) software media player and entertainment hub for digital media, designed around the 10-foot interface (living room) environment. Created in 2003 by a group of like minded programmers, Kodi is a non-profit project run and developed by volunteers located around the world. More than 1000 software developers have contributed to Kodi, and 300-plus translators have worked to expand its reach, making it available in more than 70 languages. For more information, see the page '''[[Kodi]]'''.

<br />
To get an idea of what Kodi is truly capable of, it really must be seen. Check out a few other user-created videos:<br />
[http://www.youtube.com/watch?v=NcogPuSo-DU Kodi with the default Confluence skin]<br />
[http://www.youtube.com/watch?v=4asUCtE0ONU Kodi with Aeon Nox skin]<br />
[http://www.youtube.com/watch?v=4NR57ELY28s Kodi on Raspberry Pi]<br />
[http://www.youtube.com/watch?v=e_0PB5hfz_k Kodi's new PVR functionality]<br />
<br />

Kodi is written primarily in C++ and runs on a variety of platforms including Android, iOS, Linux, OS X, and Windows. It has been ported to work on several low-power platforms including the Raspberry Pi and Android.

Kodi was a mentoring organization in 2008, 2012, 2013, 2015, 2017, 2018, 2019, 2020 and 2021 and had team members involved in GSoC for other projects during 2011.

If Kodi is selected as a mentoring organization for 2022, students will need to review the Overview of a good project proposal, follow the outline for proposals when applying, and review the list of project ideas detailed below. Students are welcome to propose ideas outside the list and are encouraged to be as creative as they like.

=== Mentors ===
All mentors and backup mentors are extremely experienced in the Kodi codebase and will thus be able to assist students in getting to know the codebase and in quickly identifying projects that are both achievable for someone unfamiliar with the internal workings of Kodi and desirable to the wider Kodi community.

==Prerequisites==
Some coding skills, basic familiarity with Git, solid understanding and interest in programming. Ability to quickly understand existing code is beneficial.

== Project Proposals ==
=== Overview ===
Qualifications for a good Summer of Code proposal:
* Discrete, well-defined, modular
* Comprised of a series of measurable sub-goals
* Based on open specs that are available free of charge
* Based on complete specs
An example of a good proposal is the implementation of a new feature or function that is not yet available in Kodi.

An example of a less desirable proposal is one that's not as measurable, such as refactoring an existing API. Bad proposals tend to be ones that would require touching a lot of core code.

To re-iterate:
* Localized/isolated code projects = ''good''
* Global code refactoring = ''bad''
* A project should have a set of subgoals, so even if the end goal turns out to be too big some of the parts will be of benefit.
* Not too big! This is an important problem when choosing a project, while it is fun to think about solving a grand project its not always realistic. It's better to finish a smaller project than to start a grand one.

Projects can have a workload of either 175 hours or 350 hours.

=== Where to submit proposals ===
In addition to submitting to the [https://g.go/gsoc Google Summer of Code] website, you are highly encouraged to submit your idea/proposal to the [https://forum.kodi.tv/forumdisplay.php?fid=317 Kodi forum] for discussion. Any proposal not submitted to the forum for discussion will likely not be considered.

=== Outline for proposals ===
{{divbox|blue||
PROJECT TITLE GOES HERE

* '''Name:'''
* '''forum/e-mail:'''
* '''Summary:''' A somewhat small but explanatory walk through of the project. It should not be overly detailed just enough to understand the problem trying to be fixed and how this project opt to solve it.
* '''How will I achieve this:''' Explain how the project will be done, what technologies are needed and how to implement them.
* '''What will the project focus on:''' Explain what the project will focus on, what is the important parts of the project.
* '''Benefits:''' Who will benefit and why from this project. Think about what a user or developer may need or do to benefit from it. Why does it benefit many users.
* '''Goals:''' What is the goal of the project, a project may not always solve the problem entirely as it may take to much time. Think hard about what can be accomplished during a summer with your skill and deduct that quite a bit. If the project can't be done after this perhaps its better to opt for a smaller one or one with subgoals.
* '''What does it touch in Kodi:''' Think about what parts of the code this may touch, Kodi is a big application and a lot of the code is spread out and very complex. If a project touches to much it may be impossible to complete.
* '''Requirements:''' What is needed to complete the project, what code language knowledge what hardware etc.
* '''Possible mentors:''' Place to add possible mentors (Team-Kodi will add this).
* '''Workload:''' Either 175 or 350 hours.
}}

== Team-Kodi proposal ideas up for discussion ==

=== Portal integration and Flatpak improvements in Kodi ===
'''Description:''' Integrate libPortal https://github.com/flatpak/libportal into Kodi, to handle fileaccess and other sandbox relevant factors as far as possible. We could also improve some other sandbox features like handling of binary addons, automatic flatpak build checks and build improvements.

'''Expected outcome:''' Integration of libPortal into Kodi and possibly other Flatpak improvements

'''Skills preferred:''' C++, libPortal

'''Possible mentors:''' Razze

'''Difficulty:''' Risky/Exploratory

'''Type:''' Linux/Kodi Core

'''Workload:''' 350 hours

=== Explore building binary addons in rust ===
'''Description:''' While Kodi has python addons, it can also handle binary addons. But these need to be build one by one for each platform and also might fail on errors. Rust might help with both of those problems and more. The idea is to use the api we have but via rust ffi and see where that leads us.

'''Expected outcome:''' Documentation and templates on how to use rust with kodi. In the best case also one or two example addons.

'''Skills preferred:''' C++, Rust, C

'''Possible mentors:''' spiff, Razze

'''Difficulty:''' Hard

'''Type:''' Binary addon development

'''Workload:''' 350 hours

=== Finish the new web interface ===
'''Description:''' Kodi has a in development webinterface by the name of elm-chorus (https://github.com/xbmc/elm-chorus) which is written in Elm and is still missing some features of Chorus2 (the old interface). So the idea would be to bring it up to speed and do some additional styling and packaging work.

'''Expected outcome:''' Finished shipable version of the webinterface

'''Skills preferred:''' HTML, CSS, Elm

'''Possible mentors:''' Razze

'''Difficulty:''' Medium

'''Type:''' Webinterface development

'''Workload:''' 350 hours




===Using fuzz testing to fuzz test Kodi===
'''Description:''' Adding fuzz testing to Kodi would be very valuable to find problems in the current code base. Especially security problems. First step would be choosing a framework either American fuzzy lop, libFuzzer or other similar projects. After we decided on that it would be time to start to fuzz different methods that are widely used in Kodi and try to expose flaws in those. If this leads to success, it should be documented and made repeatable.

'''Expected outcome:''' Being able to easily add more fuzz tests and having the process to do this documented.

'''Skills preferred:''' C++, CMake

'''Possible mentors:''' Razze

'''Difficulty:''' Medium

'''Type:''' Risky/Exploratory

'''Workload:''' 175 hours



===Other ideas===
These ideas still need expanding and/or assigned a potential mentor. If one of these ideas interests you, feel free to ask for more info in the GSoC 2022 forum area. We may be able to assign a mentor if enough interest is shown
*Improvements to Retroplayer (retro gaming integrated in Kodi core)
*Visual Studio Code addon to validate/syntax highlight Kodi Addons

*High quality scalers for OpenGL(GLSL). Scale Y and UV plane separately (possible mentors: velocity)


*Implementing a performance critical element of Kodi in Rust
*Add multiroom audio support where each Kodi instance can act as client or server. Maybe Snapcast could be used somehow.
*Implement IWYU into existing CI (Jenkins). Of note would be the requirement to create IWYU mappings for the Kodi codebase.

=== More ===
We feel it is important to note that, while we are interested in a focus on the listed ideas, we would like to stress passion, expertise, and creativity above all else. If you would like to do something completely different, definitely send in that proposal. The ideas listed above are, as always, merely suggestions. We will be interested in any idea, so long as you can communicate your interest, your background, and your solution the problem.

== Students project proposal ideas ==

Submit your own proposals on the '''[https://forum.kodi.tv/forumdisplay.php?fid=317 Kodi GSoC forum]'''. They can be as big or as small as you feel you can comfortably accomplish in the defined time (175 or 350 hours). In the end, it's better to have a smaller, completed project, rather than a larger, incomplete project.

To submit a proposal idea:
# Copy the text from '''[[#Outline for proposals]]'''.
# Create a new forum post '''[https://forum.kodi.tv/forumdisplay.php?fid=317 HERE]''' and paste the text.
# Fill out everything using your specific proposal.

[[Category:Google Summer of Code]]

Google Summer of Code/2023

2023-01-29T16:05:26Z

Yol: Created page with "{{GSOC_nav}} {{mininav| Google Summer of Code }} 150pxWelcome to the Kodi [http://summerofcode.withgoogle.com Google Summer of Code] ideas page. '''This page is currently work in progress.'''  We encourage interested students of all ethnicities and genders to review some of the ideas on this page, and then feel free..."

{{GSOC_nav}}
{{mininav| [[Google Summer of Code]] }}
[[File:GSOC_2016_logo.png|left|150px]]Welcome to the Kodi [http://summerofcode.withgoogle.com Google Summer of Code] ideas page.

'''This page is currently work in progress.'''


We encourage interested students of all ethnicities and genders to review some of the ideas on this page, and then feel free to provide input on any ideas you may have in the '''[https://forum.kodi.tv/forumdisplay.php?fid=317 Kodi GSoC 2022 forum]''' and chat about any project you’d love to cover. To propose a project, see '''[[#Students project proposal ideas]]'''.



== About Us ==
As there may be many students who have landed here as a result of GSoC, but are unfamiliar with the project, here are a few resources that may help explain what we are about.

:Kodi (formerly known as XBMC) is an award-winning free and open source (GPL) software media player and entertainment hub for digital media, designed around the 10-foot interface (living room) environment. Created in 2003 by a group of like minded programmers, Kodi is a non-profit project run and developed by volunteers located around the world. More than 1000 software developers have contributed to Kodi, and 300-plus translators have worked to expand its reach, making it available in more than 70 languages. For more information, see the page '''[[Kodi]]'''.

<br />
To get an idea of what Kodi is truly capable of, it really must be seen. Check out a few other user-created videos:<br />
[http://www.youtube.com/watch?v=NcogPuSo-DU Kodi with the default Confluence skin]<br />
[http://www.youtube.com/watch?v=4asUCtE0ONU Kodi with Aeon Nox skin]<br />
[http://www.youtube.com/watch?v=4NR57ELY28s Kodi on Raspberry Pi]<br />
[http://www.youtube.com/watch?v=e_0PB5hfz_k Kodi's new PVR functionality]<br />
<br />

Kodi is written primarily in C++ and runs on a variety of platforms including Android, iOS, Linux, OS X, and Windows. It has been ported to work on several low-power platforms including the Raspberry Pi and Android.

Kodi was a mentoring organization in 2008, 2012, 2013, 2015, 2017, 2018, 2019, 2020 and 2021 and had team members involved in GSoC for other projects during 2011.

If Kodi is selected as a mentoring organization for 2022, students will need to review the Overview of a good project proposal, follow the outline for proposals when applying, and review the list of project ideas detailed below. Students are welcome to propose ideas outside the list and are encouraged to be as creative as they like.

=== Mentors ===
All mentors and backup mentors are extremely experienced in the Kodi codebase and will thus be able to assist students in getting to know the codebase and in quickly identifying projects that are both achievable for someone unfamiliar with the internal workings of Kodi and desirable to the wider Kodi community.

==Prerequisites==
Some coding skills, basic familiarity with Git, solid understanding and interest in programming. Ability to quickly understand existing code is beneficial.

== Project Proposals ==
=== Overview ===
Qualifications for a good Summer of Code proposal:
* Discrete, well-defined, modular
* Comprised of a series of measurable sub-goals
* Based on open specs that are available free of charge
* Based on complete specs
An example of a good proposal is the implementation of a new feature or function that is not yet available in Kodi.

An example of a less desirable proposal is one that's not as measurable, such as refactoring an existing API. Bad proposals tend to be ones that would require touching a lot of core code.

To re-iterate:
* Localized/isolated code projects = ''good''
* Global code refactoring = ''bad''
* A project should have a set of subgoals, so even if the end goal turns out to be too big some of the parts will be of benefit.
* Not too big! This is an important problem when choosing a project, while it is fun to think about solving a grand project its not always realistic. It's better to finish a smaller project than to start a grand one.

Projects can have a workload of either 175 hours or 350 hours.

=== Where to submit proposals ===
In addition to submitting to the [https://g.go/gsoc Google Summer of Code] website, you are highly encouraged to submit your idea/proposal to the [https://forum.kodi.tv/forumdisplay.php?fid=317 Kodi forum] for discussion. Any proposal not submitted to the forum for discussion will likely not be considered.

=== Outline for proposals ===
{{divbox|blue||
PROJECT TITLE GOES HERE

* '''Name:'''
* '''forum/e-mail:'''
* '''Summary:''' A somewhat small but explanatory walk through of the project. It should not be overly detailed just enough to understand the problem trying to be fixed and how this project opt to solve it.
* '''How will I achieve this:''' Explain how the project will be done, what technologies are needed and how to implement them.
* '''What will the project focus on:''' Explain what the project will focus on, what is the important parts of the project.
* '''Benefits:''' Who will benefit and why from this project. Think about what a user or developer may need or do to benefit from it. Why does it benefit many users.
* '''Goals:''' What is the goal of the project, a project may not always solve the problem entirely as it may take to much time. Think hard about what can be accomplished during a summer with your skill and deduct that quite a bit. If the project can't be done after this perhaps its better to opt for a smaller one or one with subgoals.
* '''What does it touch in Kodi:''' Think about what parts of the code this may touch, Kodi is a big application and a lot of the code is spread out and very complex. If a project touches to much it may be impossible to complete.
* '''Requirements:''' What is needed to complete the project, what code language knowledge what hardware etc.
* '''Possible mentors:''' Place to add possible mentors (Team-Kodi will add this).
* '''Workload:''' Either 175 or 350 hours.
}}

== Team-Kodi proposal ideas up for discussion ==

=== Portal integration and Flatpak improvements in Kodi ===
'''Description:''' Integrate libPortal https://github.com/flatpak/libportal into Kodi, to handle fileaccess and other sandbox relevant factors as far as possible. We could also improve some other sandbox features like handling of binary addons, automatic flatpak build checks and build improvements.

'''Expected outcome:''' Integration of libPortal into Kodi and possibly other Flatpak improvements

'''Skills preferred:''' C++, libPortal

'''Possible mentors:''' Razze

'''Difficulty:''' Risky/Exploratory

'''Type:''' Linux/Kodi Core

'''Workload:''' 350 hours

=== Explore building binary addons in rust ===
'''Description:''' While Kodi has python addons, it can also handle binary addons. But these need to be build one by one for each platform and also might fail on errors. Rust might help with both of those problems and more. The idea is to use the api we have but via rust ffi and see where that leads us.

'''Expected outcome:''' Documentation and templates on how to use rust with kodi. In the best case also one or two example addons.

'''Skills preferred:''' C++, Rust, C

'''Possible mentors:''' spiff, Razze

'''Difficulty:''' Hard

'''Type:''' Binary addon development

'''Workload:''' 350 hours

=== Finish the new web interface ===
'''Description:''' Kodi has a in development webinterface by the name of elm-chorus (https://github.com/xbmc/elm-chorus) which is written in Elm and is still missing some features of Chorus2 (the old interface). So the idea would be to bring it up to speed and do some additional styling and packaging work.

'''Expected outcome:''' Finished shipable version of the webinterface

'''Skills preferred:''' HTML, CSS, Elm

'''Possible mentors:''' Razze

'''Difficulty:''' Medium

'''Type:''' Webinterface development

'''Workload:''' 350 hours




===Using fuzz testing to fuzz test Kodi===
'''Description:''' Adding fuzz testing to Kodi would be very valuable to find problems in the current code base. Especially security problems. First step would be choosing a framework either American fuzzy lop, libFuzzer or other similar projects. After we decided on that it would be time to start to fuzz different methods that are widely used in Kodi and try to expose flaws in those. If this leads to success, it should be documented and made repeatable.

'''Expected outcome:''' Being able to easily add more fuzz tests and having the process to do this documented.

'''Skills preferred:''' C++, CMake

'''Possible mentors:''' Razze

'''Difficulty:''' Medium

'''Type:''' Risky/Exploratory

'''Workload:''' 175 hours



===Other ideas===
These ideas still need expanding and/or assigned a potential mentor. If one of these ideas interests you, feel free to ask for more info in the GSoC 2022 forum area. We may be able to assign a mentor if enough interest is shown
*Improvements to Retroplayer (retro gaming integrated in Kodi core)
*Visual Studio Code addon to validate/syntax highlight Kodi Addons

*High quality scalers for OpenGL(GLSL). Scale Y and UV plane separately (possible mentors: velocity)


*Implementing a performance critical element of Kodi in Rust
*Add multiroom audio support where each Kodi instance can act as client or server. Maybe Snapcast could be used somehow.
*Implement IWYU into existing CI (Jenkins). Of note would be the requirement to create IWYU mappings for the Kodi codebase.

=== More ===
We feel it is important to note that, while we are interested in a focus on the listed ideas, we would like to stress passion, expertise, and creativity above all else. If you would like to do something completely different, definitely send in that proposal. The ideas listed above are, as always, merely suggestions. We will be interested in any idea, so long as you can communicate your interest, your background, and your solution the problem.

== Students project proposal ideas ==

Submit your own proposals on the '''[https://forum.kodi.tv/forumdisplay.php?fid=317 Kodi GSoC forum]'''. They can be as big or as small as you feel you can comfortably accomplish in the defined time (175 or 350 hours). In the end, it's better to have a smaller, completed project, rather than a larger, incomplete project.

To submit a proposal idea:
# Copy the text from '''[[#Outline for proposals]]'''.
# Create a new forum post '''[https://forum.kodi.tv/forumdisplay.php?fid=317 HERE]''' and paste the text.
# Fill out everything using your specific proposal.

[[Category:Google Summer of Code]]

Kodi Foundation

2022-09-21T16:26:57Z

Yol:

{{mininav}}
<section begin=intro />The "'''Kodi Foundation'''" is the non-profit organization that oversees the [[Kodi|{{kodi}}]] project and is registered in the US.<section end=intro />

== Members ==
Membership of the Kodi Foundation is typically taken from members of Team Kodi, but may include non Team members.

== Board of Directors ==
{| class="infobox"
|-
|
<section begin=Foundation members />
* '''Keith Herrington (keith)''' - Board member - ''Term: 11/2016 - 11/2024''
* '''Darren Hill (DarrenHill)''' - Board member - ''Term: 11/2018 - 11/2024''
* '''ronie (ronie)''' - Board member - ''Term: 11/2019 - 11/2023''
* '''Yol (Yol)''' - Board member - ''Term: 11/2019 - 11/2023''
* '''Da-Anda (Da-Anda)''' - Board member - ''Term: 11/2021 - 11/2023''<section end=Foundation members />
|}
The Kodi Board of Directors are Foundation members that manages the Kodi Foundation. The Board consists of five seats that are chosen by vote from the Kodi Foundation members. The Board's responsibilities include management of funds, publicity, and all business related issues (taxes, communication with other businesses, maintaining non-profit status etc.)
{{-}}

== Board of Directors meetings ==
The Board meets about once a month (in addition to any special meetings as required) to discuss any business that needs to be handled by the foundation. Meetings are typically conducted via teleconference using a service such as Skype.

== Board of Directors elections ==
;Who can be a Kodi Board member?
:Any existing member of the foundation, as voted by the remaining members.

;How long does a board member hold office?
:Terms last for two years. We endeavor to have a staggered cycle so that not all board members are turned over at a single election. There are no term restrictions, so Board members may even run for consecutive terms. However, in the interests of sharing the load, any and all members are encouraged to participate.

;What is expected of a Kodi Board member?
:Board members are expected to attend all meetings or will otherwise be diligent in letting the other board members know if they won't be around. Further, they'll be expected to make decisions (as a group) in the best interests of the foundation. The Board accountable to the members, so should consider recommendations made by members during the decision making process, Though they ultimately must make the final decisions. Any and all discussion should be frankly communicated to members within a reasonable time frame.

;Who elects the officers (President, Secretary, Treasurer etc?)
:The board elects the officers. In doing so, they may choose to take advice from the membership, but the decision is theirs. The President must be from within the board itself, though Secretary, Treasurer, and any other officers the board wishes to appoint may be from outside the board (or outside the membership).

=== Election process ===

Board elections occur as follows:
# A member is nominated by the Board to oversee the election.
# Nominations for the open positions are taken from within the existing membership via email and/or via a forum thread. This lasts a minimum of 10 days.
# Confirmed nominees are placed on the ballot.
# A vote of the membership is then taken using a trusted internet voting service using a ranking system. (usually via the Condorcet Internet Voting Service, http://www.cs.cornell.edu/w8/~andru/civs ) and the candidates with the highest ranks take office. This lasts about two weeks.
#: ''In the event of a tie, it will be resolved with the existing board members discussing with the tied nominees. Tied nominees that do not go on the board may be nominated as officers of the Foundation, for example.''

=== Previous elections ===
* [[/Elections/2021|2021]]
* [[/Elections/2020|2020]]
* [[/Elections/2019|2019]]
* [[Archive:XBMC_Foundation/Elections/2018|2018]]
* [[Archive:XBMC_Foundation/Elections/2017|2017]]
* [[Archive:XBMC_Foundation/Elections/2016|2016]]
* [[Archive:XBMC_Foundation/Elections/2014|2014]]
* [[Archive:XBMC_Foundation/Elections/2013|2013]]
* [[Archive:XBMC_Foundation/Elections/2012|2012]]

== Foundation Bylaws and other important documents ==
* [[Media:ByLaws.pdf]]
* [[Media:Delaware Incorporation Notice.pdf]]
* [[Media:Delaware Notice Of Good Standing.pdf]]
* [[Media:KodiFoundationIncorporationNotice.pdf]]
* [[Media:Kodi_Foundation_exempt.jpg]]

== Trademarks ==
{{see|Official:Trademark Policy index}}

== Financial information ==

=== Financial status ===

* Form 990 2016 - http://www.guidestar.org/FinDocuments/2016/474/565/2016-474565769-0e36f6e3-9.pdf
* Income and expenses 2015 - https://drive.google.com/file/d/0BwsEEPRqIzELOVpUa0p4endrRWc/view?usp=sharing
* Income and expenses 2014 - https://drive.google.com/file/d/0BwsEEPRqIzELVW9rMkpPUWZRSHM/view?usp=sharing
* Income and expenses 2013 - https://docs.google.com/spreadsheet/ccc?key=0AtlJ3dnHcw46dHpmeXlIV0hGaC13Z3I3b25hZWhWRGc#gid=8

''note'': 2014 and 2015 expenses are US Foundation account only.

=== Account details ===

'''Unites States account'''

* Bank: Wells Fargo
* Beneficiary: Kodi Foundation

== Legal representation ==
The Kodi Foundation is legally represented by the [[w:Software Freedom Law Center|SFLC (Software Freedom Law Center)]].

In addition the Kodi Foundation is member of [[w:Open_Invention_Network|OIN (Open Invention Network)]] since 9 July 2010. OIN is a defensive patent pool and community of patent non-aggression which enables freedom of action in Linux.

== Contact ==
For contact information, please see http://kodi.tv/about/contact/

[[Category:Kodi_Foundation-Archived]]

XBMC Foundation

2022-09-21T16:25:11Z

Yol: Yol moved page XBMC Foundation to Kodi Foundation

#REDIRECT [[Kodi Foundation]]

Kodi Foundation

2022-09-21T16:25:11Z

Yol: Yol moved page XBMC Foundation to Kodi Foundation

{{mininav}}
<section begin=intro />The "'''XBMC Foundation'''" is the non-profit organization that oversees the [[Kodi|{{kodi}}]] project and is registered in the US.<section end=intro />

== Members ==
Membership of the XBMC Foundation is typically taken from members of Team Kodi, but may include non Team members.

== Board of Directors ==
{| class="infobox"
|-
|
<section begin=Foundation members />
* '''Keith Herrington (keith)''' - Board member - ''Term: 11/2016 - 11/2022''
* '''Darren Hill (DarrenHill)''' - Board member - ''Term: 11/2018 - 11/2022''
* '''ronie (ronie)''' - Board member - ''Term: 11/2019 - 11/2023''
* '''Yol (Yol)''' - Board member - ''Term: 11/2019 - 11/2023''
* '''Da-Anda (Da-Anda)''' - Board member - ''Term: 11/2021 - 11/2023''<section end=Foundation members />
|}
The XBMC Board of Directors are Foundation members that manages the XBMC Foundation. The Board consists of five seats that are chosen by vote from the XBMC Foundation members. The Board's responsibilities include management of funds, publicity, and all business related issues (taxes, communication with other businesses, maintaining non-profit status etc.)
{{-}}

== Board of Directors meetings ==
The Board meets about once a month (in addition to any special meetings as required) to discuss any business that needs to be handled by the foundation. Meetings are typically conducted via teleconference using a service such as Skype.

== Board of Directors elections ==
;Who can be an XBMC Board member?
:Any existing member of the foundation, as voted by the remaining members.

;How long does a board member hold office?
:Terms last for two years. We endeavor to have a staggered cycle so that not all board members are turned over at a single election. There are no term restrictions, so Board members may even run for consecutive terms. However, in the interests of sharing the load, any and all members are encouraged to participate.

;What is expected of an XBMC Board member?
:Board members are expected to attend all meetings or will otherwise be diligent in letting the other board members know if they won't be around. Further, they'll be expected to make decisions (as a group) in the best interests of the foundation. The Board accountable to the members, so should consider recommendations made by members during the decision making process, Though they ultimately must make the final decisions. Any and all discussion should be frankly communicated to members within a reasonable time frame.

;Who elects the officers (President, Secretary, Treasurer etc?)
:The board elects the officers. In doing so, they may choose to take advice from the membership, but the decision is theirs. The President must be from within the board itself, though Secretary, Treasurer, and any other officers the board wishes to appoint may be from outside the board (or outside the membership).

=== Election process ===

Board elections occur as follows:
# A member is nominated by the Board to oversee the election.
# Nominations for the open positions are taken from within the existing membership via email and/or via a forum thread. This lasts a minimum of 10 days.
# Confirmed nominees are placed on the ballot.
# A vote of the membership is then taken using a trusted internet voting service using a ranking system. (usually via the Condorcet Internet Voting Service, http://www.cs.cornell.edu/w8/~andru/civs ) and the candidates with the highest ranks take office. This lasts about two weeks.
#: ''In the event of a tie, it will be resolved with the existing board members discussing with the tied nominees. Tied nominees that do not go on the board may be nominated as officers of the Foundation, for example.''

=== Previous elections ===
* [[/Elections/2021|2021]]
* [[/Elections/2020|2020]]
* [[/Elections/2019|2019]]
* [[Archive:XBMC_Foundation/Elections/2018|2018]]
* [[Archive:XBMC_Foundation/Elections/2017|2017]]
* [[Archive:XBMC_Foundation/Elections/2016|2016]]
* [[Archive:XBMC_Foundation/Elections/2014|2014]]
* [[Archive:XBMC_Foundation/Elections/2013|2013]]
* [[Archive:XBMC_Foundation/Elections/2012|2012]]

== Foundation Bylaws and other important documents ==
* [[Media:ByLaws.pdf]]
* [[Media:Delaware Incorporation Notice.pdf]]
* [[Media:Delaware Notice Of Good Standing.pdf]]
* [[Media:KodiFoundationIncorporationNotice.pdf]]
* [[Media:Kodi_Foundation_exempt.jpg]]

== Trademarks ==
{{see|Official:Trademark Policy index}}

== Financial information ==

=== Financial status ===

* Form 990 2016 - http://www.guidestar.org/FinDocuments/2016/474/565/2016-474565769-0e36f6e3-9.pdf
* Income and expenses 2015 - https://drive.google.com/file/d/0BwsEEPRqIzELOVpUa0p4endrRWc/view?usp=sharing
* Income and expenses 2014 - https://drive.google.com/file/d/0BwsEEPRqIzELVW9rMkpPUWZRSHM/view?usp=sharing
* Income and expenses 2013 - https://docs.google.com/spreadsheet/ccc?key=0AtlJ3dnHcw46dHpmeXlIV0hGaC13Z3I3b25hZWhWRGc#gid=8

''note'': 2014 and 2015 expenses are US Foundation account only.

=== Account details ===

'''Unites States account'''

* Bank: Wells Fargo
* Beneficiary: Kodi Foundation

== Legal representation ==
The XBMC Foundation is legally represented by the [[w:Software Freedom Law Center|SFLC (Software Freedom Law Center)]].

In addition the XBMC Foundation is member of [[w:Open_Invention_Network|OIN (Open Invention Network)]] since 9 July 2010. OIN is a defensive patent pool and community of patent non-aggression which enables freedom of action in Linux.

== Contact ==
For contact information, please see http://kodi.tv/about/contact/

[[Category:XBMC_Foundation-Archived]]

Kodi Foundation/Elections/2021

2022-09-21T16:24:46Z

Yol:

{{mininav| [[Kodi Foundation]] | [[Kodi Foundation/Elections|Elections]] }}

==Pre-election==
DarrenHill was voting admin, as his seat was not up for re-election.

==Nomination notice==
The following notice posted on the Team Kodi private forum, and linked to in an e-mail to all Foundation members, to give due notice about the election and to collect nominations. The Foundation bylaws state that at least ten days must be given for a notice about member decisions such as an election, which served as the nomination period.

:''Nominations for the XBMC Foundation Board Elections 2021", as written by DarrenHill''

:{| class="wikitable"
|-
|
It's already September, meaning it's time for the yearly [url=https://kodi.tv/about/xbmc-foundation]XBMC Foundation[/url] board elections again.

Due to his actual work commitments, Learningit has requested to resign his seat on the board early. With regret, the board have accepted his request and so his seat is also up for nomination.

This year board member seats up for election are: Yol, Ronie and Learningit.
Seats not up for election are Keith and DarrenHill (me)

The rules are pretty simple:

# Any team member can nominate, but the nominee must be a member of the Foundation*.
# You're allowed to nominate multiple people if you wish.
# The nominated member has the option to accept or decline their nomination.
# Only foundation members will be able to vote. *
# If a person has already been nominated, please don't nominate them again.

Please make sure to keep your nominations simple and clear. Eg:
[quote]
Nominate: <member>
Motivation: I would like to nominate <member> for the XBMC Foundation Board because <motivation>
[/quote]

In case you're nominated, please reply with something like..
[quote]
Thank you. I accept my nomination. <motivation>
[/quote]
or
[quote]
No, thanks. I decline my nomination. <Optional motivation>
[/quote]

The second post in this thread wil be updated with a list of members and the nomination status on a regular basis,
so you don't have to crawl through all posts/pages to check.

The nomination period is 1 month starting today and will end on October 16th.
Actual voting will begin after that and will be closed a couple of weeks later (if a vote is required)
Once the voting is over, the results will be announced in this thread as well as though a team email.

The actual starting date for the new board seats will be in November, when we would like to have a joint online meeting with the old and new board members as a smooth hand-over and to welcome the new board members.

* If you'd like to vote in the election, you need to be accepted as a foundation member and affirm the by-laws of the foundation.
Details on applying to join the Foundation are at: https://forum.kodi.tv/showthread.php?tid=335025 (Click here to join the Foundation)

A list of all foundation members can be found here: https://drive.google.com/open?id=1yy_gPbZPGeJUG5GDcZZScek7mEY-EdY0xY0UJaJRPHE (Foundation member list - only accessible to Google accounts logged in using your Kodi address).
|}

==Voting==
Voting started on Tuesday 16th October 2021 and ended on Saturday 6th November 2021 using the Condorcet Internet Voting Service with a ranking scale, https://civs.cs.cornell.edu/

Individual e-mail addresses from Foundation members were entered into the CIVS ballot and mailed each Foundation member with a unique voting key url. This also served as the notice for the start of the voting period.

A second notice was given out outside of the CVIS system in order to reduce the chance of someone accidentally not receiving a voting notice. Voting notices can be sent out again, but voting keys are generated based on e-mail addresses and thus prevent double voting.

The following description was used for the ballot:

:{| class="wikitable"
|-
|Elections for the Kodi Foundation Board for 2021.

We have 4 candidates for the 3 available seats, so please select your preference for who should take the seats.

Voting is available to all Kodi Foundation members, and will end just before the team meeting on 6th November.

The results will be announced during that meeting.

|}

;Final list of confirmed nominees:
* da-anda
* yol
* ronie
* phunkyfish

==Results==
24 Foundation members voted. The top three ranked become board members effective November 2021. Da-anda, Ronie and yol were elected as board members.

'''Results page:''' https://civs1.civs.us/cgi-bin/results.pl?id=E_3a8f50794fc75de6

# '''ronie''' (Condorcet winner: wins contests with all other choices)
# '''yol'''
# '''da-anda'''

Kodi Foundation/Elections/2020

2022-09-21T16:24:37Z

Yol:

{{mininav| [[Kodi Foundation]] | [[Kodi Foundation/Elections|Elections]] }}

==Pre-election==
Ronie was voting admin, as his seat was not up for re-election.

==Nomination notice==
The following notice posted on the Team Kodi private forum, and linked to in an e-mail to all Foundation members, to give due notice about the election and to collect nominations. The Foundation bylaws state that at least ten days must be given for a notice about member decisions such as an election, which served as the nomination period.

:''Nominations for the XBMC Foundation Board Elections 2020", as written by Ronie''

:{| class="wikitable"
|-
|
Hi everybody,

It's the end of August, meaning it's time for the yearly XBMC Foundation board elections again.

This year board member seats up for election are: Keith, lrusak and DarrenHill.
Seats not up for election are yol and ronie (me)

The rules are pretty simple:

1. Any team member can nominate, but the nominee must be a member of the Foundation*.
2. You're allowed to nominate multiple people if you wish.
3. The nominated member has the option to accept or decline their nomination.
4. Only foundation members will be able to vote. *
5. If a person has already been nominated, please don't nominate them again.

Please make sure to keep your nominations simple and clear. Eg:

Nominate: <member>
Motivation: I would like to nominate <member> for the XBMC Foundation Board because <motivation>

In case you're nominated, please reply with something like..
"Thank you. I accept my nomination. <motivation>"
or
"No, thanks. I decline my nomination. <Optional motivation>"

The second post in this thread wil be updated with a list of members and the nomination status on a regular basis,
so you don't have to crawl through all posts/pages to check.

The nomination period is 28 days starting today and will end on September 24th.
Actual voting will begin after that and will be closed the 19th of October.
Once the voting is over, the results will be announced in this thread as well as though a team email.

The actual starting date for the new board seats will be in November, when we would like to have a joint online meeting with the old and new board members as a smooth hand-over and to welcome the new board members.

* If you'd like to vote in the election, you need to be accepted as a foundation member and affirm the by-laws of the foundation.
You can do so here: https://forum.kodi.tv/showthread.php?tid=335025
A list of all foundation members can be found here: https://drive.google.com/open?id=1yy_gPb...Y0UJaJRPHE
|}

==Voting==
In the end there were only three nominees, so as there were 3 open seats no vote was held.

;Final list of confirmed nominees:
* Keith
* DarrenHill
* Learningit

==Results==

# '''Keith'''
# '''DarrenHill'''
# '''Learningit'''

Kodi Foundation/Elections/2019

2022-09-21T16:24:28Z

Yol:

{{mininav| [[Kodi Foundation]] | [[Kodi Foundation/Elections|Elections]] }}

==Pre-election==
DarrenHill was voting admin, as his seat was not up for re-election.

==Nomination notice==
The following notice posted on the Team Kodi private forum, and linked to in an e-mail to all Foundation members, to give due notice about the election and to collect nominations. The Foundation bylaws state that at least ten days must be given for a notice about member decisions such as an election, which served as the nomination period.

:''Nominations for the XBMC Foundation Board Elections 2019", as written by DarrenHill''

:{| class="wikitable"
|-
|
Hi everybody.

It's September and we have DevCon coming up, meaning it's time for [https://kodi.tv/about/xbmc-foundation XBMC Foundation] board elections again.

This year board member seats up for election are: Martijn and Kib.
Seats not up for election are Keith, lrusak and DarrenHill (me)

The rules are pretty simple:

1. Any team member can nominate, but the nominee must be a member of the Foundation*.
2. You're allowed to nominate multiple people if you wish.
3. The nominated member has the option to accept or decline their nomination.
4. Only foundation members will be able to vote. *
5. If a person has already been nominated, please don't nominate them again.

Please make sure to keep your nominations simple and clear. Eg:

Nominate: <member>
Motivation: I would like to nominate <member> for the XBMC Foundation Board because <motivation>

In case you're nominated, please reply with something like..
"Thank you. I accept my nomination. <motivation>"
or
"No, thanks. I decline my nomination. <Optional motivation>"

The second post in this thread wil be updated with a list of members and the nomination status on a regular basis,
so you don't have to crawl through all posts/pages to check.

The nomination period is 21 days starting today and will end on September 23rd.
Actual voting will begin after that and will close during DevCon (11th October), where the results will be announced.

The actual starting date for the new board seats will be in November, when we would like to have a joint meeting with the old and new board members as a smooth hand-over and to welcome the new board members.

* If you'd like to vote in the election, you need to be accepted as a foundation member and affirm the by-laws of the foundation.
You can do so here or by emailing me: https://forum.kodi.tv/showthread.php?tid=335025
If you are not sure whether you are a Foundation member, please check this thread as well.
|}

==Voting==
Voting started on Tuesday 24th September 2019 and ended on Friday 11th October 2019 using the Condorcet Internet Voting Service with a ranking scale, https://civs.cs.cornell.edu/

Individual e-mail addresses from Foundation members were entered into the CIVS ballot and mailed each Foundation member with a unique voting key url. This also served as the notice for the start of the voting period.

A second notice was given out outside of the CVIS system in order to reduce the chance of someone accidentally not receiving a voting notice. Voting notices can be sent out again, but voting keys are generated based on e-mail addresses and thus prevent double voting.

The following description was used for the ballot:

:{| class="wikitable"
|-
|Voting to fill the two board seats up for election this year.

|}

;Final list of confirmed nominees:
* jjd-uk
* yol
* ronie

==Results==
29 Foundation members voted. The top two ranked become board members effective October 2019. Ronie and yol were elected as board members.

'''Results page:''' https://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_5baf8df362fa250c&rkey=9b4a628ce74e3e16

# '''ronie''' (Condorcet winner: wins contests with all other choices)
# '''yol'''
# '''jjd-uk'''

Kodi Foundation/Elections

2022-09-21T16:24:15Z

Yol:

XBMC Foundation/Elections

2022-09-21T16:23:14Z

Yol: Yol moved page XBMC Foundation/Elections to Kodi Foundation/Elections

#REDIRECT [[Kodi Foundation/Elections]]

Kodi Foundation/Elections

2022-09-21T16:23:14Z

Yol: Yol moved page XBMC Foundation/Elections to Kodi Foundation/Elections

XBMC Foundation/Elections/2019

2022-09-21T16:22:57Z

Yol: Yol moved page XBMC Foundation/Elections/2019 to Kodi Foundation/Elections/2019

#REDIRECT [[Kodi Foundation/Elections/2019]]

Kodi Foundation/Elections/2019

2022-09-21T16:22:57Z

Yol: Yol moved page XBMC Foundation/Elections/2019 to Kodi Foundation/Elections/2019

{{mininav| [[XBMC Foundation]] | [[XBMC Foundation/Elections|Elections]] }}

==Pre-election==
DarrenHill was voting admin, as his seat was not up for re-election.

==Nomination notice==
The following notice posted on the Team Kodi private forum, and linked to in an e-mail to all Foundation members, to give due notice about the election and to collect nominations. The Foundation bylaws state that at least ten days must be given for a notice about member decisions such as an election, which served as the nomination period.

:''Nominations for the XBMC Foundation Board Elections 2019", as written by DarrenHill''

:{| class="wikitable"
|-
|
Hi everybody.

It's September and we have DevCon coming up, meaning it's time for [https://kodi.tv/about/xbmc-foundation XBMC Foundation] board elections again.

This year board member seats up for election are: Martijn and Kib.
Seats not up for election are Keith, lrusak and DarrenHill (me)

The rules are pretty simple:

1. Any team member can nominate, but the nominee must be a member of the Foundation*.
2. You're allowed to nominate multiple people if you wish.
3. The nominated member has the option to accept or decline their nomination.
4. Only foundation members will be able to vote. *
5. If a person has already been nominated, please don't nominate them again.

Please make sure to keep your nominations simple and clear. Eg:

Nominate: <member>
Motivation: I would like to nominate <member> for the XBMC Foundation Board because <motivation>

In case you're nominated, please reply with something like..
"Thank you. I accept my nomination. <motivation>"
or
"No, thanks. I decline my nomination. <Optional motivation>"

The second post in this thread wil be updated with a list of members and the nomination status on a regular basis,
so you don't have to crawl through all posts/pages to check.

The nomination period is 21 days starting today and will end on September 23rd.
Actual voting will begin after that and will close during DevCon (11th October), where the results will be announced.

The actual starting date for the new board seats will be in November, when we would like to have a joint meeting with the old and new board members as a smooth hand-over and to welcome the new board members.

* If you'd like to vote in the election, you need to be accepted as a foundation member and affirm the by-laws of the foundation.
You can do so here or by emailing me: https://forum.kodi.tv/showthread.php?tid=335025
If you are not sure whether you are a Foundation member, please check this thread as well.
|}

==Voting==
Voting started on Tuesday 24th September 2019 and ended on Friday 11th October 2019 using the Condorcet Internet Voting Service with a ranking scale, https://civs.cs.cornell.edu/

Individual e-mail addresses from Foundation members were entered into the CIVS ballot and mailed each Foundation member with a unique voting key url. This also served as the notice for the start of the voting period.

A second notice was given out outside of the CVIS system in order to reduce the chance of someone accidentally not receiving a voting notice. Voting notices can be sent out again, but voting keys are generated based on e-mail addresses and thus prevent double voting.

The following description was used for the ballot:

:{| class="wikitable"
|-
|Voting to fill the two board seats up for election this year.

|}

;Final list of confirmed nominees:
* jjd-uk
* yol
* ronie

==Results==
29 Foundation members voted. The top two ranked become board members effective October 2019. Ronie and yol were elected as board members.

'''Results page:''' https://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_5baf8df362fa250c&rkey=9b4a628ce74e3e16

# '''ronie''' (Condorcet winner: wins contests with all other choices)
# '''yol'''
# '''jjd-uk'''

XBMC Foundation/Elections/2020

2022-09-21T16:22:50Z

Yol: Yol moved page XBMC Foundation/Elections/2020 to Kodi Foundation/Elections/2020

#REDIRECT [[Kodi Foundation/Elections/2020]]

Kodi Foundation/Elections/2020

2022-09-21T16:22:50Z

Yol: Yol moved page XBMC Foundation/Elections/2020 to Kodi Foundation/Elections/2020

{{mininav| [[XBMC Foundation]] | [[XBMC Foundation/Elections|Elections]] }}

==Pre-election==
Ronie was voting admin, as his seat was not up for re-election.

==Nomination notice==
The following notice posted on the Team Kodi private forum, and linked to in an e-mail to all Foundation members, to give due notice about the election and to collect nominations. The Foundation bylaws state that at least ten days must be given for a notice about member decisions such as an election, which served as the nomination period.

:''Nominations for the XBMC Foundation Board Elections 2020", as written by Ronie''

:{| class="wikitable"
|-
|
Hi everybody,

It's the end of August, meaning it's time for the yearly XBMC Foundation board elections again.

This year board member seats up for election are: Keith, lrusak and DarrenHill.
Seats not up for election are yol and ronie (me)

The rules are pretty simple:

1. Any team member can nominate, but the nominee must be a member of the Foundation*.
2. You're allowed to nominate multiple people if you wish.
3. The nominated member has the option to accept or decline their nomination.
4. Only foundation members will be able to vote. *
5. If a person has already been nominated, please don't nominate them again.

Please make sure to keep your nominations simple and clear. Eg:

Nominate: <member>
Motivation: I would like to nominate <member> for the XBMC Foundation Board because <motivation>

In case you're nominated, please reply with something like..
"Thank you. I accept my nomination. <motivation>"
or
"No, thanks. I decline my nomination. <Optional motivation>"

The second post in this thread wil be updated with a list of members and the nomination status on a regular basis,
so you don't have to crawl through all posts/pages to check.

The nomination period is 28 days starting today and will end on September 24th.
Actual voting will begin after that and will be closed the 19th of October.
Once the voting is over, the results will be announced in this thread as well as though a team email.

The actual starting date for the new board seats will be in November, when we would like to have a joint online meeting with the old and new board members as a smooth hand-over and to welcome the new board members.

* If you'd like to vote in the election, you need to be accepted as a foundation member and affirm the by-laws of the foundation.
You can do so here: https://forum.kodi.tv/showthread.php?tid=335025
A list of all foundation members can be found here: https://drive.google.com/open?id=1yy_gPb...Y0UJaJRPHE
|}

==Voting==
In the end there were only three nominees, so as there were 3 open seats no vote was held.

;Final list of confirmed nominees:
* Keith
* DarrenHill
* Learningit

==Results==

# '''Keith'''
# '''DarrenHill'''
# '''Learningit'''

XBMC Foundation/Elections/2021

2022-09-21T16:22:27Z

Yol: Yol moved page XBMC Foundation/Elections/2021 to Kodi Foundation/Elections/2021

#REDIRECT [[Kodi Foundation/Elections/2021]]

Kodi Foundation/Elections/2021

2022-09-21T16:22:27Z

Yol: Yol moved page XBMC Foundation/Elections/2021 to Kodi Foundation/Elections/2021

{{mininav| [[XBMC Foundation]] | [[XBMC Foundation/Elections|Elections]] }}

==Pre-election==
DarrenHill was voting admin, as his seat was not up for re-election.

==Nomination notice==
The following notice posted on the Team Kodi private forum, and linked to in an e-mail to all Foundation members, to give due notice about the election and to collect nominations. The Foundation bylaws state that at least ten days must be given for a notice about member decisions such as an election, which served as the nomination period.

:''Nominations for the XBMC Foundation Board Elections 2021", as written by DarrenHill''

:{| class="wikitable"
|-
|
It's already September, meaning it's time for the yearly [url=https://kodi.tv/about/xbmc-foundation]XBMC Foundation[/url] board elections again.

Due to his actual work commitments, Learningit has requested to resign his seat on the board early. With regret, the board have accepted his request and so his seat is also up for nomination.

This year board member seats up for election are: Yol, Ronie and Learningit.
Seats not up for election are Keith and DarrenHill (me)

The rules are pretty simple:

# Any team member can nominate, but the nominee must be a member of the Foundation*.
# You're allowed to nominate multiple people if you wish.
# The nominated member has the option to accept or decline their nomination.
# Only foundation members will be able to vote. *
# If a person has already been nominated, please don't nominate them again.

Please make sure to keep your nominations simple and clear. Eg:
[quote]
Nominate: <member>
Motivation: I would like to nominate <member> for the XBMC Foundation Board because <motivation>
[/quote]

In case you're nominated, please reply with something like..
[quote]
Thank you. I accept my nomination. <motivation>
[/quote]
or
[quote]
No, thanks. I decline my nomination. <Optional motivation>
[/quote]

The second post in this thread wil be updated with a list of members and the nomination status on a regular basis,
so you don't have to crawl through all posts/pages to check.

The nomination period is 1 month starting today and will end on October 16th.
Actual voting will begin after that and will be closed a couple of weeks later (if a vote is required)
Once the voting is over, the results will be announced in this thread as well as though a team email.

The actual starting date for the new board seats will be in November, when we would like to have a joint online meeting with the old and new board members as a smooth hand-over and to welcome the new board members.

* If you'd like to vote in the election, you need to be accepted as a foundation member and affirm the by-laws of the foundation.
Details on applying to join the Foundation are at: https://forum.kodi.tv/showthread.php?tid=335025 (Click here to join the Foundation)

A list of all foundation members can be found here: https://drive.google.com/open?id=1yy_gPbZPGeJUG5GDcZZScek7mEY-EdY0xY0UJaJRPHE (Foundation member list - only accessible to Google accounts logged in using your Kodi address).
|}

==Voting==
Voting started on Tuesday 16th October 2021 and ended on Saturday 6th November 2021 using the Condorcet Internet Voting Service with a ranking scale, https://civs.cs.cornell.edu/

Individual e-mail addresses from Foundation members were entered into the CIVS ballot and mailed each Foundation member with a unique voting key url. This also served as the notice for the start of the voting period.

A second notice was given out outside of the CVIS system in order to reduce the chance of someone accidentally not receiving a voting notice. Voting notices can be sent out again, but voting keys are generated based on e-mail addresses and thus prevent double voting.

The following description was used for the ballot:

:{| class="wikitable"
|-
|Elections for the Kodi Foundation Board for 2021.

We have 4 candidates for the 3 available seats, so please select your preference for who should take the seats.

Voting is available to all Kodi Foundation members, and will end just before the team meeting on 6th November.

The results will be announced during that meeting.

|}

;Final list of confirmed nominees:
* da-anda
* yol
* ronie
* phunkyfish

==Results==
24 Foundation members voted. The top three ranked become board members effective November 2021. Da-anda, Ronie and yol were elected as board members.

'''Results page:''' https://civs1.civs.us/cgi-bin/results.pl?id=E_3a8f50794fc75de6

# '''ronie''' (Condorcet winner: wins contests with all other choices)
# '''yol'''
# '''da-anda'''

Kodi Foundation/Elections/2022

2022-09-21T16:21:31Z

Yol: Created page with "{{mininav| Kodi Foundation | Elections }} ==Pre-election== yol was voting admin, as his seat was not up for re-election. ==Nomination notic..."

{{mininav| [[Kodi Foundation]] | [[Kodi Foundation/Elections|Elections]] }}

==Pre-election==
yol was voting admin, as his seat was not up for re-election.

==Nomination notice==
The following notice posted on the Team Kodi private forum, and linked to in an e-mail to all Foundation members, to give due notice about the election and to collect nominations. The Foundation bylaws state that at least ten days must be given for a notice about member decisions such as an election, which served as the nomination period.

:''Nominations for the Kodi Foundation Board Elections 2022", as written by yol''

:{| class="wikitable"
|-
|
It's time for the yearly [url=https://kodi.tv/about/foundation/]Kodi Foundation[/url] board elections again!

This year board member seats up for election are: Keith and DarrenHill. Seats not up for election are da-anda, ronie and yol (me).

The rules are pretty simple:
[list=1]
[*]Any team member can nominate, but the nominee must be a member of the Foundation*.
[*]You're allowed to nominate multiple people if you wish.
[*]The nominated member has the option to accept or decline their nomination.
[*]Only foundation members will be able to vote. *
[*]If a person has already been nominated, please don't nominate them again.
[/list]
Please make sure to keep your nominations simple and clear. Eg:
[quote]
Nominate: <member> Motivation: I would like to nominate <member> for the XBMC Foundation Board because <motivation>
[/quote]
In case you're nominated, please reply with something like..
[quote]
Thank you. I accept my nomination. <motivation>
[/quote]
or
[quote]
No, thanks. I decline my nomination. <Optional motivation>
[/quote]
The second post in this thread will be updated with a list of members and the nomination status on a regular basis, so you don't have to crawl through all posts/pages to check.

The nomination period is[b] 1 month starting today and will end on September 20th[/b].
Actual voting will begin after that and will be closed a couple of weeks later (if a vote is required).
Once the voting is over, the results will be announced in this thread as well as through a team email.

The actual starting date for the new board seats will be in November, when we would like to have a joint online meeting with the old and new board members as a smooth hand-over and to welcome the new board members.

* If you'd like to vote in the election, you need to be accepted as a foundation member and affirm the by-laws of the foundation.
Details on applying to join the Foundation are at: [url=https://forum.kodi.tv/showthread.php?tid=335025]Click here to join the foundation[/url]
A list of all foundation members can be found here: [url]https://drive.google.com/open?id=1yy_gPbZPGeJUG5GDcZZScek7mEY-EdY0xY0UJaJRPHE[/url] (Foundation member list - only accessible to Google accounts logged in using your Kodi address).
|}

==Voting==
As two persons were nominated for two seats, voting was skipped.

==Results==
DarrenHill and keith continue to serve on the board.

Google Summer of Code/2022

2022-02-13T16:59:08Z

Yol:

{{GSOC_nav}}
{{mininav| [[Google Summer of Code]] }}
[[File:GSOC_2016_logo.png|left|150px]]Welcome to the Kodi [http://summerofcode.withgoogle.com Google Summer of Code] ideas page.

'''This page is currently work in progress. Kodi has applied as mentoring organization for GSoC 2022. Accepted organizations will be announced on March 7.'''

We encourage interested students of all ethnicities and genders to review some of the ideas on this page, and then feel free to provide input on any ideas you may have in the '''[https://forum.kodi.tv/forumdisplay.php?fid=317 Kodi GSoC 2022 forum]''' and chat about any project you’d love to cover. To propose a project, see '''[[#Students project proposal ideas]]'''.



== About Us ==
As there may be many students who have landed here as a result of GSoC, but are unfamiliar with the project, here are a few resources that may help explain what we are about.

:Kodi (formerly known as XBMC) is an award-winning free and open source (GPL) software media player and entertainment hub for digital media, designed around the 10-foot interface (living room) environment. Created in 2003 by a group of like minded programmers, Kodi is a non-profit project run and developed by volunteers located around the world. More than 1000 software developers have contributed to Kodi, and 300-plus translators have worked to expand its reach, making it available in more than 70 languages. For more information, see the page '''[[Kodi]]'''.

<br />
To get an idea of what Kodi is truly capable of, it really must be seen. Check out a few other user-created videos:<br />
[http://www.youtube.com/watch?v=NcogPuSo-DU Kodi with the default Confluence skin]<br />
[http://www.youtube.com/watch?v=4asUCtE0ONU Kodi with Aeon Nox skin]<br />
[http://www.youtube.com/watch?v=4NR57ELY28s Kodi on Raspberry Pi]<br />
[http://www.youtube.com/watch?v=e_0PB5hfz_k Kodi's new PVR functionality]<br />
<br />

Kodi is written primarily in C++ and runs on a variety of platforms including Android, iOS, Linux, OS X, and Windows. It has been ported to work on several low-power platforms including the Raspberry Pi and Android.

Kodi was a mentoring organization in 2008, 2012, 2013, 2015, 2017, 2018, 2019, 2020 and 2021 and had team members involved in GSoC for other projects during 2011.

If Kodi is selected as a mentoring organization for 2022, students will need to review the Overview of a good project proposal, follow the outline for proposals when applying, and review the list of project ideas detailed below. Students are welcome to propose ideas outside the list and are encouraged to be as creative as they like.

=== Mentors ===
All mentors and backup mentors are extremely experienced in the Kodi codebase and will thus be able to assist students in getting to know the codebase and in quickly identifying projects that are both achievable for someone unfamiliar with the internal workings of Kodi and desirable to the wider Kodi community.

==Prerequisites==
Some coding skills, basic familiarity with Git, solid understanding and interest in programming. Ability to quickly understand existing code is beneficial.

== Project Proposals ==
=== Overview ===
Qualifications for a good Summer of Code proposal:
* Discrete, well-defined, modular
* Comprised of a series of measurable sub-goals
* Based on open specs that are available free of charge
* Based on complete specs
An example of a good proposal is the implementation of a new feature or function that is not yet available in Kodi.

An example of a less desirable proposal is one that's not as measurable, such as refactoring an existing API. Bad proposals tend to be ones that would require touching a lot of core code.

To re-iterate:
* Localized/isolated code projects = ''good''
* Global code refactoring = ''bad''
* A project should have a set of subgoals, so even if the end goal turns out to be too big some of the parts will be of benefit.
* Not too big! This is an important problem when choosing a project, while it is fun to think about solving a grand project its not always realistic. It's better to finish a smaller project than to start a grand one.

Projects can have a workload of either 175 hours or 350 hours.

=== Where to submit proposals ===
In addition to submitting to the [https://g.go/gsoc Google Summer of Code] website, you are highly encouraged to submit your idea/proposal to the [https://forum.kodi.tv/forumdisplay.php?fid=317 Kodi forum] for discussion. Any proposal not submitted to the forum for discussion will likely not be considered.

=== Outline for proposals ===
{{divbox|blue||
PROJECT TITLE GOES HERE

* '''Name:'''
* '''forum/e-mail:'''
* '''Summary:''' A somewhat small but explanatory walk through of the project. It should not be overly detailed just enough to understand the problem trying to be fixed and how this project opt to solve it.
* '''How will I achieve this:''' Explain how the project will be done, what technologies are needed and how to implement them.
* '''What will the project focus on:''' Explain what the project will focus on, what is the important parts of the project.
* '''Benefits:''' Who will benefit and why from this project. Think about what a user or developer may need or do to benefit from it. Why does it benefit many users.
* '''Goals:''' What is the goal of the project, a project may not always solve the problem entirely as it may take to much time. Think hard about what can be accomplished during a summer with your skill and deduct that quite a bit. If the project can't be done after this perhaps its better to opt for a smaller one or one with subgoals.
* '''What does it touch in Kodi:''' Think about what parts of the code this may touch, Kodi is a big application and a lot of the code is spread out and very complex. If a project touches to much it may be impossible to complete.
* '''Requirements:''' What is needed to complete the project, what code language knowledge what hardware etc.
* '''Possible mentors:''' Place to add possible mentors (Team-Kodi will add this).
* '''Workload:''' Either 175 or 350 hours.
}}

== Team-Kodi proposal ideas up for discussion ==

=== Portal integration and Flatpak improvements in Kodi ===
'''Description:''' Integrate libPortal https://github.com/flatpak/libportal into Kodi, to handle fileaccess and other sandbox relevant factors as far as possible. We could also improve some other sandbox features like handling of binary addons, automatic flatpak build checks and build improvements.

'''Expected outcome:''' Integration of libPortal into Kodi and possibly other Flatpak improvements

'''Skills preferred:''' C++, libPortal

'''Possible mentors:''' Razze

'''Difficulty:''' Risky/Exploratory

'''Type:''' Linux/Kodi Core

'''Workload:''' xxx hours

=== Explore building binary addons in rust ===
'''Description:''' While Kodi has python addons, it can also handle binary addons. But these need to be build one by one for each platform and also might fail on errors. Rust might help with both of those problems and more. The idea is to use the api we have but via rust ffi and see where that leads us.

'''Expected outcome:''' Documentation and templates on how to use rust with kodi. In the best case also one or two example addons.

'''Skills preferred:''' C++, Rust, C

'''Possible mentors:''' spiff, Razze

'''Difficulty:''' Hard

'''Type:''' Binary addon development

'''Workload:''' xxx hours

=== Finish the new web interface ===
'''Description:''' Kodi has a in development webinterface by the name of elm-chorus (https://github.com/xbmc/elm-chorus) which is written in Elm and is still missing some features of Chorus2 (the old interface). So the idea would be to bring it up to speed and do some additional styling and packaging work.

'''Expected outcome:''' Finished shipable version of the webinterface

'''Skills preferred:''' HTML, CSS, Elm

'''Possible mentors:''' Razze

'''Difficulty:''' Medium

'''Type:''' Webinterface development

'''Workload:''' xxx hours




===Using fuzz testing to fuzz test Kodi===
'''Description:''' Adding fuzz testing to Kodi would be very valuable to find problems in the current code base. Especially security problems. First step would be choosing a framework either American fuzzy lop, libFuzzer or other similar projects. After we decided on that it would be time to start to fuzz different methods that are widely used in Kodi and try to expose flaws in those. If this leads to success, it should be documented and made repeatable.

'''Expected outcome:''' Being able to easily add more fuzz tests and having the process to do this documented.

'''Skills preferred:''' C++, CMake

'''Possible mentors:''' Razze

'''Difficulty:''' Medium

'''Type:''' Risky/Exploratory

'''Workload:''' xxx hours



===Other ideas===
These ideas still need expanding and/or assigned a potential mentor. If one of these ideas interests you, feel free to ask for more info in the GSoC 2022 forum area. We may be able to assign a mentor if enough interest is shown
*Improvements to Retroplayer (retro gaming integrated in Kodi core)
*Visual Studio Code addon to validate/syntax highlight Kodi Addons

*High quality scalers for OpenGL(GLSL). Scale Y and UV plane separately (possible mentors: velocity)


*Implementing a performance critical element of Kodi in Rust
*Add multiroom audio support where each Kodi instance can act as client or server. Maybe Snapcast could be used somehow.

=== More ===
We feel it is important to note that, while we are interested in a focus on the listed ideas, we would like to stress passion, expertise, and creativity above all else. If you would like to do something completely different, definitely send in that proposal. The ideas listed above are, as always, merely suggestions. We will be interested in any idea, so long as you can communicate your interest, your background, and your solution the problem.

== Students project proposal ideas ==

Submit your own proposals on the '''[https://forum.kodi.tv/forumdisplay.php?fid=317 Kodi GSoC forum]'''. They can be as big or as small as you feel you can comfortably accomplish in the defined time (175 or 350 hours). In the end, it's better to have a smaller, completed project, rather than a larger, incomplete project.

To submit a proposal idea:
# Copy the text from '''[[#Outline for proposals]]'''.
# Create a new forum post '''[https://forum.kodi.tv/forumdisplay.php?fid=317 HERE]''' and paste the text.
# Fill out everything using your specific proposal.

[[Category:Google Summer of Code]]

Google Summer of Code/2022

2022-02-13T16:57:42Z

Yol:

{{GSOC_nav}}
{{mininav| [[Google Summer of Code]] }}
[[File:GSOC_2016_logo.png|left|150px]]Welcome to the Kodi [http://summerofcode.withgoogle.com Google Summer of Code] ideas page.

'''This page is currently work in progress. Kodi has applied as mentoring organization for GSoC 2022. Accepted organizations will be announced on March 7.'''

We encourage interested students of all ethnicities and genders to review some of the ideas on this page, and then feel free to provide input on any ideas you may have in the '''[https://forum.kodi.tv/forumdisplay.php?fid=317 Kodi GSoC 2022 forum]''' and chat about any project you’d love to cover. To propose a project, see '''[[#Students project proposal ideas]]'''.



== About Us ==
As there may be many students who have landed here as a result of GSoC, but are unfamiliar with the project, here are a few resources that may help explain what we are about.

:Kodi (formerly known as XBMC) is an award-winning free and open source (GPL) software media player and entertainment hub for digital media, designed around the 10-foot interface (living room) environment. Created in 2003 by a group of like minded programmers, Kodi is a non-profit project run and developed by volunteers located around the world. More than 1000 software developers have contributed to Kodi, and 300-plus translators have worked to expand its reach, making it available in more than 70 languages. For more information, see the page '''[[Kodi]]'''.

<br />
To get an idea of what Kodi is truly capable of, it really must be seen. Check out a few other user-created videos:<br />
[http://www.youtube.com/watch?v=NcogPuSo-DU Kodi with the default Confluence skin]<br />
[http://www.youtube.com/watch?v=4asUCtE0ONU Kodi with Aeon Nox skin]<br />
[http://www.youtube.com/watch?v=4NR57ELY28s Kodi on Raspberry Pi]<br />
[http://www.youtube.com/watch?v=e_0PB5hfz_k Kodi's new PVR functionality]<br />
<br />

Kodi is written primarily in C++ and runs on a variety of platforms including Android, iOS, Linux, OS X, and Windows. It has been ported to work on several low-power platforms including the Raspberry Pi and Android.

Kodi was a mentoring organization in 2008, 2012, 2013, 2015, 2017, 2018, 2019, 2020 and 2021 and had team members involved in GSoC for other projects during 2011.

If Kodi is selected as a mentoring organization for 2022, students will need to review the Overview of a good project proposal, follow the outline for proposals when applying, and review the list of project ideas detailed below. Students are welcome to propose ideas outside the list and are encouraged to be as creative as they like.

=== Mentors ===
All mentors and backup mentors are extremely experienced in the Kodi codebase and will thus be able to assist students in getting to know the codebase and in quickly identifying projects that are both achievable for someone unfamiliar with the internal workings of Kodi and desirable to the wider Kodi community.

==Prerequisites==
Some coding skills, basic familiarity with Git, solid understanding and interest in programming. Ability to quickly understand existing code is beneficial.

== Project Proposals ==
=== Overview ===
Qualifications for a good Summer of Code proposal:
* Discrete, well-defined, modular
* Comprised of a series of measurable sub-goals
* Based on open specs that are available free of charge
* Based on complete specs
An example of a good proposal is the implementation of a new feature or function that is not yet available in Kodi.

An example of a less desirable proposal is one that's not as measurable, such as refactoring an existing API. Bad proposals tend to be ones that would require touching a lot of core code.

To re-iterate:
* Localized/isolated code projects = ''good''
* Global code refactoring = ''bad''
* A project should have a set of subgoals, so even if the end goal turns out to be too big some of the parts will be of benefit.
* Not too big! This is an important problem when choosing a project, while it is fun to think about solving a grand project its not always realistic. It's better to finish a smaller project than to start a grand one.

Projects can have a workload of either 175 hours or 350 hours.

=== Where to submit proposals ===
In addition to submitting to the [https://g.go/gsoc Google Summer of Code] website, you are highly encouraged to submit your idea/proposal to the [https://forum.kodi.tv/forumdisplay.php?fid=317 Kodi forum] for discussion. Any proposal not submitted to the forum for discussion will likely not be considered.

=== Outline for proposals ===
{{divbox|blue||
PROJECT TITLE GOES HERE

* '''Name:'''
* '''forum/e-mail:'''
* '''Summary:''' A somewhat small but explanatory walk through of the project. It should not be overly detailed just enough to understand the problem trying to be fixed and how this project opt to solve it.
* '''How will I achieve this:''' Explain how the project will be done, what technologies are needed and how to implement them.
* '''What will the project focus on:''' Explain what the project will focus on, what is the important parts of the project.
* '''Benefits:''' Who will benefit and why from this project. Think about what a user or developer may need or do to benefit from it. Why does it benefit many users.
* '''Goals:''' What is the goal of the project, a project may not always solve the problem entirely as it may take to much time. Think hard about what can be accomplished during a summer with your skill and deduct that quite a bit. If the project can't be done after this perhaps its better to opt for a smaller one or one with subgoals.
* '''What does it touch in Kodi:''' Think about what parts of the code this may touch, Kodi is a big application and a lot of the code is spread out and very complex. If a project touches to much it may be impossible to complete.
* '''Requirements:''' What is needed to complete the project, what code language knowledge what hardware etc.
* '''Possible mentors:''' Place to add possible mentors (Team-Kodi will add this).
}}

== Team-Kodi proposal ideas up for discussion ==

=== Portal integration and Flatpak improvements in Kodi ===
'''Description:''' Integrate libPortal https://github.com/flatpak/libportal into Kodi, to handle fileaccess and other sandbox relevant factors as far as possible. We could also improve some other sandbox features like handling of binary addons, automatic flatpak build checks and build improvements.

'''Expected outcome:''' Integration of libPortal into Kodi and possibly other Flatpak improvements

'''Skills preferred:''' C++, libPortal

'''Possible mentors:''' Razze

'''Difficulty:''' Risky/Exploratory

'''Type:''' Linux/Kodi Core

=== Explore building binary addons in rust ===
'''Description:''' While Kodi has python addons, it can also handle binary addons. But these need to be build one by one for each platform and also might fail on errors. Rust might help with both of those problems and more. The idea is to use the api we have but via rust ffi and see where that leads us.

'''Expected outcome:''' Documentation and templates on how to use rust with kodi. In the best case also one or two example addons.

'''Skills preferred:''' C++, Rust, C

'''Possible mentors:''' spiff, Razze

'''Difficulty:''' Hard

'''Type:''' Binary addon development

=== Finish the new web interface ===
'''Description:''' Kodi has a in development webinterface by the name of elm-chorus (https://github.com/xbmc/elm-chorus) which is written in Elm and is still missing some features of Chorus2 (the old interface). So the idea would be to bring it up to speed and do some additional styling and packaging work.

'''Expected outcome:''' Finished shipable version of the webinterface

'''Skills preferred:''' HTML, CSS, Elm

'''Possible mentors:''' Razze

'''Difficulty:''' Medium

'''Type:''' Webinterface development




===Using fuzz testing to fuzz test Kodi===
'''Description:''' Adding fuzz testing to Kodi would be very valuable to find problems in the current code base. Especially security problems. First step would be choosing a framework either American fuzzy lop, libFuzzer or other similar projects. After we decided on that it would be time to start to fuzz different methods that are widely used in Kodi and try to expose flaws in those. If this leads to success, it should be documented and made repeatable.

'''Expected outcome:''' Being able to easily add more fuzz tests and having the process to do this documented.

'''Skills preferred:''' C++, CMake

'''Possible mentors:''' Razze

'''Difficulty:''' Medium

'''Type:''' Risky/Exploratory



===Other ideas===
These ideas still need expanding and/or assigned a potential mentor. If one of these ideas interests you, feel free to ask for more info in the GSoC 2022 forum area. We may be able to assign a mentor if enough interest is shown
*Improvements to Retroplayer (retro gaming integrated in Kodi core)
*Visual Studio Code addon to validate/syntax highlight Kodi Addons

*High quality scalers for OpenGL(GLSL). Scale Y and UV plane separately (possible mentors: velocity)


*Implementing a performance critical element of Kodi in Rust
*Add multiroom audio support where each Kodi instance can act as client or server. Maybe Snapcast could be used somehow.

=== More ===
We feel it is important to note that, while we are interested in a focus on the listed ideas, we would like to stress passion, expertise, and creativity above all else. If you would like to do something completely different, definitely send in that proposal. The ideas listed above are, as always, merely suggestions. We will be interested in any idea, so long as you can communicate your interest, your background, and your solution the problem.

== Students project proposal ideas ==

Submit your own proposals on the '''[https://forum.kodi.tv/forumdisplay.php?fid=317 Kodi GSoC forum]'''. They can be as big or as small as you feel you can comfortably accomplish in the defined time (175 or 350 hours). In the end, it's better to have a smaller, completed project, rather than a larger, incomplete project.

To submit a proposal idea:
# Copy the text from '''[[#Outline for proposals]]'''.
# Create a new forum post '''[https://forum.kodi.tv/forumdisplay.php?fid=317 HERE]''' and paste the text.
# Fill out everything using your specific proposal.

[[Category:Google Summer of Code]]

Google Summer of Code/2022

2022-02-05T18:56:10Z

Yol:

{{GSOC_nav}}
{{mininav| [[Google Summer of Code]] }}
[[File:GSOC_2016_logo.png|left|150px]]Welcome to the Kodi [http://summerofcode.withgoogle.com Google Summer of Code] ideas page.

'''This page is currently work in progress. Kodi has applied as mentoring organization for GSoC 2022. Accepted organizations will be announced on March 7.'''

We encourage interested students of all ethnicities and genders to review some of the ideas on this page, and then feel free to provide input on any ideas you may have in the '''[https://forum.kodi.tv/forumdisplay.php?fid=315 Kodi GSoC 2022 forum]''' and chat about any project you’d love to cover. To propose a project, see '''[[#Students project proposal ideas]]'''.



== About Us ==
As there may be many students who have landed here as a result of GSoC, but are unfamiliar with the project, here are a few resources that may help explain what we are about.

:Kodi (formerly known as XBMC) is an award-winning free and open source (GPL) software media player and entertainment hub for digital media, designed around the 10-foot interface (living room) environment. Created in 2003 by a group of like minded programmers, Kodi is a non-profit project run and developed by volunteers located around the world. More than 500 software developers have contributed to Kodi, and 100-plus translators have worked to expand its reach, making it available in more than 60 languages. For more information, see the page '''[[Kodi]]'''.

<br />
To get an idea of what Kodi is truly capable of, it really must be seen. Check out a few other user-created videos:<br />
[http://www.youtube.com/watch?v=NcogPuSo-DU Kodi with the default Confluence skin]<br />
[http://www.youtube.com/watch?v=4asUCtE0ONU Kodi with Aeon Nox skin]<br />
[http://www.youtube.com/watch?v=4NR57ELY28s Kodi on Raspberry Pi]<br />
[http://www.youtube.com/watch?v=e_0PB5hfz_k Kodi's new PVR functionality]<br />
<br />

Kodi is written primarily in c++ and runs on a variety of platforms including Android, iOS, Linux, OS X, and Windows. It has been ported to work on several low-power platforms including the Raspberry Pi and Android.

Kodi was a mentoring organization in 2008, 2012, 2013, 2015, 2017, 2018, 2019, 2020 and 2021 and had team members involved in GSoC for other projects during 2011.

If Kodi is selected as a mentoring organization for 2022, students will need to review the Overview of a good project proposal, follow the outline for proposals when applying, and review the list of project ideas detailed below. Students are welcome to propose ideas outside the list and are encouraged to be as creative as they like.

=== Mentors ===
All mentors and backup mentors are extremely experienced in the Kodi codebase and will thus be able to assist students in getting to know the codebase and in quickly identifying projects that are both achievable for someone unfamiliar with the internal workings of Kodi and desirable to the wider Kodi community.

==Prerequisites==
Some coding skills, basic familiarity with Git, solid understanding and interest in programming. Ability to quickly understand existing code is beneficial.

== Project Proposals ==
=== Overview ===
Qualifications for a good Summer of Code proposal:
* Discrete, well-defined, modular
* Comprised of a series of measurable sub-goals
* Based on open specs that are available free of charge
* Based on complete specs
An example of a good proposal is the implementation of a new feature or function that is not yet available in Kodi.

An example of a less desirable proposal is one that's not as measurable, such as refactoring an existing API. Bad proposals tend to be ones that would require touching a lot of core code.

To re-iterate:
* Localized/isolated code projects = ''good''
* Global code refactoring = ''bad''
* A project should have a set of subgoals, so even if the end goal turns out to be too big some of the parts will be of benefit.
* Not too big! This is an important problem when choosing a project, while it is fun to think about solving a grand project its not always realistic. It's better to finish a smaller project than to start a grand one.

Projects can have a workload of either 175 hours or 350 hours.

=== Where to submit proposals ===
In addition to submitting to the [https://g.go/gsoc Google Summer of Code] website, you are highly encouraged to submit your idea/proposal to the [https://forum.kodi.tv/forumdisplay.php?fid=315 Kodi forum] for discussion. Any proposal not submitted to the forum for discussion will likely not be considered.

=== Outline for proposals ===
{{divbox|blue||
PROJECT TITLE GOES HERE

* '''Name:'''
* '''forum/e-mail:'''
* '''Summary:''' A somewhat small but explanatory walk through of the project. It should not be overly detailed just enough to understand the problem trying to be fixed and how this project opt to solve it.
* '''How will I achieve this:''' Explain how the project will be done, what technologies are needed and how to implement them.
* '''What will the project focus on:''' Explain what the project will focus on, what is the important parts of the project.
* '''Benefits:''' Who will benefit and why from this project. Think about what a user or developer may need or do to benefit from it. Why does it benefit many users.
* '''Goals:''' What is the goal of the project, a project may not always solve the problem entirely as it may take to much time. Think hard about what can be accomplished during a summer with your skill and deduct that quite a bit. If the project can't be done after this perhaps its better to opt for a smaller one or one with subgoals.
* '''What does it touch in Kodi:''' Think about what parts of the code this may touch, Kodi is a big application and a lot of the code is spread out and very complex. If a project touches to much it may be impossible to complete.
* '''Requirements:''' What is needed to complete the project, what code language knowledge what hardware etc.
* '''Possible mentors:''' Place to add possible mentors (Team-Kodi will add this).
}}

== Team-Kodi proposal ideas up for discussion ==

=== Explore building binary addons in rust ===
'''Description:''' While Kodi has python addons, it can also handle binary addons. But these need to be build one by one for each platform and also might fail on errors. Rust might help with both of those problems and more. The idea is to use the api we have but via rust ffi and see where that leads us.

'''Expected outcome:''' Documentation and templates on how to use rust with kodi. In the best case also one or two example addons.

'''Skills preferred:''' C++, Rust, C

'''Possible mentors:''' spiff, Razze

'''Difficulty:''' Hard

'''Type:''' Binary addon development

=== Finish the new web interface ===
'''Description:''' Kodi has a in development webinterface by the name of elm-chorus (https://github.com/xbmc/elm-chorus) which is written in Elm and is still missing some features of Chorus2 (the old interface). So the idea would be to bring it up to speed and do some additional styling and packaging work.

'''Expected outcome:''' Finished shipable version of the webinterface

'''Skills preferred:''' HTML, CSS, Elm

'''Possible mentors:''' Razze

'''Difficulty:''' Medium

'''Type:''' Webinterface development



===Achievements in RetroPlayer===

'''Description''': Retroarch has developed support for achievements in certain select libretro cores. This project would consist of porting whatever work might be portable and otherwise integrating the existing libretro achievement system into Kodi's RetroPlayer implemented using Kodi's UI system. Could be tackled a few different ways, including simply linking the user to the retroachievements.org or creating a full achievement database in Kodi.

'''Expected Outcome''': Users should be able to see their achievements in Kodi. Player manager and Player profile support may be in development concurrently, so thought should be given to those systems.

'''Skills preferred''': C++, python, possibly php

'''Possible mentor''': gusandrianos, NikosSiak

'''Difficulty''': medium

'''Type''': Fun/Peripheral

'''Notes''': Garbear has broken down the Retroplayer project into manageable pieces including input, core, game add-ons, peripheral add-ons, netplay, a game library implementation, and shaders to do things like emulate a CRT monitor. This is one example, but many pieces are currently being worked on or are near completion, and many more could use help from a student familiar with the area. Visit the retroplayer section of the Kodi forum to see all the major projects still to do.

===Add-ons===
====Automatic add-on checker for binary add-ons====
'''Description:''' Kodis add-on checker checks each Kodi add-on PR on GitHub for certain problems, which ultimately makes reviewing Python add-ons easier for the team. But the other type of add-ons, binary add-ons is not being checked so far, which makes reviews and coding guidelines hard to handle. Thus it would be nice to also check those add-ons, either via the current checker written in Python or a new binary add-on specific checker. Goals would include checking the addon.xml, the C++ code and a check for potentially malicious code.

'''Expected outcome:''' Being able to run the checker against all binary repo PRs on GitHub.

'''Skills preferred:''' Python, C++

'''Possible mentors:''' Razze

'''Difficulty:''' Hard

'''Type:''' Low-hanging fruit

===Using fuzz testing to fuzz test Kodi===
'''Description:''' Adding fuzz testing to Kodi would be very valuable to find problems in the current code base. Especially security problems. First step would be choosing a framework either American fuzzy lop, libFuzzer or other similar projects. After we decided on that it would be time to start to fuzz different methods that are widely used in Kodi and try to expose flaws in those. If this leads to success, it should be documented and made repeatable.

'''Expected outcome:''' Being able to easily add more fuzz tests and having the process to do this documented.

'''Skills preferred:''' C++, CMake

'''Possible mentors:''' Razze

'''Difficulty:''' Medium

'''Type:''' Risky/Exploratory



===Other ideas===
These ideas still need expanding and/or assigned a potential mentor. If one of these ideas interests you, feel free to ask for more info in the GSoC 2020 forum area. We may be able to assign a mentor if enough interest is shown
*Improvements to Retroplayer (retro gaming integrated in Kodi core)
*Visual Studio Code addon to validate/syntax highlight Kodi Addons

*High quality scalers for OpenGL(GLSL). Scale Y and UV plane separately (possible mentors: velocity)


*Implementing a performance critical element of kodi in rust
*Add multiroom audio support where each kodi instance can act as client or server. Maybe snapcast could be used somehow.

=== More ===
We feel it is important to note that, while we are interested in a focus on the listed ideas, we would like to stress passion, expertise, and creativity above all else. If you would like to do something completely different, definitely send in that proposal. The ideas listed above are, as always, merely suggestions. We will be interested in any idea, so long as you can communicate your interest, your background, and your solution the problem.

== Students project proposal ideas ==

Submit your own proposals on the '''[https://forum.kodi.tv/forumdisplay.php?fid=315 Kodi GSoC forum]'''. They can be as big or as small as you feel you can comfortably accomplish between '''June 7''' and '''August 23'''. In the end, it's better to have a smaller, completed project, rather than a larger, incomplete project.

To submit a proposal idea:
# Copy the text from '''[[#Outline for proposals]]'''.
# Create a new forum post '''[https://forum.kodi.tv/forumdisplay.php?fid=315 HERE]''' and paste the text.
# Fill out everything using your specific proposal.

[[Category:Google Summer of Code]]

HOW-TO:Submit a bug report

2021-03-30T07:25:57Z

Yol: update to Matrix

{{mininav| [[Development]] {{l2| [[Troubleshooting]] }} }}
{{see also|Log file|Bug tracker|Troubleshooting}}
So, you think you've found a bug? Great! Thanks for being proactive enough to make it this far. If you want to ensure that your report gets attention from the right people it is paramount that you answer the following questions. Please read this document in its entirety before continuing on your adventure.

== Has the bug been reported already? ==

Duplicate bug reports only clutter the communications channels with the developers. Keeping the discussion in one place not only makes the topic easy to follow but centralizes all details for easier review. Before posting your bug report, it is important to ensure that you haven't been beat to it. There are two places to look, the [http://forum.kodi.tv Kodi Forum] and [https://github.com/xbmc/xbmc/issues Github Tracker]. Both have a search button. Please use it! If you find a thread on the forum or issue on the bug tracker, please read through it and add any new information that you can provide. "Me too" and "bump" posts don't really help the matter without additional details, so please refrain.

{{divbox|red||'''Note:''' Do not use '''trac.kodi.tv''' for BUG reporting or Discussions on possible bugs anymore. [https://github.com/xbmc/xbmc/issues Github] is the new location for bug reporting.<br />
<br />
Also, '''Github issues are supported for Kodi 19 Matrix and upwards'''. Lower versions (upto v18 Leia) are no longer officially supported. }}

== Ok, so my bug is new. Now what? ==
Now that you have made sure that your problem is unique, it is time to open a dialog with the community. Where to do this is a question of your certainty that the problem is in fact a bug. Keep in mind that reporting the bug puts some responsibility on you to answer any questions a developer may have. You may want to consider "subscribing" to your forum thread (you'll be CC'd updates automatically by the bug tracker) and ensure that your registered email is one that you keep track of!

=== Yes! This must be a bug! ===
If you are sure that you're dealing with a bug, (crash, hang, failed playback, corruption, etc) please go straight to the [https://github.com/xbmc/xbmc/issues Github Tracker] and create a new issue. Be sure to fill in as information as possible, use your best judgement.

=== Hrm...I think this is a bug... ===
If the problem is more one of behaviour you didn't expect, please start in the [http://forum.kodi.tv forums] first. Kodi has many features, with these features comes design decisions. It is very possible that the behaviour you expect is not that which the developer envisioned. There is also a possibility that the feature is very complicated at the code level and that the behavior you expect would be very difficult or impossible to create. Regardless, bouncing your ideas off of forum users (most developers are forums users too!) to confirm and clarify before opening a issue on the [https://github.com/xbmc/xbmc/issues Github Tracker]. You may be opening a feature request instead! ;)

== Right, so what information do you guys need? ==
Regardless of where you're posting your report, if you expect someone to take interest in it, they will expect details from you. Don't forget, we're doing this stuff in our free time, too! Post as much of this stuff as you can upfront. We'd rather spend our time fixing problems than digging for details. If you need further help obtaining something, feel free to ask (then come back and update the wiki!).

=== Debug log ===
{{main|Log file}}
A '''[[Log file|debug log]]''' is '''ESSENTIAL''' to any and all bug reports. Debug logs are disabled by default; first, you must simply [[Settings/System/Logging|enable debugging]]. Without it your report stands a good chance of being overlooked. It provides nearly all of the information about what was going on and what you were doing in the application. The log file also contains some of the details you'll need to fill out a new issue on the [https://github.com/xbmc/xbmc/issues Github Tracker]. So it might pay to glance through it yourself.

{{divbox|yellow||'''Note:''' When submitting debug logs into Github or onto the forum, '''ALWAYS use a text paste site''' like https://paste.kodi.tv , https://pastebin.com or https://paste.ubuntu.com (supports larger files), rather than posting logs directly.}}

=== Detailed instructions to reproduce ===
To actually solve your problem, we need to be able to reproduce it. The more descriptive the instructions, the better chances are that they'll work for others screenshots go a long way in some cases use sites like [http://imgur.com imgur], [http://www.snag.gy snaggy] or [http://www.postimage.org/ postimage]. Sit down and reproduce the problem a few times, first, to make sure you understand it. If the problem is "random," [[Settings/System/Logging|enable debugging]] during normal use. Restart the application often to keep the log file short. The more time you spend isolating the problem, the quicker a developer will be able to reproduce and fix it. Please take your time with this step!

=== Sample file ===
If your problem has to do with playback of video, audio or subtitles, or display of a picture a sample file will go far in getting it fixed. The file should be as small as possible while still reproducing the issue. There are several audio/video cutting applications available (just google it until someone makes a list here). For posting/attaching bigger files, you'll have to use a file hosting site like [http://www.mediafire.com/ MediaFire] or [https://www.dropbox.com/ Dropbox]

=== Crash report ===
If Kodi has crashed, there are good odds that a crash report is available. How these are handled is platform dependent.<br />

;iOS/ATV2
:iOS will always create a Crashreporter log if any application crashes. These are found in /var/mobile/Library/Logs/CrashReporter/*.plist

;Linux
:The file will be in your user's home directory or the working directory if Kodi was launched from a terminal. It will be named "kodi_crashlog-[DATE]-[TIME].log" and contain some system information at the top, followed by a stack trace and the contents of Kodi.log. If you didn't have [[Settings/System/Logging|debugging]] enabled at the time, please enable it and recreate the problem. This feature was added in SVN revision 22194 and relies on the gnu debugger GDB being installed to work.

;Mac OS X
:OS X will always create a Crashreporter log if any application crashes. These are found in /Users/username/Library/Logs/CrashReporter/CrashReporter.log where 'username' is the login username. For the Apple TV 1, the 'username' is 'frontrow'.

;Windows
:The file will be in the same location as the [[Log file|debug log]] and named "Kodi_crashlog-[DATE]-[TIME].dmp". The dmp files will need to be uploaded to a location for download, as it's not a readable file. Moreover, we also ALWAYS require the '''kodi.pdb''' file (which is located next to the kodi.exe file) for total debugging. The pdb files are only available for test builds and releases.

== Where do I create a bug report? ==

{{divbox|red||'''Note:''' You can no longer use the bug tracker at http://trac.kodi.tv .}}

'''As per Devcon 2018, Team Kodi has decided to switch to a [https://github.com/xbmc/xbmc/issues Github Tracker] for administrating bugs/issues/projects for the Kodi application''', and to get the open issues more visible to outside developers. Currently almost no one follows what happens on trac.kodi.tv, and things tend to simply get buried over time.

Moving it to a [https://github.com/xbmc/xbmc/issues Github Tracker] will get it all in one single place in order to better handle, and whatever we as Team Kodi feel are certain goals that might be interesting for outsiders to work on. Getting rid of "trac" will also save us from a big maintenance burden.

{{updated|19}}

[[Category:Development]]
[[Category:Manual]]
[[Category:Troubleshooting]]
[[Category:How-to]]

Google Summer of Code/2021

2021-03-24T17:18:21Z

Yol:

{{GSOC_nav}}
{{mininav| [[Google Summer of Code]] }}
[[File:GSOC_2016_logo.png|left|150px]]Welcome to the Kodi [http://summerofcode.withgoogle.com Google Summer of Code] ideas page. We are pleased to announce that we have been accepted as an official GSoC mentor organization this year.



We encourage interested students of all ethnicities and genders to review some of the ideas on this page, and then feel free to provide input on any ideas you may have in the '''[https://forum.kodi.tv/forumdisplay.php?fid=315 Kodi GSoC 2021 forum]''' and chat about any project you’d love to cover. To propose a project, see '''[[#Students project proposal ideas]]'''.

From the 29th March to the 13th of April, any interested students may apply at the [https://summerofcode.withgoogle.com/ GSoC home page] to work with Kodi. After that, Google will notify applicants whether we get to work with each other according to the [https://developers.google.com/open-source/gsoc/timeline GSoC schedule].

== About Us ==
As there may be many students who have landed here as a result of GSoC, but are unfamiliar with the project, here are a few resources that may help explain what we are about.

:Kodi (formerly known as XBMC) is an award-winning free and open source (GPL) software media player and entertainment hub for digital media, designed around the 10-foot interface (living room) environment. Created in 2003 by a group of like minded programmers, Kodi is a non-profit project run and developed by volunteers located around the world. More than 500 software developers have contributed to Kodi, and 100-plus translators have worked to expand its reach, making it available in more than 60 languages. For more information, see the page '''[[Kodi]]'''.

<br />
To get an idea of what Kodi is truly capable of, it really must be seen. Check out a few other user-created videos:<br />
[http://www.youtube.com/watch?v=NcogPuSo-DU Kodi with the default Confluence skin]<br />
[http://www.youtube.com/watch?v=4asUCtE0ONU Kodi with Aeon Nox skin]<br />
[http://www.youtube.com/watch?v=4NR57ELY28s Kodi on Raspberry Pi]<br />
[http://www.youtube.com/watch?v=e_0PB5hfz_k Kodi's new PVR functionality]<br />
<br />

Kodi is written primarily in c++ and runs on a variety of platforms including Android, iOS, Linux, OS X, and Windows. It has been ported to work on several low-power platforms including the Raspberry Pi and Android.

Kodi was a mentoring organization in 2008, 2012, 2013, 2015, 2017, 2018, 2019 and 2020 and had team members involved in GSoC for other projects during 2011.

If Kodi is selected as a mentoring organization for 2021, students will need to review the Overview of a good project proposal, follow the outline for proposals when applying, and review the list of project ideas detailed below. Students are welcome to propose ideas outside the list and are encouraged to be as creative as they like.

=== Mentors ===
All mentors and backup mentors are extremely experienced in the Kodi codebase and will thus be able to assist students in getting to know the codebase and in quickly identifying projects that are both achievable for someone unfamiliar with the internal workings of Kodi and desirable to the wider Kodi community.

==Prerequisites==
Some coding skills, basic familiarity with Git, solid understanding and interest in programming. Ability to quickly understand existing code is beneficial.

== Project Proposals ==
=== Overview ===
Qualifications for a good Summer of Code proposal:
* Discrete, well-defined, modular
* Comprised of a series of measurable sub-goals
* Based on open specs that are available free of charge
* Based on complete specs
An example of a good proposal is the implementation of a new feature or function that is not yet available in Kodi.

An example of a less desirable proposal is one that's not as measurable, such as refactoring an existing API. Bad proposals tend to be ones that would require touching a lot of core code.

To re-iterate:
* Localized/isolated code projects = ''good''
* Global code refactoring = ''bad''
* A project should have a set of subgoals, so even if the end goal turns out to be too big some of the parts will be of benefit.
* Not too big! This is an important problem when choosing a project, while it is fun to think about solving a grand project its not always realistic. It's better to finish a smaller project than to start a grand one.

{{Warning |1='''GSoC 2021 is different from the years before. All projects should have a workload of ~175 hours (previously: 350 hours). Project applications that do not fit this scope will be rejected.'''|title= }}

=== Where to submit proposals ===
In addition to submitting to the [https://g.go/gsoc Google Summer of Code] website, you are highly encouraged to submit your idea/proposal to the [https://forum.kodi.tv/forumdisplay.php?fid=315 Kodi forum] for discussion. Any proposal not submitted to the forum for discussion will likely not be considered.

=== Outline for proposals ===
{{divbox|blue||
PROJECT TITLE GOES HERE

* '''Name:'''
* '''forum/e-mail:'''
* '''Summary:''' A somewhat small but explanatory walk through of the project. It should not be overly detailed just enough to understand the problem trying to be fixed and how this project opt to solve it.
* '''How will I achieve this:''' Explain how the project will be done, what technologies are needed and how to implement them.
* '''What will the project focus on:''' Explain what the project will focus on, what is the important parts of the project.
* '''Benefits:''' Who will benefit and why from this project. Think about what a user or developer may need or do to benefit from it. Why does it benefit many users.
* '''Goals:''' What is the goal of the project, a project may not always solve the problem entirely as it may take to much time. Think hard about what can be accomplished during a summer with your skill and deduct that quite a bit. If the project can't be done after this perhaps its better to opt for a smaller one or one with subgoals.
* '''What does it touch in Kodi:''' Think about what parts of the code this may touch, Kodi is a big application and a lot of the code is spread out and very complex. If a project touches to much it may be impossible to complete.
* '''Requirements:''' What is needed to complete the project, what code language knowledge what hardware etc.
* '''Possible mentors:''' Place to add possible mentors (Team-Kodi will add this).
}}

== Team-Kodi proposal ideas up for discussion ==

=== Explore building binary addons in rust ===
'''Description:''' While Kodi has python addons, it can also handle binary addons. But these need to be build one by one for each platform and also might fail on errors. Rust might help with both of those problems and more. The idea is to use the api we have but via rust ffi and see where that leads us.

'''Expected outcome:''' Documentation and templates on how to use rust with kodi. In the best case also one or two example addons.

'''Skills preferred:''' C++, Rust, C

'''Possible mentors:''' spiff, Razze

'''Difficulty:''' Hard

'''Type:''' Binary addon development

=== Finish the new web interface ===
'''Description:''' Kodi has a in development webinterface by the name of elm-chorus (https://github.com/xbmc/elm-chorus) which is written in Elm and is still missing some features of Chorus2 (the old interface). So the idea would be to bring it up to speed and do some additional styling and packaging work.

'''Expected outcome:''' Finished shipable version of the webinterface

'''Skills preferred:''' HTML, CSS, Elm

'''Possible mentors:''' Razze

'''Difficulty:''' Medium

'''Type:''' Webinterface development



===Achievements in RetroPlayer===

'''Description''': Retroarch has developed support for achievements in certain select libretro cores. This project would consist of porting whatever work might be portable and otherwise integrating the existing libretro achievement system into Kodi's RetroPlayer implemented using Kodi's UI system. Could be tackled a few different ways, including simply linking the user to the retroachievements.org or creating a full achievement database in Kodi.

'''Expected Outcome''': Users should be able to see their achievements in Kodi. Player manager and Player profile support may be in development concurrently, so thought should be given to those systems.

'''Skills preferred''': C++, python, possibly php

'''Possible mentor''': gusandrianos, NikosSiak

'''Difficulty''': medium

'''Type''': Fun/Peripheral

'''Notes''': Garbear has broken down the Retroplayer project into manageable pieces including input, core, game add-ons, peripheral add-ons, netplay, a game library implementation, and shaders to do things like emulate a CRT monitor. This is one example, but many pieces are currently being worked on or are near completion, and many more could use help from a student familiar with the area. Visit the retroplayer section of the Kodi forum to see all the major projects still to do.

===Add-ons===
====Automatic add-on checker for binary add-ons====
'''Description:''' Kodis add-on checker checks each Kodi add-on PR on GitHub for certain problems, which ultimately makes reviewing Python add-ons easier for the team. But the other type of add-ons, binary add-ons is not being checked so far, which makes reviews and coding guidelines hard to handle. Thus it would be nice to also check those add-ons, either via the current checker written in Python or a new binary add-on specific checker. Goals would include checking the addon.xml, the C++ code and a check for potentially malicious code.

'''Expected outcome:''' Being able to run the checker against all binary repo PRs on GitHub.

'''Skills preferred:''' Python, C++

'''Possible mentors:''' Razze

'''Difficulty:''' Hard

'''Type:''' Low-hanging fruit

===Using fuzz testing to fuzz test Kodi===
'''Description:''' Adding fuzz testing to Kodi would be very valuable to find problems in the current code base. Especially security problems. First step would be choosing a framework either American fuzzy lop, libFuzzer or other similar projects. After we decided on that it would be time to start to fuzz different methods that are widely used in Kodi and try to expose flaws in those. If this leads to success, it should be documented and made repeatable.

'''Expected outcome:''' Being able to easily add more fuzz tests and having the process to do this documented.

'''Skills preferred:''' C++, CMake

'''Possible mentors:''' Razze

'''Difficulty:''' Medium

'''Type:''' Risky/Exploratory



===Other ideas===
These ideas still need expanding and/or assigned a potential mentor. If one of these ideas interests you, feel free to ask for more info in the GSoC 2020 forum area. We may be able to assign a mentor if enough interest is shown
*Improvements to Retroplayer (retro gaming integrated in Kodi core)
*Visual Studio Code addon to validate/syntax highlight Kodi Addons

*High quality scalers for OpenGL(GLSL). Scale Y and UV plane separately (possible mentors: velocity)


*Implementing a performance critical element of kodi in rust

=== More ===
We feel it is important to note that, while we are interested in a focus on the listed ideas, we would like to stress passion, expertise, and creativity above all else. If you would like to do something completely different, definitely send in that proposal. The ideas listed above are, as always, merely suggestions. We will be interested in any idea, so long as you can communicate your interest, your background, and your solution the problem.

== Students project proposal ideas ==

Submit your own proposals on the '''[https://forum.kodi.tv/forumdisplay.php?fid=315 Kodi GSoC forum]'''. They can be as big or as small as you feel you can comfortably accomplish between '''June 7''' and '''August 23'''. In the end, it's better to have a smaller, completed project, rather than a larger, incomplete project.

To submit a proposal idea:
# Copy the text from '''[[#Outline for proposals]]'''.
# Create a new forum post '''[https://forum.kodi.tv/forumdisplay.php?fid=315 HERE]''' and paste the text.
# Fill out everything using your specific proposal.

[[Category:Google Summer of Code]]

Google Summer of Code/2021

2021-02-18T16:51:22Z

Yol:

Google Summer of Code/2021

2021-02-18T16:12:34Z

Yol:

Google Summer of Code/2021

2021-01-30T13:07:42Z

Yol: fix logo

{{GSOC_nav}}
{{mininav| [[Google Summer of Code]] }}
[[File:GSOC_2016_logo.png|left|150px]]Welcome to the Kodi [http://summerofcode.withgoogle.com Google Summer of Code] ideas page. 

'''This page is currently work in progress.'''



From the 29th March to the 13th of April, any interested students may apply at the [http://g.go/gsoc GSoC home page] to work with Kodi. After that, Google will notify applicants whether we get to work with each other according to the [https://developers.google.com/open-source/gsoc/timeline GSoC schedule].

== About Us ==
As there may be many students who have landed here as a result of GSoC, but are unfamiliar with the project, here are a few resources that may help explain what we are about.

:Kodi (formerly known as XBMC) is an award-winning free and open source (GPL) software media player and entertainment hub for digital media, designed around the 10-foot interface (living room) environment. Created in 2003 by a group of like minded programmers, Kodi is a non-profit project run and developed by volunteers located around the world. More than 500 software developers have contributed to Kodi, and 100-plus translators have worked to expand its reach, making it available in more than 60 languages. For more information, see the page '''[[Kodi]]'''.

<br />
To get an idea of what Kodi is truly capable of, it really must be seen. Check out a few other user-created videos:<br />
[http://www.youtube.com/watch?v=NcogPuSo-DU Kodi with the default Confluence skin]<br />
[http://www.youtube.com/watch?v=4asUCtE0ONU Kodi with Aeon Nox skin]<br />
[http://www.youtube.com/watch?v=4NR57ELY28s Kodi on Raspberry Pi]<br />
[http://www.youtube.com/watch?v=e_0PB5hfz_k Kodi's new PVR functionality]<br />
<br />

Kodi is written primarily in c++ and runs on a variety of platforms including Android, iOS, Linux, OS X, and Windows. It has been ported to work on several low-power platforms including the Raspberry Pi and Android.

Kodi was a mentoring organization in 2008, 2012, 2013, 2015, 2017, 2018, 2019 and 2020 and had team members involved in GSoC for other projects during 2011.

If Kodi is selected as a mentoring organization for 2021, students will need to review the Overview of a good project proposal, follow the outline for proposals when applying, and review the list of project ideas detailed below. Students are welcome to propose ideas outside the list and are encouraged to be as creative as they like.

=== Mentors ===
All mentors and backup mentors are extremely experienced in the Kodi codebase and will thus be able to assist students in getting to know the codebase and in quickly identifying projects that are both achievable for someone unfamiliar with the internal workings of Kodi and desirable to the wider Kodi community.

==Prerequisites==
Some coding skills, basic familiarity with Git, solid understanding and interest in programming. Ability to quickly understand existing code is beneficial.

== Project Proposals ==
=== Overview ===
Qualifications for a good Summer of Code proposal:
* Discrete, well-defined, modular
* Comprised of a series of measurable sub-goals
* Based on open specs that are available free of charge
* Based on complete specs
An example of a good proposal is the implementation of a new feature or function that is not yet available in Kodi.

An example of a less desirable proposal is one that's not as measurable, such as refactoring an existing API. Bad proposals tend to be ones that would require touching a lot of core code.

To re-iterate:
* Localized/isolated code projects = ''good''
* Global code refactoring = ''bad''
* A project should have a set of subgoals, so even if the end goal turns out to be too big some of the parts will be of benefit.
* Not too big! This is an important problem when choosing a project, while it is fun to think about solving a grand project its not always realistic. Its better to finish a smaller project than to start a grand one.

=== Where to submit proposals ===
In addition to submitting to the [https://g.go/gsoc Google Summer of Code] website, you are highly encouraged to submit your idea/proposal to the [https://forum.kodi.tv/forumdisplay.php?fid=293 Kodi forum] for discussion. Any proposal not submitted to the forum for discussion will likely not be considered.

=== Outline for proposals ===
{{divbox|blue||
PROJECT TITLE GOES HERE

* '''Name:'''
* '''forum/e-mail:'''
* '''Summary:''' A somewhat small but explanatory walk through of the project. It should not be overly detailed just enough to understand the problem trying to be fixed and how this project opt to solve it.
* '''How will I achieve this:''' Explain how the project will be done, what technologies are needed and how to implement them.
* '''What will the project focus on:''' Explain what the project will focus on, what is the important parts of the project.
* '''Benefits:''' Who will benefit and why from this project. Think about what a user or developer may need or do to benefit from it. Why does it benefit many users.
* '''Goals:''' What is the goal of the project, a project may not always solve the problem entirely as it may take to much time. Think hard about what can be accomplished during a summer with your skill and deduct that quite a bit. If the project can't be done after this perhaps its better to opt for a smaller one or one with subgoals.
* '''What does it touch in Kodi:''' Think about what parts of the code this may touch, Kodi is a big application and a lot of the code is spread out and very complex. If a project touches to much it may be impossible to complete.
* '''Requirements:''' What is needed to complete the project, what code language knowledge what hardware etc.
* '''Possible mentors:''' Place to add possible mentors (Team-Kodi will add this).
}}

== Team-Kodi proposal ideas up for discussion ==

=== Explore building binary addons in rust ===
'''Description:''' While Kodi has python addons, it can also handle binary addons. But these need to be build one by one for each platform and also might fail on errors. Rust might help with both of those problems and more. The idea is to use the api we have but via rust ffi and see where that leads us.

'''Expected outcome:''' Documentation and templates on how to use rust with kodi. In the best case also one or two example addons.

'''Skills preferred:''' C++, Rust, C

'''Possible mentors:''' spiff, Razze, velocity

'''Difficulty:''' Hard

'''Type:''' Binary addon development

=== A new web interface ===
'''Description:''' Kodi has a webinterface by the name of chorus2 (https://github.com/xbmc/chorus2) which is written in coffeescript and as it stands no team member is able to work on coffeescript. So the idea would be to implement a new interface, in a newer language. I would like to see Elm or Svelte, but others would be fine too, as long as we would be able to maintain it.

'''Expected outcome:''' A new webinterface (can be redesigned) or a port of the old one.

'''Skills preferred:''' HTML, CSS, Javascript, Typescript, Elm

'''Possible mentors:''' Razze

'''Difficulty:''' Medium

'''Type:''' Webinterface development

=== Better profile support ===
'''Description:''' Profile support inside Kodi remains extremely hacked together. Improving profile projects would likely be broken down into smaller chunks to make each chunk truly achievable in a summer. Database handling for profiles needs to be reviewed and changed so that the user experience is more streamlined. It should also be possible to better guard code paths that need to check for specific profile rights.

'''Expected outcome:''' Profiles should be more user-friendly than before and not be an afterthought. Being able to easily add more profile features is the big ultimate goal, as we want to support profiles for kids that automatically hide media that's not for them. Just as an example.

'''Skills preferred:''' C++

'''Possible mentors:''' spiff

'''Difficulty:''' Hard

'''Type:''' Core development

=== Replacing depends with a CMake-based system ===

'''Description:''' Kodi has its own system for building the many libraries Kodi depends on that supports most platforms (Linux, Android, OS X, iOS) and cross-compiling called depends. At the moment, it is implemented with autotools and hand-crafted Makefiles. This has lead to a lot of code duplication, poor maintainability, and not being very user-friendly. Also, it does not currently work on Windows. This task would be about replacing the current system with a new implementation in CMake that has better maintainability.

'''Expected outcome:''' A CMake-based dependency build system that offers roughly the same features as depends (i.e. all required libraries covered, diverse platform support, crosscompilation). If the solution can also be applied to Windows by e.g. adding minimal CMake files to replace some UNIX-only build systems, that would be a big plus, but it is not necessary.

'''Skills preferred:''' CMake, shell scripting, general familiarity with UNIX/Linux

'''Possible mentors:''' wsnipex

'''Difficulty:''' Medium

'''Type:''' Infrastructure/Automation

===Add-ons===
====Automatic add-on checker for binary add-ons====
'''Description:''' Kodis add-on checker checks each Kodi add-on PR on GitHub for certain problems, which ultimately makes reviewing Python add-ons easier for the team. But the other type of add-ons, binary add-ons is not being checked so far, which makes reviews and coding guidelines hard to handle. Thus it would be nice to also check those add-ons, either via the current checker written in Python or a new binary add-on specific checker. Goals would include checking the addon.xml, the C++ code and a check for potentially malicious code.

'''Expected outcome:''' Being able to run the checker against all binary repo PRs on GitHub.

'''Skills preferred:''' Python, C++

'''Possible mentors:''' Razze

'''Difficulty:''' Hard

'''Type:''' Low-hanging fruit

===Achievements in RetroPlayer===

'''Description''': Retroarch has developed support for achievements in certain select libretro cores. This project would consist of porting whatever work might be portable and otherwise integrating the existing libretro achievement system into Kodi's RetroPlayer implemented using Kodi's UI system. Could be tackled a few different ways, including simply linking the user to the retroachievements.org or creating a full achievement database in Kodi.

'''Expected Outcome''': Users should be able to see their achievements in Kodi. Player manager and Player profile support may be in development concurrently, so thought should be given to those systems.

'''Skills preferred''': C++, python, possibly php

'''Possible mentor''': garbear, velocity

'''Difficulty''': medium

'''Type''': Fun/Peripheral

'''Notes''': Garbear has broken down the Retroplayer project into manageable pieces including input, core, game add-ons, peripheral add-ons, netplay, a game library implementation, and shaders to do things like emulate a CRT monitor. This is one example, but many pieces are currently being worked on or are near completion, and many more could use help from a student familiar with the area. Visit the retroplayer section of the Kodi forum to see all the major projects still to do.

===Saved game manager for RetroPlayer===

'''Description''': Kodi excels at managing large movie, music, and (with add-ons) game libraries. However, savestates and in-game saves are simply stored next to the ROM or in a hard-coded folder.

This project would consist of designing a user interface for saved game management. Some database work will probably be required. As a stretch goal, automatic saved-game captioning can be performed using the "Rich Presence" feature of RetroAchievements.org.

In 2016, Garbear created an experimental saved game manager - see https://github.com/xbmc/xbmc/pull/11034. It may be possible to re-use ideas and code from this PR. Here's what the saved game manager looked like at the time:

[[File:Saved game manager.png|600px|Saved game manager from 2016]]

'''Expected Outcome''': Users should be able to manage their savestates and in-game saves in Kodi.

'''Skills preferred''': C++, optional python

'''Possible mentor''': garbear, velocity

'''Difficulty''': medium

'''Type''': Fun/Peripheral

===Runahead for RetroPlayer===

'''Description''': This feature, pioneered by libretro (see [https://www.libretro.com/index.php/retroarch-1-7-2%E2%80%8A-%E2%80%8Aachieving-better-latency-than-original-hardware-through-new-runahead-method/ Achieving better latency than original hardware through new runahead method]) allows for input latency better than the original console!

'''Expected Outcome''': Implemented runahead input

'''Skills preferred''': C++

'''Possible mentor''': garbear, velocity

'''Difficulty''': medium

'''Type''': Fun/Peripheral

===Player Manager for RetroPlayer===

'''Description''': Currently, player assignment and controller selection is hard-coded. This project would allow the user to configure which controllers are connected to the virtual console, enabling multiplayer in games that are currently hard-coded to single player.

A player management concept is outlined here: https://github.com/garbear/xbmc/issues/87. Ideas and code from the issue can possibly be re-used in this project.

[[File:Player manager.png|600px|Player manager concept art]]

'''Expected Outcome''': Players can change virtual input devices and choose which player number they are

'''Skills preferred''': C++

'''Possible mentor''': garbear, velocity

'''Difficulty''': medium

'''Type''': Fun/Peripheral

===<insert feature from RetroArch here>===

'''Description''': RetroArch is an amazing, full-featured emulator system. Many of these features would make good GSoC projects!

'''Expected Outcome''': Feature from RetroArch is implemented

'''Skills preferred''': C++, optional Python

'''Possible mentor''': garbear, velocity

'''Difficulty''': various

'''Type''': Fun/Peripheral

===Game-theoretic engine for RetroPlayer===

'''Description''': Currently, Kodi's game engine (RetroPlayer) is based on VideoPlayer - games act as "codecs" that accept input and produce audio and video streams. While this rocks for performance (we've even mirrored zero-copy support from VP), it makes many features, such as rewind, runahead, and netplay difficult to integrate.

The project is to implement the emulation equation described by the Special Theory of Emulation introduced in [https://github.com/garbear/xbmc/issues/89 Reinforcement Learning Bots], where S is State and A is Action:

[[File:S_0.gif|Initial value of S]]<br/>
[[File:A_0.gif|Initial value of A]]

[[File:State update 2.gif|State update]]<br/>
[[File:Action update 3.gif|Action update]]

The equation results in the time series:

(S<sub>0</sub>, A<sub>0</sub>, S<sub>1</sub>, A<sub>1</sub>, S<sub>2</sub>, A<sub>2</sub>, ...)

The emulation equation describes all of emulation in a game-theoretic manner. With such an engine, powerful features become incredibly easy:

* When emulation is a time series, rewind is just decrementing t
* Runahead is just replacing an A several t's ago
* Netplay is also possible - just run a consensus algorithm like RAFT over the State/Action pairs.

'''Expected Outcome''': Games play using the new engine. Rewind is now easy. Runahead is now easy. Netplay is still hard, but the emulation equation turns netplay from a networking problem into a consensus problem.

'''Skills preferred''': C++

'''Possible mentor''': garbear, velocity

'''Difficulty''': advanced

'''Type''': Fun/Peripheral

===Reinforcement learning bots for RetroPlayer===

'''Description''': Same as the above, but implement the emulation equation described by the General Theory of Emulation in [https://github.com/garbear/xbmc/issues/89 Reinforcement Learning Bots].

'''Expected Outcome''': Super-human gaming bots take over the world

'''Skills preferred''': C++

'''Possible mentor''': garbear, velocity

'''Difficulty''': hell

'''Type''': Fun/Peripheral

===Retroverse===

'''Description''': This project introduces the Retroverse: an infinitely-rewindable branching history of all gameplay.

Braid creator Jonathan Blow gave a presentation titled [https://www.youtube.com/watch?v=8dinUbg2h70 The Implementation of Rewind in Braid]. In 2013, Themaister [https://github.com/garbear/xbmc-retroplayer/commit/97e52df8a2f82a36952c8bcbebc133b3efc1babe donated] braid-style rewind to Kodi. This became the basis of the [https://github.com/xbmc/xbmc/blob/master/xbmc/cores/RetroPlayer/streams/memory/IMemoryStream.h memory streaming API] in RetroPlayer.

Recall how Blow describes his rewind feature: "Record full world state for every frame always; do not drop frames. Compress data somehow." The challenge of this project is to figure out that "somehow".

Does recording hundreds of hours of gameplay sound impossible? Assume deterministic emulation. The State can be fully reconstructed from the Action of the previous timestep, so only the Action needs to be saved. The Atari 2600, released in 1977, has 5 buttons, needing 5 bits. With a 5 bit frame size, you can store around 850 years of continuous (or nonlinear) Atari 2600 gameplay on a 1TB drive. Still seem impossible?

'''Expected Outcome''': Implement the <code>CNonlinearMemoryStream</code> class referenced in <code>[https://github.com/xbmc/xbmc/blob/master/xbmc/cores/RetroPlayer/streams/memory/IMemoryStream.h IMemoryStream.h]</code>. Enable LZ4 and/or RLE compression of savestate diffs. Enhance autosave by using interpolation to drop "base frames". Store a tree instead of a buffer!

'''Skills preferred''': C++

'''Possible mentor''': garbear, velocity

'''Difficulty''': advanced

'''Type''': Fun/Peripheral

===Using fuzz testing to fuzz test Kodi===

'''Description:''' Adding fuzz testing to Kodi would be very valuable to find problems in the current code base. Especially security problems. First step would be choosing a framework either American fuzzy lop, libFuzzer or other similar projects. After we decided on that it would be time to start to fuzz different methods that are widely used in Kodi and try to expose flaws in those. If this leads to success, it should be documented and made repeatable.

'''Expected outcome:''' Being able to easily add more fuzz tests and having the process to do this documented.

'''Skills preferred:''' C++, CMake

'''Possible mentors:''' Razze

'''Difficulty:''' Medium

'''Type:''' Risky/Exploratory

===inputstream.adaptive binary addon===

'''Description:''' inputstream.adaptive is a binary kodi inputstream addon written in C++ and handles multi bitrate streams provided in DASH / Smoothstream manifest or HLS multi bitrate playlists. The addon provides demuxed / encoded packets to kodi and kodi renders the data with its internal videoplayer. Digital Rights Management (DRM) is implemented in inputstream.adaptive to allow playback of protected media. inputstream.adaptive is used by many (> 100) addons to play (legal) encrypted media.
<br>The addon sources are still hosted in my own git repository (https://github.com/peak3d/inputstream.adaptive) but I'll hand over the sources to kodi repository if someone is interested on working at one of these 2 most urgent topics:

====Bitrate switch====

'''Description:''' In the current inputstream.adaptive implementation a stream resolution / bitrate is selected at start time. Because of network fluctations / manual window / screen changes or performance stats of rendered frames it should be possible to switch seamless to lower / higher stream representations.

'''Expected outcome:''' Automagically select / change seamless stream depending on external factors.

'''Skills preferred:''' C++, CMake

'''Possible mentors:''' peak3d

'''Difficulty:''' Medium

'''Type:''' Media playback

====Read ahead====

'''Description:''' Currently stream segments are downloaded on request (that is kodi is requesting more data to display). Because the kodi videoplayer internal buffer is small (8 seconds), network fluctuation can lead to bad user experience (stream interruption). What users want is that inputstream.adaptive buffers a configurable amount of time ahead to bypass this issue.<br> Buffering ahead in multi bitstream is not only a technical task, there are numerous resolutions / bitrates for the same movie time segment in the manifest from which the "best" one should be buffered. The concept of what to read will be an not trivial engeneering task.<br>Bitrate switch (see previous topic) will be a prerequasite to "Read ahead" because on low network times lower bitrate streams are read compared to good network times.

'''Expected outcome:''' Implementation of read ahead logic for multi bitrate streams, user configurable.

'''Skills preferred:''' C++, CMake

'''Possible mentors:''' peak3d

'''Difficulty:''' Medium

'''Type:''' Media playback

===Other ideas===
These ideas still need expanding and/or assigned a potential mentor. If one of these ideas interests you, feel free to ask for more info in the GSoC 2020 forum area. We may be able to assign a mentor if enough interest is shown
*Visual Studio Code addon to validate/syntax highlight Kodi Addons (possible mentors: velocity)
*Using fruit or similar to use DI in Kodi and write tests
*High quality scalers for OpenGL(GLSL). Scale Y and UV plane separately (possible mentors: velocity)
*Support downloading of of media items (the actual file not just the metadata) from another Kodi instance (e.g. through UPnP) into the local library. This could be done in a "send to" way and in a "download" way and it could also be combined with transcoding depending on the target device.
*UPnP device profiles. there's already a PR that goes in that direction and the problem is that right now we can only really provide device specific MIME type hacks but if we have transcoding we'll definitely need this
*Implementing a performance critical element of kodi in rust

=== More ===
We feel it is important to note that, while we are interested in a focus on the listed three areas, we would like to stress passion, expertise, and creativity above all else. If you would like to do something completely different, definitely send in that proposal. The ideas listed above are, as always, merely suggestions. We will be interested in any idea, so long as you can communicate your interest, your background, and your solution the problem.

== Students project proposal ideas ==

Submit your own proposals on the '''[https://forum.kodi.tv/forumdisplay.php?fid=301 Kodi GSoC forum]'''. They can be as big or as small as you feel you can comfortably accomplish between '''PROJECT START DATE''' and '''PROJECT END DATE'''. In the end, it's better to have a smaller, completed project, rather than a larger, incomplete project.

To submit a proposal idea:
# Copy the text from '''[[#Outline for proposals]]'''.
# Create a new forum post '''[https://forum.kodi.tv/forumdisplay.php?fid=301 HERE]''' and paste the text.
# Fill out everything using your specific proposal.

[[Category:Google Summer of Code]]

Google Summer of Code/2021

2021-01-30T13:05:15Z

Yol:

{{GSOC_nav}}
{{mininav| [[Google Summer of Code]] }}
[[File:GSoC_2016_logo.png|left|150px]]Welcome to the Kodi [http://summerofcode.withgoogle.com Google Summer of Code] ideas page. 

'''This page is currently work in progress.'''



From the 29th March to the 13th of April, any interested students may apply at the [http://g.go/gsoc GSoC home page] to work with Kodi. After that, Google will notify applicants whether we get to work with each other according to the [https://developers.google.com/open-source/gsoc/timeline GSoC schedule].

== About Us ==
As there may be many students who have landed here as a result of GSoC, but are unfamiliar with the project, here are a few resources that may help explain what we are about.

:Kodi (formerly known as XBMC) is an award-winning free and open source (GPL) software media player and entertainment hub for digital media, designed around the 10-foot interface (living room) environment. Created in 2003 by a group of like minded programmers, Kodi is a non-profit project run and developed by volunteers located around the world. More than 500 software developers have contributed to Kodi, and 100-plus translators have worked to expand its reach, making it available in more than 60 languages. For more information, see the page '''[[Kodi]]'''.

<br />
To get an idea of what Kodi is truly capable of, it really must be seen. Check out a few other user-created videos:<br />
[http://www.youtube.com/watch?v=NcogPuSo-DU Kodi with the default Confluence skin]<br />
[http://www.youtube.com/watch?v=4asUCtE0ONU Kodi with Aeon Nox skin]<br />
[http://www.youtube.com/watch?v=4NR57ELY28s Kodi on Raspberry Pi]<br />
[http://www.youtube.com/watch?v=e_0PB5hfz_k Kodi's new PVR functionality]<br />
<br />

Kodi is written primarily in c++ and runs on a variety of platforms including Android, iOS, Linux, OS X, and Windows. It has been ported to work on several low-power platforms including the Raspberry Pi and Android.

Kodi was a mentoring organization in 2008, 2012, 2013, 2015, 2017, 2018, 2019 and 2020 and had team members involved in GSoC for other projects during 2011.

If Kodi is selected as a mentoring organization for 2021, students will need to review the Overview of a good project proposal, follow the outline for proposals when applying, and review the list of project ideas detailed below. Students are welcome to propose ideas outside the list and are encouraged to be as creative as they like.

=== Mentors ===
All mentors and backup mentors are extremely experienced in the Kodi codebase and will thus be able to assist students in getting to know the codebase and in quickly identifying projects that are both achievable for someone unfamiliar with the internal workings of Kodi and desirable to the wider Kodi community.

==Prerequisites==
Some coding skills, basic familiarity with Git, solid understanding and interest in programming. Ability to quickly understand existing code is beneficial.

== Project Proposals ==
=== Overview ===
Qualifications for a good Summer of Code proposal:
* Discrete, well-defined, modular
* Comprised of a series of measurable sub-goals
* Based on open specs that are available free of charge
* Based on complete specs
An example of a good proposal is the implementation of a new feature or function that is not yet available in Kodi.

An example of a less desirable proposal is one that's not as measurable, such as refactoring an existing API. Bad proposals tend to be ones that would require touching a lot of core code.

To re-iterate:
* Localized/isolated code projects = ''good''
* Global code refactoring = ''bad''
* A project should have a set of subgoals, so even if the end goal turns out to be too big some of the parts will be of benefit.
* Not too big! This is an important problem when choosing a project, while it is fun to think about solving a grand project its not always realistic. Its better to finish a smaller project than to start a grand one.

=== Where to submit proposals ===
In addition to submitting to the [https://g.go/gsoc Google Summer of Code] website, you are highly encouraged to submit your idea/proposal to the [https://forum.kodi.tv/forumdisplay.php?fid=293 Kodi forum] for discussion. Any proposal not submitted to the forum for discussion will likely not be considered.

=== Outline for proposals ===
{{divbox|blue||
PROJECT TITLE GOES HERE

* '''Name:'''
* '''forum/e-mail:'''
* '''Summary:''' A somewhat small but explanatory walk through of the project. It should not be overly detailed just enough to understand the problem trying to be fixed and how this project opt to solve it.
* '''How will I achieve this:''' Explain how the project will be done, what technologies are needed and how to implement them.
* '''What will the project focus on:''' Explain what the project will focus on, what is the important parts of the project.
* '''Benefits:''' Who will benefit and why from this project. Think about what a user or developer may need or do to benefit from it. Why does it benefit many users.
* '''Goals:''' What is the goal of the project, a project may not always solve the problem entirely as it may take to much time. Think hard about what can be accomplished during a summer with your skill and deduct that quite a bit. If the project can't be done after this perhaps its better to opt for a smaller one or one with subgoals.
* '''What does it touch in Kodi:''' Think about what parts of the code this may touch, Kodi is a big application and a lot of the code is spread out and very complex. If a project touches to much it may be impossible to complete.
* '''Requirements:''' What is needed to complete the project, what code language knowledge what hardware etc.
* '''Possible mentors:''' Place to add possible mentors (Team-Kodi will add this).
}}

== Team-Kodi proposal ideas up for discussion ==

=== Explore building binary addons in rust ===
'''Description:''' While Kodi has python addons, it can also handle binary addons. But these need to be build one by one for each platform and also might fail on errors. Rust might help with both of those problems and more. The idea is to use the api we have but via rust ffi and see where that leads us.

'''Expected outcome:''' Documentation and templates on how to use rust with kodi. In the best case also one or two example addons.

'''Skills preferred:''' C++, Rust, C

'''Possible mentors:''' spiff, Razze, velocity

'''Difficulty:''' Hard

'''Type:''' Binary addon development

=== A new web interface ===
'''Description:''' Kodi has a webinterface by the name of chorus2 (https://github.com/xbmc/chorus2) which is written in coffeescript and as it stands no team member is able to work on coffeescript. So the idea would be to implement a new interface, in a newer language. I would like to see Elm or Svelte, but others would be fine too, as long as we would be able to maintain it.

'''Expected outcome:''' A new webinterface (can be redesigned) or a port of the old one.

'''Skills preferred:''' HTML, CSS, Javascript, Typescript, Elm

'''Possible mentors:''' Razze

'''Difficulty:''' Medium

'''Type:''' Webinterface development

=== Better profile support ===
'''Description:''' Profile support inside Kodi remains extremely hacked together. Improving profile projects would likely be broken down into smaller chunks to make each chunk truly achievable in a summer. Database handling for profiles needs to be reviewed and changed so that the user experience is more streamlined. It should also be possible to better guard code paths that need to check for specific profile rights.

'''Expected outcome:''' Profiles should be more user-friendly than before and not be an afterthought. Being able to easily add more profile features is the big ultimate goal, as we want to support profiles for kids that automatically hide media that's not for them. Just as an example.

'''Skills preferred:''' C++

'''Possible mentors:''' spiff

'''Difficulty:''' Hard

'''Type:''' Core development

=== Replacing depends with a CMake-based system ===

'''Description:''' Kodi has its own system for building the many libraries Kodi depends on that supports most platforms (Linux, Android, OS X, iOS) and cross-compiling called depends. At the moment, it is implemented with autotools and hand-crafted Makefiles. This has lead to a lot of code duplication, poor maintainability, and not being very user-friendly. Also, it does not currently work on Windows. This task would be about replacing the current system with a new implementation in CMake that has better maintainability.

'''Expected outcome:''' A CMake-based dependency build system that offers roughly the same features as depends (i.e. all required libraries covered, diverse platform support, crosscompilation). If the solution can also be applied to Windows by e.g. adding minimal CMake files to replace some UNIX-only build systems, that would be a big plus, but it is not necessary.

'''Skills preferred:''' CMake, shell scripting, general familiarity with UNIX/Linux

'''Possible mentors:''' wsnipex

'''Difficulty:''' Medium

'''Type:''' Infrastructure/Automation

===Add-ons===
====Automatic add-on checker for binary add-ons====
'''Description:''' Kodis add-on checker checks each Kodi add-on PR on GitHub for certain problems, which ultimately makes reviewing Python add-ons easier for the team. But the other type of add-ons, binary add-ons is not being checked so far, which makes reviews and coding guidelines hard to handle. Thus it would be nice to also check those add-ons, either via the current checker written in Python or a new binary add-on specific checker. Goals would include checking the addon.xml, the C++ code and a check for potentially malicious code.

'''Expected outcome:''' Being able to run the checker against all binary repo PRs on GitHub.

'''Skills preferred:''' Python, C++

'''Possible mentors:''' Razze

'''Difficulty:''' Hard

'''Type:''' Low-hanging fruit

===Achievements in RetroPlayer===

'''Description''': Retroarch has developed support for achievements in certain select libretro cores. This project would consist of porting whatever work might be portable and otherwise integrating the existing libretro achievement system into Kodi's RetroPlayer implemented using Kodi's UI system. Could be tackled a few different ways, including simply linking the user to the retroachievements.org or creating a full achievement database in Kodi.

'''Expected Outcome''': Users should be able to see their achievements in Kodi. Player manager and Player profile support may be in development concurrently, so thought should be given to those systems.

'''Skills preferred''': C++, python, possibly php

'''Possible mentor''': garbear, velocity

'''Difficulty''': medium

'''Type''': Fun/Peripheral

'''Notes''': Garbear has broken down the Retroplayer project into manageable pieces including input, core, game add-ons, peripheral add-ons, netplay, a game library implementation, and shaders to do things like emulate a CRT monitor. This is one example, but many pieces are currently being worked on or are near completion, and many more could use help from a student familiar with the area. Visit the retroplayer section of the Kodi forum to see all the major projects still to do.

===Saved game manager for RetroPlayer===

'''Description''': Kodi excels at managing large movie, music, and (with add-ons) game libraries. However, savestates and in-game saves are simply stored next to the ROM or in a hard-coded folder.

This project would consist of designing a user interface for saved game management. Some database work will probably be required. As a stretch goal, automatic saved-game captioning can be performed using the "Rich Presence" feature of RetroAchievements.org.

In 2016, Garbear created an experimental saved game manager - see https://github.com/xbmc/xbmc/pull/11034. It may be possible to re-use ideas and code from this PR. Here's what the saved game manager looked like at the time:

[[File:Saved game manager.png|600px|Saved game manager from 2016]]

'''Expected Outcome''': Users should be able to manage their savestates and in-game saves in Kodi.

'''Skills preferred''': C++, optional python

'''Possible mentor''': garbear, velocity

'''Difficulty''': medium

'''Type''': Fun/Peripheral

===Runahead for RetroPlayer===

'''Description''': This feature, pioneered by libretro (see [https://www.libretro.com/index.php/retroarch-1-7-2%E2%80%8A-%E2%80%8Aachieving-better-latency-than-original-hardware-through-new-runahead-method/ Achieving better latency than original hardware through new runahead method]) allows for input latency better than the original console!

'''Expected Outcome''': Implemented runahead input

'''Skills preferred''': C++

'''Possible mentor''': garbear, velocity

'''Difficulty''': medium

'''Type''': Fun/Peripheral

===Player Manager for RetroPlayer===

'''Description''': Currently, player assignment and controller selection is hard-coded. This project would allow the user to configure which controllers are connected to the virtual console, enabling multiplayer in games that are currently hard-coded to single player.

A player management concept is outlined here: https://github.com/garbear/xbmc/issues/87. Ideas and code from the issue can possibly be re-used in this project.

[[File:Player manager.png|600px|Player manager concept art]]

'''Expected Outcome''': Players can change virtual input devices and choose which player number they are

'''Skills preferred''': C++

'''Possible mentor''': garbear, velocity

'''Difficulty''': medium

'''Type''': Fun/Peripheral

===<insert feature from RetroArch here>===

'''Description''': RetroArch is an amazing, full-featured emulator system. Many of these features would make good GSoC projects!

'''Expected Outcome''': Feature from RetroArch is implemented

'''Skills preferred''': C++, optional Python

'''Possible mentor''': garbear, velocity

'''Difficulty''': various

'''Type''': Fun/Peripheral

===Game-theoretic engine for RetroPlayer===

'''Description''': Currently, Kodi's game engine (RetroPlayer) is based on VideoPlayer - games act as "codecs" that accept input and produce audio and video streams. While this rocks for performance (we've even mirrored zero-copy support from VP), it makes many features, such as rewind, runahead, and netplay difficult to integrate.

The project is to implement the emulation equation described by the Special Theory of Emulation introduced in [https://github.com/garbear/xbmc/issues/89 Reinforcement Learning Bots], where S is State and A is Action:

[[File:S_0.gif|Initial value of S]]<br/>
[[File:A_0.gif|Initial value of A]]

[[File:State update 2.gif|State update]]<br/>
[[File:Action update 3.gif|Action update]]

The equation results in the time series:

(S<sub>0</sub>, A<sub>0</sub>, S<sub>1</sub>, A<sub>1</sub>, S<sub>2</sub>, A<sub>2</sub>, ...)

The emulation equation describes all of emulation in a game-theoretic manner. With such an engine, powerful features become incredibly easy:

* When emulation is a time series, rewind is just decrementing t
* Runahead is just replacing an A several t's ago
* Netplay is also possible - just run a consensus algorithm like RAFT over the State/Action pairs.

'''Expected Outcome''': Games play using the new engine. Rewind is now easy. Runahead is now easy. Netplay is still hard, but the emulation equation turns netplay from a networking problem into a consensus problem.

'''Skills preferred''': C++

'''Possible mentor''': garbear, velocity

'''Difficulty''': advanced

'''Type''': Fun/Peripheral

===Reinforcement learning bots for RetroPlayer===

'''Description''': Same as the above, but implement the emulation equation described by the General Theory of Emulation in [https://github.com/garbear/xbmc/issues/89 Reinforcement Learning Bots].

'''Expected Outcome''': Super-human gaming bots take over the world

'''Skills preferred''': C++

'''Possible mentor''': garbear, velocity

'''Difficulty''': hell

'''Type''': Fun/Peripheral

===Retroverse===

'''Description''': This project introduces the Retroverse: an infinitely-rewindable branching history of all gameplay.

Braid creator Jonathan Blow gave a presentation titled [https://www.youtube.com/watch?v=8dinUbg2h70 The Implementation of Rewind in Braid]. In 2013, Themaister [https://github.com/garbear/xbmc-retroplayer/commit/97e52df8a2f82a36952c8bcbebc133b3efc1babe donated] braid-style rewind to Kodi. This became the basis of the [https://github.com/xbmc/xbmc/blob/master/xbmc/cores/RetroPlayer/streams/memory/IMemoryStream.h memory streaming API] in RetroPlayer.

Recall how Blow describes his rewind feature: "Record full world state for every frame always; do not drop frames. Compress data somehow." The challenge of this project is to figure out that "somehow".

Does recording hundreds of hours of gameplay sound impossible? Assume deterministic emulation. The State can be fully reconstructed from the Action of the previous timestep, so only the Action needs to be saved. The Atari 2600, released in 1977, has 5 buttons, needing 5 bits. With a 5 bit frame size, you can store around 850 years of continuous (or nonlinear) Atari 2600 gameplay on a 1TB drive. Still seem impossible?

'''Expected Outcome''': Implement the <code>CNonlinearMemoryStream</code> class referenced in <code>[https://github.com/xbmc/xbmc/blob/master/xbmc/cores/RetroPlayer/streams/memory/IMemoryStream.h IMemoryStream.h]</code>. Enable LZ4 and/or RLE compression of savestate diffs. Enhance autosave by using interpolation to drop "base frames". Store a tree instead of a buffer!

'''Skills preferred''': C++

'''Possible mentor''': garbear, velocity

'''Difficulty''': advanced

'''Type''': Fun/Peripheral

===Using fuzz testing to fuzz test Kodi===

'''Description:''' Adding fuzz testing to Kodi would be very valuable to find problems in the current code base. Especially security problems. First step would be choosing a framework either American fuzzy lop, libFuzzer or other similar projects. After we decided on that it would be time to start to fuzz different methods that are widely used in Kodi and try to expose flaws in those. If this leads to success, it should be documented and made repeatable.

'''Expected outcome:''' Being able to easily add more fuzz tests and having the process to do this documented.

'''Skills preferred:''' C++, CMake

'''Possible mentors:''' Razze

'''Difficulty:''' Medium

'''Type:''' Risky/Exploratory

===inputstream.adaptive binary addon===

'''Description:''' inputstream.adaptive is a binary kodi inputstream addon written in C++ and handles multi bitrate streams provided in DASH / Smoothstream manifest or HLS multi bitrate playlists. The addon provides demuxed / encoded packets to kodi and kodi renders the data with its internal videoplayer. Digital Rights Management (DRM) is implemented in inputstream.adaptive to allow playback of protected media. inputstream.adaptive is used by many (> 100) addons to play (legal) encrypted media.
<br>The addon sources are still hosted in my own git repository (https://github.com/peak3d/inputstream.adaptive) but I'll hand over the sources to kodi repository if someone is interested on working at one of these 2 most urgent topics:

====Bitrate switch====

'''Description:''' In the current inputstream.adaptive implementation a stream resolution / bitrate is selected at start time. Because of network fluctations / manual window / screen changes or performance stats of rendered frames it should be possible to switch seamless to lower / higher stream representations.

'''Expected outcome:''' Automagically select / change seamless stream depending on external factors.

'''Skills preferred:''' C++, CMake

'''Possible mentors:''' peak3d

'''Difficulty:''' Medium

'''Type:''' Media playback

====Read ahead====

'''Description:''' Currently stream segments are downloaded on request (that is kodi is requesting more data to display). Because the kodi videoplayer internal buffer is small (8 seconds), network fluctuation can lead to bad user experience (stream interruption). What users want is that inputstream.adaptive buffers a configurable amount of time ahead to bypass this issue.<br> Buffering ahead in multi bitstream is not only a technical task, there are numerous resolutions / bitrates for the same movie time segment in the manifest from which the "best" one should be buffered. The concept of what to read will be an not trivial engeneering task.<br>Bitrate switch (see previous topic) will be a prerequasite to "Read ahead" because on low network times lower bitrate streams are read compared to good network times.

'''Expected outcome:''' Implementation of read ahead logic for multi bitrate streams, user configurable.

'''Skills preferred:''' C++, CMake

'''Possible mentors:''' peak3d

'''Difficulty:''' Medium

'''Type:''' Media playback

===Other ideas===
These ideas still need expanding and/or assigned a potential mentor. If one of these ideas interests you, feel free to ask for more info in the GSoC 2020 forum area. We may be able to assign a mentor if enough interest is shown
*Visual Studio Code addon to validate/syntax highlight Kodi Addons (possible mentors: velocity)
*Using fruit or similar to use DI in Kodi and write tests
*High quality scalers for OpenGL(GLSL). Scale Y and UV plane separately (possible mentors: velocity)
*Support downloading of of media items (the actual file not just the metadata) from another Kodi instance (e.g. through UPnP) into the local library. This could be done in a "send to" way and in a "download" way and it could also be combined with transcoding depending on the target device.
*UPnP device profiles. there's already a PR that goes in that direction and the problem is that right now we can only really provide device specific MIME type hacks but if we have transcoding we'll definitely need this
*Implementing a performance critical element of kodi in rust

=== More ===
We feel it is important to note that, while we are interested in a focus on the listed three areas, we would like to stress passion, expertise, and creativity above all else. If you would like to do something completely different, definitely send in that proposal. The ideas listed above are, as always, merely suggestions. We will be interested in any idea, so long as you can communicate your interest, your background, and your solution the problem.

== Students project proposal ideas ==

Submit your own proposals on the '''[https://forum.kodi.tv/forumdisplay.php?fid=301 Kodi GSoC forum]'''. They can be as big or as small as you feel you can comfortably accomplish between '''PROJECT START DATE''' and '''PROJECT END DATE'''. In the end, it's better to have a smaller, completed project, rather than a larger, incomplete project.

To submit a proposal idea:
# Copy the text from '''[[#Outline for proposals]]'''.
# Create a new forum post '''[https://forum.kodi.tv/forumdisplay.php?fid=301 HERE]''' and paste the text.
# Fill out everything using your specific proposal.

[[Category:Google Summer of Code]]

Google Summer of Code/2021

2021-01-30T12:58:50Z

Yol: Copy of 2020

{{GSOC_nav}}
{{mininav| [[Google Summer of Code]] }}
[[File:GSOC_2016_logo.png|left|150px]]Welcome to the Kodi [http://summerofcode.withgoogle.com Google Summer of Code] ideas page. 

We encourage interested students of all ethnities and genders to review some of the ideas on this page, and then feel free to provide input on any ideas you may have in the '''[https://forum.kodi.tv/forumdisplay.php?fid=301 Kodi GSoC 2020 forum]''' and chat about any project you’d love to cover. To propose a project, see '''[[#Students project proposal ideas]]'''.

From the 25th March to the 9th of April, any interested students may apply at the [http://summerofcode.withgoogle.com GSOC home page] to work with Kodi. After that, Google will notify applicants whether we get to work with each other according to the [http://developers.google.com/open-source/gsoc/timeline GSOC schedule].
{{-}}
{| width="100%"
| align=left |
__TOC__
| align=right |
{{YouTube|kQq0mx-wshk}}
|}
== About Us ==
As there may be many students who have landed here as a result of GSOC, but are unfamiliar with the project, here are a few resources that may help explain what we are about.

:Kodi (formerly known as XBMC) is an award-winning free and open source (GPL) software media player and entertainment hub for digital media, designed around the 10-foot interface (living room) environment. Created in 2003 by a group of like minded programmers, Kodi is a non-profit project run and developed by volunteers located around the world. More than 500 software developers have contributed to Kodi, and 100-plus translators have worked to expand its reach, making it available in more than 60 languages. For more information, see the page '''[[Kodi]]'''.

<br />
To get an idea of what Kodi is truly capable of, it really must be seen. Check out a few other user-created videos:<br />
[http://www.youtube.com/watch?v=NcogPuSo-DU Kodi with the default Confluence skin]<br />
[http://www.youtube.com/watch?v=4asUCtE0ONU Kodi with Aeon Nox skin]<br />
[http://www.youtube.com/watch?v=4NR57ELY28s Kodi on Raspberry Pi]<br />
[http://www.youtube.com/watch?v=e_0PB5hfz_k Kodi's new PVR functionality]<br />
<br />

Kodi is written primarily in c++ and runs on a variety of platforms including Android, iOS, Linux, OS X, and Windows. It has been ported to work on several low-power platforms including the Raspberry Pi and Android.

Kodi was a mentoring organization in 2008, 2012, 2013, 2015, 2017, 2018, 2019 and had team members involved in GSoC for other projects during 2011.

If Kodi is selected as a mentoring organization for 2020, students will need to review the Overview of a good project proposal, follow the outline for proposals when applying, and review the list of project ideas detailed below. Students are welcome to propose ideas outside the list and are encouraged to be as creative as they like.

=== Mentors ===
All mentors and backup mentors are extremely experienced in the Kodi codebase and will thus be able to assist students in getting to know the codebase and in quickly identifying projects that are both achievable for someone unfamiliar with the internal workings of Kodi and desirable to the wider Kodi community.

==Prerequisites==
C++ coding skills, basic familiarity with Git, solid understanding and interest in programming. Ability to quickly understand existing code is beneficial.

== Project Proposals ==
=== Overview ===
Qualifications for a good Summer of Code proposal:
* Discrete, well-defined, modular
* Comprised of a series of measurable sub-goals
* Based on open specs that are available free of charge
* Based on complete specs
An example of a good proposal is the implementation of a new feature or function that is not yet available in Kodi.

An example of a less desirable proposal is one that's not as measurable, such as refactoring an existing API. Bad proposals tend to be ones that would require touching a lot of core code.

To re-iterate:
* Localized/isolated code projects = ''good''
* Global code refactoring = ''bad''
* A project should have a set of subgoals, so even if the end goal turns out to be too big some of the parts will be of benefit.
* Not too big! This is an important problem when choosing a project, while it is fun to think about solving a grand project its not always realistic. Its better to finish a smaller project than to start a grand one.

=== Where to submit proposals ===
In addition to submitting to the [https://summerofcode.withgoogle.com/ Google Summer of Code] website, you are highly encouraged to submit your idea/proposal to the [https://forum.kodi.tv/forumdisplay.php?fid=293 Kodi forum] for discussion. Any proposal not submitted to the forum for discussion will likely not be considered.

=== Outline for proposals ===
{{divbox|blue||
PROJECT TITLE GOES HERE

* '''Name:'''
* '''forum/e-mail:'''
* '''Summary:''' A somewhat small but explanatory walk through of the project. It should not be overly detailed just enough to understand the problem trying to be fixed and how this project opt to solve it.
* '''How will I achieve this:''' Explain how the project will be done, what technologies are needed and how to implement them.
* '''What will the project focus on:''' Explain what the project will focus on, what is the important parts of the project.
* '''Benefits:''' Who will benefit and why from this project. Think about what a user or developer may need or do to benefit from it. Why does it benefit many users.
* '''Goals:''' What is the goal of the project, a project may not always solve the problem entirely as it may take to much time. Think hard about what can be accomplished during a summer with your skill and deduct that quite a bit. If the project can't be done after this perhaps its better to opt for a smaller one or one with subgoals.
* '''What does it touch in Kodi:''' Think about what parts of the code this may touch, Kodi is a big application and a lot of the code is spread out and very complex. If a project touches to much it may be impossible to complete.
* '''Requirements:''' What is needed to complete the project, what code language knowledge what hardware etc.
* '''Possible mentors:''' Place to add possible mentors (Team-Kodi will add this).
}}

== Team-Kodi proposal ideas up for discussion ==

=== Explore building binary addons in rust ===
'''Description:''' While Kodi has python addons, it can also handle binary addons. But these need to be build one by one for each platform and also might fail on errors. Rust might help with both of those problems and more. The idea is to use the api we have but via rust ffi and see where that leads us.

'''Expected outcome:''' Documentation and templates on how to use rust with kodi. In the best case also one or two example addons.

'''Skills preferred:''' C++, Rust, C

'''Possible mentors:''' spiff, Razze, velocity

'''Difficulty:''' Hard

'''Type:''' Binary addon development

=== A new web interface ===
'''Description:''' Kodi has a webinterface by the name of chorus2 (https://github.com/xbmc/chorus2) which is written in coffeescript and as it stands no team member is able to work on coffeescript. So the idea would be to implement a new interface, in a newer language. I would like to see Elm or Svelte, but others would be fine too, as long as we would be able to maintain it.

'''Expected outcome:''' A new webinterface (can be redesigned) or a port of the old one.

'''Skills preferred:''' HTML, CSS, Javascript, Typescript, Elm

'''Possible mentors:''' Razze

'''Difficulty:''' Medium

'''Type:''' Webinterface development

=== Better profile support ===
'''Description:''' Profile support inside Kodi remains extremely hacked together. Improving profile projects would likely be broken down into smaller chunks to make each chunk truly achievable in a summer. Database handling for profiles needs to be reviewed and changed so that the user experience is more streamlined. It should also be possible to better guard code paths that need to check for specific profile rights.

'''Expected outcome:''' Profiles should be more user-friendly than before and not be an afterthought. Being able to easily add more profile features is the big ultimate goal, as we want to support profiles for kids that automatically hide media that's not for them. Just as an example.

'''Skills preferred:''' C++

'''Possible mentors:''' spiff

'''Difficulty:''' Hard

'''Type:''' Core development

=== Replacing depends with a CMake-based system ===

'''Description:''' Kodi has its own system for building the many libraries Kodi depends on that supports most platforms (Linux, Android, OS X, iOS) and cross-compiling called depends. At the moment, it is implemented with autotools and hand-crafted Makefiles. This has lead to a lot of code duplication, poor maintainability, and not being very user-friendly. Also, it does not currently work on Windows. This task would be about replacing the current system with a new implementation in CMake that has better maintainability.

'''Expected outcome:''' A CMake-based dependency build system that offers roughly the same features as depends (i.e. all required libraries covered, diverse platform support, crosscompilation). If the solution can also be applied to Windows by e.g. adding minimal CMake files to replace some UNIX-only build systems, that would be a big plus, but it is not necessary.

'''Skills preferred:''' CMake, shell scripting, general familiarity with UNIX/Linux

'''Possible mentors:''' wsnipex

'''Difficulty:''' Medium

'''Type:''' Infrastructure/Automation

=== Integrate TUF (The Update Framework) ===

'''Description:''' Kodi uses a self-built mechanism for installing and updating add-ons from add-on repositories. Unfortunately, it is not very secure. This project would be about replacing the add-on repository code with the usage of TUF (The Update Framework), a quite recent library that solves many common security problems for updaters. TUF does not currently have a C or C++ implementation. The reference implementation is in Python, which we do not want to integrate with C++ for this core piece of application code. Due to security concerns, we also do not want to implement TUF ourselves. That leaves using rust-tuf, an experimental Rust implementation. First step would be to write a C wrapper library so that we can use it from Kodi.

'''Expected outcome:''' Add-on repository in Kodi using TUF that builds and works on all supported platforms (beware, there are quite a lot) and is integrated into the Kodi add-on infrastructure (i.e. there are also tools to generate valid repositories). It should support all core add-on functionality (be able to list, install, and update add-ons).

'''Skills preferred:''' C++, Rust, Python (for creating the repository the TUF reference implementation could be used)

'''Possible mentors:''' yol

'''Difficulty:''' Hard

'''Type:''' Risky/Exploratory (rust-tuf is unstable and there is also a lot of work to be done on the backend side)

===Add-ons===
====Automatic add-on checker for binary add-ons====
'''Description:''' Kodis add-on checker checks each Kodi add-on PR on GitHub for certain problems, which ultimately makes reviewing Python add-ons easier for the team. But the other type of add-ons, binary add-ons is not being checked so far, which makes reviews and coding guidelines hard to handle. Thus it would be nice to also check those add-ons, either via the current checker written in Python or a new binary add-on specific checker. Goals would include checking the addon.xml, the C++ code and a check for potentially malicious code.

'''Expected outcome:''' Being able to run the checker against all binary repo PRs on GitHub.

'''Skills preferred:''' Python, C++

'''Possible mentors:''' Razze

'''Difficulty:''' Hard

'''Type:''' Low-hanging fruit

===Achievements in RetroPlayer===

'''Description''': Retroarch has developed support for achievements in certain select libretro cores. This project would consist of porting whatever work might be portable and otherwise integrating the existing libretro achievement system into Kodi's RetroPlayer implemented using Kodi's UI system. Could be tackled a few different ways, including simply linking the user to the retroachievements.org or creating a full achievement database in Kodi.

'''Expected Outcome''': Users should be able to see their achievements in Kodi. Player manager and Player profile support may be in development concurrently, so thought should be given to those systems.

'''Skills preferred''': C++, python, possibly php

'''Possible mentor''': garbear, velocity

'''Difficulty''': medium

'''Type''': Fun/Peripheral

'''Notes''': Garbear has broken down the Retroplayer project into manageable pieces including input, core, game add-ons, peripheral add-ons, netplay, a game library implementation, and shaders to do things like emulate a CRT monitor. This is one example, but many pieces are currently being worked on or are near completion, and many more could use help from a student familiar with the area. Visit the retroplayer section of the Kodi forum to see all the major projects still to do.

===Saved game manager for RetroPlayer===

'''Description''': Kodi excels at managing large movie, music, and (with add-ons) game libraries. However, savestates and in-game saves are simply stored next to the ROM or in a hard-coded folder.

This project would consist of designing a user interface for saved game management. Some database work will probably be required. As a stretch goal, automatic saved-game captioning can be performed using the "Rich Presence" feature of RetroAchievements.org.

In 2016, Garbear created an experimental saved game manager - see https://github.com/xbmc/xbmc/pull/11034. It may be possible to re-use ideas and code from this PR. Here's what the saved game manager looked like at the time:

[[File:Saved game manager.png|600px|Saved game manager from 2016]]

'''Expected Outcome''': Users should be able to manage their savestates and in-game saves in Kodi.

'''Skills preferred''': C++, optional python

'''Possible mentor''': garbear, velocity

'''Difficulty''': medium

'''Type''': Fun/Peripheral

===Runahead for RetroPlayer===

'''Description''': This feature, pioneered by libretro (see [https://www.libretro.com/index.php/retroarch-1-7-2%E2%80%8A-%E2%80%8Aachieving-better-latency-than-original-hardware-through-new-runahead-method/ Achieving better latency than original hardware through new runahead method]) allows for input latency better than the original console!

'''Expected Outcome''': Implemented runahead input

'''Skills preferred''': C++

'''Possible mentor''': garbear, velocity

'''Difficulty''': medium

'''Type''': Fun/Peripheral

===Player Manager for RetroPlayer===

'''Description''': Currently, player assignment and controller selection is hard-coded. This project would allow the user to configure which controllers are connected to the virtual console, enabling multiplayer in games that are currently hard-coded to single player.

A player management concept is outlined here: https://github.com/garbear/xbmc/issues/87. Ideas and code from the issue can possibly be re-used in this project.

[[File:Player manager.png|600px|Player manager concept art]]

'''Expected Outcome''': Players can change virtual input devices and choose which player number they are

'''Skills preferred''': C++

'''Possible mentor''': garbear, velocity

'''Difficulty''': medium

'''Type''': Fun/Peripheral

===<insert feature from RetroArch here>===

'''Description''': RetroArch is an amazing, full-featured emulator system. Many of these features would make good GSoC projects!

'''Expected Outcome''': Feature from RetroArch is implemented

'''Skills preferred''': C++, optional Python

'''Possible mentor''': garbear, velocity

'''Difficulty''': various

'''Type''': Fun/Peripheral

===Game-theoretic engine for RetroPlayer===

'''Description''': Currently, Kodi's game engine (RetroPlayer) is based on VideoPlayer - games act as "codecs" that accept input and produce audio and video streams. While this rocks for performance (we've even mirrored zero-copy support from VP), it makes many features, such as rewind, runahead, and netplay difficult to integrate.

The project is to implement the emulation equation described by the Special Theory of Emulation introduced in [https://github.com/garbear/xbmc/issues/89 Reinforcement Learning Bots], where S is State and A is Action:

[[File:S_0.gif|Initial value of S]]<br/>
[[File:A_0.gif|Initial value of A]]

[[File:State update 2.gif|State update]]<br/>
[[File:Action update 3.gif|Action update]]

The equation results in the time series:

(S<sub>0</sub>, A<sub>0</sub>, S<sub>1</sub>, A<sub>1</sub>, S<sub>2</sub>, A<sub>2</sub>, ...)

The emulation equation describes all of emulation in a game-theoretic manner. With such an engine, powerful features become incredibly easy:

* When emulation is a time series, rewind is just decrementing t
* Runahead is just replacing an A several t's ago
* Netplay is also possible - just run a consensus algorithm like RAFT over the State/Action pairs.

'''Expected Outcome''': Games play using the new engine. Rewind is now easy. Runahead is now easy. Netplay is still hard, but the emulation equation turns netplay from a networking problem into a consensus problem.

'''Skills preferred''': C++

'''Possible mentor''': garbear, velocity

'''Difficulty''': advanced

'''Type''': Fun/Peripheral

===Reinforcement learning bots for RetroPlayer===

'''Description''': Same as the above, but implement the emulation equation described by the General Theory of Emulation in [https://github.com/garbear/xbmc/issues/89 Reinforcement Learning Bots].

'''Expected Outcome''': Super-human gaming bots take over the world

'''Skills preferred''': C++

'''Possible mentor''': garbear, velocity

'''Difficulty''': hell

'''Type''': Fun/Peripheral

===Retroverse===

'''Description''': This project introduces the Retroverse: an infinitely-rewindable branching history of all gameplay.

Braid creator Jonathan Blow gave a presentation titled [https://www.youtube.com/watch?v=8dinUbg2h70 The Implementation of Rewind in Braid]. In 2013, Themaister [https://github.com/garbear/xbmc-retroplayer/commit/97e52df8a2f82a36952c8bcbebc133b3efc1babe donated] braid-style rewind to Kodi. This became the basis of the [https://github.com/xbmc/xbmc/blob/master/xbmc/cores/RetroPlayer/streams/memory/IMemoryStream.h memory streaming API] in RetroPlayer.

Recall how Blow describes his rewind feature: "Record full world state for every frame always; do not drop frames. Compress data somehow." The challenge of this project is to figure out that "somehow".

Does recording hundreds of hours of gameplay sound impossible? Assume deterministic emulation. The State can be fully reconstructed from the Action of the previous timestep, so only the Action needs to be saved. The Atari 2600, released in 1977, has 5 buttons, needing 5 bits. With a 5 bit frame size, you can store around 850 years of continuous (or nonlinear) Atari 2600 gameplay on a 1TB drive. Still seem impossible?

'''Expected Outcome''': Implement the <code>CNonlinearMemoryStream</code> class referenced in <code>[https://github.com/xbmc/xbmc/blob/master/xbmc/cores/RetroPlayer/streams/memory/IMemoryStream.h IMemoryStream.h]</code>. Enable LZ4 and/or RLE compression of savestate diffs. Enhance autosave by using interpolation to drop "base frames". Store a tree instead of a buffer!

'''Skills preferred''': C++

'''Possible mentor''': garbear, velocity

'''Difficulty''': advanced

'''Type''': Fun/Peripheral

===Using fuzz testing to fuzz test Kodi===

'''Description:''' Adding fuzz testing to Kodi would be very valuable to find problems in the current code base. Especially security problems. First step would be choosing a framework either American fuzzy lop, libFuzzer or other similar projects. After we decided on that it would be time to start to fuzz different methods that are widely used in Kodi and try to expose flaws in those. If this leads to success, it should be documented and made repeatable.

'''Expected outcome:''' Being able to easily add more fuzz tests and having the process to do this documented.

'''Skills preferred:''' C++, CMake

'''Possible mentors:''' Razze

'''Difficulty:''' Medium

'''Type:''' Risky/Exploratory

===inputstream.adaptive binary addon===

'''Description:''' inputstream.adaptive is a binary kodi inputstream addon written in C++ and handles multi bitrate streams provided in DASH / Smoothstream manifest or HLS multi bitrate playlists. The addon provides demuxed / encoded packets to kodi and kodi renders the data with its internal videoplayer. Digital Rights Management (DRM) is implemented in inputstream.adaptive to allow playback of protected media. inputstream.adaptive is used by many (> 100) addons to play (legal) encrypted media.
<br>The addon sources are still hosted in my own git repository (https://github.com/peak3d/inputstream.adaptive) but I'll hand over the sources to kodi repository if someone is interested on working at one of these 2 most urgent topics:

====Bitrate switch====

'''Description:''' In the current inputstream.adaptive implementation a stream resolution / bitrate is selected at start time. Because of network fluctations / manual window / screen changes or performance stats of rendered frames it should be possible to switch seamless to lower / higher stream representations.

'''Expected outcome:''' Automagically select / change seamless stream depending on external factors.

'''Skills preferred:''' C++, CMake

'''Possible mentors:''' peak3d

'''Difficulty:''' Medium

'''Type:''' Media playback

====Read ahead====

'''Description:''' Currently stream segments are downloaded on request (that is kodi is requesting more data to display). Because the kodi videoplayer internal buffer is small (8 seconds), network fluctuation can lead to bad user experience (stream interruption). What users want is that inputstream.adaptive buffers a configurable amount of time ahead to bypass this issue.<br> Buffering ahead in multi bitstream is not only a technical task, there are numerous resolutions / bitrates for the same movie time segment in the manifest from which the "best" one should be buffered. The concept of what to read will be an not trivial engeneering task.<br>Bitrate switch (see previous topic) will be a prerequasite to "Read ahead" because on low network times lower bitrate streams are read compared to good network times.

'''Expected outcome:''' Implementation of read ahead logic for multi bitrate streams, user configurable.

'''Skills preferred:''' C++, CMake

'''Possible mentors:''' peak3d

'''Difficulty:''' Medium

'''Type:''' Media playback

===Other ideas===
These ideas still need expanding and/or assigned a potential mentor. If one of these ideas interests you, feel free to ask for more info in the GSOC 2020 forum area. We may be able to assign a mentor if enough interest is shown
*Visual Studio Code addon to validate/syntax highlight Kodi Addons (possible mentors: velocity)
*Using fruit or similar to use DI in Kodi and write tests
*High quality scalers for OpenGL(GLSL). Scale Y and UV plane separately (possible mentors: velocity)
*Support downloading of of media items (the actual file not just the metadata) from another Kodi instance (e.g. through UPnP) into the local library. This could be done in a "send to" way and in a "download" way and it could also be combined with transcoding depending on the target device.
*UPnP device profiles. there's already a PR that goes in that direction and the problem is that right now we can only really provide device specific MIME type hacks but if we have transcoding we'll definitely need this
*Implementing a performance critical element of kodi in rust

=== More ===
We feel it is important to note that, while we are interested in a focus on the listed three areas, we would like to stress passion, expertise, and creativity above all else. If you would like to do something completely different, definitely send in that proposal. The ideas listed above are, as always, merely suggestions. We will be interested in any idea, so long as you can communicate your interest, your background, and your solution the problem.

== Students project proposal ideas ==

Submit your own proposals on the '''[https://forum.kodi.tv/forumdisplay.php?fid=301 Kodi GSoC forum]'''. They can be as big or as small as you feel you can comfortably accomplish between '''PROJECT START DATE''' and '''PROJECT END DATE'''. In the end, it's better to have a smaller, completed project, rather than a larger, incomplete project.

To submit a proposal idea:
# Copy the text from '''[[#Outline for proposals]]'''.
# Create a new forum post '''[https://forum.kodi.tv/forumdisplay.php?fid=301 HERE]''' and paste the text.
# Fill out everything using your specific proposal.

[[Category:Google Summer of Code]]

Mirrors

2020-08-24T11:14:33Z

Yol: updated with current information, removed pre-2015 content

{{mininav}}

This page contains information about our mirrors network setup.

== Download mirrors ==

To provide downloads we use a network of mirrors across the globe to provide the best possible location to download from. For actually distributing the downloads and making sure you will download from the best server available we have been using Mirrorbits, which has been operating since August 2015 and so far hasn't failed us yet. This is a great piece of software that constantly checks the status of the mirrors and dishes out files based on certain criteria, in an effort to ensure that downloads work as quickly and reliably as possible. Besides these builds it also hosts all the add-on which you can find in our official kodi.tv repository.

== Information ==

The actual mirror list is generated automatically and can be found by appending <code>?mirrorlist</code> to the URL of any mirrored file on mirrors.kodi.tv.
We also provide a status report for each server if they are still in sync at https://mirrors.kodi.tv/mirmon.html

So we would like to thank all these providers for helping us out on distributing Kodi throughout the world. If you are interested in being added to this list feel free to contact us. '''Do note that we will only accept offers from large institutions or companies to keep possible problems at a minimum.'''

Our main mirror address is: http://mirrors.kodi.tv

== rsync setup ==

We have two main rsync mirrors which are used by main Tier1 mirror hosts per continent.
All other hosts should use those hosts according to their location.

=== main ===

primary Tier1 USA server:
* Name: gatech.edu
* address: rsync://rsync.gtlib.gatech.edu/xbmc/
* Uses: rsync://rsync.kodi.tv/main/
** sync on half past the hour XX:30
* Notes:
** all other USA mirrors should sync from this host
** mirrors should sync at XX:00

=== euro ===

primary Tier1 Europe server:
* Name: heanet.ie
* address: rsync://ftp.heanet.ie/mirrors/xbmc/
* Uses: rsync://rsync.kodi.tv/euro/
** sync on the hour XX:00
* Notes:
** all other non-USA mirrors pull from them
** mirrors should sync at XX:00

== Requirements ==
* Space needed: ~100GB
* Mirrors pull at various times, the mirrorbits database contains notes about these times.
* Every couple of hours. Max is every 24h.
* If mirrors ever move to a new server, the dns entry for rsync.xbmc.org or rsync.kodi.tv can be changed and there should theoretically be no interruption. In reality, it makes sense to be sure that no one is pulling by IP or has white-listed the current IP for our constant mirror status checks.
* hosts need to provide this information to have proper setup
** http:// location (mandatory)
** ftp:// location (currently not used at all)
** rsync:// access to the mirrors for scanning available files(mandatory)
** Network bandwidth (gives indication of probability factor for traffic redirecting)
** Host webpage
** Host description
** Redirect options: AS network only / Continent only/ Country only / Global
** Admin name (will not be made public)
** Admin e-mail (will not be made public)
* rsync server is split up in two sections for providing data
** Please choose one of the TIER server rsync locations

Extra information
* rsync data could range to ~400Mb a day (amount may vary up or down)
* We have no hard data on amount of data that we redirect. We try to expand our network to reduce the amount for each mirror. We can always reduce the redirection criteria to reduce traffic to your mirror. Please contact us if needed.

[[Category:XBMC_Foundation]]

Settings/Interface/Master lock

2020-02-10T21:50:19Z

Yol: Add clarification about profiles as security feature

{{mininav| [[Settings]] | [[Settings/Interface|Interface]] }}

__TOC__
{{-}}

== General ==
The Master Lock allows users to protect their content and settings by applying a PIN to various areas of Kodi. Three attempts are available to enter the correct PIN. If the third attempt fails, restart {{kodi}} to try again.

{{note|This feature only protects the {{kodi}} interface from, say, curious children. It will not protect the content and settings files outside of {{kodi}} from being accessed via the operating system. Also, it may be bypassed via the web interface or other add-ons and advanced {{kodi}} features.}}

[[File:Interface master.JPG|600px|left]]
{{-}}

=== Master lock code and settings ===
{|
|- valign="top"
| width=120px | {{nowrap|'''Settings level:'''}}
| Standard
|- valign="top"
| '''Description:'''
| Here you can enable or disable the master lock and define the PIN code used to unlock it. You can also specify which areas of the application will need a PIN to access them.<br>
See Lock Preferences below for a description of available settings.<br>
'''Note:''' This setting is valid for the profile which was used to set the PIN only. To lock other Profiles, repeat these steps.
|}

=== Ask for master lock code on startup ===
{|
|- valign="top"
| width=120px | {{nowrap|'''Settings level:'''}}
| Standard
|- valign="top"
| '''Description:'''
| To access this setting, you must exit back to the main menu and then re-enter the Master Lock Settings Screen at which time you will be asked for the PIN. The setting will become active and can be ''Enabled'' if required.<br>
'''Note:''' This setting will affect all Profiles regardless of which Profile is used for startup.
|}

== Lock preferences ==
The following are the setting shown when selecting the ''Master lock code and settings'' option above.

=== Master Lock ===
[[File:MasterLock.jpg|600px|left]]
{{-}}

{|
|- valign="top"
| width=120px | {{nowrap|'''Settings level:'''}}
| Standard
|- valign="top"
| '''Description:'''
| Set the type of PIN to be used as shown in the image.
|}
{{-}}

=== Lock preferences ===
[[File:MasterLock1.jpg|600px|left]]
{{-}}

{|
|- valign="top"
| width=120px | {{nowrap|'''Settings level:'''}}
| Standard
|- valign="top"
| '''Description:'''
| Choose which parts of {{kodi}} to protect by enabling the item. Available selection is displayed in the image.<br>
When accessing a locked menu item, the PIN will be requested. Three attempts are available to enter the correct pin. If there are three failed attempts, restart Kodi to try again.
|}

{{Top}}

{{updated|18}}
[[Category:FAQ]]
[[Category:Index]]
[[Category:Guides]]
[[Category:Manual]]
[[Category:Karellen]]
[[Category:First time user]]
[[Category:Advanced topics]]
[[Category:Quick Start Guide]]

Profiles

2020-02-10T17:35:18Z

Yol: Add clarification about profiles as security feature

__TOC__
{{-}}
<section begin=intro />Profiles allow users to save all of settings as a profile and change them at the touch of a button. It also allows you to grant access to specific folders and network shares based on the profile being used. This is ideal for systems that have multiple users. It works much the same as setting up individual users on your home computer.<section end=intro />

{{note|While profiles do allow to share the same Kodi instance with multiple users, they are not a security feature. The web interface, for example, may still allow to change the active profile without entering a password.}}

These individual profiles allow you to customize the environment for multiple users, allowing for such functionality as:
* Customized view settings such as skins for each user
* The ability to lock folders, such as network shares on a per-user basis
* Separate media [[Databases|libraries]] for each user
* Unique RSS feeds for each user
* Unique [[Keymap|keymapping]] for each user
* Unique network settings
All options stored in the [[userdata folder]] can be customized per profile, allowing for an amazing amount of flexibility.

{{-}}

== Adding a profile ==

In order to add a profile, follow the steps below

<gallery mode="packed" widths=500px heights=283px>
File:Estuary_Profiles_Adding_Profile_1.jpg| '''Step 1:''' Select "Add profile"
File:Estuary_Profiles_Adding_Profile_2.jpg| '''Step 2:''' Enter a name for the profile
File:Estuary_Profiles_Adding_Profile_3.jpg| '''Step 3:''' Select a directory for your profile at which your personalized settings will be stored.<br />'''OK''' will choose the 'default' folder which will be stored under the [[Userdata|userdata]]-folder and will have the same name as the profile name. <br />'''New folder''' will give you the option to specify a self-created folder for your profile which you need to select after a name for it was given. The folder for the profile will then be found under: userdata -> profiles -> <created folder name>
File:Estuary_Profiles_Adding_Profile_4.jpg| '''Step 4:''' Select specific profile settions which are explained below
File:Estuary_Profiles_Adding_Profile_5.jpg| '''Step 5:''' Choose to copy settings from the defaul user ot start with default settings
File:Estuary_Profiles_Adding_Profile_6.jpg| '''Step 6:''' Choose to copy media sources from the default user or start fresh.
</gallery>

=== Specific profile settings ===

; Profile Name
: The name of the profile you entered above

; Profile picture
: Browse to some icon you would like to select as a profile picture

; Profile directory
: The path to the profile directory you might have created above

; Lock prefences
: Allows you to lock many of your preferences. This is detailed below.

; Media Info
:Allows you to have separate information saved for your media, i.e. IMdB, AllMusic, etc. The options are
::* '''Separate''' - Profiles have separate media info with full control
::* '''Shares with Default''' - Shares media info with the default user with full control
::* '''Shares with Default (Read Only)''' - Shares media info with the default user, and is locked by the master code
::* '''Separate (Locked)''' - Profile has separate media info, but you can only change it by enabling master mode.

; Media sources
:Allows you to have separate media sources for the profiles. The options are
::* '''Separate''' - Profiles have separate media sources with full control
::* '''Shares with Default''' - Shares media sources with the default user with full control
::* '''Shares with Default (Read Only)''' - Shares media sources with the default user, and is locked by the master code
::* '''Separate (Locked)''' - Profiles have separate media sources, but you can only change them by enabling master mode.
{{-}}
<br>

== Deleting a profile ==

In order to delete an unused profile, simply navigate to {{button|Settings}}->{{button|Profile Settings}}->{{button|Profiles}}, then navigate to the profile you want to delete and bring up the context menu using either {{button|guide}} on a remote or {{button|c}} on a normal keyboard. Then select {{button|Delete}} like shown in the screenshot below:
<br>

[[File:Profles-delete_profile-v17.jpg|500px]]<br />

{{-}}

== Switching profiles ==

Switching profiles from a currently running Kodi instance can be done in different ways:

You are able to switch a profile while navigating to the profiles-section, selecting the specific profile you want to use, bring up the context menu using either {{button|guide}} on a remote or {{button|c}} on a normal keyboard and select {{button|Load}} like shown in the screenshot below:<br />
<br />

[[File:Profiles-load_profile-v17.jpg|500px]]<br />
<br />

The other way is to log-off from the current Kodi session and log-in to another profile:<br />
<br />
<gallery mode="packed" widths=500px heights=283px>
File:Profiles-switch_profile-v17.jpg| '''Step 1:''' Log off from the current profile
File:Profiles-switch_profile2-v17.jpg| ''' Step 2:''' Log in to another profile
</gallery>

Another way of switching profiles is to bind ''load profile'' to a key in [[Keymaps|keymaps.xml]] by using the [[List_of_built-in_functions|built-in function]] LoadProfile. If you only have two profiles you can use the same key to switch back and forth. e.g. LoadProfile bound to {{keypress|y}}<br />

Switch from User1 to User2 (Users1's keymap.xml): <y>LoadProfile(User2)<y/><br />
Switch from User2 to User1 (Users2's keymap.xml): <y>LoadProfile(User1)<y/><br />

Keymap.xml example:
<syntaxhighlight lang=xml>
<keymap>
<global>
<keyboard>
<y>LoadProfile(User2)</y>
</keyboard>
</global>
</keymap>
</syntaxhighlight>
{{-}}

== profiles.xml and profiles folder ==

It is important to mention that this section exists so that users have some documentation to refer to in the event of profile related issues occur like profile corruption. This '''does not''' constitute a invitation to novice users to start messing around with said files/folders and cause inadvertent problems that would not otherwise exist.

{{notice|'''Do not edit the any of the xml files''' in question unless '''indicated by a Kodi developer''' or for '''backup''' purposes only|WARNING}}

=== profiles.xml ===

A ''profile.xml'' file exists after the very first installation of Kodi at its userdata-folder and unless you have created additional profiles it won't have any other information as for the '''Master user''' (Kodis default user). If you create other/additional profiles, that file will be populated with additional informations about the created profile.

The example below shows a profile.xml file containing the '''Master user''' and the user '''Test''' as an additional profile. In that case it will show that the '''Master user''' uses a lockcode which '''Test''' doesn't use. As you can see the given password is shown in plain text. So please be aware that a locked profile doesn't provide any kind of security if other users have access to the underlying file system.

For the lock preferences and the Master lock, please visit: [[Settings/Interface/Master_lock|Settings -> Interface settings -> Master lock]]

{| class="mw-collapsible mw-collapsed wikitable"
|-
! Example profiles.xml file
|-
|
<syntaxhighlight lang=xml enclose="div">
<profiles>
<lastloaded>0</lastloaded>
<useloginscreen>false</useloginscreen>
<nextIdProfile>2</nextIdProfile>
<profile>
<id>0</id>
<name>Master user</name>
<directory pathversion="1">special://masterprofile/</directory>
<thumbnail pathversion="1" />
<hasdatabases>true</hasdatabases>
<canwritedatabases>true</canwritedatabases>
<hassources>true</hassources>
<canwritesources>true</canwritesources>
<lockaddonmanager>false</lockaddonmanager>
<locksettings>false</locksettings>
<lockfiles>false</lockfiles>
<lockmusic>false</lockmusic>
<lockvideo>false</lockvideo>
<lockpictures>false</lockpictures>
<lockprograms>false</lockprograms>
<lockmode>1</lockmode>
<lockcode>c4ca4238a0b923820dcc509a6f75849b</lockcode>
<lastdate />
</profile>
<profile>
<id>1</id>
<name>TEST</name>
<directory pathversion="1">profiles/Test/</directory>
<thumbnail pathversion="1" />
<hasdatabases>true</hasdatabases>
<canwritedatabases>true</canwritedatabases>
<hassources>true</hassources>
<canwritesources>true</canwritesources>
<lockaddonmanager>false</lockaddonmanager>
<locksettings>false</locksettings>
<lockfiles>false</lockfiles>
<lockmusic>false</lockmusic>
<lockvideo>false</lockvideo>
<lockpictures>false</lockpictures>
<lockprograms>false</lockprograms>
<lockmode>0</lockmode>
<lockcode>-</lockcode>
<lastdate />
</profile>
</profiles>
</syntaxhighlight>
|}

=== Profiles folder contents ===

Any additional user(s) will have their own folder under '''userdata -> profiles -> <profile-name>''' which contains all informations about add-on data, databases, keymaps, thumbnails and such seperately from the ''Master user''. If you have selected "Copy default" at the steps above, the settings or media sources will be copied from the default Kodi user.

By default (no sources set neither on the master user nor on an additional profile) an additional profile folder contains similar folders as the userdata folder. For an explanation about the files and folders which are located under the <profile_name>-folder, please see: [[Userdata#UserData_folder_contents|Userdata folder contents]]

== Troubleshooting ==
<br />
'''Q: I installed skins and add-ons on the 'Master User' but I can't install it on the additional profile. Why?'''

A: Already installed skins or add-ons are marked as "disabled" under: {{button|Add-ons -> My add-ons -> <specific add-on section>}} and don't need to be installed again. After you enabled a specific add-on or a skin, those add-ons are available again and skins could be used from the {{button|Settings -> Interface settins -> Skin}} menu.

'''Q: After I created a profile, the Kodi screen stays black if I try to load it for the first time. Why?'''

A: That was a bug and it's already fixed in Kodi 18 alpha versions. After you have restarted Kodi Krypton, Kodi should behave normal and should display the GUI as expected.

=== Missing texts/different skins not loading while using profiles ===

That's a known issue and there's a workaround for that:

- create a [[Autoexec.py|autoexec.py]] file at your [[Userdata|userdata]] folder and under each {{button|<profile-name>}}-folder under {{button|userdata -> profiles -> <profile-name>}} (the path to that folder differs from the OS in use)<br />
- fill each autoexec.py with the following content:

<syntaxhighlight lang=python>
import xbmc
xbmc.executebuiltin('ReloadSkin()')
</syntaxhighlight>

That will cause a skin reload at every profile switch. Depending on your hardware in use you mostly won't notice it and the texts will be visible again and/or different skins for different profiles will load fine. For some hardware, like the RPi, it will be noticeable and also might take a little while.

== See also ==
* [[Settings/Interface/Master_lock]]
* [[Media sources#Locking]]

{{Krypton updated}}

[[Category:Manual]]
[[Category:Settings]]
[[Category:General topics]]

General information about migration to Python 3

2019-10-27T15:41:21Z

Yol: Update to final migration plan

== Overview ==

Python 3 was released 9 years ago and EOL for Python 2.7 is scheduled for 2020. Currently more and more Python project are switching to Python 3 or 2/3 compatible code. The issue of migrating Kodi’s built-in Python interpreter to Python 3.x was brought up on the Kodi forum several times. Now, thanks to a successful GSOC 2017 project, we have a working Python 3 interpreter for Kodi. That is why on Kodi DevCon 2017 Team Kodi decided that we will switch to Python 3 in the future Kodi release (v.19 preliminarily).

Unfortunately, Python 3.x versions are not backward-compatible with Python 2.x, so we decided to urge addon developers to start porting their addons to Python 3 by making the addons compatible with both Python 2 and 3 and submitting them to the official repo. This way, when Kodi with Python 3 is released, we won’t have a situation when we have no working addons.

== The Process ==

* For Kodi 18 (Leia), only addons that are compatible with both Python 2 and 3 will be accepted to the official addon repository.
* We will provide Kodi 18 builds with Python 3 so that addon developers can tests if their addons are really compatible with Python 3.
* A thread will be created on the Kodi forum so that addon devs can get help with their migration process.
* Starting from Kodi 19 (Matrix), only Python 3 will be offered (and therefore only addons that are compatible with Python 3 will be accepted to the official addon repository).

== Python 3 And 2 Differences ==

Below is a brief overview of the main differences between Python 3 and 2.

=== Unicode strings by default ===

In Python 2 built-in <code>str</code> type holds the sequence of bytes so it can be used to store both binary data and textual data in ASCII or any of 8-bit fixed-length encodings (there were plenty). Python 2 also has <code>unicode</code> type that can store text in various writing systems. A minimal unit of a <code>unicode</code> object is a Unicode codepoint (a Unicode character). Both <code>str</code> and <code>unicode</code> objects can be mixed and matched together, for example, concatenated using <code>+</code> operator.

In Python 3 <code>str</code> type holds Unicode characters, and for binary data a new <code>bytes</code> type was added. This type was also added to Python 2.7 to simplify porting to Python 3 but in Python 2.7 bytes is simply an alias for <code>str</code>. The <code>str</code> and <code>bytes</code> types are incompatible, and an attempt to use both together will result in <code>TypeError</code> exception. A <code>bytes</code> object can be converted to <code>str</code> using .decode() method, and a <code>str</code> is converted to <code>bytes</code> using .encode() method.

=== Absolute Import ===
Python 3 uses so called “absolute import” and you can no longer import neighbor modules from inside a package using only a module name. You need to either to use either a fully qualified name or a “dotted” notation.

Let’s assume that you have a <code>foo</code> package that contains <code>bar</code> and <code>spam</code> modules:
<pre>
foo/
__init__.py
bar.py
spam.py
</pre>
And you need to import <code>bar</code> module from <code>spam</code>. In Python 2 you can do:
<source lang="python">
import bar
</source>

But in Python 3 you need to use either

<source lang="python">
import foo.bar
</source>

or

<source lang="python">
from . import bar
</source>

=== Floating Point Division ===

In Python 2 applying division operator to int numbers produces int result. For example:

<source lang="python">
>>> 4 / 3
1
</source>

In Python 3 division operator always gives you a float result.

<source lang="python">
>>> 4/3
1.3333333333333333
</source>

To get an int result you need to use integer division operator:

<source lang="python">
>>> 4 // 3
1
</source>

=== Print Function ===

In Python 3 print statement has been replaced with print() function. This is not very relevant to Kodi because using print in Python addons is discouraged and xbmc.log() function should be used to write messages to the Kodi log.

=== Default Iterators ===

In Python 3 most function and methods that produce sequences return iterators instead of lists. For example, range() function and .items(), .keys(), .values() of dict type produce iterators instead of lists, and their Python 2 analogues — xrange() function and .iter* methods of dict type — have been removed.

=== No long Integers ===

In Python 3 long integer type has been removed and int type can now hold a number of arbitrary length.

Those are only some of the differences between Python 2 and 3. For a more complete list see [https://docs.python.org/3.6/whatsnew/3.0.html official Python documentation].

== Some Useful Information ==

As it was said above, Python 3 includes a number of incompatible changes, so to avoid situation when after upgrading Kodi for Python 3 support most Python addons will be broken developers should start to port their addons to be compatible with both Python 2 and 3. This is not a trivial task but fortunately there are a number of tools and recommendations to simplify this process. Here I’ll give you some advice and information about tools that will simplify creating portable code that runs on both Python 2 and 3.

=== Know Your Strings! ===

This is the most problematic part of porting Python 2 code to Python 3 so I put it first. One of the most notable differences between Python 2 and 3 is clear separation between “textual” and “binary” strings, that is, between textual data and their binary representation. This difference is often difficult to understand, especially for novice developers (not only in Python), and the fact that in Python 2 you can mix together str (binary data) and unicode (textual data) adds to that difficulty.

There are many explanations in the Internet, but here are the most basic things about strings that you need to know:

“Textual” or Unicode strings (unicode in Python 2 and str in Python 3) hold text as a sequence of characters. A minimal unit in such strings is a Unicode character — an abstract entity that represent an alphabet symbol, a punctuation sign or other symbol included in the Unicode character table. Of course, such symbols have concrete internal binary representation (a computer is a binary machine after all), but this representation is not relevant to us. All you need to know is that “textual” strings contain text units without being tied to concrete binary representation.

Unlike Unicode strings, binary strings (str in Python 2 and bytes in both Python 2 and 3) hold binary data, and a minimal unit of such strings is a byte or 8 bits. Historically, in Python 2 such strings are used for textual data encoded in ASCII or other 1-byte fixed-length encoding (e.g. Windows 1251 for Cyrillic alphabets). However, this approach has its limitation, that is why unicode type was introduced in Python 2, and in Python 3 it was renamed to str and made a default container for textual data.

Unfortunately, Python 2 allows to mix and match Unicode and binary strings in the same context and this creates big problems when porting Python 2 code to Python 3. So in order to successfully port your code to Python 3 you need to carefully consider how textual data are processed in your addon. The following recommendations will help you avoid problems when writing Python 2/3 compatible code.

=== Avoid using binary strings for text ===

Store all your text as Unicode strings. This means that all binary strings received from external sources (textual files, websites, various APIs) need to be decoded using appropriate encoding (UTF-8 in most cases). If you need to use strings literals (although using hardcoded strings for user-facing text in Kodi is strongly discouraged), they need to be defined as unicode strings as well. You can use either
<source lang="python">
from __future__ import unicode_literals
</source>
at the beginning of your modules to enable unicode strings by default as in Python 3 or u-strings, e.g. <code>u'foo'</code> (Python 3 understands them too) — it doesn't really matter as long as you are doing it consistently.

=== Know the libraries you are using ===
Working with Python Standard Library and third-party libraries (including Kodi Python API) you should know that types their functions and methods expect and what types they return. For example, in popular requests library Response.text property returns a Unicode string and Response.content returns a binary string.

If a function/method/property returns a binary string, you need to decode it to a Unicode string using .decode() method. Don’t use unicode class constructor because unicode type does not exist in Python 3.

If you are reading textual files from disk, it is better to use io.open() instead of built-in open(). io.open() can decode file contents to Unicode using specified encoding and works identically both in Python 2 and 3. Example:
<source lang="python">
import io

with io.open('foo.txt', 'r', encoding='utf-8') as fo:
text = fo.read()
</source>

=== Potential pitfalls ===

When writing Python 2/3-compatible code or converting existing Python 2 codebase to compatible code you should pay attention to the following Python language constructions where TypeError exceptions may happen because of incompatible string types if you don’t get your strings in order:

* String concatenations with + operator (<code>'foo' + 'bar'</code>).
* String formatting — both “old style” (<code>'foo %s' % 'bar'</code>) and “new style” (<code>'foo {}'.format('bar')</code>).
* String joining (<code>', '.join(['foo', 'bar'])</code>).

In all those cases always make sure that you work with Unicode strings only.
Another source of subtle bugs is functions and methods that accept and return binary strings (str type) in Python 2 but Unicode strings in Python 3 (again, str type but with different properties). You can use the following utility functions to “normalize” strings that are provided to such functions/methods and received from them:

<source lang="python">
import sys

__all__ = ['PY2', 'py2_encode', 'py2_decode']

PY2 = sys.version_info[0] == 2

def py2_encode(s, encoding='utf-8'):
"""
Encode Python 2 ``unicode`` to ``str``

In Python 3 the string is not changed.
"""
if PY2 and isinstance(s, unicode):
s = s.encode(encoding)
return s

def py2_decode(s, encoding='utf-8'):
"""
Decode Python 2 ``str`` to ``unicode``

In Python 3 the string is not changed.
"""
if PY2 and isinstance(s, str):
s = s.decode(encoding)
return s
</source>

Those utility functions are included in Kodi Six library that is described in the following section.

== Helper Libraries and Tools ==

=== 2to3 ===

[https://docs.python.org/2/library/2to3.html 2to3] script is created by Python developers to help converting existing Python 2 code to Python 3. On Windows it is included in Python distribution (Tools subfolder) but on other OSes you man need to install it separately. For example, on Ubuntu it is included in python-examples package. Note that this script is created for conversion from Python 2 to 3, not for writing portable code, so you need to treat its output with care.

=== Modernize ===

https://python-modernize.readthedocs.io/en/latest/ Modernize] script works on top of 2to3 and is supposed to help you to convert your existing Python 2 code to Python 2/3-compatible. However, in my experiments it did not work reliably even in simple cases so I cannot recommend it for usage.

=== Six ===

[https://pythonhosted.org/six/ Six] was the first library developed to simplify Python 2 to 3 migration. It provides a set of wrappers that hide differences between Python 2 and 3 behind its API. It is less intrusive than the following alternative because it does not monkey-patch built-in names, but in order to use Six library effectively you need to learn its API. Six can be used both for writing new Python 2/3-compatible addons and converting existing ones, but it requires good knowledge of Python 2/3 differences to pick necessary Six features that address specific differences.

Six library is included in the Kodi addon repository as '''script.module.six''' addon.

=== Future ===

[http://python-future.org/ Future] library, like Six, was created to simplify porting existing Python 2 code to 3. But it uses a different approach than Six. Future monkey-patches built-in Python objects to make Python 2 behave like Python 3. The advantage of such approach is that code written using Future is close to idiomatic Python 3 and requires little re-work if you decide to drop Python 2 support in the future. However, such approach may cause problems in some rare edge-cases.

Future library also includes <code>futurize</code> command-line utility for converting existing Python 2 code to 2/3-compatible and in my experiments this utility showed good results.
Future library (without additional utilities) is included in the Kodi addon repository as script.module.future addon.

=== Kodi Six ===

[https://github.com/romanvm/kodi.six Kodi Six] library (available as '''script.module.kodi-six''' addon) is created to normalize string handling in Kodi Python API based on different Python versions by applying wrappers around Kodi API functions and classes. In Kodi API based on Python 2 Kodi Six wrappers have the following effects:

* All functions and methods that expect string arguments can accept both UTF-8 encoded <code>str</code> objects and <code>unicode</code> objects.
* All functions and methods that return string data return <code>unicode</code> objects.

In Kodi API based on Python 3 the wrappers have no effect because Python 3-based API works only with <code>str</code> (Unicode) objects. This eliminates the need for ad hoc encoding and decoding string when working with Kodi API. To use the wrappers you need to import Kodi API <code>xbmc*</code> modules from Kodi Six instead of importing them directly:

<source lang="python">
from kodi_six import xbmc, xbmcaddon, xbmcgui, xbmcplugin, xbmcvfs
</source>

=== PyCharm ===

PyCharm, except for being a really good Python IDE, also provides code compatibility inspection that helps you write Python 2/3-portable code. Open '''Settings''' (Alt+F7) > '''Editor''' > '''Inspections''' > '''Python''' > '''Code compatibility inspections''' and check Python version that you want to support.

PyCharm Community Edition is free and provides all features you need for creating Python addons for Kodi.

== Writing Portable Code ==

Here I’ll give you some tips about how to write portable code:

* Learn the differences between Python 2 and 3. You need to know at least the most important differences between the two major Python versions.

* Use version control system — git or mercurial — to track changes in your code. If you are porting existing code, do it in a separate branch.

* No matter if you are going to write a brand new addon or to port existing addon to Python 3, carefully choose your tools. It is totally possible to write portable code without any helper tools and libraries, but you need to know what you are doing. However, in most cases I’d recommend you to use Future library and its utilities. Carefully read Future documentation.

* Put the following line at the beginning of all your modules:
<source lang="python">
from __future__ import absolute_import, division, unicode_literals
</source>
This will enable respective Python 3 features in your code. You don’t need to import print_function (another Python 3 feature) because in Kodi addons you should to use xbmc.log() to write messages to the Kodi log file.

=== Writing New Addons ===

Check the [http://python-future.org/quickstart.html#if-you-are-writing-code-from-scratch Quick Start Guide] section of Future library documentation. You can also use Six library, but, as it was said previously, you need to learn its API to pick the necessary features to address specific Python version differences, while Future allows to write your code in (almost) idiomatic Python 3.

A brief procedure for writing new Python 2/3-compatible addons with Future library:

# Create a new virtual environment with Python 3 interpreter and activate it.
# Install Future library: <code>pip install future</code>.
# Point your IDE (Integrated Development Environment) to that environment. For example, in PyCharm: '''File''' > '''Setting''' > '''Project''' > '''Project Interpreter'''.
# Put the following line at the beginning of your Python code:
<source lang="python">
from __future__ import absolute_import, division, unicode_literals
from future import standard_library
from future.builtins import *
standard_library.install_aliases()
</source>
Write your addon using Python 3 syntax and standard library names. However, you may still need to use wrappers from Future library for some specific cases (e.g. iterators over <code>dict</code> elements). Read Future docs for more info.

=== Porting Existing Addons ===

A brief procedure for porting existing code to Python 3-compatible with Future library:

# Install Future library into your working Python 2 virtual environment: <code>pip install future</code>.
# Run <code>futurize</code> utility to convert all your scripts and modules to portable code.

Test your new or converted addon in Kodi with Python 2 interpreter and fix all found issues. After that test the addon in Kodi with Python 3 interpreter and again fix all found issues.
You can use [https://github.com/romanvm/kodi.web-pdb Web-PDB] debugger for troubleshooting issues in your code. It is compatible with both Python 2 and 3.

== Links ==

* Python 2 and 3 differences: https://docs.python.org/3.6/whatsnew/3.0.html
* Future library documentation: http://python-future.org/
* Six library documentation: https://pythonhosted.org/six/
* Kodi test builds with Python 3 for Windows: http://mirrors.xbmc.org/test-builds/windows/win32/
* Kodi test builds with Python 3 for Linux Ubuntu: https://launchpad.net/~wsnipex/+archive/ubuntu/kodi-python3/+packages
* “Python 3 migration” section on the Kodi official forum: https://forum.kodi.tv/forumdisplay.php?fid=281

MySQL/Setting up MySQL

2019-01-21T08:34:23Z

Yol: Remove outdated info, add message for recommended versions

{{:MySQL/Contents}}
{{mininav| [[MySQL]] }}
You'll need to choose which of your computers, Kodi devices, or [[NAS]] will be the MySQL server. The server needs to be on 24/7 or have wake-on-lan (preferably the former), and needs to have a local static IP. You will probably want the Kodi device that is hosting most or all of your videos and music to also be the MySQL server, but this is not required.
{{-}}

{{redv|'''Please Note:'''| Don't create the MySQL databases on your server'''. Simply set up the MySQL server itself, as Kodi will create the specific databases by itself.}}
{{redv|'''Also:'''| Some versions of MySQL set their passwords to expire by default, '''even the root password'''! If the password expires, Kodi cannot access the database and the TV Series and Movies libraries will disappear.<br />
To avoid this and/or fix it after it happens, make sure the account's password does not expire. (See: https://dev.mysql.com/doc/refman/5.7/en/password-expiration-policy.html )}}

MySQL can be installed on just about every major OS:

{{redv|'''Important:'''| Please use only supported versions of the MySQL or MariaDB server. As of January 2019, this is MySQL in at least version 5.6 or MariaDB in at least version 5.5.}}

=Ubuntu Linux=
'''Ubuntu Linux:'''
#<code>$sudo apt-get install mysql-server</code> ''(see also: https://help.ubuntu.com/18.04/serverguide/mysql.html )''
#Create a password when asked
#To configure MySQL to listen for connections from network hosts, edit ''/etc/mysql/mysql.conf.d/mysqld.cnf'' and change the bind-address directive to the server's IP address:
##from: <code>bind-address = 127.0.0.1</code>
##to: <code>bind-address = 192.168.0.5</code>
#*Note: Replace 192.168.0.5 with the appropriate address.
#*Note: To allow both local and remote access (i.e. from both the MySQL host to itself and also from other clients), either comment out the bind-address using a hash (#) to disable it, or use <code>bind-address = 0.0.0.0</code> to open it completely.
#Restart your MySQL server. <code>sudo service mysql restart</code>
#Get into the MySQL command line utility: <code>mysql -u root -p</code>
#Enter the following commands:
##Type in: <code>CREATE USER 'kodi' IDENTIFIED BY 'kodi';</code> and press return
##Type in: <code>GRANT ALL ON *.* TO 'kodi';</code> and press return
##Type in: <code>flush privileges;</code> and press return
#Close out the command line tool with <code>\q</code>

=Arch Linux=
'''Arch Linux:'''
*Please note: Arch, along with many other distributions, has migrated to the faster and more open MariaDB. It is a drop in replacement to MySQL and, thus, Kodi will require no modifications to work with it.
#Install MariaDB: <code>$ sudo pacman -S mariadb</code>
#Start the service: <code>$ sudo systemctl start mysqld</code>
#To have it automatically launch at startup: <code>$ sudo systemctl enable mysqld</code>
#Create a password: <code>$ /usr/bin/mysql_secure_installation</code> ''This will also clean up the demo database.''
#Get into the MariaDB command line utility: <code>$ mysql -u root -p</code>
#Enter the following commands:
##Type in: <code>CREATE USER 'kodi' IDENTIFIED BY 'kodi';</code> and press return
##Type in: <code>GRANT ALL ON *.* TO 'kodi';</code> and press return
##Type in: <code>flush privileges;</code> and press return
#Close out the command line tool with <code>\q</code>

=RedHat based Linux=
'''RedHat based Linux (RHEL, CentOS, Fedora):'''
#<code>$sudo yum install mysql-server</code>
#Create a password when asked
#To configure MySQL to listen for connections only from network hosts, edit ''/etc/mysql/my.cnf'' and add the bind-address directive to the server's IP address:<br /><code>bind-address = 192.168.0.5</code>
#*Note: Replace 192.168.0.5 with the appropriate address.
#*Note: Alternatively you can leave this file as is to allow local and remote access.
#Restart your MySQL server. <code>$sudo /sbin/service mysqld restart</code>
#*Recommended - Set your MySQL root password with <code>/usr/bin/mysqladmin -u root password 'new-password'</code>
#Get into the MySQL command line utility: <code>$mysql -u root -p</code>
#*Enter your MySQL root password as set above, or just press enter if you didn't set one to log in with a blank password
#Enter the following commands:
##Type in: <code>CREATE USER 'kodi' IDENTIFIED BY 'kodi';</code> and press return
##Type in: <code>GRANT ALL ON *.* TO 'kodi';</code> and press return
##Type in: <code>flush privileges;</code> and press return
#Close out the command line tool with <code>\q</code>

=RaspberryPi Raspbian=

'''RaspberryPi Raspbian:'''
#<code>$sudo apt-get update && sudo apt-get dist-upgrade</code> to ensure that you have the very latest iteration of Raspbian. ''(September 2017 as of writing this)''
#<code>$sudo apt-get install mysql-server</code> to install ''MYSQL Server''.
#To configure MySQL to listen for connections from network hosts, <code>$sudo nano /etc/mysql/mariadb.conf.d/50-server.cnf</code> and change the bind-address directive to the server's IP address:
##from: <code>bind-address = 127.0.0.1</code>
##to: <code>bind-address = 192.168.0.5</code>
#*Note: Replace 192.168.0.5 with the appropriate address.
#*Note: To allow both local and remote access (i.e. from both the MySQL host to itself and also from other clients), either comment out the bind-address using a hash (#) to disable it, or use <code>bind-address = 0.0.0.0</code> to open it completely.
#Restart your MySQL server: <code>sudo service mysql restart</code>
#Get into the MySQL command line utility: <code>sudo mysql</code>
#Enter the following commands:
##Type in: <code>CREATE USER 'kodi' IDENTIFIED BY 'kodi';</code> and press return
##Type in: <code>GRANT ALL ON *.* TO 'kodi';</code> and press return
##Type in: <code>flush privileges;</code> and press return
#Close out the command line tool with <code>\q</code>

=Mac OS X=
'''Mac OS X:'''
#Download a copy of MySQL server from http://dev.mysql.com/downloads/mysql/
#In Mac OS X, go to System Preferences -> MySQL, and click on “Start MySQL Server”. You’ll also want to tick to enable the “Automatically … on Startup” option.
#Now to set up the "kodi" user in MySQL and give it access. Launch Terminal.app on your Mac and issue the following commands, one line at a time:
##<code>sudo /usr/local/mysql/bin/mysql</code>
##<code>CREATE USER 'kodi' IDENTIFIED BY 'kodi';</code>
##<code>GRANT ALL ON *.* TO 'kodi';</code>
##<code>exit</code>
#Remain in Terminal.app. Now you'll be giving other computers on your network access to MySQL. Enter the next set of commands, one line at a time:
##<code>cd /usr/local/mysql/support-files/</code>
##<code>sudo cp my-huge.cnf /etc/my.cnf</code>
##:''The command line will ask for your Mac OS X user password. Enter it and press return. No text will show when you type your password in, this is normal.
##<code>cd /etc</code>
##<code>sudo nano my.cnf</code>
##:''This opens a file in a command line text editor''
##Scroll down to the [mysqld] section and add or edit the following line so that it appears as:
##:<code>bind-address = ***.***.***.***</code>
##Save and exit from the command line text editor
#Reboot the Mac, or restart the MySQL service from the System Preferences pane you installed earlier

*Alternative guide for Mac OS X: http://forum.kodi.tv/showthread.php?tid=151631

=Windows=
== Installing MySQL on Windows ==
If you have chocolatey installed run '''choco install mysql'''
:'''or'''
#Download a copy of MySQL server from http://dev.mysql.com/downloads/mysql/
#Select ''Server only''
#Create a password when asked
#Select that you want the database to have network access when prompted during installation.

If you're using a firewall such as the one that's built into Windows, you will need to follow the steps below for the version of windows you installed Kodi on.
=== Windows 7/8/8.1 Built-in Firewall ===
: Run the following command in powershell or execute all the steps below.
:::<syntaxhighlight lang="text" enclose="div">
New-NetFirewallRule -DisplayName "Allow inbound TCP Port 3306 for MySQL" -Direction inbound –LocalPort 3306 -Protocol TCP -Action Allow
</syntaxhighlight>
:#Go to control panel and open Windows Firewall
:#Click on Advanced Settings
:#Click on Inbound Rules, then New Rule
:#For the Rule Type, choose '''''Port''''' and hit Next
:#For Protocol and Ports, select TCP protocol and type in '''''3306''''' for the '''''Specific local ports''''' and hit Next
:#For Action, leave it at default which is '''''Allow the connection''''' and hit Next
:#For Profile, you can leave it as default (everything checked by default) and hit Next
:#For Name, set it to '''''MySQL''''' or any name that you will know what it is and click Finished

== Setup users in MySQL for Kodi clients ==

#Open the "MySQL Command Line Client" from the MySQL start menu
#Enter the following commands:
##Type in: <code>CREATE USER 'kodi' IDENTIFIED BY 'kodi';</code> and press return
##Type in: <code>GRANT ALL ON *.* TO 'kodi';</code> and press return
##Type in: <code>flush privileges;</code> and press return
#Close out the command line tool

{{Note|If Kodi is unable to connect to the MySQL server, returning an error code [1130]:}}<br/>
If this occurs to you, try amending Step 2 above to read <code>GRANT ALL ON *.* TO 'kodi'@'xxx.xxx.xxx.%';</code> where xxx.xxx.xxx is the first three quadrants of your home network's IP address (192.168.1 for example) and % as the last quadrant to allow addresses on the same subnet to connect.

=Other NAS=
MySQL can also be installed on some [[w:network-attached storage|network-attached storage (NAS)]] device devices. Here are some guides for various NAS devices that can have a MySQL server installed:

*Devices running Arch Linux ARM (such as the PogoPlug, Dockstar, etc) can use the [[HOW-TO:Share libraries using MySQL/Setting up MySQL/ALARM|Arch Linux instructions]] on this page.
*[https://web.archive.org/web/20160329053954/http://quixventure.com/2011/12/configure-a-synology-nas-as-mysql-server-for-xbmc/ Synology NAS as MySQL server for XBMC] and http://youtu.be/3PmmDtK65ks
*http://www.robvanhamersveld.nl/2013/02/05/share-your-xbmc-12-0-library-on-a-synology-ds-or-other-nas/ Synology DS with MySQL guide based on Frodo
*http://forum.kodi.tv/showthread.php?tid=172548 - unRAID

After setting up a database server on you NAS, you should create a Kodi user with full administrative privileges. The user should be able to log in from your Kodi devices, so make sure you give the user login access from external machines.
You do not need to create a database as Kodi will create the required databases itself.

{{redv|'''Warning:'''| As you are giving the Kodi user full administrative privileges and external machine access it is recommended that you review your database security. It is highly recommenced that you block internet access to your database using an appropriate firewall. }}

=FreeNAS and freeBSD=

== About FreeNAS ==

http://www.freenas.org/

FreeNAS is a FreeBSD based NAS system that can be run on almost any hardware - it uses ZFS for disk and file management. It is used at home and in enterprise businesses. 99% of tasks can be done via the web interface.

Example below is based on FreeNAS 9.1.1 on 12/12/13, and assumes you have already configured your nas with drives, datasets etc

== How to ==

=== Make a jail ===

create a Jail via the FreeNAS webui - if unsure see here http://doc.freenas.org/index.php/Adding_Jails

make a note of the jail IP address shown - you will need this to put in the advancedsettings.xml file on the Kodi machine later

=== Prepare the jail ===

*ssh into FreeNAS
**If you have a windows PC use putty (http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html)
**(easiest) click the "shell" button in the left of the FreeNAS webui

type the following commands

*<code>jls</code>

Take note of the JID of the jail you created, use it in the command below and replace n with the number of the jail you just created

*<code>jexec n csh</code>

=== Install mysql ===
You are now inside your jail

*<code>pkg install mysql55-server</code>

*<code>pkg install nano</code>
**(nano is a text editor you will need shortly)

We now need to enable mysql in rc.conf

*<code>nano /etc/rc.conf</code>

insert the line below into the rc.conf file

*<code>mysql_enable="YES"</code>

save the file and exit (see bottom of nano edit page for keystrokes info)

*<code>service mysql-server start</code>

Optional step below - this is an automated script that will secure you mysql instance - it will prompt you for answers to questions. Its up to you if you do this.

*<code>mysql_secure_installation</code>

=== Configure mysql ready for Kodi to use ===

type in

*<code>mysql -u root -p</code>

You are now in mysql administration

* <code>CREATE USER 'kodi' IDENTIFIED BY 'kodi';</code>
* <code>GRANT ALL ON *.* TO 'kodi';</code>
* <code>flush privileges;</code>
* <code>quit;</code>

=Restricting MySQL access rights=
'''Optional:''' '''If you only use the MySQL server for Kodi and that server has non-critical data on it, then this probably not necessary.'''
For a more secure MySQL installation use these 2 commands to grant permission only to databases Kodi uses. This is useful if you plan on using your MySQL server for more than just Kodi, or if you're worried about your internal network being exposed and wanting to lock things down more, etc.
#<code>GRANT ALL ON `MyMusic%`.* TO 'kodi'@'%' IDENTIFIED BY 'kodi';</code>
#<code>GRANT ALL ON `MyVideos%`.* TO 'kodi'@'%' IDENTIFIED BY 'kodi';</code>

{{redv|'''Careful'''|The limited grants on this page don't give the kodi user permissions to create required TRIGGERs during install or upgrade. '''Kodi requires these TRIGGERs to function properly.''' <br />
Use the broader grant *.* statement that is explained on the previous tabs while creating or upgrading the tables. Only restrict rights afterwards, if you need to. <br>
Alternatively, figure out how to specifically give the account the right to create the require TRIGGERS - this varies between MySQL versions. }}
<headertabs />

{{Next|[[MySQL/Setting up Kodi|Setting up Kodi]]}}

{{Isengard updated}}