Getting involved!
====================================

The *Clever Team* is usually on-line at IRC #clever (irc.freenode.net)

Have you never tried IRC? Test it! http://webchat.freenode.net/

Mailing list
-----------------

Our mailing list is http://groups.google.com/group/clever-lang

We often have discussions on IRC, though that's not always the best choice.
Using a group may allow more people to follow the development process of the project.

Documentation
---------------

Help us revising and writing docs!

**Documentation repository:** https://github.com/clever-lang/clever-doc


Core Development
-------------------

Coding standards
###################

We mostly code based on the *Google C++ Style Guide* [#f1]_, which seems sane
enough.
The *LLVM* [#f2]_ one is also quite nice.

.. epigraph::

  Use the .cc extension for C++ source files and .h for C++ headers,
  hopefully your compiler is smart enough to identify C++ source inside
  a .h (don't worry, GCC and Clang are!). Oh, I almost forgot, please
  use tabs instead of spaces, UTF-8 file encoding and UNIX file endings
  (Line feed a.k.a. \n).

If you don't know how to contribute, but know how to code, it'd be nice if you
could implement one of the ideas from our whishlist:
`TODO List & Ideas <https://github.com/clever-lang/clever/wiki/TODO-List-&-Ideas>`_

**Git help:** - `Fork a repo <http://help.github.com/fork-a-repo/>`_ - `Send pull requests <http://help.github.com/send-pull-requests/>`_


**Source code repository:** https://github.com/clever-lang/clever

.. [#f1] `Google C++ Style Guide <http://google-styleguide.googlecode.com/svn/trunk/cppguide.xml>`_

.. [#f2] `LLVM Coding Standards <http://llvm.org/docs/CodingStandards.html>`_