This site has been retired. For up to date information, see handbook.gnome.org or gitlab.gnome.org.


[Home] [TitleIndex] [WordIndex

You are probably enrolled in a computer science course. You have learnt or learning C right now. You have heard about Open Source, Linux, GNOME and interested to try it out.

But you have always worked all your life in (cough...) an alien operating system....

Welcome to the exciting world of Linux, GNU, GNOME :-)

You are not alone.

This page attempts to arm you with the bare essentials that you need to know to get started off towards fixing your first bug / contributing the first line of code to the community. It also provides you pointers for good sources of further learning - setting you off on a never-ending, exciting journey.

The basic tools in your box that you will use in your craft are :

tells you all that you need to know (and may never need to know) but you can learn the basics for everyday use from here.

<Your editor> quick reference card  - print a copy and tape it to your desk. You now have access to most of the commands you would ever use, at a single glance.

generating diffs and sending patches ( and after a while, when you have arrived :-) , you will start committing them as well ). For starters, look hard at  cvs update  and  cvs diff .

* find, grep, diff and patch - your best friends - Use man/info and learn them well.

   Tip : An extremely useful (and used) command 
            find <your module directory>  -name '*.[ch]' |xargs grep -n <your search term> | less

* Learn the code naming and formatting conventions and patch generation guidelines of the module which you are hacking on. You can find the information on Evolution's guidelines here.


2024-10-23 10:59