Changes between Version 10 and Version 11 of Be a CIVL developer


Ignore:
Timestamp:
01/09/17 16:15:27 (9 years ago)
Author:
siegel
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Be a CIVL developer

    v10 v11  
    22== How to become a CIVL developer ==
    33* If you are interested in contributing to the development of CIVL, send an email to civl-users@googlegroups.com expressing your interest, and we'll get back to you.   We can use help in many areas, including testing and creating new examples, and we are very open to new ideas on all aspects of the project.
     4* The lead developer will perform the following tasks:
     5 * Add you to the civl-dev@googlegroups.com email list.  You will be able to read and post messages to this group.   Use it to discuss any development issues.
     6 * Create a Subversion account for you in the appropriate projects (CIVL, ABC, SARL, GMC).  You will then be able to commit to the `branches` directories in those repositories.  (All of the repositories are already world-readable.)
     7 * Create a Trac account for you.  You will then be able to create and modify bug/issue tickets, and write to the Wiki.  (The tickets and Wiki are already world-readable.)
    48
    59== How to make a changes or additions to CIVL ==
    6 1. Talk with the developers first, by sending email to civl-dev@googlegroups.com.  Explain what you want to do, and listen to the feedback.
     101. To make any changes or additions to CIVL, you must first become a CIVL developer.   See above.
     111. Before embarking on any major changes or additions, talk to the other developers.  This is best done using the email list civl-dev@googlegroups.com.  Explain what you want to do, and listen to the feedback.
    7121. Create a new branch for the new features you want to add into CIVL.  Name your branch anything you like and create it in the branches directory of the repository.
    8131. Proceed with development of your branch, committing as often as you like.  Periodically, merge changes from the trunk into your branch, and resolve any conflicts that result.  This will make it much easier to integrate your branch into the trunk later on.  Be sure to follow the CIVL  [wiki:"Coding Standards"] and the [wiki:"Coding Standards for CIVL models"].