Personal tools
HylaFAX The world's most advanced open source fax server

Difference between revisions of "Developers"

(Migration of the revision control system to Git.)
 
(9 intermediate revisions by 4 users not shown)
Line 1: Line 1:
The HylaFAX developer community is always looking for new recruits. Don't be scared, you're welcome to lurk until you feel comfortable! If you're looking to become involved on any level, you should definitely subscribe to to the [http://www.hylafax.org/mailing-lists.html hylafax developers mailing list].
+
The HylaFAX developer community is always looking for new recruits. Don't be scared, you're welcome to lurk until you feel comfortable! If you're looking to become involved on any level, you should definitely subscribe to to the [[Mailing Lists|hylafax developers mailing list]].
  
    The HylaFAX™ developers list is a subscriber-only list. You must subscribe first before posting.
+
==Reporting Bugs==
  
'''Reporting Bugs'''
+
Faithful to our open-source bias, HylaFAX bugs are tracked using [http://www.mozilla.org/projects/bugzilla/ Bugzilla], a product of the [http://www.mozilla.org/ Mozilla Project]. Please do your best to make sure you've really found a bug, and then file it on the HylaFAX Bugzilla, located at [http://bugs.hylafax.org/ http://bugs.hylafax.org/]. To confirm a bug one should first check the mailing list archives for other reports of this issue (and possible resolution) and then post to the developers mailing list (described above). Security-related bugs should be reported to security@hylafax.org in order to avoid exploitation of the problem before it can be publicly resolved.
  
Faithful to our open-source bias, HylaFAX™ bugs are tracked using [http://www.mozilla.org/projects/bugzilla/ Bugzilla], a product of the [http://www.mozilla.org/ Mozilla Project]. Please do your best to make sure you've really found a bug, and then file it on the HylaFAX Bugzilla, located at [http://bugs.hylafax.org/ http://bugs.hylafax.org/]. To confirm a bug one should first check the mailing list archives for other reports of this issue (and possible resolution) and then post to the developers mailing list (described above). Security-related bugs should be reported to security@hylafax.org in order to avoid exploitation of the problem before it can be publicly resolved.
+
==Developer Mailing List==
  
'''CVS'''
+
For now please visit the [[Mailing Lists|Mailing List Page]] for more information.
  
HylaFAX development is controlled by CVS. Read-access is open to all, although write access is not. Unless you're doing a large amount of coding, it is suggested that you post proposed patches and explanations of them on the hylafax-devel mailing list.
+
The HylaFAX developers list is a subscriber-only list. You must subscribe before posting.
  
HylaFAX is currently being maintained on a public CVS server. An up to date copy of the hylafax source tree can be easily obtained by accessing the server as follows:
+
==Git==
 +
 
 +
HylaFAX development is controlled by Git. Read-access is open to all, although write access is not. Unless you're doing a large amount of coding, it is suggested that you post proposed patches and explanations of them on the hylafax-devel mailing list.
 +
 
 +
HylaFAX is currently being maintained on a public Git server. An up to date copy of the hylafax source tree can be easily obtained by accessing the server as follows:
  
 
<pre>
 
<pre>
 
 
     * Browsing:
 
     * Browsing:
  
 
       The latest source code changes can be viewed at anytime from the following url:
 
       The latest source code changes can be viewed at anytime from the following url:
  
           http://www.hylafax.org/cgi-bin/cvsweb.cgi
+
           http://git.hylafax.org/HylaFAX
  
 
     * Downloading:
 
     * Downloading:
  
 
       To do this you need to:
 
       To do this you need to:
         1. Grab a recent copy of the cvs software(client software is sufficient). The latest version can be obtained from the cyclic website:
+
         1. Grab a recent copy of the Git software(client software is sufficient). Many
 +
            UNIX distributions include git, and the latest version can always be obtained
 +
            from:
  
                 http://www.cyclic.com/  
+
                 http://git-scm.com/  
  
         2. Set the CVSROOT environment variable to
+
         2. To checkout the distribution, run the command:
  
                 :pserver:cvs@cvs.hylafax.org:/cvsroot
+
                 git clone git://git.hylafax.org/HylaFAX
  
         3. Run the command:
+
         3. Whenever you want to merge with the latest code changes:
  
                 cvs login
+
                 git pull
 
 
            Enter the password string which is simply "cvs"
 
 
 
        4. To checkout the distribution, run the command:
 
 
 
                cvs co hylafax
 
 
 
        5. Whenever you want to merge with the latest code changes:
 
 
 
                cvs update -d -P
 
  
 
     * Commands:
 
     * Commands:
  
       Some cvs commands that may be of use:
+
       Some Git commands that may be of use:
  
       login login to the cvs server
+
       checkout change to a different branch
      get/checkout downloads a local copy of the requested module
+
       pull bring your working directory up to date with the repository
       update bring your wrking directory up to datec with the repository
+
       add adds a new file or changes to existing files to your local repository
       add adds a new file to the repositroy, requires write access
+
       commit apply (added) changes to your local repository
       commit apply local changes to the repositroy, requires write access
 
 
       diff shows differences between local files and repository
 
       diff shows differences between local files and repository
      history shows reports on commands against the cvs repository
+
       log shows Git log information
       log shows cvs log information
+
       status shows the working tree status
      rdiff used to prepare a diff file between releases
+
      rebase    forward-port local commits to the updated upstream head
       status shows current status if files in repository and local copies
+
       tag applies a tag to your local repository
       tag applies a tag to the repository, requires write access
+
      push      push local commits to official repository, requires write access
 
</pre>
 
</pre>
 +
 +
==Beta Versions of HylaFAX==
 +
The latest information on [[Beta Versions|HylaFAX beta versions]].

Latest revision as of 17:29, 7 August 2009

The HylaFAX developer community is always looking for new recruits. Don't be scared, you're welcome to lurk until you feel comfortable! If you're looking to become involved on any level, you should definitely subscribe to to the hylafax developers mailing list.

Reporting Bugs

Faithful to our open-source bias, HylaFAX bugs are tracked using Bugzilla, a product of the Mozilla Project. Please do your best to make sure you've really found a bug, and then file it on the HylaFAX Bugzilla, located at http://bugs.hylafax.org/. To confirm a bug one should first check the mailing list archives for other reports of this issue (and possible resolution) and then post to the developers mailing list (described above). Security-related bugs should be reported to security@hylafax.org in order to avoid exploitation of the problem before it can be publicly resolved.

Developer Mailing List

For now please visit the Mailing List Page for more information.

The HylaFAX developers list is a subscriber-only list. You must subscribe before posting.

Git

HylaFAX development is controlled by Git. Read-access is open to all, although write access is not. Unless you're doing a large amount of coding, it is suggested that you post proposed patches and explanations of them on the hylafax-devel mailing list.

HylaFAX is currently being maintained on a public Git server. An up to date copy of the hylafax source tree can be easily obtained by accessing the server as follows:

    * Browsing:

      The latest source code changes can be viewed at anytime from the following url:

          http://git.hylafax.org/HylaFAX

    * Downloading:

      To do this you need to:
         1. Grab a recent copy of the Git software(client software is sufficient). Many
            UNIX distributions include git, and the latest version can always be obtained
            from:

                http://git-scm.com/ 

         2. To checkout the distribution, run the command:

                git clone git://git.hylafax.org/HylaFAX

         3. Whenever you want to merge with the latest code changes:

                git pull 

    * Commands:

      Some Git commands that may be of use:

      checkout	change to a different branch
      pull	bring your working directory up to date with the repository
      add	adds a new file or changes to existing files to your local repository
      commit	apply (added) changes to your local repository
      diff	shows differences between local files and repository
      log	shows Git log information
      status	shows the working tree status
      rebase    forward-port local commits to the updated upstream head
      tag	applies a tag to your local repository
      push      push local commits to official repository, requires write access

Beta Versions of HylaFAX

The latest information on HylaFAX beta versions.


This page was last edited on 7 August 2009, at 17:29.

Powered by MediaWiki
Attribution-ShareAlike 2.5

Project hosted by iFAX Solutions