Changes between Version 31 and Version 32 of FAQ

Timestamp:

2016-01-08T14:57:01Z (9 years ago)

Author:

Martin Decky

Comment:

extend some of the answers

FAQ

@@ -28 +28 @@
 === What does it do, from an end-user's perspective? ===
 
-We have a command line and a simple graphical user interface which allow you to manipulate files, run applications and mount file systems from disks and disk images. You can play Tetris or edit text files. HelenOS supports multi-national text throughout thanks to using UCS (i.e. Unicode). We also have networking so you can run a simple webserver on HelenOS or control HelenOS remotely over network. HelenOS can play some music for you, too. We have ported some third-party development tools, among which are GCC, binutils, Python and pcc.
+We have a command line and a simple graphical user interface which allow you to manipulate files, run applications and mount file systems from disks and disk images. You can play Tetris or edit text files. HelenOS supports multi-national text throughout thanks to using UCS (i.e. Unicode). We also have networking so you can run a simple web server on HelenOS or control HelenOS remotely over the network. HelenOS can play some music for you, too. We have ported some third-party development tools, among which are GCC, binutils, Python and pcc.
 
 === What do you aim for with HelenOS? ===
 
-Mainly two things. One is to create a fully usable operating system (i.e. a system that could be used for at least some everyday task, for example as a router, server, PDA or desktop) that would also allow us to experiment with new ideas and approaches. The other is to have fun.
+Mainly three things. One is to create a fully usable operating system (i.e. a system that could be used for at least some everyday tasks, for example to act as a router, a server, a PDA or a desktop), The second goal is to be able to experiment with new ideas and approaches in operating system design and implementation on a system that is designed for practical usability. Last, but not least, the goal of developing HelenOS is to have fun.
 
 === How is HelenOS development organized? ===
 
-HelenOS development is community-driven. The primary communication medium for developers is our mailing list. Since most developers are currently based in Prague (or vicinity), we hold developer meetings in Prague once every month. Minutes are usually published on the mailing list.
+HelenOS development is community-driven, with a core team of long-time developers and a loose group of contributors. The primary communication medium for all developers and contributors is our [http://www.helenos.org/list development mailing list]. Since most long-time developers are currently based in Prague (or vicinity), we hold developer meetings in Prague once every month. Minutes are usually published on the mailing list. The decision processes in the HelenOS community could be described as open and consensus-seeking, but meritocratic. A working piece of code weights more than thousand words, but the code must be well-intented, well-designed, well-implemented and well-documented.
 
 === Where is HelenOS source code kept? ===
 
-HelenOS source code is managed with [http://bazaar.canonical.com/en/ Bazaar VCS]. We have a central repository which is considered as the most current code base. Several developers also have their private development branches which are publicly viewable.
+HelenOS source code is currently managed with [http://bazaar.canonical.com/en/ Bazaar DVCS]. Bazaar is distributed and similar in operation to Git or Mercurial. We have a [wiki:BazaarWorkflow central repository] which is considered as the most current official code base. Several developers also have their private development branches which are publicly viewable (usually on [https://code.launchpad.net/helenos launchpad]). A switch from Bazaar to Git is planned for the near future.
 
 === I would like to contribute to HelenOS. Where should I start? ===