Official Kodi Wiki - User contributions [en]

Kodi Foundation

2018-09-29T07:11:29Z

Natethomas: /* Financial status */

{{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.
* [[/Member list]]

== Board of Directors ==
{| class="infobox"
|-
|
<section begin=Foundation members />
* '''Peter Frühberger (fritsch)''' - Board member - ''Term: 11/2016 - 11/2018''
* '''Keith Herrington (keith)''' - Board member - ''Term: 11/2016 - 11/2018''
* '''Nathan Betzen (natethomas)''' - Board member - ''Term: 10/2012 - 11/2019''
* '''Martijn Kaijser (Martijn)''' - Board member - ''Term: 11/2013 - 11/2019''
* '''Ejal de Klerk (Kib)''' - Board member - ''Term: 11/2017 - 11/2019''
<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/2017|2017]]
* [[/Elections/2016|2016]]
* [[/Elections/2014|2014]]
* [[/Elections/2013|2013]]
* [[/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 ===

'''Europe bank account'''

* Bank: ING Netherlands
* Beneficiary: Kodi Foundation
* IBAN account: NL39 INGB 0006 6296 56
* BIC: INGBNL2A

'''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/

== See also ==

=== Similar page names ===
{{#lst:Foundation|similar pages}}

[[Category:Team Kodi]]
[[Category:Team Kodi specific notes]]
[[Category:XBMC Foundation|*]]

Kodi Foundation

2018-04-28T21:08:14Z

Natethomas: /* Board of Directors */ added Kib, updated dates, arranged first by upcoming term limit, then last name alphabetically

{{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.
* [[/Member list]]

== Board of Directors ==
{| class="infobox"
|-
|
<section begin=Foundation members />
* '''Peter Frühberger (fritsch)''' - Board member - ''Term: 11/2016 - 11/2018''
* '''Keith Herrington (keith)''' - Board member - ''Term: 11/2016 - 11/2018''
* '''Nathan Betzen (natethomas)''' - Board member - ''Term: 10/2012 - 11/2019''
* '''Martijn Kaijser (Martijn)''' - Board member - ''Term: 11/2013 - 11/2019''
* '''Ejal de Klerk (Kib)''' - Board member - ''Term: 11/2017 - 11/2019''
<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/2016|2016]]
* [[/Elections/2014|2014]]
* [[/Elections/2013|2013]]
* [[/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 partially incomplete due to software accounting issues with international currency. $10k income from sponsorships is missing and at least 10k or 20k devcon costs is also missing.

=== Account details ===

'''Europe bank account'''

* Bank: ING Netherlands
* Beneficiary: Kodi Foundation
* IBAN account: NL39 INGB 0006 6296 56
* BIC: INGBNL2A

'''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/

== See also ==

=== Similar page names ===
{{#lst:Foundation|similar pages}}

[[Category:Team Kodi]]
[[Category:Team Kodi specific notes]]
[[Category:XBMC Foundation|*]]

Kodi Foundation

2018-04-28T21:02:05Z

Natethomas: /* Financial status */ changed 2016 from gdrive to guidestar.org. gdrive is having weird sharing issues

{{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.
* [[/Member list]]

== Board of Directors ==
{| class="infobox"
|-
|
<section begin=Foundation members />
* '''Nathan Betzen (natethomas)''' - Board member - ''Term: 10/2012 - 11/2017''
* '''Martijn Kaijser (Martijn)''' - Board member - ''Term: 11/2013 - 11/2017''
* '''Sascha Montellese (Montellese)''' - Board member - ''Term: 11/2013 - 11/2017''
* '''Keith Herrington (keith)''' - Board member - ''Term: 11/2016 - 11/2018''
* '''Peter Frühberger (fritsch)''' - Board member - ''Term: 11/2016 - 11/2018''
<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/2016|2016]]
* [[/Elections/2014|2014]]
* [[/Elections/2013|2013]]
* [[/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 partially incomplete due to software accounting issues with international currency. $10k income from sponsorships is missing and at least 10k or 20k devcon costs is also missing.

=== Account details ===

'''Europe bank account'''

* Bank: ING Netherlands
* Beneficiary: Kodi Foundation
* IBAN account: NL39 INGB 0006 6296 56
* BIC: INGBNL2A

'''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/

== See also ==

=== Similar page names ===
{{#lst:Foundation|similar pages}}

[[Category:Team Kodi]]
[[Category:Team Kodi specific notes]]
[[Category:XBMC Foundation|*]]

Archive:Google Summer of Code/2018

2018-02-01T09:15:34Z

Natethomas: /* other ideas */

{{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 to review some of the ideas on this page, and then feel free to provide input on any ideas you may have in the '''[http://forum.kodi.tv/forumdisplay.php?fid=257 Kodi GSoC forum]''' and chat about any project you’d love to cover. To propose a project, see '''[[#Students project proposal ideas]]'''.

From the 12th to the 27th of March, 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 [[Google Summer of Code 2008|2008]], [[Google Summer of Code 2012|2012]], [[Google Summer of Code 2013|2013]], [[Google Summer of Code 2015|2015]], and [[Google Summer of Code/2017|2017]], and had team members involved in GSoC for other projects during 2011.

If Kodi is selected as a mentoring organization for 2018, 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 usage|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 [http://forum.kodi.tv/forumdisplay.php?fid=274 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 ==

===Intro/outro Detection===
'''Description:''' It would be nice to detect intros and outros of a file dynamically. Then make the intros and outros skipable. One way to do this would be to create a machine learning model per show and distribute those via an api. The scope of this project would focus on some examples and making it easy to add more later. Then implement an addon or core addition that takes those models and acts on them when playing a file, ultimatly making it possible to skip forward.

'''Expected outcome:''' Being able to skip past intros or outros of shows and maybe even movies.

'''Skills preferred:''' Python, C++, something to run an api - GO or Elixir would be prefered

'''Possible mentors:''' Razze

'''Difficulty:''' Hard

'''Type:''' Risky/Exploratory

=== 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 achieveable in a summer. Database handling for profiles needs to be reviewed and changed so that the user expirience 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 frendly then before and not be an after thought. 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
===Add-ons===
====Add code validation and do statistical analysis in kodis addon checker====
'''Description:''' Kodis addon checker checks each Kodi addon PR on github for certain problems, which ultimatly makes reviewing python addons easier for the team. These checks are fairly simple right now and would greatly benefit from improvements. It would be very nice to actually check the python code that is submitted for errors and also do statistical analysis on each PR. The addon checker is written in python and can be fround here https://github.com/xbmc/addon-check

'''Expected outcome:''' Safer and faster acceptance and reviews for the official kodi addon repos. As most of the code will be checked by the machine. Also fewer slipups with regard to oversight.

'''Skills preferred:''' Python

'''Possible mentors:''' Razze

'''Difficulty:''' Medium

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

====Automatic addon checker for binary addons====
'''Description:''' Kodis addon checker checks each Kodi addon PR on github for certain problems, which ultimatly makes reviewing python addons easier for the team. But the other type of addons, binary addons is not being checked so far. Which makes reviews and codeing guidlines hard to handle. Thus it would be nice to also check those addons, either via the current checker written in python or a new binary addon 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

====Addon Submissions====
'''Description:''' Write a tool or an website to easily submit addons to our addon repo. The tool will need to login at github and send a PR in the name of the author to the correct repo and branch on kodis github. The user experiance needs to be very good to not keep anyone from submitting. It should also be able to offer some oppinions on the code that will be commited before it actually get's send. So it would catch the most common errors on the client side.

'''Expected outcome:''' A tool to get more submissions with better quality and lower the bar for addon authors to get started with repo submissions.

'''Skills preferred:''' Depending if this will be a standalone tool or an website the choice of technology would be quiet different. It would be a new tool, so that's fine. For an website python/djang, elixir/phoenix or something similar would be a good choice. For a stand alone tool we might do a full ui in java or electron or settle for a commandline interface via javascript.

'''Possible mentors:''' Razze

'''Difficulty:''' Easy

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

===Gaming in Kodi ===
====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

'''Difficulty''': medium

'''Type''': Fun/Peripheral

'''Notes''': Garbear has broken down the Retroplayer project into manageable pieces including input, core, game addons, peripheral addons, 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 a picture library===
'''Description:''' At the moment kodi has the concept of libaries for movies, tvshows and music. Libraries are far nicer for users to handle as they keep their data and basically act upon the data that got collected without having to get it on each directory traversal. It also enables filtering, sorting and searches. The project would focus on adding a picture database and getting it filled via file scrapping. When that's done we would progress to write basic libary views for pictures.

'''Expected outcome:''' A functional picture library for kodi with the possiblity to scan file and having them added to your library. It should also be possible to look at your files via a libary frontend, just like it's possible for tvshows, movies or music.

'''Skills preferred:''' C++, SQLite, MySQL/MariaDB

'''Possible mentors:''' Razze

'''Difficulty:''' Easy

'''Type:''' Core development

===Use machine learning to improve suggestions===
'''Description:''' Kodi currently can't suggest simiar media to watch/listen to. It would be possible to just show media that's similar on the base of a tag, but that would be quiet rudimentary. Better would be to create something driven by the user or profile that's currently logged in. This would mean that watched/listend and collected data be added to the model and we would serve the best possible suggstion for a user. Machine learning might be the best approach as we would be able to create a model and just ship that model and act on it when kodi tries to serve suggestions.

'''Expected outcome:''' Far better suggestions then before. Some places might even just get suggestions due to this project, as it did not make much sense to do suggestions before this.

'''Skills preferred:''' Python, TensorFlow, C++, SQLite, MariaDB/MySQL

'''Possible mentors:''' Razze

'''Difficulty:''' Hard

'''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 2018 forum area. We may be able to assign a mentor if enough interest is shown
*Using fuzz testing to fuzz test Kodi
*Using fruit or similar to use DI in Kodi and write tests
*High quality scalers for OpenGL(GLSL). Scale Y and UV plane separately ('''mentor''': fernet menta)
*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. (possible mentor: montellese)
*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 (possible mentor: montellese)

=== 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 '''[http://forum.kodi.tv/forumdisplay.php?fid=257 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 '''[http://forum.kodi.tv/forumdisplay.php?fid=257 HERE]''' and paste the text.
# Fill out everything using your specific proposal.

[[Category:Google Summer of Code]]

Archive:Google Summer of Code/2018

2018-02-01T09:06:44Z

Natethomas: /* Team-Kodi proposal ideas up for discussion */

{{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 to review some of the ideas on this page, and then feel free to provide input on any ideas you may have in the '''[http://forum.kodi.tv/forumdisplay.php?fid=257 Kodi GSoC forum]''' and chat about any project you’d love to cover. To propose a project, see '''[[#Students project proposal ideas]]'''.

From the 12th to the 27th of March, 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 [[Google Summer of Code 2008|2008]], [[Google Summer of Code 2012|2012]], [[Google Summer of Code 2013|2013]], [[Google Summer of Code 2015|2015]], and [[Google Summer of Code/2017|2017]], and had team members involved in GSoC for other projects during 2011.

If Kodi is selected as a mentoring organization for 2018, 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 usage|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 [http://forum.kodi.tv/forumdisplay.php?fid=274 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 ==

===Intro/outro Detection===
'''Description:''' It would be nice to detect intros and outros of a file dynamically. Then make the intros and outros skipable. One way to do this would be to create a machine learning model per show and distribute those via an api. The scope of this project would focus on some examples and making it easy to add more later. Then implement an addon or core addition that takes those models and acts on them when playing a file, ultimatly making it possible to skip forward.

'''Expected outcome:''' Being able to skip past intros or outros of shows and maybe even movies.

'''Skills preferred:''' Python, C++, something to run an api - GO or Elixir would be prefered

'''Possible mentors:''' Razze

'''Difficulty:''' Hard

'''Type:''' Risky/Exploratory

=== 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 achieveable in a summer. Database handling for profiles needs to be reviewed and changed so that the user expirience 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 frendly then before and not be an after thought. 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
===Add-ons===
====Add code validation and do statistical analysis in kodis addon checker====
'''Description:''' Kodis addon checker checks each Kodi addon PR on github for certain problems, which ultimatly makes reviewing python addons easier for the team. These checks are fairly simple right now and would greatly benefit from improvements. It would be very nice to actually check the python code that is submitted for errors and also do statistical analysis on each PR. The addon checker is written in python and can be fround here https://github.com/xbmc/addon-check

'''Expected outcome:''' Safer and faster acceptance and reviews for the official kodi addon repos. As most of the code will be checked by the machine. Also fewer slipups with regard to oversight.

'''Skills preferred:''' Python

'''Possible mentors:''' Razze

'''Difficulty:''' Medium

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

====Automatic addon checker for binary addons====
'''Description:''' Kodis addon checker checks each Kodi addon PR on github for certain problems, which ultimatly makes reviewing python addons easier for the team. But the other type of addons, binary addons is not being checked so far. Which makes reviews and codeing guidlines hard to handle. Thus it would be nice to also check those addons, either via the current checker written in python or a new binary addon 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

====Addon Submissions====
'''Description:''' Write a tool or an website to easily submit addons to our addon repo. The tool will need to login at github and send a PR in the name of the author to the correct repo and branch on kodis github. The user experiance needs to be very good to not keep anyone from submitting. It should also be able to offer some oppinions on the code that will be commited before it actually get's send. So it would catch the most common errors on the client side.

'''Expected outcome:''' A tool to get more submissions with better quality and lower the bar for addon authors to get started with repo submissions.

'''Skills preferred:''' Depending if this will be a standalone tool or an website the choice of technology would be quiet different. It would be a new tool, so that's fine. For an website python/djang, elixir/phoenix or something similar would be a good choice. For a stand alone tool we might do a full ui in java or electron or settle for a commandline interface via javascript.

'''Possible mentors:''' Razze

'''Difficulty:''' Easy

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

===Gaming in Kodi ===
====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

'''Difficulty''': medium

'''Type''': Fun/Peripheral

'''Notes''': Garbear has broken down the Retroplayer project into manageable pieces including input, core, game addons, peripheral addons, 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 a picture library===
'''Description:''' At the moment kodi has the concept of libaries for movies, tvshows and music. Libraries are far nicer for users to handle as they keep their data and basically act upon the data that got collected without having to get it on each directory traversal. It also enables filtering, sorting and searches. The project would focus on adding a picture database and getting it filled via file scrapping. When that's done we would progress to write basic libary views for pictures.

'''Expected outcome:''' A functional picture library for kodi with the possiblity to scan file and having them added to your library. It should also be possible to look at your files via a libary frontend, just like it's possible for tvshows, movies or music.

'''Skills preferred:''' C++, SQLite, MySQL/MariaDB

'''Possible mentors:''' Razze

'''Difficulty:''' Easy

'''Type:''' Core development

===Use machine learning to improve suggestions===
'''Description:''' Kodi currently can't suggest simiar media to watch/listen to. It would be possible to just show media that's similar on the base of a tag, but that would be quiet rudimentary. Better would be to create something driven by the user or profile that's currently logged in. This would mean that watched/listend and collected data be added to the model and we would serve the best possible suggstion for a user. Machine learning might be the best approach as we would be able to create a model and just ship that model and act on it when kodi tries to serve suggestions.

'''Expected outcome:''' Far better suggestions then before. Some places might even just get suggestions due to this project, as it did not make much sense to do suggestions before this.

'''Skills preferred:''' Python, TensorFlow, C++, SQLite, MariaDB/MySQL

'''Possible mentors:''' Razze

'''Difficulty:''' Hard

'''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 2018 forum area. We may be able to assign a mentor if enough interest is shown
*Using fuzz testing to fuzz test Kodi
*Using fruit or similar to use DI in Kodi and write tests
*High quality scalers for OpenGL(GLSL). Scale Y and UV plane separately ('''mentor''': fernet menta)
*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

=== 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 '''[http://forum.kodi.tv/forumdisplay.php?fid=257 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 '''[http://forum.kodi.tv/forumdisplay.php?fid=257 HERE]''' and paste the text.
# Fill out everything using your specific proposal.

[[Category:Google Summer of Code]]

Archive:Google Summer of Code/2018

2018-02-01T09:04:10Z

Natethomas: /* Achievements in Retroplayer */

{{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 to review some of the ideas on this page, and then feel free to provide input on any ideas you may have in the '''[http://forum.kodi.tv/forumdisplay.php?fid=257 Kodi GSoC forum]''' and chat about any project you’d love to cover. To propose a project, see '''[[#Students project proposal ideas]]'''.

From the 12th to the 27th of March, 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 [[Google Summer of Code 2008|2008]], [[Google Summer of Code 2012|2012]], [[Google Summer of Code 2013|2013]], [[Google Summer of Code 2015|2015]], and [[Google Summer of Code/2017|2017]], and had team members involved in GSoC for other projects during 2011.

If Kodi is selected as a mentoring organization for 2018, 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 usage|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 [http://forum.kodi.tv/forumdisplay.php?fid=274 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 ==

===Intro/outro Detection===
'''Description:''' It would be nice to detect intros and outros of a file dynamically. Then make the intros and outros skipable. One way to do this would be to create a machine learning model per show and distribute those via an api. The scope of this project would focus on some examples and making it easy to add more later. Then implement an addon or core addition that takes those models and acts on them when playing a file, ultimatly making it possible to skip forward.

'''Expected outcome:''' Being able to skip past intros or outros of shows and maybe even movies.

'''Skills preferred:''' Python, C++, something to run an api - GO or Elixir would be prefered

'''Possible mentors:''' Razze

'''Difficulty:''' Hard

'''Type:''' Risky/Exploratory

=== 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 achieveable in a summer. Database handling for profiles needs to be reviewed and changed so that the user expirience 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 frendly then before and not be an after thought. 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

===Add code validation and do statistical analysis in kodis addon checker===
'''Description:''' Kodis addon checker checks each Kodi addon PR on github for certain problems, which ultimatly makes reviewing python addons easier for the team. These checks are fairly simple right now and would greatly benefit from improvements. It would be very nice to actually check the python code that is submitted for errors and also do statistical analysis on each PR. The addon checker is written in python and can be fround here https://github.com/xbmc/addon-check

'''Expected outcome:''' Safer and faster acceptance and reviews for the official kodi addon repos. As most of the code will be checked by the machine. Also fewer slipups with regard to oversight.

'''Skills preferred:''' Python

'''Possible mentors:''' Razze

'''Difficulty:''' Medium

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

===Automatic addon checker for binary addons===
'''Description:''' Kodis addon checker checks each Kodi addon PR on github for certain problems, which ultimatly makes reviewing python addons easier for the team. But the other type of addons, binary addons is not being checked so far. Which makes reviews and codeing guidlines hard to handle. Thus it would be nice to also check those addons, either via the current checker written in python or a new binary addon 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

===Addon Submissions===
'''Description:''' Write a tool or an website to easily submit addons to our addon repo. The tool will need to login at github and send a PR in the name of the author to the correct repo and branch on kodis github. The user experiance needs to be very good to not keep anyone from submitting. It should also be able to offer some oppinions on the code that will be commited before it actually get's send. So it would catch the most common errors on the client side.

'''Expected outcome:''' A tool to get more submissions with better quality and lower the bar for addon authors to get started with repo submissions.

'''Skills preferred:''' Depending if this will be a standalone tool or an website the choice of technology would be quiet different. It would be a new tool, so that's fine. For an website python/djang, elixir/phoenix or something similar would be a good choice. For a stand alone tool we might do a full ui in java or electron or settle for a commandline interface via javascript.

'''Possible mentors:''' Razze

'''Difficulty:''' Easy

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

===Gaming in Kodi ===
====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

'''Difficulty''': medium

'''Type''': Fun/Peripheral

'''Notes''': Garbear has broken down the Retroplayer project into manageable pieces including input, core, game addons, peripheral addons, 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 a picture library===
'''Description:''' At the moment kodi has the concept of libaries for movies, tvshows and music. Libraries are far nicer for users to handle as they keep their data and basically act upon the data that got collected without having to get it on each directory traversal. It also enables filtering, sorting and searches. The project would focus on adding a picture database and getting it filled via file scrapping. When that's done we would progress to write basic libary views for pictures.

'''Expected outcome:''' A functional picture library for kodi with the possiblity to scan file and having them added to your library. It should also be possible to look at your files via a libary frontend, just like it's possible for tvshows, movies or music.

'''Skills preferred:''' C++, SQLite, MySQL/MariaDB

'''Possible mentors:''' Razze

'''Difficulty:''' Easy

'''Type:''' Core development

===Use machine learning to improve suggestions===
'''Description:''' Kodi currently can't suggest simiar media to watch/listen to. It would be possible to just show media that's similar on the base of a tag, but that would be quiet rudimentary. Better would be to create something driven by the user or profile that's currently logged in. This would mean that watched/listend and collected data be added to the model and we would serve the best possible suggstion for a user. Machine learning might be the best approach as we would be able to create a model and just ship that model and act on it when kodi tries to serve suggestions.

'''Expected outcome:''' Far better suggestions then before. Some places might even just get suggestions due to this project, as it did not make much sense to do suggestions before this.

'''Skills preferred:''' Python, TensorFlow, C++, SQLite, MariaDB/MySQL

'''Possible mentors:''' Razze

'''Difficulty:''' Hard

'''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 2018 forum area. We may be able to assign a mentor if enough interest is shown
*Using fuzz testing to fuzz test Kodi
*Using fruit or similar to use DI in Kodi and write tests
*High quality scalers for OpenGL(GLSL). Scale Y and UV plane separately ('''mentor''': fernet menta)
*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

=== 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 '''[http://forum.kodi.tv/forumdisplay.php?fid=257 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 '''[http://forum.kodi.tv/forumdisplay.php?fid=257 HERE]''' and paste the text.
# Fill out everything using your specific proposal.

[[Category:Google Summer of Code]]

Archive:Google Summer of Code/2018

2018-02-01T09:02:42Z

Natethomas: /* Team-Kodi proposal ideas up for discussion */

{{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 to review some of the ideas on this page, and then feel free to provide input on any ideas you may have in the '''[http://forum.kodi.tv/forumdisplay.php?fid=257 Kodi GSoC forum]''' and chat about any project you’d love to cover. To propose a project, see '''[[#Students project proposal ideas]]'''.

From the 12th to the 27th of March, 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 [[Google Summer of Code 2008|2008]], [[Google Summer of Code 2012|2012]], [[Google Summer of Code 2013|2013]], [[Google Summer of Code 2015|2015]], and [[Google Summer of Code/2017|2017]], and had team members involved in GSoC for other projects during 2011.

If Kodi is selected as a mentoring organization for 2018, 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 usage|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 [http://forum.kodi.tv/forumdisplay.php?fid=274 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 ==

===Intro/outro Detection===
'''Description:''' It would be nice to detect intros and outros of a file dynamically. Then make the intros and outros skipable. One way to do this would be to create a machine learning model per show and distribute those via an api. The scope of this project would focus on some examples and making it easy to add more later. Then implement an addon or core addition that takes those models and acts on them when playing a file, ultimatly making it possible to skip forward.

'''Expected outcome:''' Being able to skip past intros or outros of shows and maybe even movies.

'''Skills preferred:''' Python, C++, something to run an api - GO or Elixir would be prefered

'''Possible mentors:''' Razze

'''Difficulty:''' Hard

'''Type:''' Risky/Exploratory

=== 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 achieveable in a summer. Database handling for profiles needs to be reviewed and changed so that the user expirience 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 frendly then before and not be an after thought. 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

===Add code validation and do statistical analysis in kodis addon checker===
'''Description:''' Kodis addon checker checks each Kodi addon PR on github for certain problems, which ultimatly makes reviewing python addons easier for the team. These checks are fairly simple right now and would greatly benefit from improvements. It would be very nice to actually check the python code that is submitted for errors and also do statistical analysis on each PR. The addon checker is written in python and can be fround here https://github.com/xbmc/addon-check

'''Expected outcome:''' Safer and faster acceptance and reviews for the official kodi addon repos. As most of the code will be checked by the machine. Also fewer slipups with regard to oversight.

'''Skills preferred:''' Python

'''Possible mentors:''' Razze

'''Difficulty:''' Medium

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

===Automatic addon checker for binary addons===
'''Description:''' Kodis addon checker checks each Kodi addon PR on github for certain problems, which ultimatly makes reviewing python addons easier for the team. But the other type of addons, binary addons is not being checked so far. Which makes reviews and codeing guidlines hard to handle. Thus it would be nice to also check those addons, either via the current checker written in python or a new binary addon 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

===Addon Submissions===
'''Description:''' Write a tool or an website to easily submit addons to our addon repo. The tool will need to login at github and send a PR in the name of the author to the correct repo and branch on kodis github. The user experiance needs to be very good to not keep anyone from submitting. It should also be able to offer some oppinions on the code that will be commited before it actually get's send. So it would catch the most common errors on the client side.

'''Expected outcome:''' A tool to get more submissions with better quality and lower the bar for addon authors to get started with repo submissions.

'''Skills preferred:''' Depending if this will be a standalone tool or an website the choice of technology would be quiet different. It would be a new tool, so that's fine. For an website python/djang, elixir/phoenix or something similar would be a good choice. For a stand alone tool we might do a full ui in java or electron or settle for a commandline interface via javascript.

'''Possible mentors:''' Razze

'''Difficulty:''' Easy

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

===Gaming in Kodi ===
====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

'''Difficulty''': medium

'''Type''': core and possibly binary addon development

'''Notes''': Garbear has broken down the Retroplayer project into manageable pieces including input, core, game addons, peripheral addons, 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 a picture library===
'''Description:''' At the moment kodi has the concept of libaries for movies, tvshows and music. Libraries are far nicer for users to handle as they keep their data and basically act upon the data that got collected without having to get it on each directory traversal. It also enables filtering, sorting and searches. The project would focus on adding a picture database and getting it filled via file scrapping. When that's done we would progress to write basic libary views for pictures.

'''Expected outcome:''' A functional picture library for kodi with the possiblity to scan file and having them added to your library. It should also be possible to look at your files via a libary frontend, just like it's possible for tvshows, movies or music.

'''Skills preferred:''' C++, SQLite, MySQL/MariaDB

'''Possible mentors:''' Razze

'''Difficulty:''' Easy

'''Type:''' Core development

===Use machine learning to improve suggestions===
'''Description:''' Kodi currently can't suggest simiar media to watch/listen to. It would be possible to just show media that's similar on the base of a tag, but that would be quiet rudimentary. Better would be to create something driven by the user or profile that's currently logged in. This would mean that watched/listend and collected data be added to the model and we would serve the best possible suggstion for a user. Machine learning might be the best approach as we would be able to create a model and just ship that model and act on it when kodi tries to serve suggestions.

'''Expected outcome:''' Far better suggestions then before. Some places might even just get suggestions due to this project, as it did not make much sense to do suggestions before this.

'''Skills preferred:''' Python, TensorFlow, C++, SQLite, MariaDB/MySQL

'''Possible mentors:''' Razze

'''Difficulty:''' Hard

'''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 2018 forum area. We may be able to assign a mentor if enough interest is shown
*Using fuzz testing to fuzz test Kodi
*Using fruit or similar to use DI in Kodi and write tests
*High quality scalers for OpenGL(GLSL). Scale Y and UV plane separately ('''mentor''': fernet menta)
*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

=== 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 '''[http://forum.kodi.tv/forumdisplay.php?fid=257 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 '''[http://forum.kodi.tv/forumdisplay.php?fid=257 HERE]''' and paste the text.
# Fill out everything using your specific proposal.

[[Category:Google Summer of Code]]

Archive:Google Summer of Code/2018

2018-02-01T08:59:56Z

Natethomas: /* other ideas */

{{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 to review some of the ideas on this page, and then feel free to provide input on any ideas you may have in the '''[http://forum.kodi.tv/forumdisplay.php?fid=257 Kodi GSoC forum]''' and chat about any project you’d love to cover. To propose a project, see '''[[#Students project proposal ideas]]'''.

From the 12th to the 27th of March, 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 [[Google Summer of Code 2008|2008]], [[Google Summer of Code 2012|2012]], [[Google Summer of Code 2013|2013]], [[Google Summer of Code 2015|2015]], and [[Google Summer of Code/2017|2017]], and had team members involved in GSoC for other projects during 2011.

If Kodi is selected as a mentoring organization for 2018, 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 usage|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 [http://forum.kodi.tv/forumdisplay.php?fid=274 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 ==

===Intro/outro Detection===
'''Description:''' It would be nice to detect intros and outros of a file dynamically. Then make the intros and outros skipable. One way to do this would be to create a machine learning model per show and distribute those via an api. The scope of this project would focus on some examples and making it easy to add more later. Then implement an addon or core addition that takes those models and acts on them when playing a file, ultimatly making it possible to skip forward.

'''Expected outcome:''' Being able to skip past intros or outros of shows and maybe even movies.

'''Skills preferred:''' Python, C++, something to run an api - GO or Elixir would be prefered

'''Possible mentors:''' Razze

'''Difficulty:''' Hard

'''Type:''' Risky/Exploratory

===UPnP Improvements including File Transfers===
*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

=== 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 achieveable in a summer. Database handling for profiles needs to be reviewed and changed so that the user expirience 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 frendly then before and not be an after thought. 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

===Add code validation and do statistical analysis in kodis addon checker===
'''Description:''' Kodis addon checker checks each Kodi addon PR on github for certain problems, which ultimatly makes reviewing python addons easier for the team. These checks are fairly simple right now and would greatly benefit from improvements. It would be very nice to actually check the python code that is submitted for errors and also do statistical analysis on each PR. The addon checker is written in python and can be fround here https://github.com/xbmc/addon-check

'''Expected outcome:''' Safer and faster acceptance and reviews for the official kodi addon repos. As most of the code will be checked by the machine. Also fewer slipups with regard to oversight.

'''Skills preferred:''' Python

'''Possible mentors:''' Razze

'''Difficulty:''' Medium

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

===Automatic addon checker for binary addons===
'''Description:''' Kodis addon checker checks each Kodi addon PR on github for certain problems, which ultimatly makes reviewing python addons easier for the team. But the other type of addons, binary addons is not being checked so far. Which makes reviews and codeing guidlines hard to handle. Thus it would be nice to also check those addons, either via the current checker written in python or a new binary addon 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

===Addon Submissions===
'''Description:''' Write a tool or an website to easily submit addons to our addon repo. The tool will need to login at github and send a PR in the name of the author to the correct repo and branch on kodis github. The user experiance needs to be very good to not keep anyone from submitting. It should also be able to offer some oppinions on the code that will be commited before it actually get's send. So it would catch the most common errors on the client side.

'''Expected outcome:''' A tool to get more submissions with better quality and lower the bar for addon authors to get started with repo submissions.

'''Skills preferred:''' Depending if this will be a standalone tool or an website the choice of technology would be quiet different. It would be a new tool, so that's fine. For an website python/djang, elixir/phoenix or something similar would be a good choice. For a stand alone tool we might do a full ui in java or electron or settle for a commandline interface via javascript.

'''Possible mentors:''' Razze

'''Difficulty:''' Easy

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

===Gaming in Kodi ===
====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

'''Difficulty''': medium

'''Type''': core and possibly binary addon development

'''Notes''': Garbear has broken down the Retroplayer project into manageable pieces including input, core, game addons, peripheral addons, 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 a picture library===
'''Description:''' At the moment kodi has the concept of libaries for movies, tvshows and music. Libraries are far nicer for users to handle as they keep their data and basically act upon the data that got collected without having to get it on each directory traversal. It also enables filtering, sorting and searches. The project would focus on adding a picture database and getting it filled via file scrapping. When that's done we would progress to write basic libary views for pictures.

'''Expected outcome:''' A functional picture library for kodi with the possiblity to scan file and having them added to your library. It should also be possible to look at your files via a libary frontend, just like it's possible for tvshows, movies or music.

'''Skills preferred:''' C++, SQLite, MySQL/MariaDB

'''Possible mentors:''' Razze

'''Difficulty:''' Easy

'''Type:''' Core development

===Use machine learning to improve suggestions===
'''Description:''' Kodi currently can't suggest simiar media to watch/listen to. It would be possible to just show media that's similar on the base of a tag, but that would be quiet rudimentary. Better would be to create something driven by the user or profile that's currently logged in. This would mean that watched/listend and collected data be added to the model and we would serve the best possible suggstion for a user. Machine learning might be the best approach as we would be able to create a model and just ship that model and act on it when kodi tries to serve suggestions.

'''Expected outcome:''' Far better suggestions then before. Some places might even just get suggestions due to this project, as it did not make much sense to do suggestions before this.

'''Skills preferred:''' Python, TensorFlow, C++, SQLite, MariaDB/MySQL

'''Possible mentors:''' Razze

'''Difficulty:''' Hard

'''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 2018 forum area. We may be able to assign a mentor if enough interest is shown
*Using fuzz testing to fuzz test Kodi
*Using fruit or similar to use DI in Kodi and write tests
*High quality scalers for OpenGL(GLSL). Scale Y and UV plane separately ('''mentor''': fernet menta)
*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

=== 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 '''[http://forum.kodi.tv/forumdisplay.php?fid=257 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 '''[http://forum.kodi.tv/forumdisplay.php?fid=257 HERE]''' and paste the text.
# Fill out everything using your specific proposal.

[[Category:Google Summer of Code]]

Archive:Google Summer of Code/2018

2018-02-01T08:58:18Z

Natethomas: /* other ideas */

{{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 to review some of the ideas on this page, and then feel free to provide input on any ideas you may have in the '''[http://forum.kodi.tv/forumdisplay.php?fid=257 Kodi GSoC forum]''' and chat about any project you’d love to cover. To propose a project, see '''[[#Students project proposal ideas]]'''.

From the 12th to the 27th of March, 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 [[Google Summer of Code 2008|2008]], [[Google Summer of Code 2012|2012]], [[Google Summer of Code 2013|2013]], [[Google Summer of Code 2015|2015]], and [[Google Summer of Code/2017|2017]], and had team members involved in GSoC for other projects during 2011.

If Kodi is selected as a mentoring organization for 2018, 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 usage|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 [http://forum.kodi.tv/forumdisplay.php?fid=274 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 ==

===Intro/outro Detection===
'''Description:''' It would be nice to detect intros and outros of a file dynamically. Then make the intros and outros skipable. One way to do this would be to create a machine learning model per show and distribute those via an api. The scope of this project would focus on some examples and making it easy to add more later. Then implement an addon or core addition that takes those models and acts on them when playing a file, ultimatly making it possible to skip forward.

'''Expected outcome:''' Being able to skip past intros or outros of shows and maybe even movies.

'''Skills preferred:''' Python, C++, something to run an api - GO or Elixir would be prefered

'''Possible mentors:''' Razze

'''Difficulty:''' Hard

'''Type:''' Risky/Exploratory

===UPnP Improvements including File Transfers===
*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

=== 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 achieveable in a summer. Database handling for profiles needs to be reviewed and changed so that the user expirience 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 frendly then before and not be an after thought. 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

===Add code validation and do statistical analysis in kodis addon checker===
'''Description:''' Kodis addon checker checks each Kodi addon PR on github for certain problems, which ultimatly makes reviewing python addons easier for the team. These checks are fairly simple right now and would greatly benefit from improvements. It would be very nice to actually check the python code that is submitted for errors and also do statistical analysis on each PR. The addon checker is written in python and can be fround here https://github.com/xbmc/addon-check

'''Expected outcome:''' Safer and faster acceptance and reviews for the official kodi addon repos. As most of the code will be checked by the machine. Also fewer slipups with regard to oversight.

'''Skills preferred:''' Python

'''Possible mentors:''' Razze

'''Difficulty:''' Medium

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

===Automatic addon checker for binary addons===
'''Description:''' Kodis addon checker checks each Kodi addon PR on github for certain problems, which ultimatly makes reviewing python addons easier for the team. But the other type of addons, binary addons is not being checked so far. Which makes reviews and codeing guidlines hard to handle. Thus it would be nice to also check those addons, either via the current checker written in python or a new binary addon 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

===Addon Submissions===
'''Description:''' Write a tool or an website to easily submit addons to our addon repo. The tool will need to login at github and send a PR in the name of the author to the correct repo and branch on kodis github. The user experiance needs to be very good to not keep anyone from submitting. It should also be able to offer some oppinions on the code that will be commited before it actually get's send. So it would catch the most common errors on the client side.

'''Expected outcome:''' A tool to get more submissions with better quality and lower the bar for addon authors to get started with repo submissions.

'''Skills preferred:''' Depending if this will be a standalone tool or an website the choice of technology would be quiet different. It would be a new tool, so that's fine. For an website python/djang, elixir/phoenix or something similar would be a good choice. For a stand alone tool we might do a full ui in java or electron or settle for a commandline interface via javascript.

'''Possible mentors:''' Razze

'''Difficulty:''' Easy

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

===Gaming in Kodi ===
====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

'''Difficulty''': medium

'''Type''': core and possibly binary addon development

'''Notes''': Garbear has broken down the Retroplayer project into manageable pieces including input, core, game addons, peripheral addons, 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 a picture library===
'''Description:''' At the moment kodi has the concept of libaries for movies, tvshows and music. Libraries are far nicer for users to handle as they keep their data and basically act upon the data that got collected without having to get it on each directory traversal. It also enables filtering, sorting and searches. The project would focus on adding a picture database and getting it filled via file scrapping. When that's done we would progress to write basic libary views for pictures.

'''Expected outcome:''' A functional picture library for kodi with the possiblity to scan file and having them added to your library. It should also be possible to look at your files via a libary frontend, just like it's possible for tvshows, movies or music.

'''Skills preferred:''' C++, SQLite, MySQL/MariaDB

'''Possible mentors:''' Razze

'''Difficulty:''' Easy

'''Type:''' Core development

===Use machine learning to improve suggestions===
'''Description:''' Kodi currently can't suggest simiar media to watch/listen to. It would be possible to just show media that's similar on the base of a tag, but that would be quiet rudimentary. Better would be to create something driven by the user or profile that's currently logged in. This would mean that watched/listend and collected data be added to the model and we would serve the best possible suggstion for a user. Machine learning might be the best approach as we would be able to create a model and just ship that model and act on it when kodi tries to serve suggestions.

'''Expected outcome:''' Far better suggestions then before. Some places might even just get suggestions due to this project, as it did not make much sense to do suggestions before this.

'''Skills preferred:''' Python, TensorFlow, C++, SQLite, MariaDB/MySQL

'''Possible mentors:''' Razze

'''Difficulty:''' Hard

'''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 2018 forum area. We may be able to assign a mentor if enough interest is shown
*Using fuzz testing to fuzz test Kodi
*Using fruit or similar to use DI in Kodi and write tests
*High quality scalers for OpenGL(GLSL). Scale Y and UV plane separately ('''mentor''': fernet menta)

=== 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 '''[http://forum.kodi.tv/forumdisplay.php?fid=257 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 '''[http://forum.kodi.tv/forumdisplay.php?fid=257 HERE]''' and paste the text.
# Fill out everything using your specific proposal.

[[Category:Google Summer of Code]]

Archive:Google Summer of Code/2018

2018-02-01T08:54:08Z

Natethomas: /* Gaming in Kodi */

{{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 to review some of the ideas on this page, and then feel free to provide input on any ideas you may have in the '''[http://forum.kodi.tv/forumdisplay.php?fid=257 Kodi GSoC forum]''' and chat about any project you’d love to cover. To propose a project, see '''[[#Students project proposal ideas]]'''.

From the 12th to the 27th of March, 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 [[Google Summer of Code 2008|2008]], [[Google Summer of Code 2012|2012]], [[Google Summer of Code 2013|2013]], [[Google Summer of Code 2015|2015]], and [[Google Summer of Code/2017|2017]], and had team members involved in GSoC for other projects during 2011.

If Kodi is selected as a mentoring organization for 2018, 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 usage|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 [http://forum.kodi.tv/forumdisplay.php?fid=274 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 ==

===Intro/outro Detection===
'''Description:''' It would be nice to detect intros and outros of a file dynamically. Then make the intros and outros skipable. One way to do this would be to create a machine learning model per show and distribute those via an api. The scope of this project would focus on some examples and making it easy to add more later. Then implement an addon or core addition that takes those models and acts on them when playing a file, ultimatly making it possible to skip forward.

'''Expected outcome:''' Being able to skip past intros or outros of shows and maybe even movies.

'''Skills preferred:''' Python, C++, something to run an api - GO or Elixir would be prefered

'''Possible mentors:''' Razze

'''Difficulty:''' Hard

'''Type:''' Risky/Exploratory

===UPnP Improvements including File Transfers===
*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

=== 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 achieveable in a summer. Database handling for profiles needs to be reviewed and changed so that the user expirience 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 frendly then before and not be an after thought. 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

===Add code validation and do statistical analysis in kodis addon checker===
'''Description:''' Kodis addon checker checks each Kodi addon PR on github for certain problems, which ultimatly makes reviewing python addons easier for the team. These checks are fairly simple right now and would greatly benefit from improvements. It would be very nice to actually check the python code that is submitted for errors and also do statistical analysis on each PR. The addon checker is written in python and can be fround here https://github.com/xbmc/addon-check

'''Expected outcome:''' Safer and faster acceptance and reviews for the official kodi addon repos. As most of the code will be checked by the machine. Also fewer slipups with regard to oversight.

'''Skills preferred:''' Python

'''Possible mentors:''' Razze

'''Difficulty:''' Medium

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

===Automatic addon checker for binary addons===
'''Description:''' Kodis addon checker checks each Kodi addon PR on github for certain problems, which ultimatly makes reviewing python addons easier for the team. But the other type of addons, binary addons is not being checked so far. Which makes reviews and codeing guidlines hard to handle. Thus it would be nice to also check those addons, either via the current checker written in python or a new binary addon 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

===Addon Submissions===
'''Description:''' Write a tool or an website to easily submit addons to our addon repo. The tool will need to login at github and send a PR in the name of the author to the correct repo and branch on kodis github. The user experiance needs to be very good to not keep anyone from submitting. It should also be able to offer some oppinions on the code that will be commited before it actually get's send. So it would catch the most common errors on the client side.

'''Expected outcome:''' A tool to get more submissions with better quality and lower the bar for addon authors to get started with repo submissions.

'''Skills preferred:''' Depending if this will be a standalone tool or an website the choice of technology would be quiet different. It would be a new tool, so that's fine. For an website python/djang, elixir/phoenix or something similar would be a good choice. For a stand alone tool we might do a full ui in java or electron or settle for a commandline interface via javascript.

'''Possible mentors:''' Razze

'''Difficulty:''' Easy

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

===Gaming in Kodi ===
====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

'''Difficulty''': medium

'''Type''': core and possibly binary addon development

'''Notes''': Garbear has broken down the Retroplayer project into manageable pieces including input, core, game addons, peripheral addons, 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 a picture library===
'''Description:''' At the moment kodi has the concept of libaries for movies, tvshows and music. Libraries are far nicer for users to handle as they keep their data and basically act upon the data that got collected without having to get it on each directory traversal. It also enables filtering, sorting and searches. The project would focus on adding a picture database and getting it filled via file scrapping. When that's done we would progress to write basic libary views for pictures.

'''Expected outcome:''' A functional picture library for kodi with the possiblity to scan file and having them added to your library. It should also be possible to look at your files via a libary frontend, just like it's possible for tvshows, movies or music.

'''Skills preferred:''' C++, SQLite, MySQL/MariaDB

'''Possible mentors:''' Razze

'''Difficulty:''' Easy

'''Type:''' Core development

===Use machine learning to improve suggestions===
'''Description:''' Kodi currently can't suggest simiar media to watch/listen to. It would be possible to just show media that's similar on the base of a tag, but that would be quiet rudimentary. Better would be to create something driven by the user or profile that's currently logged in. This would mean that watched/listend and collected data be added to the model and we would serve the best possible suggstion for a user. Machine learning might be the best approach as we would be able to create a model and just ship that model and act on it when kodi tries to serve suggestions.

'''Expected outcome:''' Far better suggestions then before. Some places might even just get suggestions due to this project, as it did not make much sense to do suggestions before this.

'''Skills preferred:''' Python, TensorFlow, C++, SQLite, MariaDB/MySQL

'''Possible mentors:''' Razze

'''Difficulty:''' Hard

'''Type:''' Risky/Exploratory

===other ideas===
*Using fuzz testing to fuzz test Kodi
*Using fruit or similar to use DI in Kodi and write tests
*High quality scalers for OpenGL(GLSL). Scale Y and UV plane separately

=== 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 '''[http://forum.kodi.tv/forumdisplay.php?fid=257 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 '''[http://forum.kodi.tv/forumdisplay.php?fid=257 HERE]''' and paste the text.
# Fill out everything using your specific proposal.

[[Category:Google Summer of Code]]

Archive:Google Summer of Code/2018

2018-02-01T08:31:08Z

Natethomas: /* Better Profile Support */

{{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 to review some of the ideas on this page, and then feel free to provide input on any ideas you may have in the '''[http://forum.kodi.tv/forumdisplay.php?fid=257 Kodi GSoC forum]''' and chat about any project you’d love to cover. To propose a project, see '''[[#Students project proposal ideas]]'''.

From the 12th to the 27th of March, 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 [[Google Summer of Code 2008|2008]], [[Google Summer of Code 2012|2012]], [[Google Summer of Code 2013|2013]], [[Google Summer of Code 2015|2015]], and [[Google Summer of Code/2017|2017]], and had team members involved in GSoC for other projects during 2011.

If Kodi is selected as a mentoring organization for 2018, 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 usage|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 [http://forum.kodi.tv/forumdisplay.php?fid=274 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 ==

===Intro/outro Detection===
'''Description:''' It would be nice to detect intros and outros of a file dynamically. Then make the intros and outros skipable. One way to do this would be to create a machine learning model per show and distribute those via an api. The scope of this project would focus on some examples and making it easy to add more later. Then implement an addon or core addition that takes those models and acts on them when playing a file, ultimatly making it possible to skip forward.

'''Expected outcome:''' Being able to skip past intros or outros of shows and maybe even movies.

'''Skills preferred:''' Python, C++, something to run an api - GO or Elixir would be prefered

'''Possible mentors:''' Razze

'''Difficulty:''' Hard

'''Type:''' Risky/Exploratory

===UPnP Improvements including File Transfers===
*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

=== 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 achieveable in a summer. Database handling for profiles needs to be reviewed and changed so that the user expirience 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 frendly then before and not be an after thought. 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

===Add code validation and do statistical analysis in kodis addon checker===
'''Description:''' Kodis addon checker checks each Kodi addon PR on github for certain problems, which ultimatly makes reviewing python addons easier for the team. These checks are fairly simple right now and would greatly benefit from improvements. It would be very nice to actually check the python code that is submitted for errors and also do statistical analysis on each PR. The addon checker is written in python and can be fround here https://github.com/xbmc/addon-check

'''Expected outcome:''' Safer and faster acceptance and reviews for the official kodi addon repos. As most of the code will be checked by the machine. Also fewer slipups with regard to oversight.

'''Skills preferred:''' Python

'''Possible mentors:''' Razze

'''Difficulty:''' Medium

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

===Automatic addon checker for binary addons===
'''Description:''' Kodis addon checker checks each Kodi addon PR on github for certain problems, which ultimatly makes reviewing python addons easier for the team. But the other type of addons, binary addons is not being checked so far. Which makes reviews and codeing guidlines hard to handle. Thus it would be nice to also check those addons, either via the current checker written in python or a new binary addon 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

===Addon Submissions===
'''Description:''' Write a tool or an website to easily submit addons to our addon repo. The tool will need to login at github and send a PR in the name of the author to the correct repo and branch on kodis github. The user experiance needs to be very good to not keep anyone from submitting. It should also be able to offer some oppinions on the code that will be commited before it actually get's send. So it would catch the most common errors on the client side.

'''Expected outcome:''' A tool to get more submissions with better quality and lower the bar for addon authors to get started with repo submissions.

'''Skills preferred:''' Depending if this will be a standalone tool or an website the choice of technology would be quiet different. It would be a new tool, so that's fine. For an website python/djang, elixir/phoenix or something similar would be a good choice. For a stand alone tool we might do a full ui in java or electron or settle for a commandline interface via javascript.

'''Possible mentors:''' Razze

'''Difficulty:''' Easy

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

===Gaming in Kodi ===
====Retroplayer====
*Developer Garbear has broken down the Retroplayer project into manageable pieces including input, core, game addons, peripheral addons, netplay, a game library implementation, and shaders to do things like emulate a CRT monitor. Any one of these pieces could make an excellent summer project depending on your familiarity in the area. Many pieces are currently being worked on or are near completion, but 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 a picture library===
'''Description:''' At the moment kodi has the concept of libaries for movies, tvshows and music. Libraries are far nicer for users to handle as they keep their data and basically act upon the data that got collected without having to get it on each directory traversal. It also enables filtering, sorting and searches. The project would focus on adding a picture database and getting it filled via file scrapping. When that's done we would progress to write basic libary views for pictures.

'''Expected outcome:''' A functional picture library for kodi with the possiblity to scan file and having them added to your library. It should also be possible to look at your files via a libary frontend, just like it's possible for tvshows, movies or music.

'''Skills preferred:''' C++, SQLite, MySQL/MariaDB

'''Possible mentors:''' Razze

'''Difficulty:''' Easy

'''Type:''' Core development

===Use machine learning to improve suggestions===
'''Description:''' Kodi currently can't suggest simiar media to watch/listen to. It would be possible to just show media that's similar on the base of a tag, but that would be quiet rudimentary. Better would be to create something driven by the user or profile that's currently logged in. This would mean that watched/listend and collected data be added to the model and we would serve the best possible suggstion for a user. Machine learning might be the best approach as we would be able to create a model and just ship that model and act on it when kodi tries to serve suggestions.

'''Expected outcome:''' Far better suggestions then before. Some places might even just get suggestions due to this project, as it did not make much sense to do suggestions before this.

'''Skills preferred:''' Python, TensorFlow, C++, SQLite, MariaDB/MySQL

'''Possible mentors:''' Razze

'''Difficulty:''' Hard

'''Type:''' Risky/Exploratory

===other ideas===
*Using fuzz testing to fuzz test Kodi
*Using fruit or similar to use DI in Kodi and write tests
*High quality scalers for OpenGL(GLSL). Scale Y and UV plane separately

=== 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 '''[http://forum.kodi.tv/forumdisplay.php?fid=257 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 '''[http://forum.kodi.tv/forumdisplay.php?fid=257 HERE]''' and paste the text.
# Fill out everything using your specific proposal.

[[Category:Google Summer of Code]]

Archive:Google Summer of Code/2018

2018-01-22T21:01:05Z

Natethomas: /* Team-Kodi proposal ideas up for discussion */ updated ideas

Archive:Google Summer of Code/2018

2018-01-09T04:02:54Z

Natethomas: /* About Us */

Archive:Google Summer of Code/2018

2018-01-09T03:46:32Z

Natethomas: page created

Kodi Foundation

2017-09-23T11:00:06Z

Natethomas: /* Board of Directors */ updated Nathan to correct start date

{{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.
* [[/Member list]]

== Board of Directors ==
{| class="infobox"
|-
|
<section begin=Foundation members />
* '''Nathan Betzen (natethomas)''' - Board member - ''Term: 10/2012 - 11/2017''
* '''Martijn Kaijser (Martijn)''' - Board member - ''Term: 11/2013 - 11/2017''
* '''Sascha Montellese (Montellese)''' - Board member - ''Term: 11/2013 - 11/2017''
* '''Keith Herrington (keith)''' - Board member - ''Term: 11/2016 - 11/2018''
* '''Peter Frühberger (fritsch)''' - Board member - ''Term: 11/2016 - 11/2018''
<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/2016|2016]]
* [[/Elections/2014|2014]]
* [[/Elections/2013|2013]]
* [[/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 - https://drive.google.com/file/d/0BwsEEPRqIzELYnNZRTlPY3liTUE/view?usp=sharing
* 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 partially incomplete due to software accounting issues with international currency. $10k income from sponsorships is missing and at least 10k or 20k devcon costs is also missing.

=== Account details ===

'''Europe bank account'''

* Bank: ING Netherlands
* Beneficiary: Kodi Foundation
* IBAN account: NL39 INGB 0006 6296 56
* BIC: INGBNL2A

'''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/

== See also ==

=== Similar page names ===
{{#lst:Foundation|similar pages}}

[[Category:Team Kodi]]
[[Category:Team Kodi specific notes]]
[[Category:XBMC Foundation|*]]

Kodi Foundation

2017-09-14T09:43:21Z

Natethomas: /* Foundation Bylaws and other important documents */ added kodi foundation exemption stuff

{{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.
* [[/Member list]]

== Board of Directors ==
{| class="infobox"
|-
|
<section begin=Foundation members />
* '''Nathan Betzen (natethomas)''' - Board member - ''Term: 11/2013 - 11/2017''
* '''Martijn Kaijser (Martijn)''' - Board member - ''Term: 11/2013 - 11/2017''
* '''Sascha Montellese (Montellese)''' - Board member - ''Term: 11/2013 - 11/2017''
* '''Keith Herrington (keith)''' - Board member - ''Term: 11/2016 - 11/2018''
* '''Peter Frühberger (fritsch)''' - Board member - ''Term: 11/2016 - 11/2018''
<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/2016|2016]]
* [[/Elections/2014|2014]]
* [[/Elections/2013|2013]]
* [[/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 - https://drive.google.com/file/d/0BwsEEPRqIzELYnNZRTlPY3liTUE/view?usp=sharing
* 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 partially incomplete due to software accounting issues with international currency. $10k income from sponsorships is missing and at least 10k or 20k devcon costs is also missing.

=== Account details ===

'''Europe bank account'''

* Bank: ING Netherlands
* Beneficiary: Kodi Foundation
* IBAN account: NL39 INGB 0006 6296 56
* BIC: INGBNL2A

'''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/

== See also ==

=== Similar page names ===
{{#lst:Foundation|similar pages}}

[[Category:Team Kodi]]
[[Category:Team Kodi specific notes]]
[[Category:XBMC Foundation|*]]

File:Kodi Foundation exempt.jpg

2017-09-14T09:41:55Z

Natethomas:

File:KodiFoundationIncorporationNotice.pdf

2017-09-14T09:40:59Z

Natethomas:

Kodi Foundation

2017-09-14T09:32:13Z

Natethomas: /* Previous elections */

{{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.
* [[/Member list]]

== Board of Directors ==
{| class="infobox"
|-
|
<section begin=Foundation members />
* '''Nathan Betzen (natethomas)''' - Board member - ''Term: 11/2013 - 11/2017''
* '''Martijn Kaijser (Martijn)''' - Board member - ''Term: 11/2013 - 11/2017''
* '''Sascha Montellese (Montellese)''' - Board member - ''Term: 11/2013 - 11/2017''
* '''Keith Herrington (keith)''' - Board member - ''Term: 11/2016 - 11/2018''
* '''Peter Frühberger (fritsch)''' - Board member - ''Term: 11/2016 - 11/2018''
<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/2016|2016]]
* [[/Elections/2014|2014]]
* [[/Elections/2013|2013]]
* [[/Elections/2012|2012]]

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

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

== Financial information ==

=== Financial status ===

* Form 990 2016 - https://drive.google.com/file/d/0BwsEEPRqIzELYnNZRTlPY3liTUE/view?usp=sharing
* 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 partially incomplete due to software accounting issues with international currency. $10k income from sponsorships is missing and at least 10k or 20k devcon costs is also missing.

=== Account details ===

'''Europe bank account'''

* Bank: ING Netherlands
* Beneficiary: Kodi Foundation
* IBAN account: NL39 INGB 0006 6296 56
* BIC: INGBNL2A

'''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/

== See also ==

=== Similar page names ===
{{#lst:Foundation|similar pages}}

[[Category:Team Kodi]]
[[Category:Team Kodi specific notes]]
[[Category:XBMC Foundation|*]]

Archive:XBMC Foundation/Elections/2016

2017-09-14T09:31:39Z

Natethomas: created 2016 election history page

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

==Pre-election==
Natethomas 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.

:''2016-10-17 "Nominations for XBMC Foundation Board", as written by natethomas''

:{| class="wikitable"
|-
|
Hi everybody, it's October, which means it's time for elections again. This year board member seats up for election are: FernetMenta and mkortstiege.

Seats not up for election are Martijn, Montellese, and Natethomas (me).

The rules are pretty simple:

1. Any team member can nominate.

2. You're allowed to re-nominate.

3. The nominated member has to accept his nomination.

4. Only foundation members will be able to vote.*

5. If a person has been nominated, please don't nominate again.

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

'''Nominate: <member>'''

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

'''I accept my nomination.'''

or

'''No, thanks. I do not accept my nomination.'''

I'll update the second post in this thread 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 10 days from 2016/10/1. After that i'll setup the actual vote.

* Anyone who has been added to the team since 2015/9/15 should also check out this thread. http://forum.kodi.tv/showthread.php?tid=292745 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.
|}

==Voting==
Voting started on October 17th 2016 and ended on October 26th 2016 using the Condorcet Internet Voting Service with a ranking scale, http://www.cs.cornell.edu/w8/~andru/civs

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"
|-
|You're voting for 2 candidates to join the XBMC Foundation board alongside Nathan (natethomas), Martijn (martijn), and Sascha (montellese), whose appointments last for another 12 months. Each of the people below have been nominated and have accepted their nomination.

The 2 candidates that receive the highest support will join the board for a period of 2 years.

Good luck to the candidates.
|}

;Final list of confirmed nominees:
* fritsch
* keith
* kib
* fernetmenta
* mkortstiege
* jjd-uk
* phil65
* pike

==Results==
33 Foundation members voted. The top two ranked become board members effective December 23rd, 2014. Mkortstiege and FernetMenta were elected as new board members.

'''Results page:''' http://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_8e0b6d7dd125a948

# '''fritsch''' (Not defeated in any contest vs. another choice)
# '''keith'''
# '''kib''', loses to keith by 16–8
# '''fernetmenta''', loses to kib by 17–14
# '''mkortstiege''', loses to fernetmenta by 15–13
# '''jjd-uk''', loses to mkortstiege by 15–12
# '''phil65''', loses to jjd-uk by 13–12
# '''pike''', loses to phil65 by 18–9

Kodi Foundation

2017-09-14T09:11:41Z

Natethomas: /* Financial status */

{{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.
* [[/Member list]]

== Board of Directors ==
{| class="infobox"
|-
|
<section begin=Foundation members />
* '''Nathan Betzen (natethomas)''' - Board member - ''Term: 11/2013 - 11/2017''
* '''Martijn Kaijser (Martijn)''' - Board member - ''Term: 11/2013 - 11/2017''
* '''Sascha Montellese (Montellese)''' - Board member - ''Term: 11/2013 - 11/2017''
* '''Keith Herrington (keith)''' - Board member - ''Term: 11/2016 - 11/2018''
* '''Peter Frühberger (fritsch)''' - Board member - ''Term: 11/2016 - 11/2018''
<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/2014|2014]]
* [[/Elections/2013|2013]]
* [[/Elections/2012|2012]]

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

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

== Financial information ==

=== Financial status ===

* Form 990 2016 - https://drive.google.com/file/d/0BwsEEPRqIzELYnNZRTlPY3liTUE/view?usp=sharing
* 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 partially incomplete due to software accounting issues with international currency. $10k income from sponsorships is missing and at least 10k or 20k devcon costs is also missing.

=== Account details ===

'''Europe bank account'''

* Bank: ING Netherlands
* Beneficiary: Kodi Foundation
* IBAN account: NL39 INGB 0006 6296 56
* BIC: INGBNL2A

'''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/

== See also ==

=== Similar page names ===
{{#lst:Foundation|similar pages}}

[[Category:Team Kodi]]
[[Category:Team Kodi specific notes]]
[[Category:XBMC Foundation|*]]

Kodi Foundation

2017-09-14T09:10:48Z

Natethomas: /* Account details */

{{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.
* [[/Member list]]

== Board of Directors ==
{| class="infobox"
|-
|
<section begin=Foundation members />
* '''Nathan Betzen (natethomas)''' - Board member - ''Term: 11/2013 - 11/2017''
* '''Martijn Kaijser (Martijn)''' - Board member - ''Term: 11/2013 - 11/2017''
* '''Sascha Montellese (Montellese)''' - Board member - ''Term: 11/2013 - 11/2017''
* '''Keith Herrington (keith)''' - Board member - ''Term: 11/2016 - 11/2018''
* '''Peter Frühberger (fritsch)''' - Board member - ''Term: 11/2016 - 11/2018''
<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/2014|2014]]
* [[/Elections/2013|2013]]
* [[/Elections/2012|2012]]

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

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

== Financial information ==

=== Financial status ===

''note'': 2014 and 2015 expenses are partially incomplete due to software accounting issues with international currency. $10k income from sponsorships is missing and at least 10k or 20k devcon costs is also missing.
* Form 990 2016 - https://drive.google.com/file/d/0BwsEEPRqIzELYnNZRTlPY3liTUE/view?usp=sharing
* 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

=== Account details ===

'''Europe bank account'''

* Bank: ING Netherlands
* Beneficiary: Kodi Foundation
* IBAN account: NL39 INGB 0006 6296 56
* BIC: INGBNL2A

'''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/

== See also ==

=== Similar page names ===
{{#lst:Foundation|similar pages}}

[[Category:Team Kodi]]
[[Category:Team Kodi specific notes]]
[[Category:XBMC Foundation|*]]

Kodi Foundation

2017-09-14T09:06:00Z

Natethomas: /* Financial status */ added tax filing for 2016

{{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.
* [[/Member list]]

== Board of Directors ==
{| class="infobox"
|-
|
<section begin=Foundation members />
* '''Nathan Betzen (natethomas)''' - Board member - ''Term: 11/2013 - 11/2017''
* '''Martijn Kaijser (Martijn)''' - Board member - ''Term: 11/2013 - 11/2017''
* '''Sascha Montellese (Montellese)''' - Board member - ''Term: 11/2013 - 11/2017''
* '''Keith Herrington (keith)''' - Board member - ''Term: 11/2016 - 11/2018''
* '''Peter Frühberger (fritsch)''' - Board member - ''Term: 11/2016 - 11/2018''
<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/2014|2014]]
* [[/Elections/2013|2013]]
* [[/Elections/2012|2012]]

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

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

== Financial information ==

=== Financial status ===

''note'': 2014 and 2015 expenses are partially incomplete due to software accounting issues with international currency. $10k income from sponsorships is missing and at least 10k or 20k devcon costs is also missing.
* Form 990 2016 - https://drive.google.com/file/d/0BwsEEPRqIzELYnNZRTlPY3liTUE/view?usp=sharing
* 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

=== Account details ===

'''Europe bank account'''

* Bank: ING Netherlands
* Beneficiary: XBMC Foundation
* IBAN account: NL39 INGB 0006 6296 56
* BIC: INGBNL2A

'''Unites States account'''

* Bank: Wells Fargo
* Beneficiary: XBMC 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/

== See also ==

=== Similar page names ===
{{#lst:Foundation|similar pages}}

[[Category:Team Kodi]]
[[Category:Team Kodi specific notes]]
[[Category:XBMC Foundation|*]]

Kodi Foundation

2017-09-14T08:58:51Z

Natethomas: /* Board of Directors */

{{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.
* [[/Member list]]

== Board of Directors ==
{| class="infobox"
|-
|
<section begin=Foundation members />
* '''Nathan Betzen (natethomas)''' - Board member - ''Term: 11/2013 - 11/2017''
* '''Martijn Kaijser (Martijn)''' - Board member - ''Term: 11/2013 - 11/2017''
* '''Sascha Montellese (Montellese)''' - Board member - ''Term: 11/2013 - 11/2017''
* '''Keith Herrington (keith)''' - Board member - ''Term: 11/2016 - 11/2018''
* '''Peter Frühberger (fritsch)''' - Board member - ''Term: 11/2016 - 11/2018''
<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/2014|2014]]
* [[/Elections/2013|2013]]
* [[/Elections/2012|2012]]

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

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

== Financial information ==

=== Financial status ===

''note'': 2014 and 2015 expenses are partially incomplete due to software accounting issues with international currency. $10k income from sponsorships is missing and at least 10k or 20k devcon costs is also missing.
* 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

=== Account details ===

'''Europe bank account'''

* Bank: ING Netherlands
* Beneficiary: XBMC Foundation
* IBAN account: NL39 INGB 0006 6296 56
* BIC: INGBNL2A

'''Unites States account'''

* Bank: Wells Fargo
* Beneficiary: XBMC 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/

== See also ==

=== Similar page names ===
{{#lst:Foundation|similar pages}}

[[Category:Team Kodi]]
[[Category:Team Kodi specific notes]]
[[Category:XBMC Foundation|*]]

Archive:Google Summer of Code/2017

2017-03-01T21:52:51Z

Natethomas: /* Where to submit proposals */

Archive:Google Summer of Code/2017

2017-02-09T11:18:10Z

Natethomas: /* Team-Kodi proposal ideas up for discussion */

Archive:Google Summer of Code/2017

2017-02-09T11:17:12Z

Natethomas: /* Team-Kodi proposal ideas up for discussion */

Archive:Google Summer of Code/2017

2017-02-09T10:58:26Z

Natethomas: /* Where to submit proposals */

Archive:Google Summer of Code/2017

2017-02-09T10:57:16Z

Natethomas: /* About Us */

Archive:Google Summer of Code/2017

2017-02-09T10:53:52Z

Natethomas: updated student app dates

Kodi Foundation

2016-08-03T17:07:17Z

Natethomas: /* Financial status */ added an incomplete 2014 and 2015

{{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.
* [[/Member list]]

== Board of Directors ==
{| class="infobox"
|-
|
<section begin=Foundation members />
* '''Nathan Betzen (natethomas)''' - Board member (President) - ''Term: 11/2013 - 11/2017''
* '''Martijn Kaijser (Martijn)''' - Board member (CFO) - ''Term: 11/2013 - 11/2017''
* '''Sascha Montellese (Montellese)''' - Board member (Secretary) - ''Term: 11/2013 - 11/2017''
* '''Matthias Kortstiege (mkortstiege)''' - Board member - ''Term: 11/2014 - 11/2016''
* '''Rainer Hochecker (FernetMenta)''' - Board member - ''Term: 11/2014 - 11/2016''
<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/2014|2014]]
* [[/Elections/2013|2013]]
* [[/Elections/2012|2012]]

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

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

== Financial information ==

=== Financial status ===

''note'': 2014 and 2015 expenses are partially incomplete due to software accounting issues with international currency. $10k income from sponsorships is missing and at least 10k or 20k devcon costs is also missing.
* 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

=== Account details ===

'''Europe bank account'''

* Bank: ING Netherlands
* Beneficiary: XBMC Foundation
* IBAN account: NL39 INGB 0006 6296 56
* BIC: INGBNL2A

'''Unites States account'''

* Bank: Wells Fargo
* Beneficiary: XBMC 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/

== See also ==

=== Similar page names ===
{{#lst:Foundation|similar pages}}

[[Category:Team Kodi]]
[[Category:Team Kodi specific notes]]
[[Category:XBMC Foundation|*]]

Archive:Google Summer of Code/2016

2016-02-19T00:08:27Z

Natethomas: added student application dates

Archive:Google Summer of Code/2016

2016-02-18T22:52:54Z

Natethomas:

Kodi Foundation

2015-09-14T06:40:39Z

Natethomas: /* Previous elections */

{{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.
* [[/Member list]]

== Board of Directors ==
{| class="infobox"
|-
|
<section begin=Foundation members />
* '''Nathan Betzen (natethomas)''' - Board member (President) - ''Term: 11/2013 - 11/2015''
* '''Martijn Kaijser (Martijn)''' - Board member (CFO) - ''Term: 11/2013 - 11/2015''
* '''Sascha Montellese (Montellese)''' - Board member (Secretary) - ''Term: 11/2013 - 11/2015''
* '''Matthias Kortstiege (mkortstiege)''' - Board member - ''Term: 11/2014 - 11/2016''
* '''Rainer Hochecker (FernetMenta)''' - Board member - ''Term: 11/2014 - 11/2016''
<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 minutes ===
* [[/Board minutes/2012-11-4]]

== 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/2014|2014]]
* [[/Elections/2013|2013]]
* [[/Elections/2012|2012]]

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

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

== Financial information ==

=== Financial status ===

* Income and expenses - https://docs.google.com/spreadsheet/ccc?key=0AtlJ3dnHcw46dHpmeXlIV0hGaC13Z3I3b25hZWhWRGc#gid=8

=== Account details ===

'''Europe bank account'''

* Bank: ING Netherlands
* Beneficiary: XBMC Foundation
* IBAN account: NL39 INGB 0006 6296 56
* BIC: INGBNL2A

'''Unites States account'''

* Bank: Wells Fargo
* Beneficiary: XBMC 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/

== See also ==

=== Similar page names ===
{{#lst:Foundation|similar pages}}

[[Category:Team Kodi]]
[[Category:Team Kodi specific notes]]
[[Category:XBMC Foundation|*]]

Kodi Foundation

2015-08-20T06:06:01Z

Natethomas: /* Account details */

{{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.
* [[/Member list]]

== Board of Directors ==
{| class="infobox"
|-
|
<section begin=Foundation members />
* '''Nathan Betzen (natethomas)''' - Board member (President) - ''Term: 11/2013 - 11/2015''
* '''Martijn Kaijser (Martijn)''' - Board member (CFO) - ''Term: 11/2013 - 11/2015''
* '''Sascha Montellese (Montellese)''' - Board member (Secretary) - ''Term: 11/2013 - 11/2015''
* '''Matthias Kortstiege (mkortstiege)''' - Board member - ''Term: 11/2014 - 11/2016''
* '''Rainer Hochecker (FernetMenta)''' - Board member - ''Term: 11/2014 - 11/2016''
<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 minutes ===
* [[/Board minutes/2012-11-4]]

== 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/2013|2013]]
* [[/Elections/2012|2012]]

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

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

== Financial information ==

=== Financial status ===

* Income and expenses - https://docs.google.com/spreadsheet/ccc?key=0AtlJ3dnHcw46dHpmeXlIV0hGaC13Z3I3b25hZWhWRGc#gid=8

=== Account details ===

'''Europe bank account'''

* Bank: ING Netherlands
* Beneficiary: XBMC Foundation
* IBAN account: NL39 INGB 0006 6296 56
* BIC: INGBNL2A

'''Unites States account'''

* Bank: Wells Fargo
* Beneficiary: XBMC 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/

== See also ==

=== Similar page names ===
{{#lst:Foundation|similar pages}}

[[Category:Team Kodi]]
[[Category:Team Kodi specific notes]]
[[Category:XBMC Foundation|*]]

Archive:XBMC Foundation/Elections/2014

2015-08-20T05:41:42Z

Natethomas: copied 2013, replaced with 2014 info

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

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

==Nomination notice==
The following notice posted on the Team XBMC 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.

:''2014-10-18 "Nominations for XBMC Foundation Board", as written by natethomas''

:{| class="wikitable"
|-
|
Hey all, as you may know, it's that time of year again for Foundation Board voting. This year, Jonathan and Cory's seats would be up, except they've now both taken a break from the project, so... I guess the seats are still basically up.

Last year Cory (aka theuni) departed almost immediately after voting ended. The simple thing to do at that time was for the board to simply fill the seat with the next highest vote getter, who was Joakim (aka elupus). It was pointed out at devcon this year that the simple thing to do was simply to make the two seats that would have been up remain up, and that appears to fit the rules as stated in the by-laws, so unless there are objections (or alternative suggestions such as adding 2 more board members for a 7 seat board), it looks like Jonathan and Cory/Joakim's seats will be up for a vote.

For now, I'd like to get some nominations for board members. In the past, in order to get on the ballot, you had to be nominated, and then you had to accept the nomination in the nomination thread (so we didn't accidentally vote in somebody that was inactive). For now, I'd like to propose we have a 1 week nomination period, so post your nominations in this thread. Also, if you have any alternative ideas for how to deal with the seats up for election, feel free to post those ideas in this thread as well. Make sure to keep your nominations clear and visible. Like:

Nominate: David Hasselhoff.

Once the week is up on Saturday the 25th of October, we'll deal with any remaining issues and then begin the vote.

P.S. Board members with seats not up for election this year are Natethomas, Martijn, and Montellese.
P.S. #2 Past board members may also be nominated again. There are no term limits.
|}

==Voting==
Voting started on December 13th 2014 and ended on December 23rd 2014 using the Condorcet Internet Voting Service with a ranking scale, http://www.cs.cornell.edu/w8/~andru/civs

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"
|-
|This is a ranked vote of available candidates to be board members of the XBMC Foundation. The top two vote getters will become board members for a period of two years, after which time their seats will be up for renewal or replacement.

Your vote is tied to your XBMC or Kodi email address. If any Foundation members state that they haven't received an invitation to vote, any other member should inform natethomas and might suggest they check their XBMC or Kodi email account.

The current list of Foundation members may be found at this link.

Notification for a formal Foundation vote requires 10 days, so voting will be closed 11 days from the date of publishing this poll on the 22nd of December to give all Foundation members adequate time to make a decision.

Good luck to the candidates.
|}

;Final list of confirmed nominees:
* mkortstiege
* FernetMenta
* kib
* da-anda
* keith
* wsnipex

==Results==
40 out of 65 Foundation members voted. The top two ranked become board members effective December 23rd, 2014. Mkortstiege and FernetMenta were elected as new board members.

'''Results page:''' http://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_eb04cb5fbb62c2a8

# '''mkortstiege''' (Condorcet winner: wins contests with all other choices)
# '''FernetMenta''' loses to mkortstiege by 22–15
# '''kib''' loses to Matthias Kortstiege - mkortstiege/vdrfan by 19–15, loses to Rainer Hochecker - FernetMenta by 22–16
# '''da-anda''' loses to Matthias Kortstiege - mkortstiege/vdrfan by 19–16, loses to Ejal de Klerk - kib by 20–13
# '''keith''' loses to Matthias Kortstiege - mkortstiege/vdrfan by 27–10, loses to Franz Koch - da-anda by 19–11
# '''wsnipex''' loses to Matthias Kortstiege - mkortstiege/vdrfan by 26–9, loses to Keith Herrington - keith by 20–17

NVIDIA SHIELD TV

2015-06-13T20:42:23Z

Natethomas: /* Videos */ added kordkutters review

{{mininav|[[Devices]]|[[Android]]}}
{{device notice}}

{{Infobox information appliance
| name = Nvidia SHIELD Android TV
| image = [[File:Nvidia_SHIELD_Console.jpg|250px]]
| manufacturer = Nvidia
| releasedate = May 28, 20152015
| os = [[wikipedia:Android TV|Android TV]] (based on [[Android]] 5.0 "Lollipop")
| soc = [[Nvidia Tegra]] X1 (TX1)
| cpu = [[Nvidia Tegra]] X1 (TX1), Big.LITTLE Octa-Core (4 x ARM Cortex A57 CPU cores and 4 x ARM Cortex A53 CPU cores)
| graphics = 256-core Maxwell GPU
| display = 2160p and 1080p
| storage = Standard model with 16 GB internal, Pro model with 500GB harddrive, plus MicroSD slot for up to 128GB SD card available in all models
| memory = 3 GB RAM
| connectivity = HDMI 2.0 supporting 4K @ 24/25/30/50/60 Hz video output (with (HDMI-CEC, HDCP 2.2, 10-bit color & HDR) and 24-bit/192 kHz audio output in 5.1 or 7.1, Bluetooth 4.1/BLE, 2 x USB 3.0 (Type A), 1 x Micro-USB 2.0 port, Dual-Band WiFi (802.11ac 2×2 MIMO), 10/100/1000 Ethernet, IR Receiver
| dimensions = 210 x 130 x 25 mm
}}

<section begin="intro" />'''Nvidia SHIELD Android TV''' (originally known as ''SHIELD Console'') is an Android-based set-top box and game console that contains a very powerful ARM processor, (that should be able to handle the most heavy of Kodi skins and more). It is one of the first Android based devices featuring high end media playback capabilities such as of and support high definition audio at up to 192 kHz, automatic refresh rate switching, 10-bit HEVC (H.265), and VP9 video codecs, and 4K (2160p) resolution via HDMI 2.0 output with support for Kodi. <section end="intro" />

Running the [[wikipedia:Android TV|Android TV]] operating system (based on [[wikipedia:Android Lollipop|Android 5.0 "Lollipop"]]) on a [[Nvidia Tegra|Tegra X1 SoC (System on Chip)]], the Nvidia SHIELD Android TV stands above most of the other high-end Android-based offerings not only because best-in-class hardware offering the fastest graphics for gaming capabilities for Android, but also because due to Nvidia's strong product support of their own SHIELD series products. It comes with [[10 foot interface|remote friendly]] versions of Netflix, Hulu, HBO Now, Google Play Movies, YouTube and other video service clients, with many supporting videos in native 4K (Ultra HD / 2160p) resolution.

The Android TV platform delivers good conversational voice search for the native app via an integrated microphone inside the included game controller. Adding to that it also comes with Nvidia's gaming ecosystem capable of running all graphically intensive [[wikipedia:AAA (game industry)|AAA ("triple A") games]] for Android in 1080p at 60fps, as well as supporting Nvidia's low-latency GameStream technologies for GeForce-equipped PC game streaming, and Nvidia's GRID cloud game-streaming service.. All this making it a very good convergence device when pairing with Kodi for media playback.

== Installing Kodi==
{{see|HOW-TO:Install Kodi for Android}}

Normal "vanilla" builds of Kodi should run just fine on the Shield. However, some advanced features, such as 4k support, might require a test build from here: http://forum.kodi.tv/showthread.php?tid=228361

== Launching Android apps within Kodi ==
{{main|HOW-TO:Launch Android apps}}
{{#lst:HOW-TO:Launch Android apps|extended intro}}
{{-}}

== Controls ==
You can use standard Bluetooth accessories, such as a wireless keyboard, mouse, or game controller with your SHIELD console.

=== Bluetooth remote ===
* Nvidia SHIELD Remote [http://shield.nvidia.com/store/remote]
* other bluetooth remotes also work, such as the Amazon Fire TV replacement remote

=== Integrated IR Reciever ===
* Logitech Harmony Remotes are supposedly supported by Nvidia?

=== CEC ===
Generic Android-level CEC support is available. Kodi will not see a CEC device directly, but instead just treat it like generic input.

=== USB ===
USB port allows for various additional remote types, such as FLIRC IR dongle, various RF dongles, etc. Most of these devices will likely show up as a keyboard type input.

=== Other bluetooth devices ===
It should be possible to pair other bluetooth controllers and remotes to the Nvidia SHIELD Console. Most of these devices will likely show up as a [[keyboard]] type input.

====Working Bluetooth Gamepads====
* Nvidia SHIELD Controller [http://shield.nvidia.com/store/controller]

====Working Bluetooth Remotes====
* Harmony Smart Control Hub (Harmony software lists device as Nvidia STB, but some of the extra commands to don't work, e.g. X, Y, A, B, Gas, Brake, etc.)
:(You can also set up the Hub as a Windows PC and have more command options, this will present the remote as a keyboard.)

== Videos ==
A Kodi oriented review of the Shield:

{{youtube|0MH73mhO0fM}}

Kodi-related videos for end-users:

{{youtube|A2i_TiIJ7uM}}

Kodi-related videos for developers:

{{youtube|QpJ3r9FWfow}}

== Hints and tips ==
Some of this is copied directly from Nvidia's GeForce Forum for SHIELD Android TV support.[https://forums.geforce.com/default/topic/836884/shield-android-tv/helpful-shield-information-for-new-shield-android-tv-users-updated-6-5-2015-/] More generic but useful info about the SHIELD Android TV that is not specific to Kodi can also be found in Nvidia's official SHIELD FAQ[http://shield.nvidia.com/support/nvidia-android-tv/faq/1] and SHIELD User Guide[http://support-shield.nvidia.com/android-tv-user-guide/index.htm#_ga=1.98702110.121900636.1426802792&t=About_SHIELD.htm].
* Did you know that if you hold the play button on the Shield game controller a mouse cursor will pop up on your screen and turn the right analog thumb stick on your game controller to a mouse controller which can control that mouse cursor.
* If you plan on using a microSD card or USB storage with your SHIELD Android TV, make sure to unmount the drive before unplugging it. This is done from "Settings" -> "Storage and reset" inside the Android TV menus, not inside Kodi. Select your storage device and then choose the unmount option. Now you may safely unplug/remove your storage device from your SHIELD Android TV.
* If you are unable to pair your SHIELD Wireless Controller during initial setup and your SHIELD Android TV is connected to your network over wired Ethernet, try temporarily disconnecting your wired Ethernet cable to go into WiFi mode and check if pairing issue is fixed.
* If the Google Play Store is not opening, check if the version is at least 5.5.15 or later. If not you should be receiving this update soon. After the update if the problem continues, try clearing the data and cache for the Google Play Store app.
* Watching 4K content from SHIELD requires a 4K display with HDMI 2.0 and HDCP 2.2 support. Connect SHIELD to only the 4K-enabled HDMI input that supports HDCP 2.2. Consult your 4K display's user guide to find the correct HDMI port to plug SHIELD into for watching 4K content. SHIELD also supports content rendered with 4:4:4, and 4:2:0 chroma subsampling frequency ratios. (NOTE: Netflix 4K content is currently only enabled for HDCP 2.2 ports. See your 4K display's user guide for further details). If one of the HDMI 2.0 ports do not work then try another until you find a port that works.
* For maximum performance, wired Ethernet is recommended. The wired Ethernet port on SHIELD supports 10/100/1000 Mbps. Once wired Ethernet is connected, SHIELD will disable Wi-Fi and automatically switch to use only wired Ethernet.
* Use of an AV Receiver with HDMI for video and Toslink for audio may result audio lagging behind video. Use the AV sync slider (not in Kodi) utility in the SHIELD menu Settings > HDMI > Audio Video Sync to calibrate for any audio lag. The AV sync slider allows you to advance audio by 1 second (in small increments of 10ms) to synchronize the audio and video. (Note: This tool is effective only when SHIELD is connected to your AV Receiver over HDMI (i.e. audio/video over HDMI); it is not meant to be used when a headset is plugged into SHIELD controller/SHIELD remote or USB audio device or Bluetooth audio device). If video lags behind audio (i.e. audio is ahead of video) then use your AV receiver’s settings to delay audio.
*?

== Known issues ==
Known issues related to usage of Kodi on Nvidia SHIELD Android TV, including limitations in the hardware, firmware, and software.
* MPEG-2 and VC-1 (or WMV-9) videos are software decoded only so far, reason for this is that Nvidia have so far only licensed H.264, HEVC (H.265), and VP9 codecs for video playback, as well as Dolby Digital (DD) and Dolby Digital Plus (DD+) for audio<ref>http://www.legitreviews.com/nvidia-shield-android-tv-review_164223/3 Legit Reviews - NVIDIA SHIELD Android TV Review</ref>, (and unfortunately Nvidia do at least not yet offer a add-on license keys for a codec pack similar to Raspberry Pi<ref name="RaspPi Codec License keys">http://www.raspberrypi.com/license-keys/ Raspberry Pi Store - License keys</ref>).<ref name="Requests to Nvidia for Codec Packs">https://forums.geforce.com/default/topic/836487/shield-android-tv/codec-support-/ GeForce Forums - Requests to Nvidia for Codec Packs</ref> There is however apparently a hack available to enable MPEG-2 and VC-1 hardware decoding by editing Android file "/system/etc/media_codecs.xml" if you have first rooted the SATV.[http://forum.xda-developers.com/showpost.php?p=61241497&postcount=47]
*HD audio, DTS-HD MA, Dolby True HD & Dolby Atoms can not be passed through/bitstreamed, nor can those formats be software decoded and output as multichannel PCM (at this time). However, DTS (core from DTS-HD MA) and DD 5.1(AC3) can be passed through/bitstreamed or software decoded and output as multichannel PCM.<ref name="Requests to Nvidia for Codec Packs" />
* Currently the Shield Android TV does not support Remote Connections, so to connect to the Shield to sideload via ADB it requires a direct connection.
* The Nexus Player remote does not pair at all with the Shield console. It did with the Razer Forge, but not the Shield console.
* ?

== Random notes ==
{{large|''Feel free to place various notes, tips, and links here. As this section of the wiki gets more organized, those notes will be properly sorted. Consider this like a dumping ground for when you're not sure where to put something.''}}

* Kodi's existing [[Settings/Videos|video setting options]] for "Adjust display refresh rate to match video" and "Sync playback to display" to sync screen refresh rate to playback frame rate option currently only works in experimental builds, and then so far only with 24/25/30/50/60 Hz refresh rates.
* HDMI-CEC is supposedly supported supported in the hardware and in the Android firmware, but no news yet on API or other interface with [[LibCEC]] for direct native Kodi support of the CEC controller.
* VP9 hardware video decode is supposedly supported at 4K (UltraHD) resolution, such as YouTube source, but not yet confirmed working in Kodi for Android on the Nvidia Tegra X1 (TX1) SoC.
* ?

==References==
{{reflist}}
* [http://www.anandtech.com/show/9289/the-nvidia-shield-android-tv-review/6 AnandTech - The NVIDIA SHIELD Android TV Review: A Premium 4K Set Top Box]
* [http://www.legitreviews.com/nvidia-shield-android-tv-review_164223/3 Legit Reviews - NVIDIA SHIELD Android TV Review]

== See also ==
* [[Android hardware]]
* [[Android]]

== Links ==
* Kodi forum discussion threads about the Nvidia SHIELD Android TV:
**Support and help thread: http://forum.kodi.tv/showthread.php?tid=228158
**General hardware discussion: http://forum.kodi.tv/showthread.php?tid=220297
*Related articles on Wikipedia:
** Wikipedia article on Nvidia SHIELD Android TV: [[wikipedia:Nvidia Shield Console]]
** Wikipedia article on Android TV (OS used on Nvidia SHIELD Console): [[wikipedia:Android TV]]
*Official Nvidia pages and sites about the SHIELD console:
** Nvidia SHIELD Android TV product page: http://shield.nvidia.com/console
***Nvidia SHIELD Remote Control http://shield.nvidia.com/store/remote
***Nvidia SHIELD Game Controller http://shield.nvidia.com/store/controller
** Nvidia SHIELD Android TV FAQ (Frequently Asked Questions): http://shield.nvidia.com/support/nvidia-android-tv/faq/1
** Nvidia SHIELD Android TV User Guide: http://support-shield.nvidia.com/android-tv-user-guide/index.htm#_ga=1.98702110.121900636.1426802792&t=About_SHIELD.htm
** Nvidia Blog post: http://blogs.nvidia.com/blog/2015/05/28/nvidia-shield-available/
** Nvidia SHIELD forum for Android TV https://forums.geforce.com/default/board/159/
** Nvidia SHIELD development tools and other resources for developers: https://developer.nvidia.com/develop4shield
**Tegra Android Development Pack: https://developer.nvidia.com/tegra-android-development-pack
* Nvidia SHIELD TV Utility App: http://goo.gl/4FiQCT

[[Category:HTPC]]
[[Category:Android]]
[[Category:ARM]]
[[Category:Nvidia SHIELD]]
[[Category:Nvidia Tegra]]

Archive:All platforms FAQ

2015-05-16T01:52:48Z

Natethomas: /* Troubleshooting */ added video guide for missing tv shows

{{XBMC FAQ}}
{{mininav| [[FAQs]] {{l2| [[Devices]] }} }}
'''F'''requently '''A'''sked '''Q'''uestions for {{kodi}} that apply to all versions/platforms/OSes.

__TOC__
{{-}}
== General ==
{| width="100%"
{| width="100%"
{{FAQ|1= XBMC
| BGcolor= WhiteSmoke
| Question= About {{kodi}}
| Answer=
{{Main|Kodi FAQ|Kodi}}
{{#lst:Kodi|intro2}}
}}

{{FAQ|1= Install
| BGcolor=
| Question= Installing Kodi
| Answer=
* See '''[[Installation]]''' and select the OS for your device for installation instructions.
* The current stable build of Kodi is {{current version}}.
}}

{{FAQ|1= uninstall |2= fresh_install
| BGcolor= WhiteSmoke
| Question= Uninstalling/fresh installing
| Answer=
* To completely uninstall {{kodi}}, or to preform a fresh reinstall, you will need to delete the [[userdata folder]] and the containing Kodi ("xbmc" on older installs) home folder that holds the userdata folder, in addition to deleting/uninstalling the Kodi application.
}}

{{FAQ|1=Kodi_version|2= XBMC_version
| BGcolor=
| Question= What version am I running?
| Answer=
* In the default skin go to: Kodi main menu > System > Lower submenu > System info
* For a nightly build, note the build date.
}}

{{FAQ|1=Quick_Start_Guide|2=Quickstart
| BGcolor= WhiteSmoke
| Question= Quick Start Guide
| Answer=
{{See|Quick Start Guide}}
}}

{{FAQ|1=Library|2=MySQL_sync|3=Roaming_profiles
| BGcolor=
| Question= Sync the Kodi library between multiple installs
| Answer=
{{See|Syncing and sharing}}
}}

{{FAQ|1= Remotes|2= Keyboard |3= Keyboard_controls
| BGcolor= WhiteSmoke
| Question= Controlling Kodi
| Answer=
{{See|Remote controls}}
{{See|Keyboard controls}}
}}

{{FAQ|1= Full_screen |2=Windowed
| BGcolor=
| Question= Switching between windowed and full screen
| Answer=
* To toggle between windowed mode and full screen mode, press the {{keypress|\}} button on a keyboard. (This, or any keyboard button, can be assigned to a remote control button if you wish. See [[Remote controls]] for more info.)
* If you have backed out of a playing video and see it behind the GUI, you can toggle back by pressing {{keypress|Tab}}.
}}
<section begin="Consoles and smartTV" />
{{FAQ|1=DLNA|2=SmartTVs|3=UPnP
| BGcolor= WhiteSmoke
| Question= Can I stream Kodi from my PC to my TV using DLNA/UPnP?
| Answer=
* Kodi has some support for this, and more is planned for the future. Normally Kodi is meant to be ran on a computer/supported-device that is directly connected to the TV by a video cable.
* Some files can be '''[[UPnP/Share|shared]]''' from Kodi using the built-in [[UPnP]] server and files scanned into the [[Video library]]. Kodi will not currently transcode any files, so only file formats that your TV/device can natively playback will work. This will only work with video (so you won't see Kodi's GUI) and currently does not work with add-on content.
}}

{{FAQ|1= xbox |2= PS3 |3= xbox360 |4=Wii
| BGcolor=
| Question= Can I install Kodi on a PS3/4, Xbox360/One, or Wii/U?
| Answer=
* Not to be confused with [[XBMC4Xbox]], which is the continued effort to run {{kodi}} on original Xbox hardware.
* Nope. The required reverse engineering (to get access to the video acceleration hardware, among other things) has typically not happened on any of these game consoles. Further more, no one on Team Kodi has expressed an interest in attempting to port Kodi to those platforms, which would be a huge undertaking.
}}

{{FAQ|1= original_xbox
| BGcolor= WhiteSmoke
| Question= Does {{kodi}} still run on the original Xbox?
| Answer=
* Team Kodi no longer officially supports the original Xbox, but the group over at [[XBMC4Xbox]] does.
}}
<section end="Consoles and smartTV" />
|}

== Videos ==
{| width="100%"
{{FAQ|1= Video_library
| BGcolor=
| Question= How do I add videos with summaries and that show up under "TV Shows" and "Movies" on the main menu?
| Answer=
{{Main|Adding videos to the library}}
* {{#lst:Video management|intro}}
}}
{{FAQ|1=Update_library
| BGcolor= WhiteSmoke
| Question= How do I update the library?
| Answer=
{{main|Updating or removing videos}}
{{#lsth:Set content and scan|Scanning and updating files}}
}}
{{FAQ|1=missing_videos
| BGcolor=
| Question=Why don't all movies/shows show up in my library?
| Answer=
{{See|Incorrect and missing videos}}
}}
{{FAQ|1= kids |2= adults|3= separate_library
| BGcolor=
| Question= How to separate the library (cartoons, documentaries, anime, etc) from normal listings
| Answer=
{{Main|Custom home items}}
{{#lst:Custom home items|intro}}
}}
{{FAQ|1=Bluray
| BGcolor= WhiteSmoke
| Question=Bluray
| Answer=
* Kodi can playback unencrypted bluray discs and bluray images. There is limited support for some bluray menus.
}}

{{FAQ|1= Multi_part|2= File_stacking
| BGcolor=
| Question= Can Kodi handle multi-part movie files?
| Answer=
{{Main|File stacking}}
* Kodi can combined multi-part video files so that they play and appear as once video.
* File stacking is currently only available for movies and not for TV shows or music videos.
}}

{{FAQ|1= Movie_sets
| BGcolor= WhiteSmoke
| Question= Movie series and sets
| Answer=
{{main|Movie sets}}
* {{#lst:Movie sets|intro}}
}}

{{FAQ|1= play_next
| BGcolor=
| Question= How do I automatically play the next video?
| Answer=
* As of Kodi v12 you can turn on automatic playing of the next video by going to {{highlight|bordered=yes|[[Settings/Videos#Playback|Settings -> Videos -> Playback -> Play next video automatically]]}}
* While selecting the video you wish to start at, bring up the contextual menu (press {{keypress|C}}) and select "Play from here".
* You can also play all items in a folder, show, or season, by selecting the folder and pressing play on your remote. If you do not have a dedicated "play" button then you can also select "Play" from the contextual menu (press {{keypress|C}} or {{button|menu}}).
}}

|}

== Music ==
{| width="100%"
{{FAQ|1= Music_library
| BGcolor=
| Question= How do I add music to the library?
| Answer=
{{main|Adding music to the library}}
{{#lst:Adding music to the library|Intro}}
}}

{{FAQ|1=MP3_tags
| BGcolor= WhiteSmoke
| Question= Why doesn't all of my music/info show up in my library?
| Answer=
* Most of the information for music is pulled from the embedded music tags inside the file. Make sure your music files are tagged correctly.
* Some tags might show up in other programs, but might still be damaged or invalid for the tag standard, causing issues in Kodi.
* You can use a program such as [[MusicBrainz Picard]] to easily tag files or fix broken tags. See also [[:Category:Music tools]] for other programs.
}}

|}

== Pictures ==
{| width="100%"
{{FAQ|1= Picture_viewing
| BGcolor=
| Question= How do I add view digital pictures and still images?
| Answer=
{{main|Pictures}}
{{#lst:Pictures|Intro}}
}}

{{FAQ|1=Picture_library
| BGcolor= WhiteSmoke
| Question= Why isn't there a picture library?
| Answer=
* No one have developed a picture library for {{Kodi}} yet, but there is a pictures section where you can add media sources and view pictures in file mode.
* Not having a picture library (and a picture database) unfortuanly means that you can not sort, browse, or search pictures by their tags.
}}

|}

== PVR (Live TV and DVR) ==
{| width="100%"
{{FAQ|1= PVR_frontend
| BGcolor=
| Question= Can I watch Live TV and control PVR/DVR function?
| Answer=
{{main|PVR}}
{{#lst:PVR|Intro}}
}}

{{FAQ|1=PVR_backends
| BGcolor= WhiteSmoke
| Question= How does Live TV and PVR work in {{Kodi}}?
| Answer=
Logically, the PVR / Live TV design in {{Kodi}} uses a [[wikipedia:distributed application|distributed application structure]] that is designed after the [[wikipedia:client–server model|client–server model]] concept which consists of two parts:
# The PVR '''backend''' (as the server side part), which communicates with a TV tuner adapter(s) to receive the Live TV signals and create a video or audio stream, and
# The PVR '''client''' (as an addon for {{Kodi}}) - an {{Kodi}} addon which controls the presentation of that content via the {{Kodi}} GUI that acts as unified frontend and common interface for all connected PVR backends.

The "'''PVR backend'''" as such is a separate application/process that directly interfaces with your TV tuner adapter(s) and the performs the task of tuning, streaming, and recording over-the-air and cable television signals and radio programming. PVR backends can either run on the same host running {{Kodi}}, or on a stand-alone host/device completely by itself with {{Kodi}} only running when needed, as long as they have a network connection between them. Some PVR backends may be able to serve several clients simultaneously, which may be {{Kodi}} clients or others applications/devices, and in those cases such PVR backends that serves multiple clients are commonly refereed to as PVR servers.

When paired with one or more matched PVR backends, a configured '''PVR client addon''' enables {{Kodi}} to handle the GUI interface, or frontend, allowing the user to watch Live TV (with pause/time-shift, if supported by the PVR backend used), display a graphical EPG (Electronic Program Guide) of all available television programming, schedule recordings or listen to radio, giving the same sort of functionality as TiVo-style video recorder devices.
}}

|}

== Add-ons ==
{{main|Add-ons}}
{| width="100%"
{{FAQ|1= Add-ons
| BGcolor=
| Question= What are add-ons?
| Answer=
* '''[[Add-ons]]''' are a way of extending Kodi's functionality easily. Common add-ons include: Skins, Scrapers, Video Add-ons, Subtitle services and many more are available.
}}

{{FAQ|1= Install_add-ons
| BGcolor= WhiteSmoke
| Question= How do I install add-ons?
| Answer=
* For a picture step by step see '''[[Add-on manager]]'''.
}}

{{FAQ|1= Repository
| BGcolor=
| Question= Where can I find unofficial add-ons/skins?
| Answer=
* Add-ons not included in the official Kodi repository can be obtained by using unofficial repositories or installing the add-on using '''Install from Zip file''' option. The two main sources for finding unofficial repos and add-ons are '''[[3rd party add-on repositories]]''' and the '''[http://forum.kodi.tv/forumdisplay.php?f=27 Kodi Add-on support forums]'''.
}}

{{FAQ|1=Repository empty listing
| BGcolor= WhiteSmoke
| Question=What should I do when Addon repositories dont list any contents?
| Answer=
See [[Add-on manager#Empty repository list|'''Empty repositories list''']]
}}

{{FAQ|1= Add-on_help
| BGcolor=
| Question= Where do I get help with add-ons or skins?
| Answer=
* You can get help with add-ons at the '''[http://forum.kodi.tv/forumdisplay.php?f=27 Kodi Add-on support forums]''', with some add-ons even having dedicated threads with FAQs, and more. For skins see the '''[http://forum.kodi.tv/forumdisplay.php?f=67 Kodi Skin support forums]''', which has sub-forums for several skins as well as general help threads. '''''Be sure to use the search function to see if your question has been answered before'''''.
}}
|}

== Special features ==
{| width="100%"
{{FAQ|1=Netflix|2=LoveFilm|3=Silverlight
| BGcolor=
| Question= Netflix, LoveFilm, and other Silverlight-based video services
| Answer=
* Both [[w:Netflix|Netflix]] and [[w:LoveFilm|LoveFilm]] use [[w:silverlight|silverlight]], making it all but impossible to play inside of Kodi directly, even with an add-on. Sometimes there are add-ons for Kodi that will launch a web browser to load the service, but you will require an OS that has silverlight support (Mac OS X or Windows).
* {{editor note|Know of a guide for [[Advanced Launcher]], or a working add-on for launching Netflix or LoveFilm? Feel free to add that info/links here}}
}}

{{FAQ|1=Hulu|2=Amazon|3=Flash
| BGcolor= WhiteSmoke
| Question= Hulu, Amazon, and other Flash-based video services
| Answer=
* While Kodi does not have [[w:Adobe Flash|Flash]] video support directly, very often videos can be extracted from the Flash video stream/file container. Some sites also have non-flash video streams that can be accessed from within Kodi. Sometimes these streams/files can be accessed by using a [[STRM]] file, while others are more complicated and need an add-on to access the content. For example, there is an add-on for [[Hulu]] and Amazon Prime video services (see Bluecop's add-on repo for both). Be sure to check out [[:Category:Video add-ons]] and the Kodi forums to see what is currently available.
}}

{{FAQ|1=AirPlay
| BGcolor= WhiteSmoke
| Question= AirPlay
| Answer=
{{main|AirPlay}}
* To enable Kodi's [[AirPlay]] server go to: {{highlight|[[Settings/Network#Services|Settings -> Network -> Services -> Allow Kodi to receive AirPlay content]]}}
}}

|}

== Troubleshooting ==
{{main|Troubleshooting}}

{| width="100%"
{{FAQ|1= Bug_report
| BGcolor=
| Question= Reporting bugs
| Answer=
* For how to report bugs in Kodi see: '''[[HOW-TO:Submit a proper bug report]]'''.
}}

{{FAQ|1=os_specific_bugs
| BGcolor= WhiteSmoke
| Question= Platform/OS specific troubleshooting
| Answer=
* [[Android FAQ#Troubleshooting]]
* [[iOS FAQ#Troubleshooting]]
* [[Linux FAQ#Troubleshooting]]
* [[Mac FAQ #Troubleshooting]]
* [[Windows FAQ#Troubleshooting]]

* [[Raspberry Pi FAQ#Troubleshooting]]
}}

{{FAQ|1=Forum|2=IRC
| BGcolor=
| Question= Getting more help
| Answer=
* Check out the '''[http://forum.kodi.tv/forumdisplay.php?f=33 Help and Support forums]''' or the '''[irc://irc.freenode.org/kodi #kodi]''' [[w:IRC|IRC]] chat channel on irc.freenode.org
* Also check out the platform specific FAQs:
** [[Android FAQ]]
** [[iOS FAQ]]
** [[Linux FAQ]]
** [[Mac FAQ]]
** [[Windows FAQ]]
** [[KodiBuntu FAQ]]
** [[Raspberry Pi FAQ]]
}}

{{FAQ|1=Cache_full|2=Cache|3=buffering
| BGcolor= WhiteSmoke
| Question=Cache full messages and constant buffering
| Answer=
* This message refers to the playback cache that Kodi uses when a video is loading/streaming from the network (local or internet). It indicates that the video is loading too slowly for Kodi to play it back smoothly, and Kodi can't fully buffer it without having to buffer again as the video plays. The common cause for this is simply a slow connection to the file, often on the server's connection.
* The cache is loaded in RAM and is cleared out every time a video is stopped.
* Cache settings can be adjusted using [[advancedsettings.xml]]. See: '''[[HOW-TO:Modify the video cache]]'''.
* {{note|In most cases, this simply means that the server on the other side of the connection is too slow, and there's nothing you can do about it. No matter how fast your internet is, the server on the other side might simply be slow.}}
}}

{{FAQ|1=Missing_videos2
| BGcolor=
| Question= Not all videos are scanned into the library
| Answer=
{{See|Incorrect and missing videos}}
}}

{{FAQ|1= hide_watched
| BGcolor= WhiteSmoke
| Question= Previously watched videos are no longer listed/ Videos seem to go missing
| Answer=
* Bring up the side menu (arrow over left or right on a keyboard or remote) and toggle the "Hide Watched" option.
* See this video for quick guide on how to fix it.
{{youtube|4vMRBRdu5uU}}
}}

{{FAQ|1=mute
| BGcolor=
| Question= No sound and red speaker icon in the corner
| Answer=
[[File:mute.png|right]]This means that Kodi is muted. Turn the volume up.
}}

{{FAQ|1= Known issues
| BGcolor= WhiteSmoke
| Question= Is there a list of some known issues?
| Answer=
{{See|Common issues}}
}}

|}

{{Gotham updated}}

[[Category:Manual]]
[[Category:FAQ|**]]

Video management

2015-05-11T22:26:30Z

Natethomas: /* Alternative guides */

{{mininav|[[Video library]]}}
<section begin="intro" />To use your video files with "metadata" like summaries, cast info, DVD covers, thumbnails, and more, you need to '''[[Adding videos to the library|add those video files]]''' to the [[video library]].<section end="intro" />

See '''[[Adding videos to the library]]''' for just the basic topics on adding videos.

== Preparing files ==
To use your video files with "metadata" like summaries, cast info, DVD covers, thumbnails, and more, you need to add those video files to the video library.

<section begin="prep" />There are a couple of important parts to getting things imported into your {{Kodi}} library. First, the metadata for the video file should exist someplace (the metadata are things like the title of the show, the plot description, the season and episode number if the video file happens to be an episode of a TV series, the actors, the director, cover art and episode art, etc.) The second part is naming the video files so the file gets matched up with the metadata available online.

{{Kodi}} uses plugins called scrapers to pull information from a video file and coordinate it with a source of metadata available someplace on the internet. For a TV show the scraper basically looks for the show name, season number, and episode number. The default scrapers look at TheTVDB.com (for TV shows) and TheMovieDB.org (for Movies).

If some video file is not scraping properly, the first step is to go to the website of the scraper you are using on that source and see if the video is already listed there. If you can't find an entry on one of those two sites for the video you're interested in, you can hunt for different scrapers which search other websites for metadata (and go through the same process of making sure your show is listed there, then naming the video files to match). Alternatively, you can create new entries on those sites with some basic information about your show, and then let the scrapers do their work. This is nice, because it means that other people will benefit from your work, and may contribute additional information about the show over time.
Adding info to a site like TheTVDB.org is easy, but make sure you read the site rules before you start adding.

If none of that works, you can create .nfo files for each video by hand so that {{Kodi}} will bypass the normal looking online for information about your show. This is the least attractive option, though. It's a lot of work, and it doesn't benefit anyone else the way creating entries on the metadata sites does.<section end="prep" />

=== Naming files ===
{{main|Naming video files}}
{{#lst:Naming video files|intro}}

* [[Naming video files/Movies]]
* [[Naming video files/TV shows]]
* [[Naming video files/Music videos]]

=== NFO files ===
{{Main|NFO files}}
{{#lst:NFO files|intro}}

== Adding media sources ==
{{main|Adding video sources}}
{{#lst:Adding video sources|intro}}

=== Media sources ===
{{Main|Media sources}}
{{#lst:Media sources|intro}}

== Media stubs ==
{{Main|Media stubs}}
{{#lst:Media stubs|intro}}
{{-}}

== Internet streams ==
{{Main|Internet streams}}
{{#lst:Internet streams|intro}}

== Setting content and scanning ==
{{main|Set content and scan}}
{{#lst:Set content and scan|intro}}

=== Incorrect and missing videos ===
{{Main|Incorrect and missing videos}}
{{#lst:Incorrect and missing videos|intro}}

=== Custom video entries ===
{{Main|Custom video entries}}
{{#lst:Custom video entries|intro}}

=== Updating or removing videos ===
{{Main|Updating or removing videos}}
{{#lst:Updating or removing videos|intro}}

== Grouping media ==

=== File stacking ===
{{Main|File stacking}}
{{#lst:File stacking|intro}}

=== Movie sets ===
{{Main|Movie sets}}
{{#lst:Movie sets|intro}}

=== Video library tags ===
{{Main|Video library tags}}
{{#lst:Video library tags|intro}}

=== How to separate the library (cartoons, documentaries, anime, etc) ===
{{Main|Custom home items}}
{{#lst:Custom home items|intro}}

=== Playlists ===
{{Main|Playlists}}
* {{big|'''[[Basic playlists]] -'''}} {{#lst:Basic playlists|intro}}

* {{big|'''[[Smart playlists]] -'''}} {{#lst:Smart playlists|intro}}

=== Linking movies to TV shows ===
{{#lst:Linking movies to TV shows|movie TV link}}
{{-}}

=== Video nodes ===
{{Main|Video nodes}}
{{#lst:Video nodes|intro}}
{{-}}

== Alternative guides ==
<section begin="Alternative guides" />
* [http://lifehacker.com/5900626/create-a-kickass-seamless-play+everything-media-center-the-complete-guide Lifehacker.com - Create a Kickass, Seamless, Play-Everything Media Center: The Complete Guide]
* [http://tbueter.com/?page_id=324 The Frodo Guide] by Henry Ford
* [http://kordkutters.com/setting-up-your-kodi-movies-and-tv-shows-library/ Beginner Tip: How to add videos to Kodi from a network share] by Nathan Betzen
* [http://www.makeuseof.com/pages/xbmc-full-html Makeuseof.com - How to set up your Kodi Media Center]
* [http://youresuchageek.blogspot.fr/2012/06/xbmc-install-and-config-howto-for-linux.html Kodi Install and Config] HOW-TO for Linux Its for xvba, however apart from drivers the rest is a '''MUST''' read for Linux novices.

=== Video guides ===

{{youtube|UBGKcLu7aGk}} {{youtube|EkWYxqoOF3c}} {{youtube|ueqwMbdMVHU}}
<section end="Alternative guides" />

== See also ==
* [[Import-export library]]
* [[Parental controls|Locking video sources / Parental controls]]
* [[Video library settings]]
* [[First time user]]
* [[UPnP]]

{{Helix updated}}

[[Category:Video library]]
[[Category:Manual]]
[[Category:Index]]

Video management

2015-05-11T22:25:30Z

Natethomas: /* Video guides */

{{mininav|[[Video library]]}}
<section begin="intro" />To use your video files with "metadata" like summaries, cast info, DVD covers, thumbnails, and more, you need to '''[[Adding videos to the library|add those video files]]''' to the [[video library]].<section end="intro" />

See '''[[Adding videos to the library]]''' for just the basic topics on adding videos.

== Preparing files ==
To use your video files with "metadata" like summaries, cast info, DVD covers, thumbnails, and more, you need to add those video files to the video library.

<section begin="prep" />There are a couple of important parts to getting things imported into your {{Kodi}} library. First, the metadata for the video file should exist someplace (the metadata are things like the title of the show, the plot description, the season and episode number if the video file happens to be an episode of a TV series, the actors, the director, cover art and episode art, etc.) The second part is naming the video files so the file gets matched up with the metadata available online.

{{Kodi}} uses plugins called scrapers to pull information from a video file and coordinate it with a source of metadata available someplace on the internet. For a TV show the scraper basically looks for the show name, season number, and episode number. The default scrapers look at TheTVDB.com (for TV shows) and TheMovieDB.org (for Movies).

If some video file is not scraping properly, the first step is to go to the website of the scraper you are using on that source and see if the video is already listed there. If you can't find an entry on one of those two sites for the video you're interested in, you can hunt for different scrapers which search other websites for metadata (and go through the same process of making sure your show is listed there, then naming the video files to match). Alternatively, you can create new entries on those sites with some basic information about your show, and then let the scrapers do their work. This is nice, because it means that other people will benefit from your work, and may contribute additional information about the show over time.
Adding info to a site like TheTVDB.org is easy, but make sure you read the site rules before you start adding.

If none of that works, you can create .nfo files for each video by hand so that {{Kodi}} will bypass the normal looking online for information about your show. This is the least attractive option, though. It's a lot of work, and it doesn't benefit anyone else the way creating entries on the metadata sites does.<section end="prep" />

=== Naming files ===
{{main|Naming video files}}
{{#lst:Naming video files|intro}}

* [[Naming video files/Movies]]
* [[Naming video files/TV shows]]
* [[Naming video files/Music videos]]

=== NFO files ===
{{Main|NFO files}}
{{#lst:NFO files|intro}}

== Adding media sources ==
{{main|Adding video sources}}
{{#lst:Adding video sources|intro}}

=== Media sources ===
{{Main|Media sources}}
{{#lst:Media sources|intro}}

== Media stubs ==
{{Main|Media stubs}}
{{#lst:Media stubs|intro}}
{{-}}

== Internet streams ==
{{Main|Internet streams}}
{{#lst:Internet streams|intro}}

== Setting content and scanning ==
{{main|Set content and scan}}
{{#lst:Set content and scan|intro}}

=== Incorrect and missing videos ===
{{Main|Incorrect and missing videos}}
{{#lst:Incorrect and missing videos|intro}}

=== Custom video entries ===
{{Main|Custom video entries}}
{{#lst:Custom video entries|intro}}

=== Updating or removing videos ===
{{Main|Updating or removing videos}}
{{#lst:Updating or removing videos|intro}}

== Grouping media ==

=== File stacking ===
{{Main|File stacking}}
{{#lst:File stacking|intro}}

=== Movie sets ===
{{Main|Movie sets}}
{{#lst:Movie sets|intro}}

=== Video library tags ===
{{Main|Video library tags}}
{{#lst:Video library tags|intro}}

=== How to separate the library (cartoons, documentaries, anime, etc) ===
{{Main|Custom home items}}
{{#lst:Custom home items|intro}}

=== Playlists ===
{{Main|Playlists}}
* {{big|'''[[Basic playlists]] -'''}} {{#lst:Basic playlists|intro}}

* {{big|'''[[Smart playlists]] -'''}} {{#lst:Smart playlists|intro}}

=== Linking movies to TV shows ===
{{#lst:Linking movies to TV shows|movie TV link}}
{{-}}

=== Video nodes ===
{{Main|Video nodes}}
{{#lst:Video nodes|intro}}
{{-}}

== Alternative guides ==
<section begin="Alternative guides" />
* [http://lifehacker.com/5900626/create-a-kickass-seamless-play+everything-media-center-the-complete-guide Lifehacker.com - Create a Kickass, Seamless, Play-Everything Media Center: The Complete Guide]
* [http://tbueter.com/?page_id=324 The Frodo Guide] by Henry Ford
* [http://xbmc.us/njbetzen/2012/08/01/beginner-tip-how-to-add-videos-to-xbmc-frodopre-frodo-from-a-network-share/ Beginner Tip: How to add videos to Kodi Frodo/pre-Frodo from a network share] by Nathan Betzen
* [http://www.makeuseof.com/pages/xbmc-full-html Makeuseof.com - How to set up your Kodi Media Center]
* [http://youresuchageek.blogspot.fr/2012/06/xbmc-install-and-config-howto-for-linux.html Kodi Install and Config] HOW-TO for Linux Its for xvba, however apart from drivers the rest is a '''MUST''' read for Linux novices.

=== Video guides ===

{{youtube|UBGKcLu7aGk}} {{youtube|EkWYxqoOF3c}} {{youtube|ueqwMbdMVHU}}
<section end="Alternative guides" />

== See also ==
* [[Import-export library]]
* [[Parental controls|Locking video sources / Parental controls]]
* [[Video library settings]]
* [[First time user]]
* [[UPnP]]

{{Helix updated}}

[[Category:Video library]]
[[Category:Manual]]
[[Category:Index]]

Official:Visual Identity Guidelines

2015-04-17T18:51:47Z

Natethomas:

{{mininav|[[XBMC Foundation]]|[[Official:Trademark Policy index|Trademarks]]}}

== Trademarked Logo/Wordmark Usage ==

:* Our logos are to be displayed in its entirety on either a solid light or dark background (avoid mid-tone or strongly colored backgrounds).
:* The proportions and alignment of icon and text in the logo must not be changed in any way.
:* The logo and icon may be used in a monochrome version (all white, black or grey) if colour is not possible or would conflict with the background colour
:* The logo must have a space or margin on all sides at no less than the height of the logo font in every direction.
:* The logo should not be displayed in parts, with color variations, or with other elements superimposed on top of the logo.
:* The logo must either include the trademark (TM) or (®) symbol depending on the mark.
:* The logo may not be placed in such close proximity to other content that it is indistinguishable.
:* The logo may not be be made the most distinctive or prominent feature on your website, printed material, or other content.
:* The logo may not be used by individuals or organizations in any way that suggests any type of association or partnership with Team Kodi or the XBMC Foundation, or approval, sponsorship, or endorsement by Team Kodi or the XBMC Foundation (unless allowed by Team Kodi or the XBMC Foundation).
:* The logo may not be used in a way that is harmful, deceptive, obscene or otherwise objectionable to the average person.
:* The logo may not be used to, or in connection with, content that disparages us or sullies Team Kodi or the XBMC Foundation reputation

== Common Mistakes ==

:* The trademarked logos/wordmarks or any other should not be displayed in modified or displayed in ways that visually compromise the logo.
:* missing shadow, incorrect colors, incomplete logo, strongly colored background, strong patterned background
:* incorrect font face, incorrect font color, non-standard orientation and sizing of logo and text, incorrect logo/text size ratio and position

[[Category:Trademark Policy]]

Add-on:Rooster Teeth

2015-04-08T23:01:13Z

Natethomas: added demo video

{{Addon
|Name=Rooster Teeth
|provider-name=Divingmule, Skipmode A1
|ID=plugin.video.roosterteeth
|latest-version=0.1.1
|extension point=xbmc.python.pluginsource
|provides=video
|Summary=Videos from RoosterTeeth.com and AchievementHunter.com
|Description=Comedy and gaming shows from Rooster Teeth and Achievement Hunter, including the popular "Red vs Blue" series.

|Platform=all
|Language=en
|License=GNU GENERAL PUBLIC LICENSE. Version 3, June 2007
|Forum=http://forum.kodi.tv/showthread.php?tid=177932
|Website=http://roosterteeth.com
|Source=git://github.com/skipmodea1/plugin.video.roosterteeth
|Email=

|broken=
|icon url=http://mirrors.kodi.tv/addons/gotham/plugin.video.roosterteeth/icon.png}}

==Demo video==
{{youtube|uPv6d0qZBG8}}

[[Category:Frodo add-on repository]]
[[Category:Gotham add-on repository]]

Add-on:Rooster Teeth

2015-04-08T22:54:52Z

Natethomas:

{{Addon
|Name=Rooster Teeth
|provider-name=Divingmule, Skipmode A1
|ID=plugin.video.roosterteeth
|latest-version=0.1.1
|extension point=xbmc.python.pluginsource
|provides=video
|Summary=Videos from RoosterTeeth.com and AchievementHunter.com
|Description=Comedy and gaming shows from Rooster Teeth and Achievement Hunter, including the popular "Red vs Blue" series.

|Platform=all
|Language=en
|License=GNU GENERAL PUBLIC LICENSE. Version 3, June 2007
|Forum=http://forum.kodi.tv/showthread.php?tid=177932
|Website=http://roosterteeth.com
|Source=git://github.com/skipmodea1/plugin.video.roosterteeth
|Email=

|broken=
|icon url=http://mirrors.kodi.tv/addons/gotham/plugin.video.roosterteeth/icon.png}}

[[Category:Frodo add-on repository]]
[[Category:Gotham add-on repository]]

Kodi Foundation

2015-03-27T20:31:34Z

Natethomas: /* Board of Directors */ updated BOD

{{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.
* [[/Member list]]

== Board of Directors ==
{| class="infobox"
|-
|
<section begin=Foundation members />
* '''Nathan Betzen (natethomas)''' - Board member (President) - ''Term: 11/2013 - 11/2015''
* '''Martijn Kaijser (Martijn)''' - Board member (CFO) - ''Term: 11/2013 - 11/2015''
* '''Sascha Montellese (Montellese)''' - Board member (Secretary) - ''Term: 11/2013 - 11/2015''
* '''Matthias Kortstiege (mkortstiege)''' - Board member - ''Term: 11/2014 - 11/2016''
* '''Rainer Hochecker (FernetMenta)''' - Board member - ''Term: 11/2014 - 11/2016''
<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 minutes ===
* [[/Board minutes/2012-11-4]]

== 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/2013|2013]]
* [[/Elections/2012|2012]]

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

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

== Financial information ==

=== Financial status ===

* Income and expenses - https://docs.google.com/spreadsheet/ccc?key=0AtlJ3dnHcw46dHpmeXlIV0hGaC13Z3I3b25hZWhWRGc#gid=8

=== Account details ===

'''Europe bank account'''

* Bank: ING Netherlands
* Beneficiary: XBMC Foundation
* IBAN account: NL39 INGB 0006 6296 56
* BIC: INGBNL2A

'''Unites States account'''

* Bank:
* Beneficiary: XBMC 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/

== See also ==

=== Similar page names ===
{{#lst:Foundation|similar pages}}

[[Category:Team Kodi]]
[[Category:Team Kodi specific notes]]
[[Category:XBMC Foundation|*]]

Add-on:HDHomeRun

2015-03-20T18:55:14Z

Natethomas: /* Controls */

{{Addon
|Name=HDHomeRun Live TV
|provider-name=SiliconDust
|ID=script.hdhomerun.view
|latest-version=2015.3.19
|extension point=xbmc.python.script
|provides=video
|Summary=Browse lineup and watch streams from your HDHomeRun devices
|Description=HDHomeRun on Kodi the easy way. Automatically finds all the compatible HDHomeRun devices on your network, collects available channels, and starts showing TV. Pressing select or right brings up the episode guide, where you can see what's on, and what's coming next.
|Platform=all
|Language=
|License=GNU GENERAL PUBLIC LICENSE. Version 2, June 1991
|Forum=https://www.silicondust.com/forum/viewforum.php?f=87
|Website=https://www.hdhomerun.com
|Source=
|Email=
|broken=
|icon url=http://mirrors.kodi.tv/addons/gotham/script.hdhomerun.view/icon.png}}

== What is HDHomeRun ==
{{main|HDHomeRun}}
{{intro|HDHomeRun}}
=== Supported models ===
{{note|1=Be sure to install the latest beta firmware for your HDHomeRun unit to enable all of the features of the add-on: https://www.silicondust.com/forum/viewtopic.php?t=2484}}
* HDHomeRun PRIME
* HDHomeRun CONNECT
* HDHomeRun EXTEND

== Controls ==
'''Channel changing''' - Using up/down arrow keys and enter/select will allow the user to select which channel they want and then go to that channel.

'''Search''' - a search box can be triggered by pressing {{button|MENU}} on a remote or {{keypress|C}} on a keyboard. This will bring up the on-screen-keyboard and allow the user to search both channel names and program descriptions. The search results show up as filtered channel listings.

'''Direct channel input''' - Pressing numbers on a remote or keyboard + enter/select will allow the user to go directly to that channel number.

'''Tablet Controls''' - Because this add-on doesn't include the traditional GUI, when using with a tablet, exiting the add-on requires a two-finger swipe to the left.

== Video demo ==
[http://lon.tv LON.TV] review of the HDHomeRun Live TV Kodi add-on<br />
{{youtube|-MY-Kk76x9w}}

== Settings ==
The settings for the HDHomeRun add-on can be accessed by:

: {{highlight|bordered=yes|highlighting the add-on in Kodi -> bringing up the [[context menu]] ({{button|MENU}} on a remote and {{keypress|C}} on a keyboard) -> and selecting '''Add-on settings'''.}}

Be sure to select '''Okay''' when you are done changing settings in order to save those changes.

[[File:HDHomeRun add-on settings.png|500px|right]]

; Confirm exit
: ''on by default''
: Disables the prompt asking if you really want to edit when escaping/existing out of the add-on.

; Stop video on exit
: ''on by default''
: Prevents the current channel from continuing playback after existing the add-on.

; Enable enhancements for touch devices
: ''off by default''
: Currently allows 'flinging' of the guide when swiping up and down by using a different display method. Uses more CPU when enabled.

; Guide auto-hide delay seconds (0 = never hide)
: ''0/never by default''
: Allows you to hide the channel info and guide when the guide is manually displayed by pressing select or left.

; Transcoding profile
: ''HDHomeRun EXTEND only''
: Selects what transcoding profile to use for the video feeds.

; Show DRM channels
: ''HDHomeRun PRIME only''
: Shows channels in the guide that Kodi cannot play due to restrictions imposed by your cable provider.

; Enable debug logging
: Enables extra data that is saved to Kodi's [[debug log]]. This is used for troubleshooting and bug reporting for the add-on.

{{-}}

== FAQ ==
=== Do I need to provide EPG data? ===
:Nope. SiliconDust pays for providing the EPG (electronic programming guide), channel icons, and other data from FYI Television. [http://www.silicondust.com/about/in-the-news/] This data is downloaded directly onto your HDHomeRun unit and the add-on loads that data from there.

=== How do I enable deinterlacing? ===
:Because the HDHomeRun Live TV add-on blocks the normal on-screen-display video controls, enabling deinterlacing is a little tricky to get to at this time. This is currently being investigated by the add-on's developer.
:A work-around for the time being is to enable automatic detection for if videos need deinterlacing or not, and setting that as the default for all videos. For most Kodi hardware this setting should be safe, but might not always enable deinterlacing in certain situations. This can be reverted later using these same instructions:
:# Play a normal video file, outside of the HDHomeRun Live TV add-on.
:# Bring up the '''[[Video playback#On screen display (OSD)|on-screen-display controls]]''' by pressing select/enter.
:# Navigate to the '''[[Video playback#OSD video settings|video settings button]]'''
:# Change the '''Deinterlace video''' option to '''Auto'''
:# Scroll down in the video settings window and select '''Save as default for all videos'''
:# You can now stop playing the video and use the HDHomeRun Live TV add-on

=== Can the add-on record video? ===
:Currently, no. The add-on is just for viewing live TV.

== Links and further reading ==
* SiliconDust press release - http://blog.fyitelevision.com/2015/03/hdhomerun-kodi-add-on-brings-gorgeous.html
* SiliconDust announcement post - https://www.silicondust.com/forum/viewtopic.php?f=87&t=18949
* SD support forum for the add-on - https://www.silicondust.com/forum/viewforum.php?f=87
* Kodi.tv blog announcement post - http://kodi.tv/addon-spotlight-hdhomerun-live-tv/

[[Category:Gotham add-on repository]]

Archive:Google Summer of Code/2015

2015-03-02T19:47:19Z

Natethomas: fixed opening paragraph to point to 2015 instead of 2014 forum

{{mininav| [[Google Summer of Code]] }}
[[File:GSOC_2015_logo-blog.jpg‎|left|200px]]Welcome to the Kodi [http://www.google-melange.com/gsoc/homepage/google/gsoc2015 Google Summer of Code] ideas page. 

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

From '''16 March''' to '''27 March''', any interested students may apply at the [http://www.google-melange.com/gsoc/homepage/google/gsoc2015 GSOC home page] to work with Kodi. After that, we’ll notify applicants whether we get to work with each other according to the [http://www.google-melange.com/gsoc/events/google/gsoc2015 GSOC schedule].
{{-}}
{| width="100%"
| align=left |
__TOC__
| align=right |
{{YouTube|i2vWBqqqlHg}}
|}
== 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 [[Google Summer of Code 2008|2008]], [[Google Summer of Code 2012|2012]] and [[Google Summer of Code 2013|2013]], and had team members involved in GSoC for other projects during 2011.

If Kodi is selected as a mentoring organization for 2015, 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.

== 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.

=== 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 ==

=== Server Improvement ===

====Transcoding====
*Transcoding is already supported in a number of other open source projects and FFMPEG. Additionally, limited audio transcoding is available in Kodi right now. However to fully support the wide range of devices out there, not to mention better support file transfers on low memory devices, Kodi needs to fully support audio and video transcoding.

====UPnP Improvements including File Transfers====
*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

=== Better Profile Support ===
Profile support inside Kodi remains extremely hacked together. Improving profile projects would likely be broken down into smaller chunks to make each chunk truly achieveable in a summer.

===Web Browser in Kodi===
Initial work on Web Browser implementation already exists, but much is left to do on this project, and many developers are excited to help act as a mentor for this particular project.

===Gaming in Kodi ===
====Retroplayer====
*Developer Garbear has broken down the Retroplayer project into manageable pieces including input, core, game addons, peripheral addons, netplay, a game library implementation, and shaders to do things like emulate a CRT monitor. Any one of these pieces could make an excellent summer project depending on your familiarity in the area.
====NVIDIA Gamestream in Kodi====
*Limelight is a GPL licensed project that runs on a variety of platforms and is primarily written in java that should be relatively easily integrated into the Kodi file system, allowing for any device running Kodi with access to a controller or a keyboard and mouse to launch and play any game or application being served on a local PC with a relatively recent NVIDIA graphics card.

=== 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 '''[http://forum.kodi.tv/forumdisplay.php?fid=220 Kodi GSOC 2015 forum]'''. They can be as big or as small as you feel you can comfortably accomplish between '''25 May''' and '''21 August'''. 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 '''[http://forum.kodi.tv/forumdisplay.php?fid=220 here]''' and paste the text.
# Fill out everything using your specific proposal.

[[Category:Google Summer of Code]]

Archive:Google Summer of Code/2015

2015-02-20T10:05:47Z

Natethomas: /* Team-Kodi proposal ideas up for discussion */

{{mininav| [[Google Summer of Code]] }}
[[File:GSOC_2015_logo-blog.jpg‎|left|200px]]Welcome to the Kodi [http://www.google-melange.com/gsoc/homepage/google/gsoc2015 Google Summer of Code] ideas page. 

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

From '''16 March''' to '''27 March''', any interested students may apply at the [http://www.google-melange.com/gsoc/homepage/google/gsoc2015 GSOC home page] to work with Kodi. After that, we’ll notify applicants whether we get to work with each other according to the [http://www.google-melange.com/gsoc/events/google/gsoc2015 GSOC schedule].
{{-}}
{| width="100%"
| align=left |
__TOC__
| align=right |
{{YouTube|i2vWBqqqlHg}}
|}
== 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 50 software developers have contributed to Kodi, and 100-plus translators have worked to expand its reach, making it available in more than 40 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 [[Google Summer of Code 2008|2008]], [[Google Summer of Code 2012|2012]] and [[Google Summer of Code 2013|2013]], and had team members involved in GSoC for other projects during 2011.

If Kodi is selected as a mentoring organization for 2015, 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.

== 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.

=== 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 ==

=== Server Improvement ===

====Transcoding====
*Transcoding is already supported in a number of other open source projects and FFMPEG. Additionally, limited audio transcoding is available in Kodi right now. However to fully support the wide range of devices out there, not to mention better support file transfers on low memory devices, Kodi needs to fully support audio and video transcoding.

====UPnP Improvements including File Transfers====
*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

=== Better Profile Support ===
Profile support inside Kodi remains extremely hacked together. Improving profile projects would likely be broken down into smaller chunks to make each chunk truly achieveable in a summer.

===Web Browser in Kodi===
Initial work on Web Browser implementation already exists, but much is left to do on this project, and many developers are excited to help act as a mentor for this particular project.

===Gaming in Kodi ===
====Retroplayer====
*Developer Garbear has broken down the Retroplayer project into manageable pieces including input, core, game addons, peripheral addons, netplay, a game library implementation, and shaders to do things like emulate a CRT monitor. Any one of these pieces could make an excellent summer project depending on your familiarity in the area.
====NVIDIA Gamestream in Kodi====
*Limelight is a GPL licensed project that runs on a variety of platforms and is primarily written in java that should be relatively easily integrated into the Kodi file system, allowing for any device running Kodi with access to a controller or a keyboard and mouse to launch and play any game or application being served on a local PC with a relatively recent NVIDIA graphics card.

=== 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 '''[http://forum.kodi.tv/forumdisplay.php?fid=220 Kodi GSOC 2015 forum]'''. They can be as big or as small as you feel you can comfortably accomplish between '''25 May''' and '''21 August'''. 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 '''[http://forum.kodi.tv/forumdisplay.php?fid=220 here]''' and paste the text.
# Fill out everything using your specific proposal.

[[Category:Google Summer of Code]]

MediaWiki:Common.css

2015-02-20T10:05:20Z

Natethomas: revert

*/

/* <pre><nowiki> */

/* Edit window toolbar */
#toolbar {
height: 22px;
margin-bottom: 6px;
}

/* Highlight clicked reference in blue to help navigation */
ol.references li:target,
sup.reference:target,
span.citation:target {
background-color: #DEF;
}

/* Ensure refs in table headers and the like aren't bold or italic */
sup.reference {
font-weight: normal;
font-style: normal;
}

/* Allow hidden ref errors to be shown by user CSS */
span.brokenref {
display: none;
}

/* Styling for citations (CSS3). Breaks long urls, etc., rather than overflowing box */
.citation {
word-wrap: break-word;
}

/* For linked citation numbers and document IDs, where
the number need not be shown on a screen or a handheld,
but should be included in the printed version */
@media screen, handheld {
.citation *.printonly {
display: none;
}
}

/* wikitable/prettytable class for skinning normal tables */
table.wikitable,
table.prettytable {
margin: 1em 1em 1em 0;
background: #f9f9f9;
border: 1px #aaa solid;
border-collapse: collapse;
}
.wikitable th, .wikitable td,
.prettytable th, .prettytable td {
border: 1px #aaa solid;
padding: 0.2em;
}
.wikitable th,
.prettytable th {
background: lightgrey;
text-align: center;
}
.wikitable caption,
.prettytable caption {
font-weight: bold;
}

/* Style for [[Template:Flowlist]] that Lets lists flow around floating objecs */
.flowlist ul {
overflow-x: hidden;
margin-left: 0em;
padding-left: 1.6em;
}
.flowlist ol {
overflow-x: hidden;
margin-left: 0em;
padding-left: 3.2em;
}
.flowlist dl {
overflow-x: hidden;
}

/* Unbulleted lists */
.plainlist ul {
line-height: inherit;
list-style: none none;
margin: 0;
}
.plainlist ul li {
margin-bottom: 0;
}

/* Default style for navigation boxes */
.navbox { /* Navbox container style */
border: 1px solid #aaa;
width: 100%;
margin: auto;
clear: both;
font-size: 88%;
text-align: center;
padding: 1px;
}
.navbox-inner,
.navbox-subgroup {
width: 100%;
}
.navbox-group,
.navbox-title,
.navbox-abovebelow {
padding: 0.25em 1em; /* Title, group and above/below styles */
line-height: 1.5em;
text-align: center;
}
th.navbox-group { /* Group style */
white-space: nowrap;
/* @noflip */
text-align: right;
}
.navbox,
.navbox-subgroup {
background: #fdfdfd; /* Background color */
}
.navbox-list {
line-height: 1.8em;
border-color: #fdfdfd; /* Must match background color */
}
.navbox th,
.navbox-title {
background: #ccccff; /* Level 1 color */
}
.navbox-abovebelow,
th.navbox-group,
.navbox-subgroup .navbox-title {
background: #ddddff; /* Level 2 color */
}
.navbox-subgroup .navbox-group,
.navbox-subgroup .navbox-abovebelow {
background: #e6e6ff; /* Level 3 color */
}
.navbox-even {
background: #f7f7f7; /* Even row striping */
}
.navbox-odd {
background: transparent; /* Odd row striping */
}
table.navbox + table.navbox { /* Single pixel border between adjacent navboxes */
margin-top: -1px; /* (doesn't work for IE6, but that's okay) */
}
.navbox .hlist td dl,
.navbox .hlist td ol,
.navbox .hlist td ul,
.navbox td.hlist dl,
.navbox td.hlist ol,
.navbox td.hlist ul {
padding: 0.125em 0; /* Adjust hlist padding in navboxes */
}
ol + table.navbox,
ul + table.navbox {
margin-top: 0.5em; /* Prevent lists from clinging to navboxes */
}

/* Default styling for Navbar template */
.navbar {
display: inline;
font-size: 88%;
font-weight: normal;
}
.navbar ul {
display: inline;
white-space: nowrap;
}
.navbar li {
word-spacing: -0.125em;
}
.navbar.mini li span {
font-variant: small-caps;
}
/* Navbar styling when nested in infobox and navbox */
.infobox .navbar {
font-size: 100%;
}
.navbox .navbar {
display: block;
font-size: 100%;
}
.navbox-title .navbar {
/* @noflip */
float: left;
/* @noflip */
text-align: left;
/* @noflip */
margin-right: 0.5em;
width: 6em;
}

/* 'show'/'hide' buttons created dynamically by the CollapsibleTables javascript
in [[MediaWiki:Common.js]] are styled here so they can be customised. */
.collapseButton {
/* @noflip */
float: right;
font-weight: normal;
/* @noflip */
margin-left: 0.5em;
/* @noflip */
text-align: right;
width: auto;
}
/* In navboxes, the show/hide button balances the v·d·e links
from [[Template:Navbar]], so they need to be the same width. */
.navbox .collapseButton {
width: 6em;
}

/* Styling for JQuery makeCollapsible, matching that of collapseButton */
.mw-collapsible-toggle {
font-weight: normal;
/* @noflip */
text-align: right;
}
.navbox .mw-collapsible-toggle {
width: 6em;
}

/* Infobox template style */
.infobox {
border: 1px solid #aaa;
background-color: #f9f9f9;
color: black;
/* @noflip */
margin: 0.5em 0 0.5em 1em;
padding: 0.2em;
/* @noflip */
float: right;
/* @noflip */
clear: right;
/* @noflip */
}
.infobox caption {
font-size: larger;
}
.infobox td,
.infobox th {
vertical-align: top;
}
.infobox.bordered {
border-collapse: collapse;
}
.infobox.bordered td,
.infobox.bordered th {
border: 1px solid #aaa;
}
.infobox.bordered .borderless td,
.infobox.bordered .borderless th {
border: 0;
}

.infobox.sisterproject {
width: 20em;
font-size: 90%;
}

.infobox.standard-talk {
border: 1px solid #c0c090;
background-color: #f8eaba;
}
.infobox.standard-talk.bordered td,
.infobox.standard-talk.bordered th {
border: 1px solid #c0c090;
}

/* styles for bordered infobox with merged rows */
.infobox.bordered .mergedtoprow td,
.infobox.bordered .mergedtoprow th {
border: 0;
border-top: 1px solid #aaa;
/* @noflip */
border-right: 1px solid #aaa;
}

.infobox.bordered .mergedrow td,
.infobox.bordered .mergedrow th {
border: 0;
/* @noflip */
border-right: 1px solid #aaa;
}

/* Styles for geography infoboxes, eg countries,
country subdivisions, cities, etc. */
.infobox.geography {
/* @noflip */
text-align: left;
border-collapse: collapse;
line-height: 1.2em;
font-size: 90%;
}

.infobox.geography td,
.infobox.geography th {
border-top: 1px solid #aaa;
padding: 0.4em 0.6em 0.4em 0.6em;
}
.infobox.geography .mergedtoprow td,
.infobox.geography .mergedtoprow th {
border-top: 1px solid #aaa;
padding: 0.4em 0.6em 0.2em 0.6em;
}

.infobox.geography .mergedrow td,
.infobox.geography .mergedrow th {
border: 0;
padding: 0 0.6em 0.2em 0.6em;
}

.infobox.geography .mergedbottomrow td,
.infobox.geography .mergedbottomrow th {
border-top: 0;
border-bottom: 1px solid #aaa;
padding: 0 0.6em 0.4em 0.6em;
}

.infobox.geography .maptable td,
.infobox.geography .maptable th {
border: 0;
padding: 0;
}

/* Makes redirects appear in italics in categories and on [[Special:Allpages]] */
.redirect-in-category, .allpagesredirect {
font-style: italic;
}

/* Normal font styling for table row headers with scope="row" tag */
.wikitable.plainrowheaders th[scope=row] {
font-weight: normal;
/* @noflip */
text-align: left;
}

/* Lists in data cells are always left-aligned */
.wikitable td ul,
.wikitable td ol,
.wikitable td dl {
/* @noflip */
text-align: left;
}

/* Change the external link icon to an Adobe icon for all PDF files
in browsers that support these CSS selectors, like Mozilla and Opera */
div#content a[href$=".pdf"].external,
div#content a[href*=".pdf?"].external,
div#content a[href*=".pdf#"].external,
div#content a[href$=".PDF"].external,
div#content a[href*=".PDF?"].external,
div#content a[href*=".PDF#"].external,
div#mw_content a[href$=".pdf"].external,
div#mw_content a[href*=".pdf?"].external,
div#mw_content a[href*=".pdf#"].external,
div#mw_content a[href$=".PDF"].external,
div#mw_content a[href*=".PDF?"].external,
div#mw_content a[href*=".PDF#"].external {
background: url("//upload.wikimedia.org/wikipedia/commons/2/23/Icons-mini-file_acrobat.gif") no-repeat right;
/* @noflip */
padding-right: 18px;
}

/* Change the external link icon to an Adobe icon anywhere the PDFlink class
is used (notably Template:PDFlink). This works in IE, unlike the above. */
div#content span.PDFlink a,
div#mw_content span.PDFlink a {
background: url("//upload.wikimedia.org/wikipedia/commons/2/23/Icons-mini-file_acrobat.gif") no-repeat right;
/* @noflip */
padding-right: 18px;
}

/* Content in columns with CSS instead of tables [[Template:Columns]] */
div.columns-2 div.column {
/* @noflip */
float: left;
width: 50%;
min-width: 300px;
}
div.columns-3 div.column {
/* @noflip */
float: left;
width: 33.3%;
min-width: 200px;
}
div.columns-4 div.column {
/* @noflip */
float: left;
width: 25%;
min-width: 150px;
}
div.columns-5 div.column {
/* @noflip */
float: left;
width: 20%;
min-width: 120px;
}

/* Messagebox templates */
.messagebox {
border: 1px solid #aaa;
background-color: #f9f9f9;
width: 80%;
margin: 0 auto 1em auto;
padding: .2em;
}
.messagebox.merge {
border: 1px solid #c0b8cc;
background-color: #f0e5ff;
text-align: center;
}
.messagebox.cleanup {
border: 1px solid #9f9fff;
background-color: #efefff;
text-align: center;
}
.messagebox.standard-talk {
border: 1px solid #c0c090;
background-color: #f8eaba;
margin: 4px auto;
}
/* For old WikiProject banners inside banner shells. */
.mbox-inside .standard-talk,
.messagebox.nested-talk {
border: 1px solid #c0c090;
background-color: #f8eaba;
width: 100%;
margin: 2px 0;
padding: 2px;
}
.messagebox.small {
width: 238px;
font-size: 85%;
/* @noflip */
float: right;
clear: both;
/* @noflip */
margin: 0 0 1em 1em;
line-height: 1.25em;
}
.messagebox.small-talk {
width: 238px;
font-size: 85%;
/* @noflip */
float: right;
clear: both;
/* @noflip */
margin: 0 0 1em 1em;
line-height: 1.25em;
background: #F8EABA;
}

/* Cell sizes for ambox/tmbox/imbox/cmbox/ombox/fmbox/dmbox message boxes */
th.mbox-text, td.mbox-text { /* The message body cell(s) */
border: none;
/* @noflip */
padding: 0.25em 0.9em; /* 0.9em left/right */
width: 100%; /* Make all mboxes the same width regardless of text length */
}
td.mbox-image { /* The left image cell */
border: none;
/* @noflip */
padding: 2px 0 2px 0.9em; /* 0.9em left, 0px right */
text-align: center;
}
td.mbox-imageright { /* The right image cell */
border: none;
/* @noflip */
padding: 2px 0.9em 2px 0; /* 0px left, 0.9em right */
text-align: center;
}
td.mbox-empty-cell { /* An empty narrow cell */
border: none;
padding: 0px;
width: 1px;
}

/* Article message box styles */
table.ambox {
margin: 0px 10%; /* 10% = Will not overlap with other elements */
border: 1px solid #aaa;
/* @noflip */
border-left: 10px solid #1e90ff; /* Default "notice" blue */
background: #fbfbfb;
}
table.ambox + table.ambox { /* Single border between stacked boxes. */
margin-top: -1px;
}
.ambox th.mbox-text,
.ambox td.mbox-text { /* The message body cell(s) */
padding: 0.25em 0.5em; /* 0.5em left/right */
}
.ambox td.mbox-image { /* The left image cell */
/* @noflip */
padding: 2px 0 2px 0.5em; /* 0.5em left, 0px right */
}
.ambox td.mbox-imageright { /* The right image cell */
/* @noflip */
padding: 2px 0.5em 2px 0; /* 0px left, 0.5em right */
}

table.ambox-notice {
/* @noflip */
border-left: 10px solid #1e90ff; /* Blue */
}
table.ambox-speedy {
/* @noflip */
border-left: 10px solid #b22222; /* Red */
background: #fee; /* Pink */
}
table.ambox-delete {
/* @noflip */
border-left: 10px solid #b22222; /* Red */
}
table.ambox-content {
/* @noflip */
border-left: 10px solid #f28500; /* Orange */
}
table.ambox-style {
/* @noflip */
border-left: 10px solid #f4c430; /* Yellow */
}
table.ambox-move {
/* @noflip */
border-left: 10px solid #9932cc; /* Purple */
}
table.ambox-protection {
/* @noflip */
border-left: 10px solid #bba; /* Gray-gold */
}

/* Image message box styles */
table.imbox {
margin: 4px 10%;
border-collapse: collapse;
border: 3px solid #1e90ff; /* Default "notice" blue */
background: #fbfbfb;
}
.imbox .mbox-text .imbox { /* For imboxes inside imbox-text cells. */
margin: 0 -0.5em; /* 0.9 - 0.5 = 0.4em left/right. */
display: block; /* Fix for webkit to force 100% width. */
}
.mbox-inside .imbox { /* For imboxes inside other templates. */
margin: 4px;
}

table.imbox-notice {
border: 3px solid #1e90ff; /* Blue */
}
table.imbox-speedy {
border: 3px solid #b22222; /* Red */
background: #fee; /* Pink */
}
table.imbox-delete {
border: 3px solid #b22222; /* Red */
}
table.imbox-content {
border: 3px solid #f28500; /* Orange */
}
table.imbox-style {
border: 3px solid #f4c430; /* Yellow */
}
table.imbox-move {
border: 3px solid #9932cc; /* Purple */
}
table.imbox-protection {
border: 3px solid #bba; /* Gray-gold */
}
table.imbox-license {
border: 3px solid #88a; /* Dark gray */
background: #f7f8ff; /* Light gray */
}
table.imbox-featured {
border: 3px solid #cba135; /* Brown-gold */
}

/* Category message box styles */
table.cmbox {
margin: 3px 10%;
border-collapse: collapse;
border: 1px solid #aaa;
background: #DFE8FF; /* Default "notice" blue */
}

table.cmbox-notice {
background: #D8E8FF; /* Blue */
}
table.cmbox-speedy {
margin-top: 4px;
margin-bottom: 4px;
border: 4px solid #b22222; /* Red */
background: #FFDBDB; /* Pink */
}
table.cmbox-delete {
background: #FFDBDB; /* Red */
}
table.cmbox-content {
background: #FFE7CE; /* Orange */
}
table.cmbox-style {
background: #FFF9DB; /* Yellow */
}
table.cmbox-move {
background: #E4D8FF; /* Purple */
}
table.cmbox-protection {
background: #EFEFE1; /* Gray-gold */
}

/* Other pages message box styles */
table.ombox {
margin: 4px 10%;
border-collapse: collapse;
border: 1px solid #aaa; /* Default "notice" gray */
background: #f9f9f9;
}

table.ombox-notice {
border: 1px solid #aaa; /* Gray */
}
table.ombox-speedy {
border: 2px solid #b22222; /* Red */
background: #fee; /* Pink */
}
table.ombox-delete {
border: 2px solid #b22222; /* Red */
}
table.ombox-content {
border: 1px solid #f28500; /* Orange */
}
table.ombox-style {
border: 1px solid #f4c430; /* Yellow */
}
table.ombox-move {
border: 1px solid #9932cc; /* Purple */
}
table.ombox-protection {
border: 2px solid #bba; /* Gray-gold */
}

/* Talk page message box styles */
table.tmbox {
margin: 4px 10%;
border-collapse: collapse;
border: 1px solid #c0c090; /* Default "notice" gray-brown */
background: #f8eaba;
}
.mediawiki .mbox-inside .tmbox { /* For tmboxes inside other templates. The "mediawiki" class ensures that */
margin: 2px 0; /* this declaration overrides other styles (including mbox-small above) */
width: 100%; /* For Safari and Opera */
}
.mbox-inside .tmbox.mbox-small { /* "small" tmboxes should not be small when */
line-height: 1.5em; /* also "nested", so reset styles that are */
font-size: 100%; /* set in "mbox-small" above. */
}

table.tmbox-speedy {
border: 2px solid #b22222; /* Red */
background: #fee; /* Pink */
}
table.tmbox-delete {
border: 2px solid #b22222; /* Red */
}
table.tmbox-content {
border: 2px solid #f28500; /* Orange */
}
table.tmbox-style {
border: 2px solid #f4c430; /* Yellow */
}
table.tmbox-move {
border: 2px solid #9932cc; /* Purple */
}
table.tmbox-protection,
table.tmbox-notice {
border: 1px solid #c0c090; /* Gray-brown */
}

/* Disambig and set index box styles */
table.dmbox {
clear: both;
margin: 0.9em 1em;
border-top: 1px solid #ccc;
border-bottom: 1px solid #ccc;
background: transparent;
}

/* Footer and header message box styles */
table.fmbox {
clear: both;
margin: 0.2em 0;
width: 100%;
border: 1px solid #aaa;
background: #f9f9f9; /* Default "system" gray */
}
table.fmbox-system {
background: #f9f9f9;
}
table.fmbox-warning {
border: 1px solid #bb7070; /* Dark pink */
background: #ffdbdb; /* Pink */
}
table.fmbox-editnotice {
background: transparent;
}

/* Div based "warning" style fmbox messages. */
div.mw-warning-with-logexcerpt,
div.mw-lag-warn-high,
div.mw-cascadeprotectedwarning {
clear: both;
margin: 0.2em 0;
border: 1px solid #bb7070;
background: #ffdbdb;
padding: 0.25em 0.9em;
}
/* Div based "system" style fmbox messages. Used in
[[MediaWiki:Noarticletext]] and [[MediaWiki:Readonly lag]]. */
div.mw-lag-warn-normal,
div.noarticletext,
div.fmbox-system {
clear: both;
margin: 0.2em 0;
border: 1px solid #aaa;
background: #f9f9f9;
padding: 0.25em 0.9em;
}

/* These mbox-small classes must be placed after all other
ambox/tmbox/ombox etc classes. "body.mediawiki" is so
they override "table.ambox + table.ambox" above. */
body.mediawiki table.mbox-small { /* For the "small=yes" option. */
/* @noflip */
clear: right;
/* @noflip */
float: right;
/* @noflip */
margin: 4px 0 4px 1em;
width: 238px;
font-size: 88%;
line-height: 1.25em;
}
body.mediawiki table.mbox-small-left { /* For the "small=left" option. */
/* @noflip */
margin: 4px 1em 4px 0;
width: 238px;
border-collapse: collapse;
font-size: 88%;
line-height: 1.25em;
}

/* Style for compact ambox */
/* Hide the images */
.compact-ambox table .mbox-image,
.compact-ambox table .mbox-imageright,
.compact-ambox table .mbox-empty-cell {
display: none;
}
/* Remove borders, backgrounds, padding, etc. */
.compact-ambox table.ambox {
border: none;
border-collapse: collapse;
background: transparent;
margin: 0 0 0 1.6em !important;
padding: 0 !important;
width: auto;
display: block;
}
body.mediawiki .compact-ambox table.mbox-small-left {
font-size: 100%;
width: auto;
margin: 0;
}
/* Style the text cell as a list item and remove its padding */
.compact-ambox table .mbox-text {
padding: 0 !important;
margin: 0 !important;
}
.compact-ambox table .mbox-text-span {
display: list-item;
line-height: 1.5em;
list-style-type: square;
list-style-image: url(//bits.wikimedia.org/skins/common/images/bullet.gif);
}
.skin-vector .compact-ambox table .mbox-text-span {
list-style-type: circle;
list-style-image: url(//bits.wikimedia.org/skins/vector/images/bullet-icon.png)
}
/* Allow for hiding text in compact form */
.compact-ambox .hide-when-compact {
display: none;
}

/* Remove default styles for [[MediaWiki:Noarticletext]]. */
div.noarticletext {
border: none;
background: transparent;
padding: 0;
}

/* class hiddenStructure is defunct. See [[Wikipedia:hiddenStructure]] */
.hiddenStructure {
display: inline ! important;
color: #f00;
background-color: #0f0;
}

/* Bold save button */
#wpSave {
font-weight: bold;
}

/* Standard Navigationsleisten, aka box hiding thingy
from .de. Documentation at [[Wikipedia:NavFrame]]. */
div.NavFrame {
margin: 0;
padding: 4px;
border: 1px solid #aaa;
text-align: center;
border-collapse: collapse;
font-size: 95%;
}
div.NavFrame + div.NavFrame {
border-top-style: none;
border-top-style: hidden;
}
div.NavPic {
background-color: #fff;
margin: 0;
padding: 2px;
/* @noflip */
float: left;
}
div.NavFrame div.NavHead {
height: 1.6em;
font-weight: bold;
background-color: #ccf;
position: relative;
}
div.NavFrame p,
div.NavFrame div.NavContent,
div.NavFrame div.NavContent p {
font-size: 100%;
}
div.NavEnd {
margin: 0;
padding: 0;
line-height: 1px;
clear: both;
}
a.NavToggle {
position: absolute;
top: 0;
/* @noflip */
right: 3px;
font-weight: normal;
font-size: 90%;
}

/* Coloured watchlist numbers */
.mw-plusminus-pos { color: #006400; } /* dark green */
.mw-plusminus-neg { color: #8B0000; } /* dark red */

.rellink,
.dablink {
font-style: italic;
padding-left: 2em;
}
.rellink i,
.dablink i {
font-style: normal;
}

/* Hatnotes and disambiguation notices */
.rellink,
.dablink {
font-style: italic;
/* @noflip */
padding-left: 1.6em;
margin-bottom: 0.5em;
}
.rellink i,
.dablink i {
font-style: normal;
}

/* Style for horizontal UL lists */
.horizontal ul {
padding: 0;
margin: 0;
}
.horizontal li {
padding: 0 0.6em 0 0.4em;
display: inline;
border-right: 1px solid;
}
.horizontal li:last-child {
border-right: none;
padding-right: 0;
}

/* Allow transcluded pages to display in lists rather than a table.
Compatible in Firefox; incompatible in IE6. */
.listify td { display: list-item; }
.listify tr { display: block; }
.listify table { display: block; }

/* When <div class="nonumtoc"> is used on the table of contents,
the ToC will display without numbers */
.nonumtoc .tocnumber { display: none; }
.nonumtoc #toc ul,
.nonumtoc .toc ul {
line-height: 1.5em;
list-style: none none;
margin: .3em 0 0;
padding: 0;
}
.nonumtoc #toc ul ul,
.nonumtoc .toc ul ul {
/* @noflip */
margin: 0 0 0 2em;
}

/* Allow limiting of which header levels are shown in a TOC;
<div class="toclimit-3">, for instance, will limit to
showing ==headings== and ===headings=== but no further
(as long as there are no =headings= on the page, which
there shouldn't be according to the MoS). */
.toclimit-2 .toclevel-1 ul,
.toclimit-3 .toclevel-2 ul,
.toclimit-4 .toclevel-3 ul,
.toclimit-5 .toclevel-4 ul,
.toclimit-6 .toclevel-5 ul,
.toclimit-7 .toclevel-6 ul {
display: none;
}

/* Prevent line breaks in silly places:
1) Where desired
2) Links when we don't want them to
3) Bold "links" to the page itself
4) Ref tags with group names <ref group="Note"> --> "[Note 1]" */
.nowrap,
.nowraplinks a,
.nowraplinks .selflink,
sup.reference a {
white-space: nowrap;
}
/* But allow wrapping where desired: */
.wrap,
.wraplinks a {
white-space: normal;
}

/* For template documentation */
.template-documentation {
clear: both;
margin: 1em 0 0 0;
border: 1px solid #aaa;
background-color: #ecfcf4;
padding: 1em;
}

/* Inline divs in ImageMaps (code borrowed from de.wiki) */
.imagemap-inline div {
display: inline;
}

/* Increase the height of the image upload box */
#wpUploadDescription {
height: 13em;
}

/* Minimum thumb width */
.thumbinner {
min-width: 100px;
}

/* Makes the background of a framed image white instead of gray.
Only visible with transparent images. */
div.thumb img.thumbimage {
background-color: #fff;
}

/* The backgrounds for galleries. */
div#content .gallerybox div.thumb {
/* Light gray padding */
background-color: #F9F9F9;
}
/* Put a chequered background behind images, only visible if they have transparency.
'.filehistory a img' and '#file img:hover' are handled by MediaWiki core (as of 1.19) */
.gallerybox .thumb img {
background: #fff url(//bits.wikimedia.org/skins/common/images/Checker-16x16.png) repeat;
}
/* But not on articles, user pages, portals or with opt-out. */
.ns-0 .gallerybox .thumb img,
.ns-2 .gallerybox .thumb img,
.ns-100 .gallerybox .thumb img,
.nochecker .gallerybox .thumb img {
background: #fff;
}

/* Category tree styling. Works in conjuction with [[MediaWiki:Categorytree-expand-bullet]],
[[MediaWiki:Categorytree-collapse-bullet]] and [[MediaWiki:Categorytree-empty-bullet]]. */
#mw-subcategories ul {
list-style: none none;
margin-left: 0.25em;
}
.CategoryTreeChildren {
margin-left: 1.25em;
}

/* Prevent floating boxes from overlapping any category listings,
file histories, edit previews, and edit [Show changes] views. */
#mw-subcategories, #mw-pages, #mw-category-media,
#filehistory, #wikiPreview, #wikiDiff {
clear: both;
}

/* Disable the automatic text-size adjust of WebKit on iPhones etc.
It scales some text, and not the other. Use none, or fixed percentage instead.
Use media selector, because defining a value, overwrites platform defaults. */
@media only screen and (max-device-width: 480px) {
body {
-webkit-text-size-adjust: none;
}
}

/* Fix so <syntaxhighlight> tags and .css and .js pages get normal text size.
[[Bugzilla:26204]]. See also [[Wikipedia:Typography#The monospace 'bug']] */
div.mw-geshi div,
div.mw-geshi div pre,
span.mw-geshi,
pre.source-css,
pre.source-javascript,
pre.source-lua {
font-family: monospace, Courier !important;
}

/* For announcements */
#bodyContent .letterhead {
background-image:url('//upload.wikimedia.org/wikipedia/commons/e/e0/Tan-page-corner.png');
background-repeat:no-repeat;
padding: 2em;
background-color: #faf9f2;
}

/* Tree style lists */
.treeview ul {
padding: 0;
margin: 0;
}
.treeview li {
padding: 0;
margin: 0;
list-style-type: none;
list-style-image: none;
zoom: 1; /* BE KIND TO IE6 */;
}
.treeview li li {
background: url("//upload.wikimedia.org/wikipedia/commons/f/f2/Treeview-grey-line.png") no-repeat 0 -2981px;
/* @noflip */
padding-left: 20px;
text-indent: 0.3em;
}
.treeview li li.lastline {
background-position: 0 -5971px
}
.treeview li.emptyline > ul {
/* @noflip */
margin-left: -1px;
}
.treeview li.emptyline > ul > li:first-child {
background-position: 0 9px
}

/* Hide charinsert base for those not using the gadget */
#editpage-specialchars {
display: none;
}

/* work-around for [[bugzilla:23965]] (Kaltura advertisement) */
.k-player .k-attribution {
visibility: hidden;
}

/* Unicode font families, for [[Template:Unicode]] */
.UnicodeAnimal { font-family: "Apple Color Emoji", Symbola, "Segoe UI Symbol", Brampton, "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodeAstro { font-family: Symbola, Quivira, "Segoe UI Symbol", FreeSerif, Brampton, "Apple Color Emoji", FreeMono, "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodeChem { font-family: Quivira, Symbola, "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodeCommunication { font-family: Symbola, "Segoe UI Symbol", "Apple Color Emoji", Quivira, Brampton, FreeSerif, "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodeDentistry { font-family: "Segoe UI Symbol", Quivira, FreeMono, Symbola, "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodeEducation { font-family: "Segoe UI Symbol", Symbola, "Apple Color Emoji", Brampton, "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodeEmoticon { font-family: "Apple Color Emoji", "Segoe UI Symbol", Symbola, Brampton, FreeMono, "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodeEnclosed { font-family: Quivira, Brampton, "Apple Color Emoji", "Segoe UI Symbol", FreeSans, FreeSerif, FreeMono, "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodeEvent { font-family: "Apple Color Emoji", "Segoe UI Symbol", Symbola, Brampton, "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodeFood { font-family: "Apple Color Emoji", Symbola, "Segoe UI Symbol", Brampton, "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodeGame { font-family: Symbola, Quivira, FreeSerif, Brampton, "Segoe UI Symbol", "Apple Color Emoji", "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodeMap { font-family: Symbola, "Apple Color Emoji", "Segoe UI Symbol", Quivira, Brampton, "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodeMedicine { font-family: "Segoe UI Symbol", Quivira, Symbola, "Apple Color Emoji", Brampton, FreeSerif, "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodeMoney { font-family: Symbola, Quivira, FreeSerif, FreeSans, FreeMono, "Segoe UI Symbol", "Apple Color Emoji", Brampton, "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodeMusic { font-family: Symbola, FreeSerif, Quivira, "Segoe UI Symbol", Brampton, "Apple Color Emoji", "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodePerson { font-family: "Apple Color Emoji", Symbola, "Segoe UI Symbol", Quivira, Brampton, "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodePicto { font-family: Symbola, "Segoe UI Symbol", FreeSerif, Quivira, Brampton, "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodePlant { font-family: Symbola, "Apple Color Emoji", "Segoe UI Symbol", Brampton, "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodePoliticsReligion { font-family: Symbola, "Segoe UI Symbol", FreeSerif, Quivira, Brampton, FreeMono, "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodeRegion { font-family: "Apple Color Emoji", Brampton, "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodeSport { font-family: Symbola, "Apple Color Emoji", "Segoe UI Symbol", "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodeTechnology { font-family: Symbola, "Segoe UI Symbol", FreeMono, FreeSerif, Quivira, FreeSans, Brampton, "Apple Color Emoji", "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodeTime { font-family: Quivira, Symbola, "Apple Color Emoji", Brampton, "Segoe UI Symbol", "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodeUI { font-family: Symbola, Quivira, "Segoe UI Symbol", "Apple Color Emoji", FreeSerif, FreeMono, Brampton, "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodeWarning { font-family: Symbola, "Segoe UI Symbol", Quivira, "Apple Color Emoji", Brampton, FreeSerif, "Arial Unicode MS", "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodeWeather { font-family: Symbola, Quivira, "Segoe UI Symbol", FreeSerif, "Apple Color Emoji", Brampton, "Arial Unicode MS", "Lucida Sans Unicode"; }

/* Dynamic menus */
.dmenu { width: 180px }

.dmenu, .dmenu ul { /* all lists */
padding: 0;
margin: 0;
list-style: none;
}
.dmenu .selflink { font-weight: normal; }

.dmenu li { /* all list items */
position: relative;
float: left;
width: 172px;
padding: 4px;
z-index: 100;
}

.dmenu li,
.dmenu li.even a,
.dmenu li.odd a,
.dmenu li li,
.dmenu li li a,
.dmenu li li li,
.dmenu li li li a {
color : black;
}

.dmenu li li { margin: 0; }

.dmenu li ul { /* second-level lists */
position: absolute;
left: -999em;
z-index: 101;
border: 1px solid #ccc;
}

.dmenu li ul ul { /* third-and-above-level lists */
position: absolute;
left: -999em;
margin: 0 0 0 0;
z-index: 102;
}

.dmenu li.odd .submenu {
width: 12px;
height: 15px;
float: right;
background: url(/common/images/rarr-lt.png) 0 3px no-repeat;
}
.dmenu li.even .submenu {
width: 12px;
height: 15px;
float: right;
background: url(/common/images/rarr-dk.png) 0 3px no-repeat;
}
.dmenu li.odd {
background: #E9EDF4;
border: 2px solid #E9EDF4;
}
.dmenu li.even {
background: #D0D8E8;
border: 2px solid #D0D8E8;
}

.dmenu li:hover, .dmenu li.sfhover {
border: 2px solid #385D8A;
}

.dmenu li:hover ul ul,
.dmenu li:hover ul ul ul,
.dmenu li.sfhover ul ul,
.dmenu li.sfhover ul ul ul {
left: -999em;
}

.dmenu li:hover ul,
.dmenu li li:hover ul,
.dmenu li li li:hover ul,
.dmenu li.sfhover ul,
.dmenu li li.sfhover ul,
.dmenu li li li.sfhover ul { /* lists nested under hovered list items */
left: 182px;
top: -3px;
}

.dtree {
font-family: Verdana, Geneva, Arial, Helvetica, sans-serif;
font-size: 11px;
color: #666;
white-space: nowrap;
}
.dtree img {
border: 0px;
vertical-align: middle;
}
.dtree a {
color: #333;
text-decoration: none;
}
.dtree a.node, .dtree a.nodeSel {
white-space: nowrap;
padding: 1px 2px 1px 2px;
}
.dtree a.node:hover, .dtree a.nodeSel:hover {
color: #333;
text-decoration: underline;
}
.dtree a.nodeSel {
background-color: #c0d2ec;
}
.dtree .clip {
overflow: hidden;
padding-bottom: 1px;
}

/*
* MenuSidebar
*/
/* this has to be overridden for every menu */
#p-Menu,
#p-Menu2,
#p-Menu3 {
overflow: visible;
}

/* this has to be overridden for every menu */
#p-Menu div,
#p-Menu2 div,
#p-Menu3 div {
margin: 0;
padding: 0;
}

/* this is an example to make the list of the second entry bigger e.g. when ther is a longer text in a list item
#p-Menu ul li.item2 ul {
width: 16em;
}
*/

/* this an example to change the background color of every second list item
li.even {
background-color: #eeeeee;
}
*/

.menuSidebar ul { /* remove bullets and list indents */
list-style: none;
margin: 0;
padding: 0;
}

/* this div is only for better handling and navigation ... could also be done in inner ul*/
.menuSidebar ul div {
position: absolute;
top: -6px;
left: 100%; /* to position them to the right of their containing block */
width: 100%; /* width is based on the containing block */
z-index: 100; /* show ul on top */
}

.menuSidebar ul ul {
background-color: white;
border: 1px solid #aaaaaa;
margin-top: 5px; /* make navigation easier*/
margin-bottom: 5px; /* make navigation easier*/
z-index: 101; /* show on top; Needed for IE 7 */
width: 12em; /* width of inner menu, Needed for IE 7 */
}

.menuSidebar li {
position: relative; /* make li a container for inner elements */
margin: 1px;
z-index: 102; /* show on top; Needed for IE 7 */
}

/* style, color and size links and headings to suit */
.menuSidebar a {
font-weight: bold;
display: block;
border-width: 0px 0px 1px 0px;
border-style: solid;
border-color: #aaaaaa;
margin: 0px;
padding: 1px;
padding-left: 5px;
color: #000000;
text-decoration: none;
}

/* move the > to the right */
.menuSidebar a em {
position: absolute;
right: 4px;
}

.menuSidebar li:hover, /* Needed for IE 7 */
.menuSidebar a:hover {
background: #ccccff;
}

.menuSidebar li.separator a:hover {
background: white;
}

/* Needed for IE 7 */
.menuSidebar li.separator a,
.menuSidebar li.separator {
line-height: 0px;
height: 0px;
font-size: 0px;
}

.menuSidebar ul li:last-Child a {
border-width: 0px 0px 0px 0px; // remove the last bottom line
padding-bottom: 0px;
}

/* hides the first level */
.menuSidebar ul li div { display: none; }

/* shows the first level and hide the second */
.menuSidebar ul li:hover div,
.menuSidebar ul li div:hover { display: block; } /* div is again used for easier navigation*/
.menuSidebar ul li:hover ul li div { display: none; } /* hide the next level */

/* second level*/
.menuSidebar ul li ul li:hover div,
.menuSidebar ul li ul li div:hover { display: block; } /* div is again used for easier navigation*/
.menuSidebar ul li ul li:hover ul li div { display: none; } /* hide the next level */

/* third level */
.menuSidebar ul li ul li ul li:hover div,
.menuSidebar ul li ul li ul li div:hover { display: block; } /* div is again used for easier navigation*/
.menuSidebar ul li ul li ul li:hover ul li div { display: none; } /* hide the next level */

/* General purpose "pretty (data) tables" */
table.datatable {
background-color: transparent;
}

table.datatable th,
table.datatable td {
padding: 4px;
}

table.datatable th {
text-align: left;
background-color: #999999;
}

table.datatable tr {
background-color: #cccccc;
}

table.datatable tr:hover {
background-color: #ffffcc;
}

/* SideBox styling */
div.sideBox {
position: relative;
float: right;
background: white;
margin-left: 1em;
border: 1px solid gray;
padding: 0.3em;
width: 200px;
overflow: hidden;
clear: right;
}
div.sideBox dl {
padding: 0;
margin: 0 0 0.3em 0;
font-size: 96%;
}
div.sideBox dl dt {
background: none;
margin: 0.4em 0 0 0;
}
div.sideBox dl dd {
margin: 0.1em 0 0 1.1em;
background-color: #f3f3f3;
}

MediaWiki:Common.css

2015-02-20T10:04:24Z

Natethomas:

*/

/* <pre><nowiki> */

/* Edit window toolbar */
#toolbar {
height: 22px;
margin-bottom: 6px;
}

/* Highlight clicked reference in blue to help navigation */
ol.references li:target,
sup.reference:target,
span.citation:target {
background-color: #DEF;
}

/* Ensure refs in table headers and the like aren't bold or italic */
sup.reference {
font-weight: normal;
font-style: normal;
}

/* Allow hidden ref errors to be shown by user CSS */
span.brokenref {
display: none;
}

/* Styling for citations (CSS3). Breaks long urls, etc., rather than overflowing box */
.citation {
word-wrap: break-word;
}

/* For linked citation numbers and document IDs, where
the number need not be shown on a screen or a handheld,
but should be included in the printed version */
@media screen, handheld {
.citation *.printonly {
display: none;
}
}

/* wikitable/prettytable class for skinning normal tables */
table.wikitable,
table.prettytable {
margin: 1em 1em 1em 0;
background: #f9f9f9;
border: 1px #aaa solid;
border-collapse: collapse;
}
.wikitable th, .wikitable td,
.prettytable th, .prettytable td {
border: 1px #aaa solid;
padding: 0.2em;
}
.wikitable th,
.prettytable th {
background: lightgrey;
text-align: center;
}
.wikitable caption,
.prettytable caption {
font-weight: bold;
}

/* Style for [[Template:Flowlist]] that Lets lists flow around floating objecs */
.flowlist ul {
overflow-x: hidden;
margin-left: 0em;
padding-left: 1.6em;
}
.flowlist ol {
overflow-x: hidden;
margin-left: 0em;
padding-left: 3.2em;
}
.flowlist dl {
overflow-x: hidden;
}

/* Unbulleted lists */
.plainlist ul {
line-height: inherit;
list-style: none none;
margin: 0;
}
.plainlist ul li {
margin-bottom: 0;
}

/* Default style for navigation boxes */
.navbox { /* Navbox container style */
border: 1px solid #aaa;
width: 100%;
margin: auto;
clear: both;
font-size: 88%;
text-align: center;
padding: 1px;
}
.navbox-inner,
.navbox-subgroup {
width: 100%;
}
.navbox-group,
.navbox-title,
.navbox-abovebelow {
padding: 0.25em 1em; /* Title, group and above/below styles */
line-height: 1.5em;
text-align: center;
}
th.navbox-group { /* Group style */
white-space: nowrap;
/* @noflip */
text-align: right;
}
.navbox,
.navbox-subgroup {
background: #fdfdfd; /* Background color */
}
.navbox-list {
line-height: 1.8em;
border-color: #fdfdfd; /* Must match background color */
}
.navbox th,
.navbox-title {
background: #ccccff; /* Level 1 color */
}
.navbox-abovebelow,
th.navbox-group,
.navbox-subgroup .navbox-title {
background: #ddddff; /* Level 2 color */
}
.navbox-subgroup .navbox-group,
.navbox-subgroup .navbox-abovebelow {
background: #e6e6ff; /* Level 3 color */
}
.navbox-even {
background: #f7f7f7; /* Even row striping */
}
.navbox-odd {
background: transparent; /* Odd row striping */
}
table.navbox + table.navbox { /* Single pixel border between adjacent navboxes */
margin-top: -1px; /* (doesn't work for IE6, but that's okay) */
}
.navbox .hlist td dl,
.navbox .hlist td ol,
.navbox .hlist td ul,
.navbox td.hlist dl,
.navbox td.hlist ol,
.navbox td.hlist ul {
padding: 0.125em 0; /* Adjust hlist padding in navboxes */
}
ol + table.navbox,
ul + table.navbox {
margin-top: 0.5em; /* Prevent lists from clinging to navboxes */
}

/* Default styling for Navbar template */
.navbar {
display: inline;
font-size: 88%;
font-weight: normal;
}
.navbar ul {
display: inline;
white-space: nowrap;
}
.navbar li {
word-spacing: -0.125em;
}
.navbar.mini li span {
font-variant: small-caps;
}
/* Navbar styling when nested in infobox and navbox */
.infobox .navbar {
font-size: 100%;
}
.navbox .navbar {
display: block;
font-size: 100%;
}
.navbox-title .navbar {
/* @noflip */
float: left;
/* @noflip */
text-align: left;
/* @noflip */
margin-right: 0.5em;
width: 6em;
}

/* 'show'/'hide' buttons created dynamically by the CollapsibleTables javascript
in [[MediaWiki:Common.js]] are styled here so they can be customised. */
.collapseButton {
/* @noflip */
float: right;
font-weight: normal;
/* @noflip */
margin-left: 0.5em;
/* @noflip */
text-align: right;
width: auto;
}
/* In navboxes, the show/hide button balances the v·d·e links
from [[Template:Navbar]], so they need to be the same width. */
.navbox .collapseButton {
width: 6em;
}

/* Styling for JQuery makeCollapsible, matching that of collapseButton */
.mw-collapsible-toggle {
font-weight: normal;
/* @noflip */
text-align: right;
}
.navbox .mw-collapsible-toggle {
width: 6em;
}

/* Infobox template style */
.infobox {
border: 1px solid #aaa;
background-color: #f9f9f9;
color: black;
/* @noflip */
margin: 0.5em 0 0.5em 1em;
padding: 0.2em;
/* @noflip */
float: right;
/* @noflip */
clear: right;
/* @noflip */
}
.infobox caption {
font-size: larger;
}
.infobox td,
.infobox th {
vertical-align: top;
}
.infobox.bordered {
border-collapse: collapse;
}
.infobox.bordered td,
.infobox.bordered th {
border: 1px solid #aaa;
}
.infobox.bordered .borderless td,
.infobox.bordered .borderless th {
border: 0;
}

.infobox.sisterproject {
width: 20em;
font-size: 90%;
}

.infobox.standard-talk {
border: 1px solid #c0c090;
background-color: #f8eaba;
}
.infobox.standard-talk.bordered td,
.infobox.standard-talk.bordered th {
border: 1px solid #c0c090;
}

/* styles for bordered infobox with merged rows */
.infobox.bordered .mergedtoprow td,
.infobox.bordered .mergedtoprow th {
border: 0;
border-top: 1px solid #aaa;
/* @noflip */
border-right: 1px solid #aaa;
}

.infobox.bordered .mergedrow td,
.infobox.bordered .mergedrow th {
border: 0;
/* @noflip */
border-right: 1px solid #aaa;
}

/* Styles for geography infoboxes, eg countries,
country subdivisions, cities, etc. */
.infobox.geography {
/* @noflip */
text-align: left;
border-collapse: collapse;
line-height: 1.2em;
font-size: 90%;
}

.infobox.geography td,
.infobox.geography th {
border-top: 1px solid #aaa;
padding: 0.4em 0.6em 0.4em 0.6em;
}
.infobox.geography .mergedtoprow td,
.infobox.geography .mergedtoprow th {
border-top: 1px solid #aaa;
padding: 0.4em 0.6em 0.2em 0.6em;
}

.infobox.geography .mergedrow td,
.infobox.geography .mergedrow th {
border: 0;
padding: 0 0.6em 0.2em 0.6em;
}

.infobox.geography .mergedbottomrow td,
.infobox.geography .mergedbottomrow th {
border-top: 0;
border-bottom: 1px solid #aaa;
padding: 0 0.6em 0.4em 0.6em;
}

.infobox.geography .maptable td,
.infobox.geography .maptable th {
border: 0;
padding: 0;
}

/* Makes redirects appear in italics in categories and on [[Special:Allpages]] */
.redirect-in-category, .allpagesredirect {
font-style: italic;
}

/* Normal font styling for table row headers with scope="row" tag */
.wikitable.plainrowheaders th[scope=row] {
font-weight: normal;
/* @noflip */
text-align: left;
}

/* Lists in data cells are always left-aligned */
.wikitable td ul,
.wikitable td ol,
.wikitable td dl {
/* @noflip */
text-align: left;
}

/* Change the external link icon to an Adobe icon for all PDF files
in browsers that support these CSS selectors, like Mozilla and Opera */
div#content a[href$=".pdf"].external,
div#content a[href*=".pdf?"].external,
div#content a[href*=".pdf#"].external,
div#content a[href$=".PDF"].external,
div#content a[href*=".PDF?"].external,
div#content a[href*=".PDF#"].external,
div#mw_content a[href$=".pdf"].external,
div#mw_content a[href*=".pdf?"].external,
div#mw_content a[href*=".pdf#"].external,
div#mw_content a[href$=".PDF"].external,
div#mw_content a[href*=".PDF?"].external,
div#mw_content a[href*=".PDF#"].external {
background: url("//upload.wikimedia.org/wikipedia/commons/2/23/Icons-mini-file_acrobat.gif") no-repeat right;
/* @noflip */
padding-right: 18px;
}

/* Change the external link icon to an Adobe icon anywhere the PDFlink class
is used (notably Template:PDFlink). This works in IE, unlike the above. */
div#content span.PDFlink a,
div#mw_content span.PDFlink a {
background: url("//upload.wikimedia.org/wikipedia/commons/2/23/Icons-mini-file_acrobat.gif") no-repeat right;
/* @noflip */
padding-right: 18px;
}

/* Content in columns with CSS instead of tables [[Template:Columns]] */
div.columns-2 div.column {
/* @noflip */
float: left;
width: 50%;
min-width: 300px;
}
div.columns-3 div.column {
/* @noflip */
float: left;
width: 33.3%;
min-width: 200px;
}
div.columns-4 div.column {
/* @noflip */
float: left;
width: 25%;
min-width: 150px;
}
div.columns-5 div.column {
/* @noflip */
float: left;
width: 20%;
min-width: 120px;
}

/* Messagebox templates */
.messagebox {
border: 1px solid #aaa;
background-color: #f9f9f9;
width: 80%;
margin: 0 auto 1em auto;
padding: .2em;
}
.messagebox.merge {
border: 1px solid #c0b8cc;
background-color: #f0e5ff;
text-align: center;
}
.messagebox.cleanup {
border: 1px solid #9f9fff;
background-color: #efefff;
text-align: center;
}
.messagebox.standard-talk {
border: 1px solid #c0c090;
background-color: #f8eaba;
margin: 4px auto;
}
/* For old WikiProject banners inside banner shells. */
.mbox-inside .standard-talk,
.messagebox.nested-talk {
border: 1px solid #c0c090;
background-color: #f8eaba;
width: 100%;
margin: 2px 0;
padding: 2px;
}
.messagebox.small {
width: 238px;
font-size: 85%;
/* @noflip */
float: right;
clear: both;
/* @noflip */
margin: 0 0 1em 1em;
line-height: 1.25em;
}
.messagebox.small-talk {
width: 238px;
font-size: 85%;
/* @noflip */
float: right;
clear: both;
/* @noflip */
margin: 0 0 1em 1em;
line-height: 1.25em;
background: #F8EABA;
}

/* Cell sizes for ambox/tmbox/imbox/cmbox/ombox/fmbox/dmbox message boxes */
th.mbox-text, td.mbox-text { /* The message body cell(s) */
border: none;
/* @noflip */
padding: 0.25em 0.9em; /* 0.9em left/right */
width: 100%; /* Make all mboxes the same width regardless of text length */
}
td.mbox-image { /* The left image cell */
border: none;
/* @noflip */
padding: 2px 0 2px 0.9em; /* 0.9em left, 0px right */
text-align: center;
}
td.mbox-imageright { /* The right image cell */
border: none;
/* @noflip */
padding: 2px 0.9em 2px 0; /* 0px left, 0.9em right */
text-align: center;
}
td.mbox-empty-cell { /* An empty narrow cell */
border: none;
padding: 0px;
width: 1px;
}

/* Article message box styles */
table.ambox {
margin: 0px 10%; /* 10% = Will not overlap with other elements */
border: 1px solid #aaa;
/* @noflip */
border-left: 10px solid #1e90ff; /* Default "notice" blue */
background: #fbfbfb;
}
table.ambox + table.ambox { /* Single border between stacked boxes. */
margin-top: -1px;
}
.ambox th.mbox-text,
.ambox td.mbox-text { /* The message body cell(s) */
padding: 0.25em 0.5em; /* 0.5em left/right */
}
.ambox td.mbox-image { /* The left image cell */
/* @noflip */
padding: 2px 0 2px 0.5em; /* 0.5em left, 0px right */
}
.ambox td.mbox-imageright { /* The right image cell */
/* @noflip */
padding: 2px 0.5em 2px 0; /* 0px left, 0.5em right */
}

table.ambox-notice {
/* @noflip */
border-left: 10px solid #1e90ff; /* Blue */
}
table.ambox-speedy {
/* @noflip */
border-left: 10px solid #b22222; /* Red */
background: #fee; /* Pink */
}
table.ambox-delete {
/* @noflip */
border-left: 10px solid #b22222; /* Red */
}
table.ambox-content {
/* @noflip */
border-left: 10px solid #f28500; /* Orange */
}
table.ambox-style {
/* @noflip */
border-left: 10px solid #f4c430; /* Yellow */
}
table.ambox-move {
/* @noflip */
border-left: 10px solid #9932cc; /* Purple */
}
table.ambox-protection {
/* @noflip */
border-left: 10px solid #bba; /* Gray-gold */
}

/* Image message box styles */
table.imbox {
margin: 4px 10%;
border-collapse: collapse;
border: 3px solid #1e90ff; /* Default "notice" blue */
background: #fbfbfb;
}
.imbox .mbox-text .imbox { /* For imboxes inside imbox-text cells. */
margin: 0 -0.5em; /* 0.9 - 0.5 = 0.4em left/right. */
display: block; /* Fix for webkit to force 100% width. */
}
.mbox-inside .imbox { /* For imboxes inside other templates. */
margin: 4px;
}

table.imbox-notice {
border: 3px solid #1e90ff; /* Blue */
}
table.imbox-speedy {
border: 3px solid #b22222; /* Red */
background: #fee; /* Pink */
}
table.imbox-delete {
border: 3px solid #b22222; /* Red */
}
table.imbox-content {
border: 3px solid #f28500; /* Orange */
}
table.imbox-style {
border: 3px solid #f4c430; /* Yellow */
}
table.imbox-move {
border: 3px solid #9932cc; /* Purple */
}
table.imbox-protection {
border: 3px solid #bba; /* Gray-gold */
}
table.imbox-license {
border: 3px solid #88a; /* Dark gray */
background: #f7f8ff; /* Light gray */
}
table.imbox-featured {
border: 3px solid #cba135; /* Brown-gold */
}

/* Category message box styles */
table.cmbox {
margin: 3px 10%;
border-collapse: collapse;
border: 1px solid #aaa;
background: #DFE8FF; /* Default "notice" blue */
}

table.cmbox-notice {
background: #D8E8FF; /* Blue */
}
table.cmbox-speedy {
margin-top: 4px;
margin-bottom: 4px;
border: 4px solid #b22222; /* Red */
background: #FFDBDB; /* Pink */
}
table.cmbox-delete {
background: #FFDBDB; /* Red */
}
table.cmbox-content {
background: #FFE7CE; /* Orange */
}
table.cmbox-style {
background: #FFF9DB; /* Yellow */
}
table.cmbox-move {
background: #E4D8FF; /* Purple */
}
table.cmbox-protection {
background: #EFEFE1; /* Gray-gold */
}

/* Other pages message box styles */
table.ombox {
margin: 4px 10%;
border-collapse: collapse;
border: 1px solid #aaa; /* Default "notice" gray */
background: #f9f9f9;
}

table.ombox-notice {
border: 1px solid #aaa; /* Gray */
}
table.ombox-speedy {
border: 2px solid #b22222; /* Red */
background: #fee; /* Pink */
}
table.ombox-delete {
border: 2px solid #b22222; /* Red */
}
table.ombox-content {
border: 1px solid #f28500; /* Orange */
}
table.ombox-style {
border: 1px solid #f4c430; /* Yellow */
}
table.ombox-move {
border: 1px solid #9932cc; /* Purple */
}
table.ombox-protection {
border: 2px solid #bba; /* Gray-gold */
}

/* Talk page message box styles */
table.tmbox {
margin: 4px 10%;
border-collapse: collapse;
border: 1px solid #c0c090; /* Default "notice" gray-brown */
background: #f8eaba;
}
.mediawiki .mbox-inside .tmbox { /* For tmboxes inside other templates. The "mediawiki" class ensures that */
margin: 2px 0; /* this declaration overrides other styles (including mbox-small above) */
width: 100%; /* For Safari and Opera */
}
.mbox-inside .tmbox.mbox-small { /* "small" tmboxes should not be small when */
line-height: 1.5em; /* also "nested", so reset styles that are */
font-size: 100%; /* set in "mbox-small" above. */
}

table.tmbox-speedy {
border: 2px solid #b22222; /* Red */
background: #fee; /* Pink */
}
table.tmbox-delete {
border: 2px solid #b22222; /* Red */
}
table.tmbox-content {
border: 2px solid #f28500; /* Orange */
}
table.tmbox-style {
border: 2px solid #f4c430; /* Yellow */
}
table.tmbox-move {
border: 2px solid #9932cc; /* Purple */
}
table.tmbox-protection,
table.tmbox-notice {
border: 1px solid #c0c090; /* Gray-brown */
}

/* Disambig and set index box styles */
table.dmbox {
clear: both;
margin: 0.9em 1em;
border-top: 1px solid #ccc;
border-bottom: 1px solid #ccc;
background: transparent;
}

/* Footer and header message box styles */
table.fmbox {
clear: both;
margin: 0.2em 0;
width: 100%;
border: 1px solid #aaa;
background: #f9f9f9; /* Default "system" gray */
}
table.fmbox-system {
background: #f9f9f9;
}
table.fmbox-warning {
border: 1px solid #bb7070; /* Dark pink */
background: #ffdbdb; /* Pink */
}
table.fmbox-editnotice {
background: transparent;
}

/* Div based "warning" style fmbox messages. */
div.mw-warning-with-logexcerpt,
div.mw-lag-warn-high,
div.mw-cascadeprotectedwarning {
clear: both;
margin: 0.2em 0;
border: 1px solid #bb7070;
background: #ffdbdb;
padding: 0.25em 0.9em;
}
/* Div based "system" style fmbox messages. Used in
[[MediaWiki:Noarticletext]] and [[MediaWiki:Readonly lag]]. */
div.mw-lag-warn-normal,
div.noarticletext,
div.fmbox-system {
clear: both;
margin: 0.2em 0;
border: 1px solid #aaa;
background: #f9f9f9;
padding: 0.25em 0.9em;
}

/* These mbox-small classes must be placed after all other
ambox/tmbox/ombox etc classes. "body.mediawiki" is so
they override "table.ambox + table.ambox" above. */
body.mediawiki table.mbox-small { /* For the "small=yes" option. */
/* @noflip */
clear: right;
/* @noflip */
float: right;
/* @noflip */
margin: 4px 0 4px 1em;
width: 238px;
font-size: 88%;
line-height: 1.25em;
}
body.mediawiki table.mbox-small-left { /* For the "small=left" option. */
/* @noflip */
margin: 4px 1em 4px 0;
width: 238px;
border-collapse: collapse;
font-size: 88%;
line-height: 1.25em;
}

/* Style for compact ambox */
/* Hide the images */
.compact-ambox table .mbox-image,
.compact-ambox table .mbox-imageright,
.compact-ambox table .mbox-empty-cell {
display: none;
}
/* Remove borders, backgrounds, padding, etc. */
.compact-ambox table.ambox {
border: none;
border-collapse: collapse;
background: transparent;
margin: 0 0 0 1.6em !important;
padding: 0 !important;
width: auto;
display: block;
}
body.mediawiki .compact-ambox table.mbox-small-left {
font-size: 100%;
width: auto;
margin: 0;
}
/* Style the text cell as a list item and remove its padding */
.compact-ambox table .mbox-text {
padding: 0 !important;
margin: 0 !important;
}
.compact-ambox table .mbox-text-span {
display: list-item;
line-height: 1.5em;
list-style-type: square;
list-style-image: url(//bits.wikimedia.org/skins/common/images/bullet.gif);
}
.skin-vector .compact-ambox table .mbox-text-span {
list-style-type: circle;
list-style-image: url(//bits.wikimedia.org/skins/vector/images/bullet-icon.png)
}
/* Allow for hiding text in compact form */
.compact-ambox .hide-when-compact {
display: none;
}

/* Remove default styles for [[MediaWiki:Noarticletext]]. */
div.noarticletext {
border: none;
background: transparent;
padding: 0;
}

/* class hiddenStructure is defunct. See [[Wikipedia:hiddenStructure]] */
.hiddenStructure {
display: inline ! important;
color: #f00;
background-color: #0f0;
}

/* Bold save button */
#wpSave {
font-weight: bold;
}

/* Standard Navigationsleisten, aka box hiding thingy
from .de. Documentation at [[Wikipedia:NavFrame]]. */
div.NavFrame {
margin: 0;
padding: 4px;
border: 1px solid #aaa;
text-align: center;
border-collapse: collapse;
font-size: 95%;
}
div.NavFrame + div.NavFrame {
border-top-style: none;
border-top-style: hidden;
}
div.NavPic {
background-color: #fff;
margin: 0;
padding: 2px;
/* @noflip */
float: left;
}
div.NavFrame div.NavHead {
height: 1.6em;
font-weight: bold;
background-color: #ccf;
position: relative;
}
div.NavFrame p,
div.NavFrame div.NavContent,
div.NavFrame div.NavContent p {
font-size: 100%;
}
div.NavEnd {
margin: 0;
padding: 0;
line-height: 1px;
clear: both;
}
a.NavToggle {
position: absolute;
top: 0;
/* @noflip */
right: 3px;
font-weight: normal;
font-size: 90%;
}

/* Coloured watchlist numbers */
.mw-plusminus-pos { color: #006400; } /* dark green */
.mw-plusminus-neg { color: #8B0000; } /* dark red */

.rellink,
.dablink {
font-style: italic;
padding-left: 2em;
}
.rellink i,
.dablink i {
font-style: normal;
}

/* Hatnotes and disambiguation notices */
.rellink,
.dablink {
font-style: italic;
/* @noflip */
padding-left: 1.6em;
margin-bottom: 0.5em;
}
.rellink i,
.dablink i {
font-style: normal;
}

/* Style for horizontal UL lists */
.horizontal ul {
padding: 0;
margin: 0;
}
.horizontal li {
padding: 0 0.6em 0 0.4em;
display: inline;
border-right: 1px solid;
}
.horizontal li:last-child {
border-right: none;
padding-right: 0;
}

/* Allow transcluded pages to display in lists rather than a table.
Compatible in Firefox; incompatible in IE6. */
.listify td { display: list-item; }
.listify tr { display: block; }
.listify table { display: block; }

/* When <div class="nonumtoc"> is used on the table of contents,
the ToC will display without numbers */
.nonumtoc .tocnumber { display: none; }
.nonumtoc #toc ul,
.nonumtoc .toc ul {
line-height: 1.5em;
list-style: none none;
margin: .3em 0 0;
padding: 0;
}
.nonumtoc #toc ul ul,
.nonumtoc .toc ul ul {
/* @noflip */
margin: 0 0 0 2em;
}

/* Allow limiting of which header levels are shown in a TOC;
<div class="toclimit-3">, for instance, will limit to
showing ==headings== and ===headings=== but no further
(as long as there are no =headings= on the page, which
there shouldn't be according to the MoS). */
.toclimit-2 .toclevel-1 ul,
.toclimit-3 .toclevel-2 ul,
.toclimit-4 .toclevel-3 ul,
.toclimit-5 .toclevel-4 ul,
.toclimit-6 .toclevel-5 ul,
.toclimit-7 .toclevel-6 ul {
display: none;
}

.toclevel-3 {
padding-left:25px;
}

/* Prevent line breaks in silly places:
1) Where desired
2) Links when we don't want them to
3) Bold "links" to the page itself
4) Ref tags with group names <ref group="Note"> --> "[Note 1]" */
.nowrap,
.nowraplinks a,
.nowraplinks .selflink,
sup.reference a {
white-space: nowrap;
}
/* But allow wrapping where desired: */
.wrap,
.wraplinks a {
white-space: normal;
}

/* For template documentation */
.template-documentation {
clear: both;
margin: 1em 0 0 0;
border: 1px solid #aaa;
background-color: #ecfcf4;
padding: 1em;
}

/* Inline divs in ImageMaps (code borrowed from de.wiki) */
.imagemap-inline div {
display: inline;
}

/* Increase the height of the image upload box */
#wpUploadDescription {
height: 13em;
}

/* Minimum thumb width */
.thumbinner {
min-width: 100px;
}

/* Makes the background of a framed image white instead of gray.
Only visible with transparent images. */
div.thumb img.thumbimage {
background-color: #fff;
}

/* The backgrounds for galleries. */
div#content .gallerybox div.thumb {
/* Light gray padding */
background-color: #F9F9F9;
}
/* Put a chequered background behind images, only visible if they have transparency.
'.filehistory a img' and '#file img:hover' are handled by MediaWiki core (as of 1.19) */
.gallerybox .thumb img {
background: #fff url(//bits.wikimedia.org/skins/common/images/Checker-16x16.png) repeat;
}
/* But not on articles, user pages, portals or with opt-out. */
.ns-0 .gallerybox .thumb img,
.ns-2 .gallerybox .thumb img,
.ns-100 .gallerybox .thumb img,
.nochecker .gallerybox .thumb img {
background: #fff;
}

/* Category tree styling. Works in conjuction with [[MediaWiki:Categorytree-expand-bullet]],
[[MediaWiki:Categorytree-collapse-bullet]] and [[MediaWiki:Categorytree-empty-bullet]]. */
#mw-subcategories ul {
list-style: none none;
margin-left: 0.25em;
}
.CategoryTreeChildren {
margin-left: 1.25em;
}

/* Prevent floating boxes from overlapping any category listings,
file histories, edit previews, and edit [Show changes] views. */
#mw-subcategories, #mw-pages, #mw-category-media,
#filehistory, #wikiPreview, #wikiDiff {
clear: both;
}

/* Disable the automatic text-size adjust of WebKit on iPhones etc.
It scales some text, and not the other. Use none, or fixed percentage instead.
Use media selector, because defining a value, overwrites platform defaults. */
@media only screen and (max-device-width: 480px) {
body {
-webkit-text-size-adjust: none;
}
}

/* Fix so <syntaxhighlight> tags and .css and .js pages get normal text size.
[[Bugzilla:26204]]. See also [[Wikipedia:Typography#The monospace 'bug']] */
div.mw-geshi div,
div.mw-geshi div pre,
span.mw-geshi,
pre.source-css,
pre.source-javascript,
pre.source-lua {
font-family: monospace, Courier !important;
}

/* For announcements */
#bodyContent .letterhead {
background-image:url('//upload.wikimedia.org/wikipedia/commons/e/e0/Tan-page-corner.png');
background-repeat:no-repeat;
padding: 2em;
background-color: #faf9f2;
}

/* Tree style lists */
.treeview ul {
padding: 0;
margin: 0;
}
.treeview li {
padding: 0;
margin: 0;
list-style-type: none;
list-style-image: none;
zoom: 1; /* BE KIND TO IE6 */;
}
.treeview li li {
background: url("//upload.wikimedia.org/wikipedia/commons/f/f2/Treeview-grey-line.png") no-repeat 0 -2981px;
/* @noflip */
padding-left: 20px;
text-indent: 0.3em;
}
.treeview li li.lastline {
background-position: 0 -5971px
}
.treeview li.emptyline > ul {
/* @noflip */
margin-left: -1px;
}
.treeview li.emptyline > ul > li:first-child {
background-position: 0 9px
}

/* Hide charinsert base for those not using the gadget */
#editpage-specialchars {
display: none;
}

/* work-around for [[bugzilla:23965]] (Kaltura advertisement) */
.k-player .k-attribution {
visibility: hidden;
}

/* Unicode font families, for [[Template:Unicode]] */
.UnicodeAnimal { font-family: "Apple Color Emoji", Symbola, "Segoe UI Symbol", Brampton, "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodeAstro { font-family: Symbola, Quivira, "Segoe UI Symbol", FreeSerif, Brampton, "Apple Color Emoji", FreeMono, "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodeChem { font-family: Quivira, Symbola, "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodeCommunication { font-family: Symbola, "Segoe UI Symbol", "Apple Color Emoji", Quivira, Brampton, FreeSerif, "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodeDentistry { font-family: "Segoe UI Symbol", Quivira, FreeMono, Symbola, "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodeEducation { font-family: "Segoe UI Symbol", Symbola, "Apple Color Emoji", Brampton, "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodeEmoticon { font-family: "Apple Color Emoji", "Segoe UI Symbol", Symbola, Brampton, FreeMono, "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodeEnclosed { font-family: Quivira, Brampton, "Apple Color Emoji", "Segoe UI Symbol", FreeSans, FreeSerif, FreeMono, "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodeEvent { font-family: "Apple Color Emoji", "Segoe UI Symbol", Symbola, Brampton, "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodeFood { font-family: "Apple Color Emoji", Symbola, "Segoe UI Symbol", Brampton, "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodeGame { font-family: Symbola, Quivira, FreeSerif, Brampton, "Segoe UI Symbol", "Apple Color Emoji", "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodeMap { font-family: Symbola, "Apple Color Emoji", "Segoe UI Symbol", Quivira, Brampton, "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodeMedicine { font-family: "Segoe UI Symbol", Quivira, Symbola, "Apple Color Emoji", Brampton, FreeSerif, "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodeMoney { font-family: Symbola, Quivira, FreeSerif, FreeSans, FreeMono, "Segoe UI Symbol", "Apple Color Emoji", Brampton, "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodeMusic { font-family: Symbola, FreeSerif, Quivira, "Segoe UI Symbol", Brampton, "Apple Color Emoji", "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodePerson { font-family: "Apple Color Emoji", Symbola, "Segoe UI Symbol", Quivira, Brampton, "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodePicto { font-family: Symbola, "Segoe UI Symbol", FreeSerif, Quivira, Brampton, "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodePlant { font-family: Symbola, "Apple Color Emoji", "Segoe UI Symbol", Brampton, "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodePoliticsReligion { font-family: Symbola, "Segoe UI Symbol", FreeSerif, Quivira, Brampton, FreeMono, "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodeRegion { font-family: "Apple Color Emoji", Brampton, "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodeSport { font-family: Symbola, "Apple Color Emoji", "Segoe UI Symbol", "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodeTechnology { font-family: Symbola, "Segoe UI Symbol", FreeMono, FreeSerif, Quivira, FreeSans, Brampton, "Apple Color Emoji", "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodeTime { font-family: Quivira, Symbola, "Apple Color Emoji", Brampton, "Segoe UI Symbol", "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodeUI { font-family: Symbola, Quivira, "Segoe UI Symbol", "Apple Color Emoji", FreeSerif, FreeMono, Brampton, "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodeWarning { font-family: Symbola, "Segoe UI Symbol", Quivira, "Apple Color Emoji", Brampton, FreeSerif, "Arial Unicode MS", "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodeWeather { font-family: Symbola, Quivira, "Segoe UI Symbol", FreeSerif, "Apple Color Emoji", Brampton, "Arial Unicode MS", "Lucida Sans Unicode"; }

/* Dynamic menus */
.dmenu { width: 180px }

.dmenu, .dmenu ul { /* all lists */
padding: 0;
margin: 0;
list-style: none;
}
.dmenu .selflink { font-weight: normal; }

.dmenu li { /* all list items */
position: relative;
float: left;
width: 172px;
padding: 4px;
z-index: 100;
}

.dmenu li,
.dmenu li.even a,
.dmenu li.odd a,
.dmenu li li,
.dmenu li li a,
.dmenu li li li,
.dmenu li li li a {
color : black;
}

.dmenu li li { margin: 0; }

.dmenu li ul { /* second-level lists */
position: absolute;
left: -999em;
z-index: 101;
border: 1px solid #ccc;
}

.dmenu li ul ul { /* third-and-above-level lists */
position: absolute;
left: -999em;
margin: 0 0 0 0;
z-index: 102;
}

.dmenu li.odd .submenu {
width: 12px;
height: 15px;
float: right;
background: url(/common/images/rarr-lt.png) 0 3px no-repeat;
}
.dmenu li.even .submenu {
width: 12px;
height: 15px;
float: right;
background: url(/common/images/rarr-dk.png) 0 3px no-repeat;
}
.dmenu li.odd {
background: #E9EDF4;
border: 2px solid #E9EDF4;
}
.dmenu li.even {
background: #D0D8E8;
border: 2px solid #D0D8E8;
}

.dmenu li:hover, .dmenu li.sfhover {
border: 2px solid #385D8A;
}

.dmenu li:hover ul ul,
.dmenu li:hover ul ul ul,
.dmenu li.sfhover ul ul,
.dmenu li.sfhover ul ul ul {
left: -999em;
}

.dmenu li:hover ul,
.dmenu li li:hover ul,
.dmenu li li li:hover ul,
.dmenu li.sfhover ul,
.dmenu li li.sfhover ul,
.dmenu li li li.sfhover ul { /* lists nested under hovered list items */
left: 182px;
top: -3px;
}

.dtree {
font-family: Verdana, Geneva, Arial, Helvetica, sans-serif;
font-size: 11px;
color: #666;
white-space: nowrap;
}
.dtree img {
border: 0px;
vertical-align: middle;
}
.dtree a {
color: #333;
text-decoration: none;
}
.dtree a.node, .dtree a.nodeSel {
white-space: nowrap;
padding: 1px 2px 1px 2px;
}
.dtree a.node:hover, .dtree a.nodeSel:hover {
color: #333;
text-decoration: underline;
}
.dtree a.nodeSel {
background-color: #c0d2ec;
}
.dtree .clip {
overflow: hidden;
padding-bottom: 1px;
}

/*
* MenuSidebar
*/
/* this has to be overridden for every menu */
#p-Menu,
#p-Menu2,
#p-Menu3 {
overflow: visible;
}

/* this has to be overridden for every menu */
#p-Menu div,
#p-Menu2 div,
#p-Menu3 div {
margin: 0;
padding: 0;
}

/* this is an example to make the list of the second entry bigger e.g. when ther is a longer text in a list item
#p-Menu ul li.item2 ul {
width: 16em;
}
*/

/* this an example to change the background color of every second list item
li.even {
background-color: #eeeeee;
}
*/

.menuSidebar ul { /* remove bullets and list indents */
list-style: none;
margin: 0;
padding: 0;
}

/* this div is only for better handling and navigation ... could also be done in inner ul*/
.menuSidebar ul div {
position: absolute;
top: -6px;
left: 100%; /* to position them to the right of their containing block */
width: 100%; /* width is based on the containing block */
z-index: 100; /* show ul on top */
}

.menuSidebar ul ul {
background-color: white;
border: 1px solid #aaaaaa;
margin-top: 5px; /* make navigation easier*/
margin-bottom: 5px; /* make navigation easier*/
z-index: 101; /* show on top; Needed for IE 7 */
width: 12em; /* width of inner menu, Needed for IE 7 */
}

.menuSidebar li {
position: relative; /* make li a container for inner elements */
margin: 1px;
z-index: 102; /* show on top; Needed for IE 7 */
}

/* style, color and size links and headings to suit */
.menuSidebar a {
font-weight: bold;
display: block;
border-width: 0px 0px 1px 0px;
border-style: solid;
border-color: #aaaaaa;
margin: 0px;
padding: 1px;
padding-left: 5px;
color: #000000;
text-decoration: none;
}

/* move the > to the right */
.menuSidebar a em {
position: absolute;
right: 4px;
}

.menuSidebar li:hover, /* Needed for IE 7 */
.menuSidebar a:hover {
background: #ccccff;
}

.menuSidebar li.separator a:hover {
background: white;
}

/* Needed for IE 7 */
.menuSidebar li.separator a,
.menuSidebar li.separator {
line-height: 0px;
height: 0px;
font-size: 0px;
}

.menuSidebar ul li:last-Child a {
border-width: 0px 0px 0px 0px; // remove the last bottom line
padding-bottom: 0px;
}

/* hides the first level */
.menuSidebar ul li div { display: none; }

/* shows the first level and hide the second */
.menuSidebar ul li:hover div,
.menuSidebar ul li div:hover { display: block; } /* div is again used for easier navigation*/
.menuSidebar ul li:hover ul li div { display: none; } /* hide the next level */

/* second level*/
.menuSidebar ul li ul li:hover div,
.menuSidebar ul li ul li div:hover { display: block; } /* div is again used for easier navigation*/
.menuSidebar ul li ul li:hover ul li div { display: none; } /* hide the next level */

/* third level */
.menuSidebar ul li ul li ul li:hover div,
.menuSidebar ul li ul li ul li div:hover { display: block; } /* div is again used for easier navigation*/
.menuSidebar ul li ul li ul li:hover ul li div { display: none; } /* hide the next level */

/* General purpose "pretty (data) tables" */
table.datatable {
background-color: transparent;
}

table.datatable th,
table.datatable td {
padding: 4px;
}

table.datatable th {
text-align: left;
background-color: #999999;
}

table.datatable tr {
background-color: #cccccc;
}

table.datatable tr:hover {
background-color: #ffffcc;
}

/* SideBox styling */
div.sideBox {
position: relative;
float: right;
background: white;
margin-left: 1em;
border: 1px solid gray;
padding: 0.3em;
width: 200px;
overflow: hidden;
clear: right;
}
div.sideBox dl {
padding: 0;
margin: 0 0 0.3em 0;
font-size: 96%;
}
div.sideBox dl dt {
background: none;
margin: 0.4em 0 0 0;
}
div.sideBox dl dd {
margin: 0.1em 0 0 1.1em;
background-color: #f3f3f3;
}

MediaWiki:Common.css

2015-02-20T10:03:33Z

Natethomas:

*/

/* <pre><nowiki> */

/* Edit window toolbar */
#toolbar {
height: 22px;
margin-bottom: 6px;
}

/* Highlight clicked reference in blue to help navigation */
ol.references li:target,
sup.reference:target,
span.citation:target {
background-color: #DEF;
}

/* Ensure refs in table headers and the like aren't bold or italic */
sup.reference {
font-weight: normal;
font-style: normal;
}

/* Allow hidden ref errors to be shown by user CSS */
span.brokenref {
display: none;
}

/* Styling for citations (CSS3). Breaks long urls, etc., rather than overflowing box */
.citation {
word-wrap: break-word;
}

/* For linked citation numbers and document IDs, where
the number need not be shown on a screen or a handheld,
but should be included in the printed version */
@media screen, handheld {
.citation *.printonly {
display: none;
}
}

/* wikitable/prettytable class for skinning normal tables */
table.wikitable,
table.prettytable {
margin: 1em 1em 1em 0;
background: #f9f9f9;
border: 1px #aaa solid;
border-collapse: collapse;
}
.wikitable th, .wikitable td,
.prettytable th, .prettytable td {
border: 1px #aaa solid;
padding: 0.2em;
}
.wikitable th,
.prettytable th {
background: lightgrey;
text-align: center;
}
.wikitable caption,
.prettytable caption {
font-weight: bold;
}

/* Style for [[Template:Flowlist]] that Lets lists flow around floating objecs */
.flowlist ul {
overflow-x: hidden;
margin-left: 0em;
padding-left: 1.6em;
}
.flowlist ol {
overflow-x: hidden;
margin-left: 0em;
padding-left: 3.2em;
}
.flowlist dl {
overflow-x: hidden;
}

/* Unbulleted lists */
.plainlist ul {
line-height: inherit;
list-style: none none;
margin: 0;
}
.plainlist ul li {
margin-bottom: 0;
}

/* Default style for navigation boxes */
.navbox { /* Navbox container style */
border: 1px solid #aaa;
width: 100%;
margin: auto;
clear: both;
font-size: 88%;
text-align: center;
padding: 1px;
}
.navbox-inner,
.navbox-subgroup {
width: 100%;
}
.navbox-group,
.navbox-title,
.navbox-abovebelow {
padding: 0.25em 1em; /* Title, group and above/below styles */
line-height: 1.5em;
text-align: center;
}
th.navbox-group { /* Group style */
white-space: nowrap;
/* @noflip */
text-align: right;
}
.navbox,
.navbox-subgroup {
background: #fdfdfd; /* Background color */
}
.navbox-list {
line-height: 1.8em;
border-color: #fdfdfd; /* Must match background color */
}
.navbox th,
.navbox-title {
background: #ccccff; /* Level 1 color */
}
.navbox-abovebelow,
th.navbox-group,
.navbox-subgroup .navbox-title {
background: #ddddff; /* Level 2 color */
}
.navbox-subgroup .navbox-group,
.navbox-subgroup .navbox-abovebelow {
background: #e6e6ff; /* Level 3 color */
}
.navbox-even {
background: #f7f7f7; /* Even row striping */
}
.navbox-odd {
background: transparent; /* Odd row striping */
}
table.navbox + table.navbox { /* Single pixel border between adjacent navboxes */
margin-top: -1px; /* (doesn't work for IE6, but that's okay) */
}
.navbox .hlist td dl,
.navbox .hlist td ol,
.navbox .hlist td ul,
.navbox td.hlist dl,
.navbox td.hlist ol,
.navbox td.hlist ul {
padding: 0.125em 0; /* Adjust hlist padding in navboxes */
}
ol + table.navbox,
ul + table.navbox {
margin-top: 0.5em; /* Prevent lists from clinging to navboxes */
}

/* Default styling for Navbar template */
.navbar {
display: inline;
font-size: 88%;
font-weight: normal;
}
.navbar ul {
display: inline;
white-space: nowrap;
}
.navbar li {
word-spacing: -0.125em;
}
.navbar.mini li span {
font-variant: small-caps;
}
/* Navbar styling when nested in infobox and navbox */
.infobox .navbar {
font-size: 100%;
}
.navbox .navbar {
display: block;
font-size: 100%;
}
.navbox-title .navbar {
/* @noflip */
float: left;
/* @noflip */
text-align: left;
/* @noflip */
margin-right: 0.5em;
width: 6em;
}

/* 'show'/'hide' buttons created dynamically by the CollapsibleTables javascript
in [[MediaWiki:Common.js]] are styled here so they can be customised. */
.collapseButton {
/* @noflip */
float: right;
font-weight: normal;
/* @noflip */
margin-left: 0.5em;
/* @noflip */
text-align: right;
width: auto;
}
/* In navboxes, the show/hide button balances the v·d·e links
from [[Template:Navbar]], so they need to be the same width. */
.navbox .collapseButton {
width: 6em;
}

/* Styling for JQuery makeCollapsible, matching that of collapseButton */
.mw-collapsible-toggle {
font-weight: normal;
/* @noflip */
text-align: right;
}
.navbox .mw-collapsible-toggle {
width: 6em;
}

/* Infobox template style */
.infobox {
border: 1px solid #aaa;
background-color: #f9f9f9;
color: black;
/* @noflip */
margin: 0.5em 0 0.5em 1em;
padding: 0.2em;
/* @noflip */
float: right;
/* @noflip */
clear: right;
/* @noflip */
}
.infobox caption {
font-size: larger;
}
.infobox td,
.infobox th {
vertical-align: top;
}
.infobox.bordered {
border-collapse: collapse;
}
.infobox.bordered td,
.infobox.bordered th {
border: 1px solid #aaa;
}
.infobox.bordered .borderless td,
.infobox.bordered .borderless th {
border: 0;
}

.infobox.sisterproject {
width: 20em;
font-size: 90%;
}

.infobox.standard-talk {
border: 1px solid #c0c090;
background-color: #f8eaba;
}
.infobox.standard-talk.bordered td,
.infobox.standard-talk.bordered th {
border: 1px solid #c0c090;
}

/* styles for bordered infobox with merged rows */
.infobox.bordered .mergedtoprow td,
.infobox.bordered .mergedtoprow th {
border: 0;
border-top: 1px solid #aaa;
/* @noflip */
border-right: 1px solid #aaa;
}

.infobox.bordered .mergedrow td,
.infobox.bordered .mergedrow th {
border: 0;
/* @noflip */
border-right: 1px solid #aaa;
}

/* Styles for geography infoboxes, eg countries,
country subdivisions, cities, etc. */
.infobox.geography {
/* @noflip */
text-align: left;
border-collapse: collapse;
line-height: 1.2em;
font-size: 90%;
}

.infobox.geography td,
.infobox.geography th {
border-top: 1px solid #aaa;
padding: 0.4em 0.6em 0.4em 0.6em;
}
.infobox.geography .mergedtoprow td,
.infobox.geography .mergedtoprow th {
border-top: 1px solid #aaa;
padding: 0.4em 0.6em 0.2em 0.6em;
}

.infobox.geography .mergedrow td,
.infobox.geography .mergedrow th {
border: 0;
padding: 0 0.6em 0.2em 0.6em;
}

.infobox.geography .mergedbottomrow td,
.infobox.geography .mergedbottomrow th {
border-top: 0;
border-bottom: 1px solid #aaa;
padding: 0 0.6em 0.4em 0.6em;
}

.infobox.geography .maptable td,
.infobox.geography .maptable th {
border: 0;
padding: 0;
}

/* Makes redirects appear in italics in categories and on [[Special:Allpages]] */
.redirect-in-category, .allpagesredirect {
font-style: italic;
}

/* Normal font styling for table row headers with scope="row" tag */
.wikitable.plainrowheaders th[scope=row] {
font-weight: normal;
/* @noflip */
text-align: left;
}

/* Lists in data cells are always left-aligned */
.wikitable td ul,
.wikitable td ol,
.wikitable td dl {
/* @noflip */
text-align: left;
}

/* Change the external link icon to an Adobe icon for all PDF files
in browsers that support these CSS selectors, like Mozilla and Opera */
div#content a[href$=".pdf"].external,
div#content a[href*=".pdf?"].external,
div#content a[href*=".pdf#"].external,
div#content a[href$=".PDF"].external,
div#content a[href*=".PDF?"].external,
div#content a[href*=".PDF#"].external,
div#mw_content a[href$=".pdf"].external,
div#mw_content a[href*=".pdf?"].external,
div#mw_content a[href*=".pdf#"].external,
div#mw_content a[href$=".PDF"].external,
div#mw_content a[href*=".PDF?"].external,
div#mw_content a[href*=".PDF#"].external {
background: url("//upload.wikimedia.org/wikipedia/commons/2/23/Icons-mini-file_acrobat.gif") no-repeat right;
/* @noflip */
padding-right: 18px;
}

/* Change the external link icon to an Adobe icon anywhere the PDFlink class
is used (notably Template:PDFlink). This works in IE, unlike the above. */
div#content span.PDFlink a,
div#mw_content span.PDFlink a {
background: url("//upload.wikimedia.org/wikipedia/commons/2/23/Icons-mini-file_acrobat.gif") no-repeat right;
/* @noflip */
padding-right: 18px;
}

/* Content in columns with CSS instead of tables [[Template:Columns]] */
div.columns-2 div.column {
/* @noflip */
float: left;
width: 50%;
min-width: 300px;
}
div.columns-3 div.column {
/* @noflip */
float: left;
width: 33.3%;
min-width: 200px;
}
div.columns-4 div.column {
/* @noflip */
float: left;
width: 25%;
min-width: 150px;
}
div.columns-5 div.column {
/* @noflip */
float: left;
width: 20%;
min-width: 120px;
}

/* Messagebox templates */
.messagebox {
border: 1px solid #aaa;
background-color: #f9f9f9;
width: 80%;
margin: 0 auto 1em auto;
padding: .2em;
}
.messagebox.merge {
border: 1px solid #c0b8cc;
background-color: #f0e5ff;
text-align: center;
}
.messagebox.cleanup {
border: 1px solid #9f9fff;
background-color: #efefff;
text-align: center;
}
.messagebox.standard-talk {
border: 1px solid #c0c090;
background-color: #f8eaba;
margin: 4px auto;
}
/* For old WikiProject banners inside banner shells. */
.mbox-inside .standard-talk,
.messagebox.nested-talk {
border: 1px solid #c0c090;
background-color: #f8eaba;
width: 100%;
margin: 2px 0;
padding: 2px;
}
.messagebox.small {
width: 238px;
font-size: 85%;
/* @noflip */
float: right;
clear: both;
/* @noflip */
margin: 0 0 1em 1em;
line-height: 1.25em;
}
.messagebox.small-talk {
width: 238px;
font-size: 85%;
/* @noflip */
float: right;
clear: both;
/* @noflip */
margin: 0 0 1em 1em;
line-height: 1.25em;
background: #F8EABA;
}

/* Cell sizes for ambox/tmbox/imbox/cmbox/ombox/fmbox/dmbox message boxes */
th.mbox-text, td.mbox-text { /* The message body cell(s) */
border: none;
/* @noflip */
padding: 0.25em 0.9em; /* 0.9em left/right */
width: 100%; /* Make all mboxes the same width regardless of text length */
}
td.mbox-image { /* The left image cell */
border: none;
/* @noflip */
padding: 2px 0 2px 0.9em; /* 0.9em left, 0px right */
text-align: center;
}
td.mbox-imageright { /* The right image cell */
border: none;
/* @noflip */
padding: 2px 0.9em 2px 0; /* 0px left, 0.9em right */
text-align: center;
}
td.mbox-empty-cell { /* An empty narrow cell */
border: none;
padding: 0px;
width: 1px;
}

/* Article message box styles */
table.ambox {
margin: 0px 10%; /* 10% = Will not overlap with other elements */
border: 1px solid #aaa;
/* @noflip */
border-left: 10px solid #1e90ff; /* Default "notice" blue */
background: #fbfbfb;
}
table.ambox + table.ambox { /* Single border between stacked boxes. */
margin-top: -1px;
}
.ambox th.mbox-text,
.ambox td.mbox-text { /* The message body cell(s) */
padding: 0.25em 0.5em; /* 0.5em left/right */
}
.ambox td.mbox-image { /* The left image cell */
/* @noflip */
padding: 2px 0 2px 0.5em; /* 0.5em left, 0px right */
}
.ambox td.mbox-imageright { /* The right image cell */
/* @noflip */
padding: 2px 0.5em 2px 0; /* 0px left, 0.5em right */
}

table.ambox-notice {
/* @noflip */
border-left: 10px solid #1e90ff; /* Blue */
}
table.ambox-speedy {
/* @noflip */
border-left: 10px solid #b22222; /* Red */
background: #fee; /* Pink */
}
table.ambox-delete {
/* @noflip */
border-left: 10px solid #b22222; /* Red */
}
table.ambox-content {
/* @noflip */
border-left: 10px solid #f28500; /* Orange */
}
table.ambox-style {
/* @noflip */
border-left: 10px solid #f4c430; /* Yellow */
}
table.ambox-move {
/* @noflip */
border-left: 10px solid #9932cc; /* Purple */
}
table.ambox-protection {
/* @noflip */
border-left: 10px solid #bba; /* Gray-gold */
}

/* Image message box styles */
table.imbox {
margin: 4px 10%;
border-collapse: collapse;
border: 3px solid #1e90ff; /* Default "notice" blue */
background: #fbfbfb;
}
.imbox .mbox-text .imbox { /* For imboxes inside imbox-text cells. */
margin: 0 -0.5em; /* 0.9 - 0.5 = 0.4em left/right. */
display: block; /* Fix for webkit to force 100% width. */
}
.mbox-inside .imbox { /* For imboxes inside other templates. */
margin: 4px;
}

table.imbox-notice {
border: 3px solid #1e90ff; /* Blue */
}
table.imbox-speedy {
border: 3px solid #b22222; /* Red */
background: #fee; /* Pink */
}
table.imbox-delete {
border: 3px solid #b22222; /* Red */
}
table.imbox-content {
border: 3px solid #f28500; /* Orange */
}
table.imbox-style {
border: 3px solid #f4c430; /* Yellow */
}
table.imbox-move {
border: 3px solid #9932cc; /* Purple */
}
table.imbox-protection {
border: 3px solid #bba; /* Gray-gold */
}
table.imbox-license {
border: 3px solid #88a; /* Dark gray */
background: #f7f8ff; /* Light gray */
}
table.imbox-featured {
border: 3px solid #cba135; /* Brown-gold */
}

/* Category message box styles */
table.cmbox {
margin: 3px 10%;
border-collapse: collapse;
border: 1px solid #aaa;
background: #DFE8FF; /* Default "notice" blue */
}

table.cmbox-notice {
background: #D8E8FF; /* Blue */
}
table.cmbox-speedy {
margin-top: 4px;
margin-bottom: 4px;
border: 4px solid #b22222; /* Red */
background: #FFDBDB; /* Pink */
}
table.cmbox-delete {
background: #FFDBDB; /* Red */
}
table.cmbox-content {
background: #FFE7CE; /* Orange */
}
table.cmbox-style {
background: #FFF9DB; /* Yellow */
}
table.cmbox-move {
background: #E4D8FF; /* Purple */
}
table.cmbox-protection {
background: #EFEFE1; /* Gray-gold */
}

/* Other pages message box styles */
table.ombox {
margin: 4px 10%;
border-collapse: collapse;
border: 1px solid #aaa; /* Default "notice" gray */
background: #f9f9f9;
}

table.ombox-notice {
border: 1px solid #aaa; /* Gray */
}
table.ombox-speedy {
border: 2px solid #b22222; /* Red */
background: #fee; /* Pink */
}
table.ombox-delete {
border: 2px solid #b22222; /* Red */
}
table.ombox-content {
border: 1px solid #f28500; /* Orange */
}
table.ombox-style {
border: 1px solid #f4c430; /* Yellow */
}
table.ombox-move {
border: 1px solid #9932cc; /* Purple */
}
table.ombox-protection {
border: 2px solid #bba; /* Gray-gold */
}

/* Talk page message box styles */
table.tmbox {
margin: 4px 10%;
border-collapse: collapse;
border: 1px solid #c0c090; /* Default "notice" gray-brown */
background: #f8eaba;
}
.mediawiki .mbox-inside .tmbox { /* For tmboxes inside other templates. The "mediawiki" class ensures that */
margin: 2px 0; /* this declaration overrides other styles (including mbox-small above) */
width: 100%; /* For Safari and Opera */
}
.mbox-inside .tmbox.mbox-small { /* "small" tmboxes should not be small when */
line-height: 1.5em; /* also "nested", so reset styles that are */
font-size: 100%; /* set in "mbox-small" above. */
}

table.tmbox-speedy {
border: 2px solid #b22222; /* Red */
background: #fee; /* Pink */
}
table.tmbox-delete {
border: 2px solid #b22222; /* Red */
}
table.tmbox-content {
border: 2px solid #f28500; /* Orange */
}
table.tmbox-style {
border: 2px solid #f4c430; /* Yellow */
}
table.tmbox-move {
border: 2px solid #9932cc; /* Purple */
}
table.tmbox-protection,
table.tmbox-notice {
border: 1px solid #c0c090; /* Gray-brown */
}

/* Disambig and set index box styles */
table.dmbox {
clear: both;
margin: 0.9em 1em;
border-top: 1px solid #ccc;
border-bottom: 1px solid #ccc;
background: transparent;
}

/* Footer and header message box styles */
table.fmbox {
clear: both;
margin: 0.2em 0;
width: 100%;
border: 1px solid #aaa;
background: #f9f9f9; /* Default "system" gray */
}
table.fmbox-system {
background: #f9f9f9;
}
table.fmbox-warning {
border: 1px solid #bb7070; /* Dark pink */
background: #ffdbdb; /* Pink */
}
table.fmbox-editnotice {
background: transparent;
}

/* Div based "warning" style fmbox messages. */
div.mw-warning-with-logexcerpt,
div.mw-lag-warn-high,
div.mw-cascadeprotectedwarning {
clear: both;
margin: 0.2em 0;
border: 1px solid #bb7070;
background: #ffdbdb;
padding: 0.25em 0.9em;
}
/* Div based "system" style fmbox messages. Used in
[[MediaWiki:Noarticletext]] and [[MediaWiki:Readonly lag]]. */
div.mw-lag-warn-normal,
div.noarticletext,
div.fmbox-system {
clear: both;
margin: 0.2em 0;
border: 1px solid #aaa;
background: #f9f9f9;
padding: 0.25em 0.9em;
}

/* These mbox-small classes must be placed after all other
ambox/tmbox/ombox etc classes. "body.mediawiki" is so
they override "table.ambox + table.ambox" above. */
body.mediawiki table.mbox-small { /* For the "small=yes" option. */
/* @noflip */
clear: right;
/* @noflip */
float: right;
/* @noflip */
margin: 4px 0 4px 1em;
width: 238px;
font-size: 88%;
line-height: 1.25em;
}
body.mediawiki table.mbox-small-left { /* For the "small=left" option. */
/* @noflip */
margin: 4px 1em 4px 0;
width: 238px;
border-collapse: collapse;
font-size: 88%;
line-height: 1.25em;
}

/* Style for compact ambox */
/* Hide the images */
.compact-ambox table .mbox-image,
.compact-ambox table .mbox-imageright,
.compact-ambox table .mbox-empty-cell {
display: none;
}
/* Remove borders, backgrounds, padding, etc. */
.compact-ambox table.ambox {
border: none;
border-collapse: collapse;
background: transparent;
margin: 0 0 0 1.6em !important;
padding: 0 !important;
width: auto;
display: block;
}
body.mediawiki .compact-ambox table.mbox-small-left {
font-size: 100%;
width: auto;
margin: 0;
}
/* Style the text cell as a list item and remove its padding */
.compact-ambox table .mbox-text {
padding: 0 !important;
margin: 0 !important;
}
.compact-ambox table .mbox-text-span {
display: list-item;
line-height: 1.5em;
list-style-type: square;
list-style-image: url(//bits.wikimedia.org/skins/common/images/bullet.gif);
}
.skin-vector .compact-ambox table .mbox-text-span {
list-style-type: circle;
list-style-image: url(//bits.wikimedia.org/skins/vector/images/bullet-icon.png)
}
/* Allow for hiding text in compact form */
.compact-ambox .hide-when-compact {
display: none;
}

/* Remove default styles for [[MediaWiki:Noarticletext]]. */
div.noarticletext {
border: none;
background: transparent;
padding: 0;
}

/* class hiddenStructure is defunct. See [[Wikipedia:hiddenStructure]] */
.hiddenStructure {
display: inline ! important;
color: #f00;
background-color: #0f0;
}

/* Bold save button */
#wpSave {
font-weight: bold;
}

/* Standard Navigationsleisten, aka box hiding thingy
from .de. Documentation at [[Wikipedia:NavFrame]]. */
div.NavFrame {
margin: 0;
padding: 4px;
border: 1px solid #aaa;
text-align: center;
border-collapse: collapse;
font-size: 95%;
}
div.NavFrame + div.NavFrame {
border-top-style: none;
border-top-style: hidden;
}
div.NavPic {
background-color: #fff;
margin: 0;
padding: 2px;
/* @noflip */
float: left;
}
div.NavFrame div.NavHead {
height: 1.6em;
font-weight: bold;
background-color: #ccf;
position: relative;
}
div.NavFrame p,
div.NavFrame div.NavContent,
div.NavFrame div.NavContent p {
font-size: 100%;
}
div.NavEnd {
margin: 0;
padding: 0;
line-height: 1px;
clear: both;
}
a.NavToggle {
position: absolute;
top: 0;
/* @noflip */
right: 3px;
font-weight: normal;
font-size: 90%;
}

/* Coloured watchlist numbers */
.mw-plusminus-pos { color: #006400; } /* dark green */
.mw-plusminus-neg { color: #8B0000; } /* dark red */

.rellink,
.dablink {
font-style: italic;
padding-left: 2em;
}
.rellink i,
.dablink i {
font-style: normal;
}

/* Hatnotes and disambiguation notices */
.rellink,
.dablink {
font-style: italic;
/* @noflip */
padding-left: 1.6em;
margin-bottom: 0.5em;
}
.rellink i,
.dablink i {
font-style: normal;
}

/* Style for horizontal UL lists */
.horizontal ul {
padding: 0;
margin: 0;
}
.horizontal li {
padding: 0 0.6em 0 0.4em;
display: inline;
border-right: 1px solid;
}
.horizontal li:last-child {
border-right: none;
padding-right: 0;
}

/* Allow transcluded pages to display in lists rather than a table.
Compatible in Firefox; incompatible in IE6. */
.listify td { display: list-item; }
.listify tr { display: block; }
.listify table { display: block; }

/* When <div class="nonumtoc"> is used on the table of contents,
the ToC will display without numbers */
.nonumtoc .tocnumber { display: none; }
.nonumtoc #toc ul,
.nonumtoc .toc ul {
line-height: 1.5em;
list-style: none none;
margin: .3em 0 0;
padding: 0;
}
.nonumtoc #toc ul ul,
.nonumtoc .toc ul ul {
/* @noflip */
margin: 0 0 0 2em;
}

/* Allow limiting of which header levels are shown in a TOC;
<div class="toclimit-3">, for instance, will limit to
showing ==headings== and ===headings=== but no further
(as long as there are no =headings= on the page, which
there shouldn't be according to the MoS). */
.toclimit-2 .toclevel-1 ul,
.toclimit-3 .toclevel-2 ul,
.toclimit-4 .toclevel-3 ul,
.toclimit-5 .toclevel-4 ul,
.toclimit-6 .toclevel-5 ul,
.toclimit-7 .toclevel-6 ul {
display: none;
}

.toclevel-3 {
text-indent:5px;
}

/* Prevent line breaks in silly places:
1) Where desired
2) Links when we don't want them to
3) Bold "links" to the page itself
4) Ref tags with group names <ref group="Note"> --> "[Note 1]" */
.nowrap,
.nowraplinks a,
.nowraplinks .selflink,
sup.reference a {
white-space: nowrap;
}
/* But allow wrapping where desired: */
.wrap,
.wraplinks a {
white-space: normal;
}

/* For template documentation */
.template-documentation {
clear: both;
margin: 1em 0 0 0;
border: 1px solid #aaa;
background-color: #ecfcf4;
padding: 1em;
}

/* Inline divs in ImageMaps (code borrowed from de.wiki) */
.imagemap-inline div {
display: inline;
}

/* Increase the height of the image upload box */
#wpUploadDescription {
height: 13em;
}

/* Minimum thumb width */
.thumbinner {
min-width: 100px;
}

/* Makes the background of a framed image white instead of gray.
Only visible with transparent images. */
div.thumb img.thumbimage {
background-color: #fff;
}

/* The backgrounds for galleries. */
div#content .gallerybox div.thumb {
/* Light gray padding */
background-color: #F9F9F9;
}
/* Put a chequered background behind images, only visible if they have transparency.
'.filehistory a img' and '#file img:hover' are handled by MediaWiki core (as of 1.19) */
.gallerybox .thumb img {
background: #fff url(//bits.wikimedia.org/skins/common/images/Checker-16x16.png) repeat;
}
/* But not on articles, user pages, portals or with opt-out. */
.ns-0 .gallerybox .thumb img,
.ns-2 .gallerybox .thumb img,
.ns-100 .gallerybox .thumb img,
.nochecker .gallerybox .thumb img {
background: #fff;
}

/* Category tree styling. Works in conjuction with [[MediaWiki:Categorytree-expand-bullet]],
[[MediaWiki:Categorytree-collapse-bullet]] and [[MediaWiki:Categorytree-empty-bullet]]. */
#mw-subcategories ul {
list-style: none none;
margin-left: 0.25em;
}
.CategoryTreeChildren {
margin-left: 1.25em;
}

/* Prevent floating boxes from overlapping any category listings,
file histories, edit previews, and edit [Show changes] views. */
#mw-subcategories, #mw-pages, #mw-category-media,
#filehistory, #wikiPreview, #wikiDiff {
clear: both;
}

/* Disable the automatic text-size adjust of WebKit on iPhones etc.
It scales some text, and not the other. Use none, or fixed percentage instead.
Use media selector, because defining a value, overwrites platform defaults. */
@media only screen and (max-device-width: 480px) {
body {
-webkit-text-size-adjust: none;
}
}

/* Fix so <syntaxhighlight> tags and .css and .js pages get normal text size.
[[Bugzilla:26204]]. See also [[Wikipedia:Typography#The monospace 'bug']] */
div.mw-geshi div,
div.mw-geshi div pre,
span.mw-geshi,
pre.source-css,
pre.source-javascript,
pre.source-lua {
font-family: monospace, Courier !important;
}

/* For announcements */
#bodyContent .letterhead {
background-image:url('//upload.wikimedia.org/wikipedia/commons/e/e0/Tan-page-corner.png');
background-repeat:no-repeat;
padding: 2em;
background-color: #faf9f2;
}

/* Tree style lists */
.treeview ul {
padding: 0;
margin: 0;
}
.treeview li {
padding: 0;
margin: 0;
list-style-type: none;
list-style-image: none;
zoom: 1; /* BE KIND TO IE6 */;
}
.treeview li li {
background: url("//upload.wikimedia.org/wikipedia/commons/f/f2/Treeview-grey-line.png") no-repeat 0 -2981px;
/* @noflip */
padding-left: 20px;
text-indent: 0.3em;
}
.treeview li li.lastline {
background-position: 0 -5971px
}
.treeview li.emptyline > ul {
/* @noflip */
margin-left: -1px;
}
.treeview li.emptyline > ul > li:first-child {
background-position: 0 9px
}

/* Hide charinsert base for those not using the gadget */
#editpage-specialchars {
display: none;
}

/* work-around for [[bugzilla:23965]] (Kaltura advertisement) */
.k-player .k-attribution {
visibility: hidden;
}

/* Unicode font families, for [[Template:Unicode]] */
.UnicodeAnimal { font-family: "Apple Color Emoji", Symbola, "Segoe UI Symbol", Brampton, "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodeAstro { font-family: Symbola, Quivira, "Segoe UI Symbol", FreeSerif, Brampton, "Apple Color Emoji", FreeMono, "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodeChem { font-family: Quivira, Symbola, "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodeCommunication { font-family: Symbola, "Segoe UI Symbol", "Apple Color Emoji", Quivira, Brampton, FreeSerif, "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodeDentistry { font-family: "Segoe UI Symbol", Quivira, FreeMono, Symbola, "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodeEducation { font-family: "Segoe UI Symbol", Symbola, "Apple Color Emoji", Brampton, "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodeEmoticon { font-family: "Apple Color Emoji", "Segoe UI Symbol", Symbola, Brampton, FreeMono, "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodeEnclosed { font-family: Quivira, Brampton, "Apple Color Emoji", "Segoe UI Symbol", FreeSans, FreeSerif, FreeMono, "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodeEvent { font-family: "Apple Color Emoji", "Segoe UI Symbol", Symbola, Brampton, "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodeFood { font-family: "Apple Color Emoji", Symbola, "Segoe UI Symbol", Brampton, "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodeGame { font-family: Symbola, Quivira, FreeSerif, Brampton, "Segoe UI Symbol", "Apple Color Emoji", "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodeMap { font-family: Symbola, "Apple Color Emoji", "Segoe UI Symbol", Quivira, Brampton, "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodeMedicine { font-family: "Segoe UI Symbol", Quivira, Symbola, "Apple Color Emoji", Brampton, FreeSerif, "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodeMoney { font-family: Symbola, Quivira, FreeSerif, FreeSans, FreeMono, "Segoe UI Symbol", "Apple Color Emoji", Brampton, "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodeMusic { font-family: Symbola, FreeSerif, Quivira, "Segoe UI Symbol", Brampton, "Apple Color Emoji", "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodePerson { font-family: "Apple Color Emoji", Symbola, "Segoe UI Symbol", Quivira, Brampton, "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodePicto { font-family: Symbola, "Segoe UI Symbol", FreeSerif, Quivira, Brampton, "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodePlant { font-family: Symbola, "Apple Color Emoji", "Segoe UI Symbol", Brampton, "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodePoliticsReligion { font-family: Symbola, "Segoe UI Symbol", FreeSerif, Quivira, Brampton, FreeMono, "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodeRegion { font-family: "Apple Color Emoji", Brampton, "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodeSport { font-family: Symbola, "Apple Color Emoji", "Segoe UI Symbol", "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodeTechnology { font-family: Symbola, "Segoe UI Symbol", FreeMono, FreeSerif, Quivira, FreeSans, Brampton, "Apple Color Emoji", "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodeTime { font-family: Quivira, Symbola, "Apple Color Emoji", Brampton, "Segoe UI Symbol", "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodeUI { font-family: Symbola, Quivira, "Segoe UI Symbol", "Apple Color Emoji", FreeSerif, FreeMono, Brampton, "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodeWarning { font-family: Symbola, "Segoe UI Symbol", Quivira, "Apple Color Emoji", Brampton, FreeSerif, "Arial Unicode MS", "Arial Unicode MS", "Lucida Sans Unicode"; }
.UnicodeWeather { font-family: Symbola, Quivira, "Segoe UI Symbol", FreeSerif, "Apple Color Emoji", Brampton, "Arial Unicode MS", "Lucida Sans Unicode"; }

/* Dynamic menus */
.dmenu { width: 180px }

.dmenu, .dmenu ul { /* all lists */
padding: 0;
margin: 0;
list-style: none;
}
.dmenu .selflink { font-weight: normal; }

.dmenu li { /* all list items */
position: relative;
float: left;
width: 172px;
padding: 4px;
z-index: 100;
}

.dmenu li,
.dmenu li.even a,
.dmenu li.odd a,
.dmenu li li,
.dmenu li li a,
.dmenu li li li,
.dmenu li li li a {
color : black;
}

.dmenu li li { margin: 0; }

.dmenu li ul { /* second-level lists */
position: absolute;
left: -999em;
z-index: 101;
border: 1px solid #ccc;
}

.dmenu li ul ul { /* third-and-above-level lists */
position: absolute;
left: -999em;
margin: 0 0 0 0;
z-index: 102;
}

.dmenu li.odd .submenu {
width: 12px;
height: 15px;
float: right;
background: url(/common/images/rarr-lt.png) 0 3px no-repeat;
}
.dmenu li.even .submenu {
width: 12px;
height: 15px;
float: right;
background: url(/common/images/rarr-dk.png) 0 3px no-repeat;
}
.dmenu li.odd {
background: #E9EDF4;
border: 2px solid #E9EDF4;
}
.dmenu li.even {
background: #D0D8E8;
border: 2px solid #D0D8E8;
}

.dmenu li:hover, .dmenu li.sfhover {
border: 2px solid #385D8A;
}

.dmenu li:hover ul ul,
.dmenu li:hover ul ul ul,
.dmenu li.sfhover ul ul,
.dmenu li.sfhover ul ul ul {
left: -999em;
}

.dmenu li:hover ul,
.dmenu li li:hover ul,
.dmenu li li li:hover ul,
.dmenu li.sfhover ul,
.dmenu li li.sfhover ul,
.dmenu li li li.sfhover ul { /* lists nested under hovered list items */
left: 182px;
top: -3px;
}

.dtree {
font-family: Verdana, Geneva, Arial, Helvetica, sans-serif;
font-size: 11px;
color: #666;
white-space: nowrap;
}
.dtree img {
border: 0px;
vertical-align: middle;
}
.dtree a {
color: #333;
text-decoration: none;
}
.dtree a.node, .dtree a.nodeSel {
white-space: nowrap;
padding: 1px 2px 1px 2px;
}
.dtree a.node:hover, .dtree a.nodeSel:hover {
color: #333;
text-decoration: underline;
}
.dtree a.nodeSel {
background-color: #c0d2ec;
}
.dtree .clip {
overflow: hidden;
padding-bottom: 1px;
}

/*
* MenuSidebar
*/
/* this has to be overridden for every menu */
#p-Menu,
#p-Menu2,
#p-Menu3 {
overflow: visible;
}

/* this has to be overridden for every menu */
#p-Menu div,
#p-Menu2 div,
#p-Menu3 div {
margin: 0;
padding: 0;
}

/* this is an example to make the list of the second entry bigger e.g. when ther is a longer text in a list item
#p-Menu ul li.item2 ul {
width: 16em;
}
*/

/* this an example to change the background color of every second list item
li.even {
background-color: #eeeeee;
}
*/

.menuSidebar ul { /* remove bullets and list indents */
list-style: none;
margin: 0;
padding: 0;
}

/* this div is only for better handling and navigation ... could also be done in inner ul*/
.menuSidebar ul div {
position: absolute;
top: -6px;
left: 100%; /* to position them to the right of their containing block */
width: 100%; /* width is based on the containing block */
z-index: 100; /* show ul on top */
}

.menuSidebar ul ul {
background-color: white;
border: 1px solid #aaaaaa;
margin-top: 5px; /* make navigation easier*/
margin-bottom: 5px; /* make navigation easier*/
z-index: 101; /* show on top; Needed for IE 7 */
width: 12em; /* width of inner menu, Needed for IE 7 */
}

.menuSidebar li {
position: relative; /* make li a container for inner elements */
margin: 1px;
z-index: 102; /* show on top; Needed for IE 7 */
}

/* style, color and size links and headings to suit */
.menuSidebar a {
font-weight: bold;
display: block;
border-width: 0px 0px 1px 0px;
border-style: solid;
border-color: #aaaaaa;
margin: 0px;
padding: 1px;
padding-left: 5px;
color: #000000;
text-decoration: none;
}

/* move the > to the right */
.menuSidebar a em {
position: absolute;
right: 4px;
}

.menuSidebar li:hover, /* Needed for IE 7 */
.menuSidebar a:hover {
background: #ccccff;
}

.menuSidebar li.separator a:hover {
background: white;
}

/* Needed for IE 7 */
.menuSidebar li.separator a,
.menuSidebar li.separator {
line-height: 0px;
height: 0px;
font-size: 0px;
}

.menuSidebar ul li:last-Child a {
border-width: 0px 0px 0px 0px; // remove the last bottom line
padding-bottom: 0px;
}

/* hides the first level */
.menuSidebar ul li div { display: none; }

/* shows the first level and hide the second */
.menuSidebar ul li:hover div,
.menuSidebar ul li div:hover { display: block; } /* div is again used for easier navigation*/
.menuSidebar ul li:hover ul li div { display: none; } /* hide the next level */

/* second level*/
.menuSidebar ul li ul li:hover div,
.menuSidebar ul li ul li div:hover { display: block; } /* div is again used for easier navigation*/
.menuSidebar ul li ul li:hover ul li div { display: none; } /* hide the next level */

/* third level */
.menuSidebar ul li ul li ul li:hover div,
.menuSidebar ul li ul li ul li div:hover { display: block; } /* div is again used for easier navigation*/
.menuSidebar ul li ul li ul li:hover ul li div { display: none; } /* hide the next level */

/* General purpose "pretty (data) tables" */
table.datatable {
background-color: transparent;
}

table.datatable th,
table.datatable td {
padding: 4px;
}

table.datatable th {
text-align: left;
background-color: #999999;
}

table.datatable tr {
background-color: #cccccc;
}

table.datatable tr:hover {
background-color: #ffffcc;
}

/* SideBox styling */
div.sideBox {
position: relative;
float: right;
background: white;
margin-left: 1em;
border: 1px solid gray;
padding: 0.3em;
width: 200px;
overflow: hidden;
clear: right;
}
div.sideBox dl {
padding: 0;
margin: 0 0 0.3em 0;
font-size: 96%;
}
div.sideBox dl dt {
background: none;
margin: 0.4em 0 0 0;
}
div.sideBox dl dd {
margin: 0.1em 0 0 1.1em;
background-color: #f3f3f3;
}