[Sommaire] [Imprimer]

   1  ====================
   2   Horde: How to Help
   3  ====================
   4  
   5  :Last update:   $Date: 2004/09/24 21:02:01 $
   6  :Revision:      $Revision: 1.4 $
   7  :Contact:       core@horde.org
   8  
   9  There are many ways in which you can help out in the development of any of the
  10  Horde projects. The first and best way you are already doing: you're using
  11  them. One of the keys to a great product is its users. Without users we can't
  12  find bugs or get feedback on what's good and what's bad.
  13  
  14  It is darn near impossible for the developers to test the code on every
  15  Operating System and every different version of Web Browser available to make
  16  sure the code runs smoothly everywhere.  Linux is not Windows, and IE is not
  17  Mozilla, and it is (frequently) difficult to to predict behavior between
  18  platforms/browsers.
  19  
  20  With this said, one of the best ways you can help is to test. If you can help
  21  us smooth out the code across all (or even any) platforms, you're doing a
  22  great service to the project.
  23  
  24  Now, if that's not enough and you want to dig in and help code, you should
  25  first subscribe to the project lists, particularly the general Horde
  26  developers list dev@lists.horde.org (see http://www.horde.org/mail/ for
  27  information on subscribing to the mailing lists).  Additionally, you **MUST**
  28  read the `Horde Coding Standards`_ to ensure that the code your submitting
  29  will want to be analyzed and potentially committed by the developers.  You
  30  should probably read the various README files (for that matter, all the
  31  documentation in the ``docs/`` directory) for the particular application you
  32  are working on also.
  33  
  34  .. _`Horde Coding Standards`: ?f=CODING_STANDARDS.html