Available Reports
New Custom Query
Compose a new ticket query by selecting filters and columns to display.
SQL reports and saved custom queries Sort by: Identifier Title
{1} Active Tickets
- List all active tickets by priority.
- Color each row based on priority.
{14} HelenOS and Google Summer of Code 2010
Google Summer of Code
Google Summer of Code is a program that offers student developers stipends to write code for various open source projects. Historically, the program has brought together over 3,400 students with over 200 open source projects, to create millions of lines of code. The program, which kicked off in 2005, is now in its sixth year…
HelenOS
HelenOS is a microkernel-based multiserver operating system designed from scratch. It decomposes key operating system functionality into many isolated but intensively communicating server processes that reside entirely in user space. HelenOS thus provides a computing environment that has several virtues, such as flexibility, increased robustness, well defined explicit interfaces and reduced complexity of individual components as compared to other operating systems.
HelenOS does not aim to be another clone of Unix or some other legacy system and is not POSIX-compliant (even though it may seem POSIX-similar at times). Instead, we try to design it according to our taste and sense for what is the most elegant and right thing to do. What makes HelenOS unique among the other multiserver operating systems is its multiplatform and multiprocessor microkernel. HelenOS will run on seven different processor architectures, ranging from a 32-bit uniprocessor little-endian ARMv4 to a 64-bit multicore big-endian UltraSPARC T1.
A Little Bit of History
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. HelenOS and the Google Summer of Code are therefore a perfect match enabling more students from more universities to experience the thrill of the multiserver operating system development and also an opportunity for the project to get something back.
Students
We are looking for students with real interest in HelenOS. We are looking for people who will play nicely with our community and by our rules. We are looking for those who are willing to give their project the necessary time and care. If you only want to pass with the minimum effort, chances are that HelenOS is not for you. We are looking for already experienced C coders as all our projects start at the medium difficulty level and the code itself is by no means trivial.
If you are accepted, you will likely be asked to participate in the community mailing list and IRC channel from day one. We will also want you to periodically document your progress via mailing list write-ups and/or blog entries in a dedicated project blog. You will have a buddy (a.k.a mentor) in our team who will monitor your development and also provide you with guidance when necessary. Participating in our community will bring you the advantage of the possibility to discuss issues with more buddies than just your mentor.
Ideas List
The below Ideas List for the Google Summer of Code 2010 can be characterized as things that will greatly improve the usability of HelenOS while building on the core functionality already delivered by us in the past years and months. The individual projects are not excessively difficult and none of them poses a research topic in the academic sense. Instead, each item on the list is rather implementation-oriented, achievable in one trimester and something that we really need to be done. We especially did not plague the list with things that we do not need. In contrary, each idea on it is accompanied by a short explanation of why we think somebody should work it.
As you can see, the Ideas List is just a small subset of all open tickets for HelenOS. If you did not find an appealing topic on this list, you might want to consider looking at the broader list or suggest a completely new topic or a variation on an already existing topic. In both cases, talk to us so that we can see whether the new topic would work for HelenOS during the Google Summer of Code. If not, the idea may still seem interesting to us even outside of the Google Summer of Code program.
{15} HelenOS and Google Summer of Code 2011
Google Summer of Code
Google Summer of Code is a global program that offers student developers stipends to write code for various open source software projects. We have worked with several open source, free software, and technology-related groups to identify and fund several projects over a three month period. Since its inception in 2005, the program has brought together over 4,500 students and more than more than 4,000 mentors & co-mentors from over 85 countries worldwide, all for the love of code…
HelenOS
HelenOS is a microkernel-based multiserver operating system designed from scratch. It decomposes key operating system functionality into many isolated but intensively communicating server processes that reside entirely in user space. HelenOS thus provides a computing environment that has several virtues, such as flexibility, increased robustness, well defined explicit interfaces and reduced complexity of individual components as compared to other operating systems.
HelenOS does not aim to be another clone of Unix or some other legacy system and is not POSIX-compliant (even though it may seem POSIX-similar at times). Instead, we try to design it according to our taste and sense for what is the most elegant and right thing to do. What makes HelenOS unique among the other multiserver operating systems is its multiplatform and multiprocessor microkernel. HelenOS will run on seven different processor architectures, ranging from a 32-bit uniprocessor little-endian ARMv4 to a 64-bit multicore big-endian UltraSPARC T1.
A Little Bit of History
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. HelenOS and the Google Summer of Code are therefore a perfect match enabling more students from more universities to experience the thrill of the multiserver operating system development and also an opportunity for the project to get something back.
Students
We are looking for students with real interest in HelenOS. We are looking for people who will play nicely with our community and by our rules. We are looking for those who are willing to give their project the necessary time and care. If you only want to pass with the minimum effort, chances are that HelenOS is not for you. We are looking for already experienced C coders as all our projects start at the medium difficulty level and the code itself is by no means trivial.
If you are accepted, you will likely be asked to participate in the community mailing list and IRC channel from day one. We will also want you to periodically document your progress via mailing list write-ups and/or blog entries in a dedicated project blog. You will have a buddy (a.k.a mentor) in our team who will monitor your development and also provide you with guidance when necessary. Participating in our community will bring you the advantage of the possibility to discuss issues with more buddies than just your mentor.
We would like to invite prospective students to demonstrate their abilities and determination to work on a HelenOS project during the Google Summer of Code 2011 by completing a simple HelenOS task before the student application deadline on April 8. The task should involve building the latest mainline and either fixing a simple bug or contributing an improvement over the current HelenOS behavior.
Ideas List
The below Ideas List for the Google Summer of Code 2011 can be characterized as things that will greatly improve the usability of HelenOS while building on the core functionality already delivered by us in the past years and months. The individual projects are not excessively difficult and none of them poses a research topic in the academic sense. Instead, each item on the list is rather implementation-oriented, achievable in one trimester and something that we really need to be done. We especially did not plague the list with things that we do not need. In contrary, each idea on it is accompanied by a short explanation of why we think somebody should work it.
As you can see, the Ideas List is just a small subset of all open tickets for HelenOS. If you did not find an appealing topic on this list, you might want to consider looking at the broader list or suggest a completely new topic or a variation on an already existing topic. In both cases, talk to us so that we can see whether the new topic would work for HelenOS during the Google Summer of Code. If not, the idea may still seem interesting to us even outside of the Google Summer of Code program.
{17} HelenOS and Google Summer of Code 2012
Google Summer of Code
Google Summer of Code is a global program that offers student developers stipends to write code for various open source software projects. We have worked with several open source, free software, and technology-related groups to identify and fund several projects over a three month period. Since its inception in 2005, the program has brought together nearly 5,500 successful student participants and over 3000 mentors from over 100 countries worldwide, all for the love of code…
HelenOS
HelenOS is a microkernel-based multiserver operating system designed from scratch. It decomposes key operating system functionality into many isolated but intensively communicating server processes that reside entirely in user space. HelenOS thus provides a computing environment that has several virtues, such as flexibility, increased robustness, well defined explicit interfaces and reduced complexity of individual components as compared to other operating systems.
HelenOS does not aim to be another clone of Unix or some other legacy system and is not POSIX-compliant (even though it may seem POSIX-similar at times). Instead, we try to design it according to our taste and sense for what is the most elegant and right thing to do. What makes HelenOS unique among the other multiserver operating systems is its multiplatform and multiprocessor microkernel. HelenOS runs on seven different processor architectures, ranging from a 32-bit uniprocessor little-endian ARMv4 and commodity x86 and x86-64 PC to a 64-bit multicore big-endian UltraSPARC T1.
A Little Bit of History
HelenOS has traditionally been a project with significant student participation. Its first lines were written by a student in 2001, now more than a decade ago. 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, HelenOS became a Google Summer of Code mentoring organization and successfully mentored three students during their journey through the program. HelenOS and the Google Summer of Code are therefore a perfect match enabling more students from more universities to experience the thrill of the multiserver operating system development and also an opportunity for the project to get something back.
Students
We are looking for students with real interest in HelenOS. We are looking for people who will play nicely with our community and by our rules. We are looking for those who are willing to give their project the necessary time and care. If a student only wants to pass with the minimum effort, chances are that HelenOS is not for him or her. We are looking for already experienced C coders as all our projects start at the medium difficulty level and the code itself is not trivial. Besides being an experienced C coder, a successful candidate should be a good communicator too.
If a student is accepted, they will be asked to participate in the community mailing list and IRC channel from day one. We will also want them to periodically document their progress via mailing list write-ups and/or blog entries in a dedicated project blog. They will have a buddy (a.k.a mentor) in our team who will monitor their development and also provide them with guidance when necessary. Participating in our community will bring them the advantage of the possibility to discuss issues with more buddies than just their mentor.
We would like to invite prospective students to demonstrate their abilities and determination to work on a HelenOS project during the Google Summer of Code 2012 by completing a simple HelenOS task before the student application deadline on April 6. The student should check out the latest mainline sources from our VCS repository, build the system, then either pick up an existing bug or enhancement or think of their own one, implement it, test it and submit the patch / public bzr branch / merge directive to us.
Interested students will need to fill out the following application form and attach it in their application.
Ideas List
The below Ideas List for the Google Summer of Code 2012 can be characterized as things that will greatly improve the usability of HelenOS while building on the core functionality already delivered by us in the past years and months. The individual projects are not excessively difficult and none of them poses a research topic in the academic sense. Instead, each item on the list is rather implementation-oriented, achievable in one trimester and something that we really need to be done. We especially did not plague the list with things that we do not need. In contrary, each idea on it is accompanied by a short explanation of why we think somebody should work it.
Last year we learned that some students may be under the false impression that the project ideas for HelenOS need to involve kernel programming. In general, this is a false assumption. Even though HelenOS is a microkernel-based system, most of the project ideas involve work on userspace parts of the system, such as libraries or server tasks. Having said that, we don't object kernel projects either.
As you can see, the Ideas List is just a small subset of all open tickets for HelenOS. If you did not find an appealing topic on this list, you might want to consider looking at the broader list or suggest a completely new topic or a variation on an already existing topic. In both cases, talk to us so that we can see whether the new topic would work for HelenOS during the Google Summer of Code. If not, the idea may still seem interesting to us even outside of the Google Summer of Code program.
Besides our regular project ideas, the HelenOS team will also sponsor ideas for selected related projects in the form of mentoring or co-mentoring.
{19} HelenOS and Google Summer of Code 2013
Google Summer of Code is a global program that offers student developers stipends to write code for various open source software projects. We work with many open source, free software, and technology-related groups to identify and fund projects over a three month period. Since its inception in 2005, the program has brought together nearly 6,000 successful student participants and over 3000 mentors from over 100 countries worldwide, all for the love of code.
HelenOS
HelenOS is a microkernel-based multiserver operating system designed from scratch. It decomposes key operating system functionality into isolated but intensively communicating server tasks that reside entirely in user space. HelenOS thus provides a computing environment that has several virtues, such as flexibility, increased robustness, well defined explicit interfaces and reduced complexity of individual components as compared to other operating systems.
HelenOS does not aim to be another clone of Unix or some other legacy system and is not POSIX-compliant (even though it may seem POSIX-similar at times). Instead, we try to design it according to our sense for what is the most elegant and right thing to do. What makes HelenOS unique among the other multiserver operating systems is its multiplatform and multiprocessor microkernel. HelenOS runs on seven different processor architectures, ranging from a 32-bit uniprocessor little-endian ARMv4 and commodity PC (x86 and x86-64) to a 64-bit multicore big-endian UltraSPARC T1.
A Bit of History
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 and 2012, HelenOS became a Google Summer of Code mentoring organization and mentored 8 students in total during their journey through the program. HelenOS and the Google Summer of Code make a perfect match enabling students from more universities to experience the thrill of the multiserver operating system development and also an opportunity for the project to get something back.
Who Are We Looking For?
We are looking for students with real interest in operating systems and HelenOS. We are looking for people who will play nicely with our community and by our coding style. We are looking for those who are willing to give their project the necessary time and care. If a student only wants to pass with the minimum effort, HelenOS is not a good match for him or her. We are looking for already experienced C coders as all our projects start at the medium difficulty level and the code itself is not trivial. The successful candidate should be a good communicator, too.
We would like to invite prospective students to demonstrate their abilities and determination to work on a HelenOS project during the Google Summer of Code 2013 by completing a simple HelenOS task before the student application deadline on May 3. The student should check out the latest mainline sources from our repository, build the system, then either pick up an existing bug or enhancement or think of their own one, implement it, test it and submit the patch / public bzr branch / merge directive to us. Interested students will also need to fill out the application form and attach it in their application.
If a student is accepted, they will be asked to participate in the community mailing list and IRC channel from day one. We will also want them to periodically document their progress via mailing list write-ups and/or blog entries. The mentor will act as a buddy in our team who will monitor their development and provide them with guidance when necessary. However, participating in our community will allow them to receive feedback also from other developers besides their mentor.
Ideas List
The project ideas for the Google Summer of Code 2013 can be characterized as things that will improve the usability of HelenOS while building on the core functionality already delivered by us in the past. The individual projects are not excessively difficult and none of them poses an open-questions topic in the academic sense. Instead, each item on the list is rather implementation-oriented, achievable in one trimester and something that we really need to be done. We especially did not plague the list with things that we do not need. In contrary, each idea is accompanied by a short explanation of why we think somebody should work on it.
In the past years we learned that some students may be under the false impression that the projects for HelenOS need to involve kernel programming. In general, this is a false assumption. Because HelenOS is a microkernel-based system, most of the projects involve work on the user space parts of the system, such as libraries or server tasks. Having said that, we don't object kernel projects either.
The Ideas List is just a small subset of all open tickets for HelenOS. If you do not see an appealing topic on this list, you might want to consider looking at the broader list or suggest a completely new topic or a variation on an already existing topic. Remember that the ideas are not set in stone and, after all, it is the student who is going to suggest the idea to us. In any case, talk to us so that we can see whether the new topic would work for HelenOS during the Google Summer of Code. If not, the idea may still seem interesting to us even outside of the Google Summer of Code program. Besides our regular project ideas, the HelenOS team will also sponsor ideas for selected related projects in the form of mentoring or co-mentoring.
For your convenience, before presenting the entire Ideas List, we provide several views on the ideas grouped by a common theme. Click on the idea of your interest to see the detailed description.
Porting of existing applications to HelenOS, preferably HelenOS build dependencies or applications that can take HelenOS closer to being self-hosting
Ticket | Summary | Component |
---|---|---|
#402 | Port QEMU to HelenOS | helenos/app/other |
#403 | Port Python to HelenOS | helenos/app/other |
#517 | Port the clang (LLVM) compiler to HelenOS | helenos/app/other |
#526 | Port DOSBox to HelenOS | helenos/app/other |
Networking related
Ticket | Summary | Component |
---|---|---|
#194 | Driver for AMD Lance network card clone | helenos/net/other |
#481 | Support for IEEE802.11 wireless networking (a.k.a. WiFi) | helenos/net/other |
#519 | Driver for the family of Realtek Gigabit Ethernet network cards | helenos/net/other |
Device drivers
Ticket | Summary | Component |
---|---|---|
#194 | Driver for AMD Lance network card clone | helenos/net/other |
#358 | IRQ pseudocode compiler | helenos/lib/other |
#415 | Convert the ATA block device driver into a regular DDF driver | helenos/bd/ata |
#519 | Driver for the family of Realtek Gigabit Ethernet network cards | helenos/net/other |
#520 | Driver for VESA-compatible graphics adapter | helenos/gui |
Domain-specific languages and code generation
Ticket | Summary | Component |
---|---|---|
#358 | IRQ pseudocode compiler | helenos/lib/other |
#424 | RPC/IPC generator | helenos-infrastructure |
Improving debugging support
Ticket | Summary | Component |
---|---|---|
#310 | Support for DWARF Debugging Information Format | helenos-debugging |
#313 | Enhancement of user space debugging and observability features | helenos-debugging |
Support for a new architecture, machine or improving support for an existing one
Ticket | Summary | Component |
---|---|---|
#11 | Support PAE on ia32 | helenos/kernel/ia32 |
#40 | Implement support for Sgi Octane (mips64) | helenos/kernel/mips64 |
#425 | Implement support for Lemote Fuloong/Yeeloong (mips64) | helenos/kernel/mips64 |
#523 | Implement support for Raspberry Pi (arm32) | helenos/kernel/arm32 |
#524 | Implement support for Ben NanoNote (mips32) | helenos/kernel/mips32 |
Infrastructure projects
Ticket | Summary | Component |
---|---|---|
#414 | Graceful system shutdown | helenos-infrastructure |
#518 | Switch to Waf build system | helenos-build |
#525 | Service manager | helenos/app/init |
Recapitulation of the Complete Ideas List
{20} HelenOS and ESA Summer of Code in Space 2013
ESA Summer of Code in Space 2013 (SOCIS 2013) is a program run by the European Space Agency. It aims at offering student developers stipends to write code for various space-related open source software projects. Through SOCIS, accepted student applicants are paired with a mentor or mentors from the participating projects, thus gaining exposure to real-world software development scenarios. In turn, the participating projects are able to more easily identify and bring in new developers.
HelenOS
HelenOS is a microkernel-based multiserver operating system designed from scratch. It decomposes key operating system functionality into isolated but intensively communicating server tasks that reside entirely in user space. HelenOS thus provides a computing environment that has several virtues, such as flexibility, increased robustness, well defined explicit interfaces and reduced complexity of individual components as compared to other operating systems.
HelenOS does not aim to be another clone of Unix or some other legacy system and is not POSIX-compliant (even though it may seem POSIX-similar at times). Instead, we try to design it according to our sense for what is the most elegant and right thing to do. What makes HelenOS unique among the other multiserver operating systems is its multiplatform and multiprocessor microkernel. HelenOS runs on seven different processor architectures, ranging from a 32-bit uniprocessor little-endian ARMv4 and commodity PC (x86 and x86-64) to a 64-bit multicore big-endian UltraSPARC T1.
A Bit of History
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.
Who Are We Looking For?
We are looking for students with real interest in operating systems and HelenOS. We are looking for people who will play nicely with our community and by our coding style. We are looking for those who are willing to give their project the necessary time and care. If a student only wants to pass with the minimum effort, HelenOS is not a good match for him or her. We are looking for already experienced C coders as all our projects start at the medium difficulty level and the code itself is not trivial. The successful candidate should be a good communicator, too.
We would like to invite prospective students to demonstrate their abilities and determination to work on a HelenOS project during the ESA Summer of Code in Space 2013 by completing a simple HelenOS task before the student application deadline on August 4. The student should check out the latest mainline sources from our repository, build the system, then either pick up an existing bug or enhancement or think of their own one, implement it, test it and submit the patch / public bzr branch / merge directive to us. Interested students will also need to fill out the application form and attach it in their application.
If a student is accepted, they will be asked to participate in the community mailing list and IRC channel from day one. We will also want them to periodically document their progress via mailing list write-ups and/or blog entries. The mentor will act as a buddy in our team who will monitor their development and provide them with guidance when necessary. However, participating in our community will allow them to receive feedback also from other developers besides their mentor.
Ideas List
The project ideas for the ESA Summer of Code in Space 2013 can be characterized as things that will improve the usability of HelenOS (especially for future use as space on-board software) while building on the core functionality already delivered by us in the past. The individual projects are not excessively difficult and none of them poses an open-questions topic in the academic sense. Instead, each item on the list is rather implementation-oriented and achievable in one trimester. Each idea is accompanied by a short explanation of why we think somebody should work on it.
The Ideas List is just a small subset of all open tickets for HelenOS. If you do not see an appealing topic on this list, you might want to consider looking at the broader list or suggest a completely new topic or a variation on an already existing topic. Remember that the ideas are not set in stone and, after all, it is the student who is going to suggest the idea to us. In any case, talk to us so that we can see whether the new topic would work for HelenOS during the ESA Summer of Code in Space. If not, the idea may still seem interesting to us even outside of the ESA Summer of Code in Space program.
{21} HelenOS and Google Summer of Code 2014
Google Summer of Code is a global program that offers student developers stipends to write code for various open source software projects. We work with many open source, free software, and technology-related groups to identify and fund projects over a three month period. Since its inception in 2005, the program has brought together over 7,500 successful student participants from 97 countries and over 7,000 mentors from over 100 countries worldwide to produce over 50 million lines of code.
HelenOS
HelenOS is a portable microkernel-based multiserver operating system designed from scratch. It decomposes key operating system functionality into isolated but intensively communicating server tasks that reside entirely in user space. HelenOS thus provides a computing environment that has several virtues, such as flexibility, increased robustness, well defined explicit interfaces and reduced complexity of individual components as compared to other operating systems.
HelenOS does not aim to be another clone of Unix or some other legacy system and is not POSIX-compliant (even though it may seem POSIX-similar at times). Instead, we try to design it according to our sense for what is the most elegant and right thing to do. What makes HelenOS unique among the other multiserver operating systems is its multiplatform and multiprocessor microkernel. HelenOS runs on seven different processor architectures, ranging from a 32-bit uniprocessor little-endian ARMv4 and commodity PC (x86 and x86-64) to a 64-bit multicore big-endian UltraSPARC T1.
A Bit of History
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 and 2012, HelenOS became a Google Summer of Code mentoring organization and mentored 8 students in total during their journey through the program. 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.
Who Are We Looking For?
We are looking for students with real interest in operating systems, system-level programming, software design and HelenOS. We are looking for people who will play nicely with our community and by our 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 C coders as all our projects start at the medium difficulty level and the code itself is not trivial. The successful candidate should be a good communicator, too.
We would like to invite prospective students to demonstrate their abilities and determination to work on a HelenOS project during the Google Summer of Code 2014 by completing a simple HelenOS task before the student application deadline on March 21. The student should check out the latest mainline sources of HelenOS, build the system, then either pick an existing bug or enhancement or think of their own improvement, implement it, test it and submit the patch / public bzr branch / merge directive to our mailing list. Students interested in applying for a Google Summer of Code project also need to fill out the application form and attach it to their application.
If a student is accepted, he or she will be asked to participate in the community mailing list and IRC channel from day one. We will also want 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.
Ideas List
The 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.
In the past years we learned that some students may be under the false impression that the projects for HelenOS need to involve kernel programming. In general, this is a false assumption. Because HelenOS is a microkernel-based operating system, most of the projects involve work on the user space parts of the system, such as libraries and server tasks. Having said that, we don't object pure kernel projects either.
The Ideas List is just a small subset of all open tickets for HelenOS. If you do not see an appealing topic on this list, you might want to consider looking at the broader list or suggest a completely new topic or a variation on an already existing topic. Remember that the ideas are not set in stone and, after all, it is the student who is going to suggest the idea to us. In any case, talk to us so that we can see whether the new topic would work for HelenOS during the Google Summer of Code. If not, the idea may still seem interesting to us even outside of the Google Summer of Code program. Besides our regular project ideas, the HelenOS team might also sponsor ideas for related projects in the form of mentoring or co-mentoring (see the list of cross-project ideas for inspiration).
For your convenience, before presenting the entire ideas list, we provide several views on the ideas grouped by a common theme. Click on the idea of your interest to see the detailed description.
Porting of existing applications to HelenOS
Ticket | Summary | Component |
---|---|---|
#402 | Port QEMU to HelenOS | helenos/app/other |
#517 | Port the clang (LLVM) compiler to HelenOS | helenos/app/other |
#526 | Port DOSBox to HelenOS | helenos/app/other |
#573 | Port Bazaar to HelenOS | helenos/app/other |
Networking related
Ticket | Summary | Component |
---|---|---|
#194 | Driver for AMD Lance network card clone | helenos/net/other |
#481 | Support for IEEE802.11 wireless networking (a.k.a. WiFi) | helenos/net/other |
#519 | Driver for the family of Realtek Gigabit Ethernet network cards | helenos/net/other |
#576 | Network file server and network file system client | helenos/srv/vfs |
Graphics stack related
Ticket | Summary | Component |
---|---|---|
#520 | Driver for VESA-compatible graphics adapter | helenos/gui |
#571 | Driver for Broadcom VideoCore IV (Raspberry Pi) | helenos/drv/other |
#572 | USB DisplayLink driver | helenos/drv/other |
Sound related
Ticket | Summary | Component |
---|---|---|
#575 | Intel HD Audio driver | helenos/drv/other |
#577 | AC'97 Audio driver | helenos/drv/other |
Device drivers
Ticket | Summary | Component |
---|---|---|
#194 | Driver for AMD Lance network card clone | helenos/net/other |
#358 | IRQ pseudocode compiler | helenos/lib/other |
#519 | Driver for the family of Realtek Gigabit Ethernet network cards | helenos/net/other |
#520 | Driver for VESA-compatible graphics adapter | helenos/gui |
#571 | Driver for Broadcom VideoCore IV (Raspberry Pi) | helenos/drv/other |
#572 | USB DisplayLink driver | helenos/drv/other |
#575 | Intel HD Audio driver | helenos/drv/other |
#577 | AC'97 Audio driver | helenos/drv/other |
Domain-specific languages and code generation
Ticket | Summary | Component |
---|---|---|
#358 | IRQ pseudocode compiler | helenos/lib/other |
#424 | RPC/IPC generator | helenos-infrastructure |
Improving debugging support
Ticket | Summary | Component |
---|---|---|
#310 | Support for DWARF Debugging Information Format | helenos-debugging |
#313 | Enhancement of user space debugging and observability features | helenos-debugging |
Support for a new architecture, machine or improving support for an existing one
Ticket | Summary | Component |
---|---|---|
#11 | Support PAE on ia32 | helenos/kernel/ia32 |
#40 | Implement support for Sgi Octane (mips64) | helenos/kernel/mips64 |
#425 | Implement support for Lemote Fuloong/Yeeloong (mips64) | helenos/kernel/mips64 |
#524 | Implement support for Ben NanoNote (mips32) | helenos/kernel/mips32 |
Infrastructure projects
Ticket | Summary | Component |
---|---|---|
#414 | Graceful system shutdown | helenos-infrastructure |
#518 | Switch to Waf build system | helenos-build |
#525 | Service manager | helenos/app/init |
Recapitulation of all ideas
{22} HelenOS and Google Summer of Code 2015
Google Summer of Code is a program that offers student developers stipends to write code for various open source projects. We work with many open source, free software, and technology-related groups to identify and fund projects over a three month period. Since its inception in 2005, the program has brought together over 8,500 successful student participants from over countries and over 8,000 mentors from 109 countries worldwide to produce over 55 million lines of code.
HelenOS
HelenOS is a portable microkernel-based multiserver operating system designed from scratch. It decomposes key operating system functionality into isolated but intensively communicating server tasks that reside entirely in user space. HelenOS thus provides a computing environment that has several virtues, such as flexibility, increased robustness, well defined explicit interfaces and reduced complexity of individual components as compared to other operating systems.
HelenOS does not aim to be another clone of Unix or some other legacy operating system and it is by design not POSIX-compliant (even though it may seem POSIX-similar at times). Instead, we try to design it according to our sense for what is the most elegant and right thing to do. What makes HelenOS unique among the other multiserver operating systems is its multiplatform and multiprocessor microkernel. HelenOS runs on eight different processor architectures, ranging from a 32-bit uniprocessor little-endian ARMv4 and commodity PC (x86 and x86-64) to a 64-bit multicore big-endian UltraSPARC T1.
A Bit of History
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. 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.
Who Are We Looking For?
We are looking for students with real interest in operating systems, system-level programming, software design and HelenOS. We are looking for people who will play nicely with our community and by our 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 C coders because all our projects start at the medium difficulty level and the code itself is not trivial. The successful candidate should be a good communicator, too.
We would like to invite prospective students to demonstrate their abilities and determination to work on a HelenOS project during the Google Summer of Code 2015 by completing a simple HelenOS task before the student application deadline on March 27. The student should check out the latest mainline sources of HelenOS, build the system, then either pick an existing bug or enhancement or think of their own improvement, implement it, test it and submit the patch / public bzr branch / merge directive to our mailing list. Students interested in applying for a Google Summer of Code project also need to fill out the application form and attach it to their application.
If a student is accepted, he or she will be invited to participate in the community development mailing list and 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.
Ideas List
The 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.
In the past years we learned that some students may be under the false impression that the projects for HelenOS need to involve kernel programming. In general, this is a false assumption. Because HelenOS is a microkernel-based operating system, most of the projects involve work on the user space parts of the system, such as libraries and server tasks. Having said that, we don't object pure kernel projects either.
The Ideas List is just a small subset of all open tickets for HelenOS. If you do not see an appealing topic on this list, you might want to consider looking at the broader list or suggest a completely new topic or a variation on an existing topic. Remember that the ideas are not set in stone and, after all, it is the student who is going to suggest the idea to us. In any case, talk to us so that we can discuss whether the new topic would work for HelenOS during the Google Summer of Code. If not, the idea may still seem interesting to us even outside of the Google Summer of Code program. Besides our regular project ideas, the HelenOS team might also sponsor ideas for related projects in the form of mentoring or co-mentoring (see the list of cross-project ideas for inspiration).
For your convenience, before presenting the entire ideas list, we provide several views on the ideas grouped by a common theme. Click on the idea of your interest to see the detailed description.
Porting of existing applications to HelenOS
Ticket | Summary | Component |
---|---|---|
#402 | Port QEMU to HelenOS | helenos/app/other |
#517 | Port the clang (LLVM) compiler to HelenOS | helenos/app/other |
#526 | Port DOSBox to HelenOS | helenos/app/other |
#573 | Port Bazaar to HelenOS | helenos/app/other |
Networking related
Ticket | Summary | Component |
---|---|---|
#194 | Driver for AMD Lance network card clone | helenos/net/other |
#576 | Network file server and network file system client | helenos/srv/vfs |
Graphics stack related
Ticket | Summary | Component |
---|---|---|
#520 | Driver for VESA-compatible graphics adapter | helenos/gui |
#571 | Driver for Broadcom VideoCore IV (Raspberry Pi) | helenos/drv/other |
#572 | USB DisplayLink driver | helenos/drv/other |
Sound related
Ticket | Summary | Component |
---|---|---|
#577 | AC'97 Audio driver | helenos/drv/other |
Device drivers
Ticket | Summary | Component |
---|---|---|
#194 | Driver for AMD Lance network card clone | helenos/net/other |
#358 | IRQ pseudocode compiler | helenos/lib/other |
#520 | Driver for VESA-compatible graphics adapter | helenos/gui |
#571 | Driver for Broadcom VideoCore IV (Raspberry Pi) | helenos/drv/other |
#572 | USB DisplayLink driver | helenos/drv/other |
#577 | AC'97 Audio driver | helenos/drv/other |
#621 | Raspberry Pi USB controller driver | helenos/usb/other |
Domain-specific languages and code generation
Ticket | Summary | Component |
---|---|---|
#358 | IRQ pseudocode compiler | helenos/lib/other |
#424 | RPC/IPC generator | helenos-infrastructure |
Improving debugging support
Ticket | Summary | Component |
---|---|---|
#310 | Support for DWARF Debugging Information Format | helenos-debugging |
Support for a new architecture, machine or improving support for an existing one
Ticket | Summary | Component |
---|---|---|
#11 | Support PAE on ia32 | helenos/kernel/ia32 |
#40 | Implement support for Sgi Octane (mips64) | helenos/kernel/mips64 |
#425 | Implement support for Lemote Fuloong/Yeeloong (mips64) | helenos/kernel/mips64 |
#524 | Implement support for Ben NanoNote (mips32) | helenos/kernel/mips32 |
Infrastructure projects
Ticket | Summary | Component |
---|---|---|
#518 | Switch to Waf build system | helenos-build |
Recapitulation of all ideas
{23} HelenOS and ESA Summer of Code in Space 2015
ESA Summer of Code in Space 2015 (SOCIS 2015) is a program run by the European Space Agency. It aims at offering student developers stipends to write code for various space-related open source software projects. Through SOCIS, accepted student applicants are paired with a mentor or mentors from the participating projects, thus gaining exposure to real-world software development scenarios. In turn, the participating projects are able to more easily identify and bring in new developers.
HelenOS
HelenOS is a portable microkernel-based multiserver operating system designed from scratch. It decomposes key operating system functionality into isolated but intensively communicating server tasks that reside entirely in user space. HelenOS thus provides a computing environment that has several virtues, such as flexibility, increased robustness, well defined explicit interfaces and reduced complexity of individual components as compared to other operating systems.
HelenOS does not aim to be another clone of Unix or some other legacy operating system and it is by design not POSIX-compliant (even though it may seem POSIX-similar at times). Instead, we try to design it according to our sense for what is the most elegant and right thing to do. What makes HelenOS unique among the other multiserver operating systems is its multiplatform and multiprocessor microkernel. HelenOS runs on eight different processor architectures, ranging from a 32-bit uniprocessor little-endian ARMv4 and commodity PC (x86 and x86-64) to a 64-bit multicore big-endian UltraSPARC T1.
A Bit of History
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. HelenOS participated in ESA SOCIS 2013.
Who Are We Looking For?
We are looking for students with real interest in operating systems, system-level programming, software design and HelenOS. We are looking for people who will play nicely with our community and by our 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 ESA Summer of Code in Space with the minimum effort, HelenOS is not a good match for him or her. We are looking for already experienced C coders because all our projects start at the medium difficulty level and the code itself is not trivial. The successful candidate should be a good communicator, too.
We would like to invite prospective students to demonstrate their abilities and determination to work on a HelenOS project during the ESA Summer of Code in Space 2015 by completing a simple HelenOS task before the extended student application deadline on May 7. The student should check out the latest mainline sources of HelenOS, build the system, then either pick an existing bug or enhancement or think of their own improvement, implement it, test it and submit the patch / public bzr branch / merge directive to our mailing list. Students interested in applying for a ESA Summer of Code in Space project also need to fill out the application form and attach it to their application.
If a student is accepted, he or she will be invited to participate in the community development mailing list and 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.
Ideas List
The project ideas for the ESA Summer of Code in Space 2015 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.
The Ideas List is just a small subset of all open tickets for HelenOS. If you do not see an appealing topic on this list, you might want to consider looking at the broader list or suggest a completely new topic or a variation on an existing topic. Remember that the ideas are not set in stone and, after all, it is the student who is going to suggest the idea to us. In any case, talk to us so that we can discuss whether the new topic would work for HelenOS during the ESA Summer of Code in Space. If not, the idea may still seem interesting to us even outside of the ESA Summer of Code in Space program.
{24} HelenOS and Google Summer of Code 2016
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 almost 11,000 student participants and 10,000 mentors from over 113 countries worldwide. Google Summer of Code has produced over 50 million lines of code for 515 open source organizations.
HelenOS
HelenOS 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.
HelenOS 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.
HelenOS runs on eight 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.
A Bit of History
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. 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.
Who Are We Looking for?
We are looking for students with real interest in operating systems, system-level programming, software design and HelenOS. We are looking for people who will play nicely with our community and by our 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 C coders because all our projects start at the medium difficulty level and the code itself is not trivial. The successful candidate should be a good communicator, too.
We would like to invite prospective students to demonstrate their abilities and determination to work on a HelenOS project during the Google Summer of Code 2016 by completing a simple HelenOS task before the student application deadline on March 25. The student should check out the latest mainline sources of HelenOS, build the system, then either pick an existing bug or enhancement or think of their own improvement, implement it, test it and submit the patch / public bzr branch / merge directive to our mailing list. Students interested in applying for a Google Summer of Code project also need to fill out the application form and attach it to their application.
If a student is accepted, he or she will be invited to participate in the community development mailing list and 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.
Ideas List
The 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.
In the past years we learned that some students may be under the false impression that the projects for HelenOS need to involve kernel programming. In general, this is a false assumption. Because HelenOS is a microkernel-based operating system, most of the projects involve work on the user space parts of the system, such as libraries and server tasks. Having said that, we don't object pure kernel projects either.
The Ideas List is just a small subset of all open tickets for HelenOS. If you do not see an appealing topic on this list, you might want to consider looking at the broader list or suggest a completely new topic or a variation on an existing topic. Remember that the ideas are not set in stone and, after all, it is the student who is going to suggest the idea to us. In any case, talk to us so that we can discuss whether the new topic would work for HelenOS during the Google Summer of Code. If not, the idea may still seem interesting to us even outside of the Google Summer of Code program. Besides our regular project ideas, the HelenOS team might also sponsor ideas for related projects in the form of mentoring or co-mentoring (see the list of cross-project ideas for inspiration).
For your convenience, before presenting the entire ideas list, we provide several views on the ideas grouped by a common theme. Click on the idea of your interest to see the detailed description.
Porting of existing applications to HelenOS
Ticket | Summary | Component |
---|---|---|
#517 | Port the clang (LLVM) compiler to HelenOS | helenos/app/other |
#526 | Port DOSBox to HelenOS | helenos/app/other |
Networking related
Ticket | Summary | Component |
---|---|---|
#194 | Driver for AMD Lance network card clone | helenos/net/other |
#655 | Networking stabilization campaign | helenos/net/other |
Graphics stack related
Ticket | Summary | Component |
---|---|---|
#571 | Driver for Broadcom VideoCore IV (Raspberry Pi) | helenos/drv/other |
#572 | USB DisplayLink driver | helenos/drv/other |
#652 | Graphics stack (GUI) improvements | helenos/gui |
Sound related
Ticket | Summary | Component |
---|---|---|
#577 | AC'97 Audio driver | helenos/drv/other |
Device drivers
Ticket | Summary | Component |
---|---|---|
#194 | Driver for AMD Lance network card clone | helenos/net/other |
#571 | Driver for Broadcom VideoCore IV (Raspberry Pi) | helenos/drv/other |
#572 | USB DisplayLink driver | helenos/drv/other |
#577 | AC'97 Audio driver | helenos/drv/other |
#621 | Raspberry Pi USB controller driver | helenos/usb/other |
#647 | USB support on BeagleBoard XM and BeagleBone computers | helenos/drv/other |
Domain-specific languages and code generation
Ticket | Summary | Component |
---|---|---|
#358 | IRQ pseudocode compiler | helenos/lib/other |
#424 | RPC/IPC generator | helenos-infrastructure |
Improving debugging support
Ticket | Summary | Component |
---|---|---|
#310 | Support for DWARF Debugging Information Format | helenos-debugging |
#646 | GDB stub for remote debugging | helenos-debugging |
Support for a new architecture, machine or improving support for an existing one
Ticket | Summary | Component |
---|---|---|
#11 | Support PAE on ia32 | helenos/kernel/ia32 |
#40 | Implement support for Sgi Octane (mips64) | helenos/kernel/mips64 |
#425 | Implement support for Lemote Fuloong/Yeeloong (mips64) | helenos/kernel/mips64 |
#524 | Implement support for Ben NanoNote (mips32) | helenos/kernel/mips32 |
#649 | Implement support for Creator Ci40 (mips32) | helenos/kernel/mips32 |
#650 | Implement support for a MikroTik RouterBoard (mips32) | helenos/kernel/mips32 |
#651 | Implement Turris Omnia support (arm32) | helenos/kernel/arm32 |
Infrastructure projects
Ticket | Summary | Component |
---|---|---|
#419 | HelenOS as a Genode platform | helenos/unspecified |
#424 | RPC/IPC generator | helenos-infrastructure |
#518 | Switch to Waf build system | helenos-build |
#648 | Extend dynamic linking support to (an)other architecture(s) | helenos/srv/loader |
#653 | Advanced shell scripting in Bdsh | helenos/app/bdsh |
#654 | C++ support | helenos/unspecified |
Recapitulation of all ideas
{25} HelenOS and Google Summer of Code 2017
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 12,000+ student participants and 11,000 mentors from over 118 countries worldwide. Google Summer of Code has produced 30,000,000+ lines of code for 568 open source organizations.
HelenOS
HelenOS participates in GSoC 2017 as part of the Microkernel Devroom umbrella organization.
HelenOS 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.
HelenOS 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.
HelenOS 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.
A Bit of History
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. 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.
Who Are We Looking for?
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 community and by our 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.
We would like to invite prospective students to demonstrate their abilities and determination to work on HelenOS during the Google Summer of Code 2017 by completing a simple task before the student application deadline on April 3rd 2017. The student should check out the latest mainline sources of HelenOS, build the system, then either pick an existing bug or enhancement or think of their own improvement, implement it, test it and submit the patch / public bzr branch / merge directive to our mailing list.
Students interested in applying for a Google Summer of Code project also need to fill out the application form and attach it to their application.
If a student is accepted, he or she will be invited to participate in the community development mailing list and 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.
Ideas List
The 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.
Note 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.
The Ideas List is just a small subset of all open tickets for HelenOS. If you do not see an appealing topic on this list, you might want to consider looking at the broader list or suggest a completely new topic or a variation on an existing topic. Remember that the ideas are not set in stone and, after all, it is the student who is going to suggest the idea to us. In any case, talk to us so that we can discuss whether the new topic would work for HelenOS during the Google Summer of Code.
For your convenience, before presenting the entire ideas list, we provide several views on the ideas grouped by a common theme. Click on the idea of your interest to see the detailed description.
Porting of existing applications to HelenOS
Ticket | Summary | Component |
---|---|---|
#517 | Port the clang (LLVM) compiler to HelenOS | helenos/app/other |
#526 | Port DOSBox to HelenOS | helenos/app/other |
Networking related
Ticket | Summary | Component |
---|---|---|
#194 | Driver for AMD Lance network card clone | helenos/net/other |
#655 | Networking stabilization campaign | helenos/net/other |
Graphics stack related
Ticket | Summary | Component |
---|---|---|
#571 | Driver for Broadcom VideoCore IV (Raspberry Pi) | helenos/drv/other |
#572 | USB DisplayLink driver | helenos/drv/other |
#652 | Graphics stack (GUI) improvements | helenos/gui |
Sound related
Ticket | Summary | Component |
---|---|---|
#577 | AC'97 Audio driver | helenos/drv/other |
Device drivers
Ticket | Summary | Component |
---|---|---|
#194 | Driver for AMD Lance network card clone | helenos/net/other |
#571 | Driver for Broadcom VideoCore IV (Raspberry Pi) | helenos/drv/other |
#572 | USB DisplayLink driver | helenos/drv/other |
#577 | AC'97 Audio driver | helenos/drv/other |
#621 | Raspberry Pi USB controller driver | helenos/usb/other |
#647 | USB support on BeagleBoard XM and BeagleBone computers | helenos/drv/other |
Domain-specific languages and code generation
Ticket | Summary | Component |
---|---|---|
#358 | IRQ pseudocode compiler | helenos/lib/other |
#424 | RPC/IPC generator | helenos-infrastructure |
Improving debugging support
Ticket | Summary | Component |
---|---|---|
#310 | Support for DWARF Debugging Information Format | helenos-debugging |
#646 | GDB stub for remote debugging | helenos-debugging |
Support for a new architecture, machine or improving support for an existing one
Ticket | Summary | Component |
---|---|---|
#11 | Support PAE on ia32 | helenos/kernel/ia32 |
#40 | Implement support for Sgi Octane (mips64) | helenos/kernel/mips64 |
#425 | Implement support for Lemote Fuloong/Yeeloong (mips64) | helenos/kernel/mips64 |
#524 | Implement support for Ben NanoNote (mips32) | helenos/kernel/mips32 |
#649 | Implement support for Creator Ci40 (mips32) | helenos/kernel/mips32 |
#650 | Implement support for a MikroTik RouterBoard (mips32) | helenos/kernel/mips32 |
#651 | Implement Turris Omnia support (arm32) | helenos/kernel/arm32 |
Infrastructure projects
Ticket | Summary | Component |
---|---|---|
#419 | HelenOS as a Genode platform | helenos/unspecified |
#424 | RPC/IPC generator | helenos-infrastructure |
#518 | Switch to Waf build system | helenos-build |
#648 | Extend dynamic linking support to (an)other architecture(s) | helenos/srv/loader |
#653 | Advanced shell scripting in Bdsh | helenos/app/bdsh |
#654 | C++ support | helenos/unspecified |
Recapitulation of all ideas