Google Summer of Code 2015: Difference between revisions

(40 intermediate revisions by 3 users not shown)

Line 1:

[[Image:GSoC2015.png|right]]

== Introduction ==

KolibriOS is going to apply as a mentoring organization for [http://www.google-melange.com/gsoc/homepage/google/gsoc2015 Google Summer of Code 2015]. This page contains our ideas list and some additional information for students and mentors.

We have previously participated as a Mentoring Organization in [http://www.google-melange.com/gsoc/homepage/google/gsoc2014 Google Summer of Code 2014]. The [[Google Summer of Code 2014|ideas page for 2014]] is available for your reference. Our organization page for GSoC 2014 and successfully completed projects for that year can be accessed [https://www.google-melange.com/gsoc/org2/google/gsoc2014/kolibrios via this link]. To our great delight, both successful students of GSoC2014 stayed with the project and continue contributing to KolibriOS voluntarily in their spare time.

In 2013, we have run an [[KolibriOS Summer of Code 2013|independent Summer of Code]] using money we [http://www.kickstarter.com/projects/kolibrios/kolibrios-help-us-hold-our-own-summer-of-code-2013 collected with Kickstarter]. Two students have worked on KolibriOS, and the results of 2013 Summer of Code were: adding write support for EXT2 filesystem, and adding (read-only) support for XFS filesystem.

== Student Requirements ==

Line 7:

Line 12:

# Full Name (First + Last Name).

# E-mail address.

# Phone (home or mobile).

# Another phone '''for emergency cases''' (if we cannot contact you) - parents, boy/girlfriend, husband/wife etc.

# Nickname you plan to use on our forums, SVN repository or IRC chat.

# Age.

# Country + city of residence.

# Human languages you speak (~~write~~ all languages and knowledge level - basic/intermediate/expert/mother tongue).

# Human languages you speak (state all languages and knowledge level - basic/intermediate/expert/mother tongue).

# Name of college or university you are accepted into or enrolled in + link to their website.

# Name of program (or faculty, or department) in that college/university you are accepted into or enrolled in.

Line 16:

Line 23:

# Have you been involved with any open-source project in the past? If yes, which one, and what have you done for that project?

# Code samples - please provide links to code that you have written. It can be your high school project, contribution to open-source organization, your college/university task or anything like that.

# The task you are willing to work on from our list of Summer of Code 2015 ideas (or suggest your own idea, if you don't like any of the proposed ideas).

# The task you are willing to work on from our list of Summer of Code 2015 ideas (or suggest your own idea, if you don't like any of the proposed ideas). Please provide an approximate work plan for your task split to 1-week intervals, as well as expected outcome of your work. '''This point should be detailed as much as possible, as your application would be evaluated mainly based on what you write here.''' You are welcome (and even encouraged!) to collaborate with potential mentors on this paragraph.

# What other time commitments, such as school work, another job, planned vacation, etc., will you have between May 19 and August 18?

# What other time commitments, such as school work, university studies, another job, planned vacation, etc., will you have between May 25 and August 21 (coding period)? Please be as specific as possible. ''Bear in mind that GSoC is like a full-time job, so if you consider taking a summer semester at the university (with more than 1-2 courses), or intend to perform an internship or work elsewhere during the summer in addition to GSoC, you will likely be '''NOT''' accepted.''

== Organization ==

Line 46:

Line 53:

|}

We have discussed "Google Summer of Code 2015" application with all active members of the KolibriOS Project Team, and selected only those 3 (three) people who have both the knowledge, the dedication, and the time to help their students during the entire summer. Each one of them was assigned to mentor projects in his area of specialization only. In a rare event when a Mentor from the above list cannot continue mentoring his student(s) due to personal circumstances, we will try to find a replacement Mentor, or ask the remaining Mentors to cover for the missing one. Additionally, there is always a number of knowledgeable members of our team hanging around our [http://board.kolibrios.org/chat.php forum chat], and they will gladly answer any student questions that may arise, even if they haven't volunteered as Mentors themselves.

Mentors selected for this year are the same that were originally proposed for last year, and they have already proved to be responsible, helpful and knowledgeable during GSoC2014.

== Ideas for Google Summer of Code 2015 ==

Line 51:

Line 60:

Students are welcome ('''and even encouraged''') to suggest their own ideas for GSoC, provided they can find a mentor amongst KolibriOS developers to guide them.

=== QR-code in boot log ===

=== Sortable list of ideas for easy navigation ===

'''Summary:''' ~~Add a~~ [http://en.wikipedia.org/wiki/~~QR_code QR-code~~] ~~(containing the debug log) at the end of boot process~~

{| class="wikitable sortable" border="1"

|-

! Idea Name

! Area

! Required Skill Level

! Importance for KolibriOS

! Programming Language

! Mentor

|-

| [[#XDXF_dictionary|XDXF dictionary]]

| Application

| Basic

| Low

| Assembler(FASM)

| dunkaist

|-

| [[#CPUID_tool|CPUID tool]]

| Application

| Beginner

| Low

| Assembler(FASM)

| dunkaist

|-

| [[#FTP_client|FTP client]]

| Application

| Basic

| Medium

| Assembler(FASM)

| hidnplayr

|-

| [[#Torrent_client|Torrent client]]

| Application

| Advanced

| High

| Assembler(FASM)/C/C++

| hidnplayr

|-

| [[#XMPP.2FJabber_client|XMPP/Jabber client]]

| Application

| Intermediate

| Medium

| Assembler(FASM)

| dunkaist

|-

| [[#Music_player|Music player]]

| Application

| Advanced

| Medium

| Assembler(FASM)/C/C++

| dunkaist/hidnplayr

|-

| [[#Web_browser:_WebView|Web browser: WebView]]

| Application

| intermediate

| Standard

| [http://www.dev0.de/cmm/indexe.htm Sphinx C--]

| punk_joker/hidnplayr

|-

| [[#Ethernet_driver.28s.29|Ethernet driver(s)]]

| Driver

| Advanced

| High

| Assembler(FASM)

| hidnplayr

|-

| [[#SD_Host_Controller|SD Host Controller driver]]

| Driver

| Advanced

| Low

| Assembler(FASM)

| dunkaist

|-

| [[#USB_devices|USB device drivers]]

| Driver

| Expert

| High

| Assembler(FASM)

| hidnplayr

|-

| [[#Filesystem_support|Filesystem support]]

| Driver

| Expert

| High

| Assembler(FASM)

| dunkaist

|-

| [[#Unicode_support|Unicode support]]

| System wide task

| Intermediate

| Critical

| Assembler(FASM)

| dunkaist

|-

| [[#Widget_toolkit|Widget toolkit]]

| System wide task

| intermediate

| Standard

| Assembler(FASM)

| dunkaist

|-

| [[#Unit_testing_framework|Unit testing framework]]

| System wide task

| intermediate

| High

| Any

| dunkaist

|-

| [[#QR-code_in_boot_log|QR-code in boot log]]

| Kernel/Library

| Basic

| Medium

| Assembler(FASM)

| dunkaist

|}

Explanation of required skill level:

* Beginner: No knowledge at all of the topic,

* Basic: A very basic knowledge of the topic but no professional usage,

* Intermediate: A basic knowledge of the topic but no regular professional usage,

* Advanced: A good knowledge of the topic and a regular professional usage,

* Expert: a perfect knowledge of the topic and a daily professional usage.

Explanation of importance for the project:

* Low: For sure it doesn't hurt to implement, but if nobody does it, no one will even notice.

* Medium: Nice-to-have feature. Will improve everyday life of users and developers.

* High: This feature is needed for the project to start being adopted by masses.

* Critical: This functionality is vital for the project to become useful.

=== Applications ===

These are userspace tasks. They often require only basic knowledge of algorithms and data structures.<br>

No specific experience is required but welcome.

==== XDXF dictionary ====

'''Summary:''' Write dictionary application with support of XDXF (XML Dictionary eXchange Format)

'''Details:'''

* Primary goal: Write library and corresponding dictionary application

* Additional goal: Support of other dictioinary formats

* Language: Assembler/FASM

* Skill level: intermediate

* Importance: Standard

* Mentor: dunkaist

* Links: [http://tibleiz.net/asm-xml/ fasm xml library], [https://en.wikipedia.org/wiki/XDXF XDXF format]

~~[[File~~:~~QR-code.png]]~~

==== CPUID tool ====

'''Summary:''' Update existing CPUID application to be aware of new CPUs and their features

'''Details:'''

* ~~Description~~: ~~Sometimes KolibriOS cannot boot on a certain hardware configuration (gets stuck during or after boot process). In such cases, we request the user having this problem~~ to ~~enable debug log at boot time, take a photo of the screen~~ and ~~show it~~ to us (~~in the forum). However~~, ~~sometimes taking a good quality photo can be quite challenging (bad camera~~, ~~shaking hands~~ etc.) and the attached photo is so blurry to the point the debug log cannot be even read. The idea suggested hereby is to simultaneously encode the debug log which is outputted on the screen, to the form of QR-code, and [http://wiki.kolibrios.org/wiki/File:QR-code.png show the resulting QR-code on empty space on the screen]. In such way, any user possessing a smartphone with a camera and QR-code scanner, could scan the QR-code and submit the encoded text directly on our forums (without having a need to take a photo), and our developers, in turn, would get the debug log text immediately and won't have to unscramble a blurry photo.

* Primary goal: Write code to detect and report new CPUs and features

* Additional goal: Refactor code as to use system libraries (libimg, box_lib, etc.)

* Language: Assembler/FASM

* Skill level: beginner/intermediate

* ~~Suggested by~~: ~~People on [http://habrahabr.ru/company/kolibrios/blog/ habrahabr.ru]~~

* Importance: Standard

* Mentor: dunkaist

* Links: [http://websvn.kolibrios.org/listing.php?repname=Kolibri+OS&path=%2Fprograms%2Fsystem%2Fcpuid%2Ftrunk%2F&#aec5d374b78ae8f08110b3327c3ba5f56 CPUID program], [http://bochs.sourceforge.net/techspec/24161821.pdf Intel cpuid], [http://support.amd.com/TechDocs/25481.pdf AMD cpuid]

==== FTP client ====

'''Summary:''' Create a GUI based FTP client or add FTP support to one of the existing file managers

=== Torrent client ===

'''Details:'''

'''Summary:''' Write a (bit-)torrent client for KolibriOS

* Primary goal: FTP access (download/upload/etc.)

* Additional goal: Create an FTP client library

* Language: Assembler/FASM

* Skill level: beginner/intermediate

* Importance: High

* Mentor: hidnplayr

* Links: [https://www.ietf.org/rfc/rfc959.txt File Transfer Protocol (RFC959)], [http://board.kolibrios.org/viewtopic.php?f=40&t=2360 CLI FTP client (demo)]

==== Torrent client ====

'''Summary:''' Write a (bit-)torrent client for KolibriOS, or port an existing one

'''Details:'''

* Primary goal: Implement a torrent client similar to [http://www.utorrent.com/ µTorrent Free edition]

* Alternative goal (less preferred, but still possible): Port an existing torrent client to KolibriOS