This wiki is archived and useful information is being migrated to the main bzflag.org website
Difference between revisions of "Category:Development"
m (→Release Managers) |
(Update to current data, mention 2.4.2, roadmap, etc..) |
||
Line 1: | Line 1: | ||
==Overview== | ==Overview== | ||
− | BZFlag is developed as an open source | + | BZFlag is developed as an open source guided development process involving a number of developers all over the world. |
==Organization== | ==Organization== | ||
− | + | Open source development tends to not have as formal a structure as traditional development, but the bzflag project does have a group of developers that are responsible for various aspects of projet. | |
− | ===Maintainer=== | + | ===Copyright Maintainer=== |
− | Tim Riker (TimRiker) is the copyright holder and intellectual property manager for | + | Tim Riker (TimRiker) is the copyright holder and intellectual property manager for the project and manages its various legal operations. |
− | === | + | ===Development Leads=== |
− | Scott Wichser (Blast007) and Jeffery Myers (JeffM) are the | + | Scott Wichser (Blast007) and Jeffery Myers (JeffM) are the development leads. They are responsible for the day to day development and planning of the various releases of BZFlag. They maintain the [[BZFlag Source]] Code, [[BZFlag_SVN|SVN]] repository, and ensure that development of the game goes according to the design goals and [[Development_RoadMap]]. |
===Service Managers=== | ===Service Managers=== | ||
Line 15: | Line 15: | ||
====Forum Administrators==== | ====Forum Administrators==== | ||
− | A number of | + | A number of community members maintain the [[BZFlag Forums]] including; |
* L4m3r | * L4m3r | ||
* DTRemenak | * DTRemenak | ||
− | * | + | * BRLCAD |
* Blast007 | * Blast007 | ||
− | |||
* Bryjen | * Bryjen | ||
* joevano | * joevano | ||
Line 49: | Line 48: | ||
BZFlag can always use new developers. Users that wish to become more involved in the development process are encouraged to join the IRC channel and talk to the developers and players there. | BZFlag can always use new developers. Users that wish to become more involved in the development process are encouraged to join the IRC channel and talk to the developers and players there. | ||
− | The next step is to submit patches to the patch tracker so the new developer can get the hang of how the codebase works and so that project management can evaluate the coding ability/style of the new developer. | + | The next step is to submit patches to the patch tracker so the new developer can get the hang of how the codebase works and so that project management can evaluate the coding ability/style of the new developer. The best way to get started is to take a look at the bugs in the Bug Tracker. |
If a new developer fits into the project well and is productive they will often be given '''commit access''' to the SVN system so they may make changes directly to the code. | If a new developer fits into the project well and is productive they will often be given '''commit access''' to the SVN system so they may make changes directly to the code. | ||
==Versions== | ==Versions== | ||
− | The current shipping version is based on the 2. | + | The current shipping version is based on the 2.4.2 tag '''tags/v2_4_2/''' in svn |
− | The current development version is 2.3 | + | The current development version is 2.4.3 and is maintenance for the 2.4.x line, it is located in '''trunk/bzflag''' in svn. |
Revision as of 06:44, 9 February 2013
Contents
Overview
BZFlag is developed as an open source guided development process involving a number of developers all over the world.
Organization
Open source development tends to not have as formal a structure as traditional development, but the bzflag project does have a group of developers that are responsible for various aspects of projet.
Copyright Maintainer
Tim Riker (TimRiker) is the copyright holder and intellectual property manager for the project and manages its various legal operations.
Development Leads
Scott Wichser (Blast007) and Jeffery Myers (JeffM) are the development leads. They are responsible for the day to day development and planning of the various releases of BZFlag. They maintain the BZFlag Source Code, SVN repository, and ensure that development of the game goes according to the design goals and Development_RoadMap.
Service Managers
Scott Wichser (Blast007) and Joe Vano (JoeVano) manage the public services that BZFlag clients and servers use such as the List Server and Global Registration System.
Forum Administrators
A number of community members maintain the BZFlag Forums including;
- L4m3r
- DTRemenak
- BRLCAD
- Blast007
- Bryjen
- joevano
- Bullet Catcher
- Constitution
Communications
Development communications mostly happens in the BZFlag IRC channel. There are development mailing lists on the sourceforge site but they are rarely used. Many developers are often on the IRC channel and are more then willing to discuss things relating to bzflag development.
Coding Policy
BZFlag has a documented coding policy that is in the DEVINFO file that is included with every source code release.
Resources
SVN repository stored on sourceforge.
BZFlag Source Information on the source code for the game.
BZFS API Information on the API for plug-in development.
SourceForge Patch Tracker where code changes from new developers are submitted.
SourceForge Bug Tracker where users report bugs or problems in the game.
SourceForge Feature Requests where users request new features ( pending approval).
Helping Out
BZFlag can always use new developers. Users that wish to become more involved in the development process are encouraged to join the IRC channel and talk to the developers and players there.
The next step is to submit patches to the patch tracker so the new developer can get the hang of how the codebase works and so that project management can evaluate the coding ability/style of the new developer. The best way to get started is to take a look at the bugs in the Bug Tracker.
If a new developer fits into the project well and is productive they will often be given commit access to the SVN system so they may make changes directly to the code.
Versions
The current shipping version is based on the 2.4.2 tag tags/v2_4_2/ in svn
The current development version is 2.4.3 and is maintenance for the 2.4.x line, it is located in trunk/bzflag in svn.
Subcategories
This category has the following 2 subcategories, out of 2 total.
Pages in category "Development"
The following 24 pages are in this category, out of 24 total.