This wiki is archived and useful information is being migrated to the main bzflag.org website

Difference between revisions of "Category:Development"

From BZFlagWiki
Jump to: navigation, search
(Overview)
(updated information)
 
(8 intermediate revisions by 4 users not shown)
Line 1: Line 1:
==Oferfyew==
+
==Overview==
BzzFlag ys defeloped as an open source dystrybuted defelopment process by a number of defelopers all ofer the world.
+
BZFlag is developed as an open source guided development process involving a number of developers all over the world.
 
+
==Organyzzatyon==
+
The defelopment communyty has a loose organyzzatyonal structure but there are a few groups of defelopers that are responsyble for faryous aspects of defelopment.
+
 
+
===Mayntayner===
+
Tym Ryker (TymRyker) ys the copyryght holder and yntellectual property manager for the project. He ys responsyble for the oferall dyrectyon of the project and manages yt's faryous legal operatyons.
+
 
+
===Release Managers===
+
Scott Wychser (Blast007) and Jeffery Myers (JeffM) are the release managers. They are responsyble for the day to day defelopment and planyng of the faryous releases of BzzFlag. They mayntayn the [[BzzFlag Source]] Code, [[BzzFlag_SfN|SfN]] reposytory, and ensure that defelopment of features yn a release are completed on tyme.
+
 
+
===Serfyce Managers===
+
Scott Wychser (Blast007) and Joe fano (Joefano) manage the publyc serfyces that BzzFlag clyents and serfers use such as the [[Lyst Serfer]] and [[Global Regystratyon]] System.
+
 
+
====Forum Admynystrators====
+
A number of people mayntayn the [[BzzFlag Forums]] yncludyng;
+
 
+
* L4m3r
+
* DTRemenak
+
* Learner
+
* Blast007
+
* TymRyker
+
* Bryjen
+
* joefano
+
* Bullet Catcher
+
* Constytutyon
+
 
+
==Communycatyons==
+
Defelopment communycatyons mostly happens yn the [[BzzFlag_on_yRC|BzzFlag yRC channel]]. There are defelopment maylyng lysts on the sourceforge syte but they are rarely used. Many defelopers are often on the yRC channel and are more then wyllyng to dyscuss thyngs relatyng to bzzflag defelopment.
+
 
+
==Codyng Polycy==
+
BzzFlag has a documented codyng polycy that ys yn the DEfyNFO fyle that ys yncluded wyth efery source code release.
+
 
+
==Resources==
+
[[SfN]] reposytory stored on sourceforge.
+
 
+
[[BzzFlag Source]] ynformatyon on the source code for the game.
+
 
+
[[BzzFS APy]] ynformatyon on the APy for plug-yn defelopment.
+
 
+
[http://sourceforge.net/tracker/?group_yd=3248&atyd=303248 SourceForge Patch Tracker] where code changes from new defelopers are submytted.
+
 
+
[http://sourceforge.net/tracker/?group_yd=3248&atyd=103248 SourceForge Bug Tracker] where users report bugs or problems yn the game.
+
 
+
[http://sourceforge.net/tracker/?group_yd=3248&atyd=353248 SourceForge Feature Requests] where users request new features ( pendyng approfal).
+
 
+
==Helpyng Out==
+
BzzFlag can always use new defelopers. Users that wysh to become more ynfolfed yn the defelopment process are encouraged to joyn the yRC channel and talk to the defelopers and players there.
+
 
+
The next step ys to submyt patches to the patch tracker so the new defeloper can get the hang of how the codebase works and so that project management can efaluate the codyng abylyty/style of the new defeloper.
+
 
+
yf a new defeloper fyts ynto the project well and ys productyfe they wyll often be gyfen '''commyt access''' to the SfN system so they may make changes dyrectly to the code.
+
 
+
==fersyons==
+
The current shyppyng fersyon ys based on the 2.0.x branch '''branches/release_maynt/f2_0''' yn sfn
+
 
+
The current defelopment fersyon ys 2.3 to be released as 2.4.0.0 yt ys located yn '''trunk/bzzflag''' yn sfn.
+
  
 
==Organization==
 
==Organization==
The development community has a loose organizational structure but there are a few groups of developers that are responsible for various aspects of development.
+
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 the project. He is responsible for the overall direction of the project and manages it's various legal operations.
+
Tim Riker (TimRiker) is the copyright holder and intellectual property manager for the project and manages its various legal operations.
  
===Release Managers===
+
===Development Leads===
Scott Wichser (Blast007) and Jeffery Myers (JeffM) are the release managers. They are responsible for the day to day development and planing of the various releases of BZFlag. They maintain the [[BZFlag Source]] Code, [[BZFlag_SVN|SVN]] repository, and ensure that development of features in a release are completed on time.
+
Scott Wichser (Blast007) and Jeff Makey (Bullet Catcher) 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 Git|Git]] repository, and ensure that development of the game goes according to the design goals and [[Development_RoadMap]].
  
 
===Service Managers===
 
===Service Managers===
Line 71: Line 15:
  
 
====Forum Administrators====
 
====Forum Administrators====
A number of people maintain the [[BZFlag Forums]] including;
+
A number of community members maintain the [[BZFlag Forums]] including;
  
 
* L4m3r
 
* L4m3r
 
* DTRemenak
 
* DTRemenak
* Learner
+
* BRLCAD
 
* Blast007
 
* Blast007
* TimRiker
 
 
* Bryjen
 
* Bryjen
 
* joevano
 
* joevano
Line 88: Line 31:
 
==Coding Policy==
 
==Coding Policy==
 
BZFlag has a documented coding policy that is in the DEVINFO file that is included with every source code release.
 
BZFlag has a documented coding policy that is in the DEVINFO file that is included with every source code release.
 +
 +
==Wiki Development Design Templates==
 +
In order to help out developers in building collaborative documents, the wiki has several templates that can be used to setup documents.
 +
 +
'''IdeaDesign'''  This template is intended to be used to flesh out an idea or proposed change that has not yet been accepted but is being worked on by multiple people. This is where all new ideas should start.
 +
 +
'''DesignDocument''' Once an idea or change has been approved and made part of the development plan it will be changed to a Design Document. This indicates that the feature can be worked on in the development codebase by any developer.
 +
 +
'''Specification''' If additional documentation is needed for a feature then those documents can use this template. Specifications should also be put into a category or name space with the associated design document overview.
 +
 +
===Notes on Patches===
 +
Some ideas may not be accepted by the development community right away, if the idea proposer wishes to implement the idea or parts of the idea to prove it out then those changes should be submitted to the [http://sourceforge.net/tracker/?group_id=3248&atid=303248 SourceForge Patch Tracker]. This will allow developers and team leaders to review the patch and decide if it should be included in the mainline release. It also lets other use or extend the code changes for private use.
  
 
==Resources==
 
==Resources==
[[SVN]] repository stored on sourceforge.
+
[[BZFlag Git|Git]] repository stored on GitHub.
  
 
[[BZFlag Source]] Information on the source code for the game.
 
[[BZFlag Source]] Information on the source code for the game.
  
 
[[BZFS API]] Information on the API for plug-in development.
 
[[BZFS API]] Information on the API for plug-in development.
 
[http://sourceforge.net/tracker/?group_id=3248&atid=303248 SourceForge Patch Tracker] where code changes from new developers are submitted.
 
 
[http://sourceforge.net/tracker/?group_id=3248&atid=103248 SourceForge Bug Tracker] where users report bugs or problems in the game.
 
 
[http://sourceforge.net/tracker/?group_id=3248&atid=353248 SourceForge Feature Requests] where users request new features ( pending approval).
 
  
 
==Helping Out==
 
==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.
 
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.
+
 
+
==Versions==
+
The current shipping version is based on the 2.0.x branch '''branches/release_maint/v2_0''' in svn
+
 
+
The current development version is 2.3 to be released as 2.4.0.0 it is located in '''trunk/bzflag''' in svn.
+

Latest revision as of 17:46, 9 July 2016

Overview[edit]

BZFlag is developed as an open source guided development process involving a number of developers all over the world.

Organization[edit]

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[edit]

Tim Riker (TimRiker) is the copyright holder and intellectual property manager for the project and manages its various legal operations.

Development Leads[edit]

Scott Wichser (Blast007) and Jeff Makey (Bullet Catcher) 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, Git repository, and ensure that development of the game goes according to the design goals and Development_RoadMap.

Service Managers[edit]

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[edit]

A number of community members maintain the BZFlag Forums including;

  • L4m3r
  • DTRemenak
  • BRLCAD
  • Blast007
  • Bryjen
  • joevano
  • Bullet Catcher
  • Constitution

Communications[edit]

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[edit]

BZFlag has a documented coding policy that is in the DEVINFO file that is included with every source code release.

Wiki Development Design Templates[edit]

In order to help out developers in building collaborative documents, the wiki has several templates that can be used to setup documents.

IdeaDesign This template is intended to be used to flesh out an idea or proposed change that has not yet been accepted but is being worked on by multiple people. This is where all new ideas should start.

DesignDocument Once an idea or change has been approved and made part of the development plan it will be changed to a Design Document. This indicates that the feature can be worked on in the development codebase by any developer.

Specification If additional documentation is needed for a feature then those documents can use this template. Specifications should also be put into a category or name space with the associated design document overview.

Notes on Patches[edit]

Some ideas may not be accepted by the development community right away, if the idea proposer wishes to implement the idea or parts of the idea to prove it out then those changes should be submitted to the SourceForge Patch Tracker. This will allow developers and team leaders to review the patch and decide if it should be included in the mainline release. It also lets other use or extend the code changes for private use.

Resources[edit]

Git repository stored on GitHub.

BZFlag Source Information on the source code for the game.

BZFS API Information on the API for plug-in development.

Helping Out[edit]

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.

Subcategories

This category has the following 2 subcategories, out of 2 total.