| 6,6 → 6,7 |
|---|
| SPARTAN kernel\footnote{The SPARTAN kernel has been developed by {\JJ} |
| since 2001.} as a foundation for their new operating system. |
| |
| \section{Specification} |
| The team had then worked on a specification\cite{helenos-spec} until |
| March 8, 2005. The specification was based on \MD's draft and |
| incorporated many suggestions from other members of the team. The |
| 37,11 → 38,37 |
|---|
| was also an optional part comprising of three research or experimental |
| topics. We hoped to eventually find time to work on them. |
| |
| \section{Project meetings} |
| After adopting our specification, we started to meet regularily every two weeks |
| for the sake of consultations. The regular meetings were cancelled only during |
| the exam periods and summer holiday. The first meeting took place on April 28, |
| April. There had been twenty project meetings before 1.0.0 release. |
| April. There had been exactly twenty three project meetings before 1.0.0 release. |
| |
| The Faculty of Mathematics and Physics officially opened our project on June 10, |
| 2005. |
| 2005. However, serious collective work on the project, preceeded by individual |
| efforts of some team members, began two months later. |
| |
| \section{Planning work} |
| In the beginning, we structured our work by creating three two-member teams, |
| each dedicated to one new architecture (i.e. amd64, ia64 and ppc32). However, |
| dividing into couples didn't work out for the amd64 and ppc32 teams. In the end, |
| both of those architectures were supported only with one member of respective |
| team. This might have been because of two factors. First, the collective responsibility |
| for the project allowed the less motivated members to work less than others. |
| Second, over the time, some developers profiled out to be good at specific tasks to which |
| they later adhered and were forwarded more similar work. It was generally accepted |
| within the team if one of the couple traded one architecure-specific task for another task |
| on HelenOS. |
| |
| \section{Kernel camps} |
| There were two really important moments in our development process. Both of them |
| took place in Harrachov, Czech Republic, where five team members moved two times, each |
| time for a week of full-time intensive HelenOS development. These actions were |
| called Kernel Camp 2005 and Winter Camp 2006. The former camp took place in August 2005 |
| and was focused on getting all the architectures into our source tree and deepening |
| their support. The latter camp took place in March 2006 and was dedicated to userspace |
| support. In fact, we made the second camp the deadline for userspace milestone. With the |
| exception of ppc32, all ports had some support for userspace prior to the second camp. |
| Both of the camps moved the project miles ahead. |
| |
| |