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

Changes between Version 1 and Version 2 of GSOC/2018


Ignore:
Timestamp:
2018-01-28T16:46:32Z (15 months ago)
Author:
Jakub Jermář
Comment:

Streamline the ideas page a bit

Legend:

Unmodified
Added
Removed
Modified
  • GSOC/2018

    v1 v2  
    1616HelenOS 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.
    1717
    18 === A Bit of History ===
    19 HelenOS 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? ==
    22 We 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 
    24 We 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 
    26 Students 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 
    28 If 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.
     18== Students ==
     19If you are interested in working on one of our project ideas below, please get in touch with us on our [wiki:MailingList mailing list] and/or [wiki:IRCChannel IRC channel]. In order to qualify, we would like to invite you to demonstrate your ability 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. You 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].
    2920
    3021== Ideas List ==