Category:Development - Revision history

Zehra: updated information

2016-07-09T17:46:34Z

updated information

← Older revision		Revision as of 17:46, 9 July 2016
Line 9:		Line 9:

	===Development Leads===		===Development Leads===
	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_SVN~~\|~~SVN~~]] repository, and ensure that development of the game goes according to the design goals and [[Development_RoadMap]].		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 45:		Line 45:

	==Resources==		==Resources==
	[[~~SVN~~]] repository stored on ~~Source Forge~~.		[[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==
Line 61:		Line 55:

	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.		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.~~

JeffM2501 at 18:45, 12 April 2015

2015-04-12T18:45:34Z

← Older revision		Revision as of 18:45, 12 April 2015
Line 9:		Line 9:

	===Development Leads===		===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, [[BZFlag_SVN\|SVN]] repository, and ensure that development of the game goes according to the design goals and [[Development_RoadMap]].		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_SVN\|SVN]] repository, and ensure that development of the game goes according to the design goals and [[Development_RoadMap]].

	===Service Managers===		===Service Managers===

JeffM2501: Add notes on the various dev templates and when each should be used, and point out the patch tracker for submissions of code for new ideas

2013-02-10T08:38:48Z

Add notes on the various dev templates and when each should be used, and point out the patch tracker for submissions of code for new ideas

← Older revision		Revision as of 08:38, 10 February 2013
Line 31:		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~~.		[[SVN]] repository stored on Source Forge.

	[[BZFlag Source]] Information on the source code for the game.		[[BZFlag Source]] Information on the source code for the game.

JeffM2501: Update to current data, mention 2.4.2, roadmap, etc..

2013-02-09T06:44:50Z

Update to current data, mention 2.4.2, roadmap, etc..

← Older revision		Revision as of 06:44, 9 February 2013
Line 1:		Line 1:
	==Overview==		==Overview==
	BZFlag is developed as an open source ~~distributed~~ development process by a number of developers all over the world.		BZFlag is developed as an open source guided development process involving a number of developers all over the world.

	==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 its 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 planning 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 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 ~~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 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.0.~~x branch~~ '''~~branches~~/~~release_maint~~/~~v2_0~~''' in svn		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 ~~to be released as~~ 2.4.~~0.0~~ it is located in '''trunk/bzflag''' 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.

Khonkhortisan: /* Release Managers */

2013-01-06T03:57:52Z

Release Managers

← Older revision		Revision as of 03:57, 6 January 2013
Line 9:		Line 9:

	===Release Managers===		===Release Managers===
	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 Jeffery Myers (JeffM) are the release managers. 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 features in a release are completed on time.

	===Service Managers===		===Service Managers===

Khonkhortisan: /* Maintainer */

2013-01-06T03:57:19Z

Maintainer

← Older revision		Revision as of 03:57, 6 January 2013
Line 6:		Line 6:

	===Maintainer===		===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. He is responsible for the overall direction of the project and manages its various legal operations.

	===Release Managers===		===Release Managers===

A11: Undo revision 7880 by 88.198.240.139 (talk)

2011-07-25T04:07:39Z

Undo revision 7880 by 88.198.240.139 (talk)

@@ 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 distributed development process by a number of developers all over the world.
 ==Organization==

A11: Undo revision 7881 by 173.236.27.154 (talk)

2011-07-25T04:07:07Z

Undo revision 7881 by 173.236.27.154 (talk)

@@ Line 109: / Line 109: @@
 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.
-==Oferfyew==
+==Versions==
-BzzFlag ys defeloped as an open source dystrybuted defelopment process by a number of defelopers all ofer the world.
+The current shipping version is based on the 2.0.x branch '''branches/release_maint/v2_0''' in svn
-==Organyzzatyon==
+The current development version is 2.3 to be released as 2.4.0.0 it is located in '''trunk/bzflag''' in svn.

173.236.27.154: /* Versions */

2011-07-25T03:43:22Z

Versions

@@ Line 109: / Line 109: @@
 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==
+==Oferfyew==
-The current shipping version is based on the 2.0.x branch '''branches/release_maint/v2_0''' in svn
+BzzFlag ys defeloped as an open source dystrybuted defelopment process by a number of defelopers all ofer the world.
-The current development version is 2.3 to be released as 2.4.0.0 it is located in '''trunk/bzflag''' in svn.
+==Organyzzatyon==

88.198.240.139: /* Overview */

2011-07-25T03:41:27Z

Overview

@@ Line 1: / Line 1: @@
-==Overview==
+==Oferfyew==
-BZFlag is developed as an open source distributed development process by a number of developers all over the world.
+BzzFlag ys defeloped as an open source dystrybuted defelopment process by a number of defelopers all ofer the world.
 ==Organization==