Fork us on GitHub Follow us on Facebook Follow us on Twitter

Changes between Initial Version and Version 1 of GSOC/2018


Ignore:
Timestamp:
2018-01-23T09:46:37Z (20 months ago)
Author:
Jakub Jermář
Comment:

Use a wikipage for gsoc rather than a query

Legend:

Unmodified
Added
Removed
Modified
  • GSOC/2018

    v1 v1  
     1  ''Google Summer of Code is a global program focused on introducing students to open source software development. Students work on a 3 month programming project with an open source organization during their break from university. Since its inception in 2005, the program has brought together 13,000+ student participants and 12,000 mentors from over 125 countries worldwide. Google Summer of Code has produced 33,000,000+ lines of code for 608 open source organizations.''
     2
     3{{{
     4#!html
     5<div style="text-align: right;">[ ... from <a class="ext-link" href="https://summerofcode.withgoogle.com/about/"><span class="icon"></span>Google Summer of Code 2018</a> site. ]</div>
     6}}}
     7
     8== HelenOS ==
     9[[Image(htdocs:screenshot.png,256px,right,margin-left=30, margin-bottom=30, title="HelenOS features in a single screenshot")]]
     10HelenOS participates in GSoC 2018 as part of the [http://gsoc.microkernel.info Microkernel Devroom umbrella organization].
     11
     12HelenOS is a portable microkernel-based multiserver operating system designed and implemented from scratch. It decomposes key operating system functionality such as file systems, networking, device drivers and graphical user interface into a collection of fine-grained user space components that interact with each other via message passing. A failure or crash of one component does not directly harm others. HelenOS is therefore flexible, modular, extensible, fault tolerant and easy to understand.
     13
     14HelenOS does not aim to be a clone of any existing operating system and trades compatibility with legacy APIs for cleaner design. Most of HelenOS components have been made to order specifically for HelenOS so that its essential parts can stay free of adaptation and glue layers, franken-components and the maintenance burden incurred by them.
     15
     16HelenOS runs on seven different processor architectures and machines ranging from embedded ARM devices and single-board computers through multicore 32-bit and 64-bit desktop PCs to 64-bit Itanium and SPARC rack-mount servers.
     17
     18=== A Bit of History ===
     19HelenOS has traditionally been a project with significant student participation. Its first lines were written by a student in 2001. In 2004, the project turned into a collective academic effort and ever since then, new students have been joining every year to work on HelenOS-related theses and assignments. In 2011, 2012 and 2014, HelenOS became a Google Summer of Code mentoring organization and mentored 10 students in total during their journey through the program. In 2017, HelenOS participated under the umbrella of the Microkernel devroom for the first time. HelenOS and the Google Summer of Code make a perfect match enabling students from universities worldwide to experience the thrill of the microkernel multiserver operating system development.
     20
     21== Who Are We Looking for? ==
     22We are looking for students with real interest in microkernel-based operating systems, system-level programming, software design and HelenOS. We are looking for people who will play nicely with our [wiki:StudentTips#Socialinteractiontips community] and by our [wiki:StudentTips#Codingtips guidelines]. We are looking for those who are willing to give their project the necessary time and care. If a student only wants to pass Google Summer of Code with the minimum effort, HelenOS is not a good match for him or her. We are looking for already experienced coders (although specific experience with microkernel-based operating systems is not necessary) because most of our projects start at the medium difficulty level and the code itself is not trivial. The successful candidate should be a good communicator, too.
     23
     24We would like to invite prospective students to demonstrate their abilities and determination to work on HelenOS during the Google Summer of Code 2018 by completing a small programming task before the student application deadline on April 23rd 2018. The student should check out the latest master branch of HelenOS, [wiki:UsersGuide/CompilingFromSource build the system], then think of small programming task (ideally) related to their proposal, implement it, test it and [wiki:HowToContribute submit the patch to us].
     25
     26Students interested in applying for a Google Summer of Code project also need to fill out the [http://gsoc.microkernel.info/form.html application form] and attach it to their application.
     27
     28If a student is accepted, he or she will be invited to participate in the community [wiki:MailingList development mailing list] and [wiki:IRCChannel IRC channel] from day one. We will also ask him or her to periodically document his or her progress via mailing list write-ups and/or blog entries. The mentor will act as a buddy in our team who will monitor the development and provide the student with guidance when necessary. However, as a first-class member of our development community the student will also receive feedback from other developers besides the designated mentor.
     29
     30== Ideas List ==
     31The project ideas for the Google Summer of Code can be characterized as things that will improve the usability of HelenOS while building on the functionality already present in the source tree. No project in the list poses an open-questions topic in the academic sense. Instead, each project is rather implementation-oriented and achievable in one trimester. Each idea is also accompanied by a motivation and a short explanation of why we think somebody should work on it. We expect the students to deliver code that could be seamlessly integrated with the mainline development branch of HelenOS.
     32
     33Note that contributing to HelenOS does '''not''' have to involve kernel programming. In a microkernel-based operating system, most of the features involve work on the user space parts of the system, such as libraries and server tasks. Having said that, we do not object pure kernel projects either.
     34
     35=== Userspace device drivers development ===
     36  * [ticket:674 Implement virtio-net driver]
     37  * [ticket:675 Implement Xen PV network device driver]
     38  * [ticket:621 Raspberry Pi USB controller driver]
     39  * [ticket:647 USB support on BeagleBoard XM and BeagleBone computers]
     40  * [ticket:572 USB DisplayLink driver]
     41  * [ticket:571 Driver for Broadcom VideoCore IV (Raspberry Pi)]
     42  * [ticket:577 AC'97 Audio driver]
     43
     44=== Kernel programming and platform support ===
     45  * [ticket:11 Support PAE on ia32]
     46  * [ticket:649 Implement support for Creator Ci40 (mips32)]
     47
     48=== Improving support for debugging and observability ===
     49  * [ticket:310 Support for DWARF Debugging Information Format]
     50  * [ticket:646 GDB stub for remote debugging]
     51
     52=== Improving user experience, GUI ===
     53  * [ticket:652 Graphics stack (GUI) improvements]
     54  * [ticket:719 Terminal resizing and scrolling]
     55
     56=== Libraries and tooling ===
     57  * [ticket:648 Extend dynamic linking support to (an)other architecture(s)]
     58  * [ticket:424 RPC/IPC generator]
     59
     60=== Porting of third-party components to HelenOS ===
     61  * [ticket:712 Port Git to HelenOS]