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

Changes between Version 11 and Version 12 of StudentTips


Ignore:
Timestamp:
2011-08-26T14:26:07Z (8 years ago)
Author:
Jakub Jermář
Comment:

More levels of tips.

Legend:

Unmodified
Added
Removed
Modified
  • StudentTips

    v11 v12  
    33On this page, we provide tips for authors of HelenOS master and bachelor theses, and various software projects. The tips are based on previous experience in this area. For official guidance, please consult your thesis / project supervisor.
    44
    5 == Content ==
     5== Writing tips ==
     6
     7=== Content ===
    68  * If you provide some sort of HelenOS overview chapter, please do not blindly follow the pretty much outdated 0.2.0 design documentation (i.e. forget about pseudothreads) and stick to the things that seem relevant to your own thesis (e.g. no need to provide in-depth description of the kernel architecture if your focus is on some userspace application). There is also no point in retelling the early history of the project in each thesis.
    79  * If you provide a related work chapter, consider providing comparison with similar multiserver operating systems (if applicable), i.e. the Hurd and MINIX 3. These will be very interesting and useful as you will be comparing apples with apples and not apples with elephants.
    810
    9 == Form ==
     11=== Form ===
    1012  * Always differentiate your own words from words of someone else by providing proper citation information. Never let other people think that some ideas or words are yours whereas in reality you just saw some handy text or used some notoriously known phrase. Note that these things can happen even [http://en.wikipedia.org/wiki/Meme unintentionally].
    1113
    12 == Planning ==
     14=== Planning ===
    1315  * Getting the thesis into a good shape (grammatically, stylistically and visually) can take as much as half of the entire time you reserved for working on the text of the thesis. People don't usually believe this advice or don't take it seriously enough, but then all of them are found to have a very eventful and exciting submission week and the end result is not as good as it might have been if more time was spent on editing the thesis.
    1416  * Most of the time, there will be people willing to proof-read your thesis, so plan ahead to allow enough time for these proof-readers to do you this favor and also to incorporate their suggestions.
    1517
    16 == Implementation ==
     18== Coding tips ==
     19
     20=== Implementation ===
    1721  * Stick to the [http://www.helenos.org/cstyle HelenOS coding style]. We really mean this. Your failure to adhere to the coding style of the surrounding code requires someone else's extra work to perform the cleanup after you. The fact that you may prefer another coding style is quite insignificant in the context of HelenOS. Get over it and use our coding style.
    1822  * Adhere to good coding practices, such as adequate commenting, avoiding dense code, using horizontal spacing as visual delimiter and keeping the block nesting level under control.
     
    2226  * Always use English for writing comments.
    2327
    24 == Source history
     28=== Source history ===
    2529  * Remember that the revision control system does not forget things. Whatever you commit to your local branch will often eventually be merged into the HelenOS mainline repository.
    2630  * Always use English for writing commit logs.
     
    3034  * Don't forget to review your changes before committing them.
    3135
    32 == Interacting with the community ==
     36== Social interaction tips ==
     37
     38=== Interacting with the community ===
    3339  * The HelenOS community can provide invaluable feedback to your ideas so make sure to interact with the community effectively. Simply put, participate on the mailing list and, if possible, attend the monthly project meetings.
    3440  * Prefer open communication on the mailing list over one-to-one private communication of any sort.