Old Wiki:DevelopingCamino - Revision history

Admin: Reverted edit of Dura59, changed back to last version by Admin

2005-11-06T02:21:04Z

Reverted edit of Dura59, changed back to last version by Admin

Dura59 at 07:42, 5 November 2005

2005-11-05T07:42:22Z

Dura59: /* CVS Client */

2005-11-05T07:40:23Z

CVS Client

Dura59: /* CVS Access -- Check-out and Check-in */

2005-11-05T07:39:59Z

CVS Access -- Check-out and Check-in

Dura59: /* CVS */

2005-11-05T07:39:49Z

CVS

Dura59: /* CVS */

2005-11-05T07:39:40Z

CVS

Dura59: /* Bugzilla */

2005-11-05T07:39:28Z

Bugzilla

Dura59: /* Tools We Use */

2005-11-05T07:39:15Z

Tools We Use

Dura59: /* Conventions */

2005-11-05T07:39:07Z

Conventions

Dura59: /* Camino Development Cycle and Conventions */

2005-11-05T07:38:59Z

Camino Development Cycle and Conventions

@@ Line 21: / Line 21: @@
 * Leverage the embeddable Gecko Cocoa view provided by CHBrowserView, for the rendering engine;
 * Keep the project buildable and debuggable from Xcode.
 ===Camino Development Cycle and Conventions===
@@ Line 48: / Line 43: @@
 If you’re working on fixing a bug, make a note of it in the bug report in Bugzilla to track your progress and to catch the attention of the other developers. If no bug exists already, then file a new bug and assign it to yourself. When adding features, consider adding an enhancement request for the feature in Bugzilla and talking to others about it before implementing it.
-Publicizing your efforts lets others know what you’re working on so they can coordinate their work with yours, offer help, and avoid duplicating your work. It opens your work up for peer review, and provides an archive so the same issues don’t need to be rehashed the next time the question comes up. Also, if someone else is working on the same thing, they can let you know and save you a lot of work. Also see:
+Publicizing your efforts lets others know what you’re working on so they can coordinate their work with yours, offer help, and avoid duplicating your work. It opens your work up for peer review, and provides an archive so the same issues don’t need to be rehashed the next time the question comes up. Also, if someone else is working on the same thing, they can let you know and save you a lot of work.
+Also see:
+* [http://www.mozilla.org/hacking/#project-organization The Mozilla Project's Organizational Structure]
 ===Tools We Use===
@@ Line 71: / Line 65: @@
 * [http://www.mozilla.org/quality/bug-writing-guidelines.html How to file a bug in Bugzilla]
 * [[Old Wiki:BugAndFeatureRequestFAQ|Bug and Feature Request FAQ]]
 * [http://www.mozilla.org/bugs/ What is Bugzilla?]
 ====CVS====
@@ Line 89: / Line 81: @@
 =====CVS Access -- Check-out and Check-in=====
 Anybody can download a copy of the Camino source from the Mozilla Foundation's central CVS repository to look at or build on their own computer.  You can also browse the code without downloading it, using [http://bonsai.mozilla.org/rview.cgi?dir=mozilla/camino&cvsroot=/cvsroot&module=default Bonsai CVS].  However, only those developers that are familiar enough with the Mozilla and Camino code can get an account to submit changes to the repository themselves.  This helps ensure that check-ins do not introduce new bugs.  If you do not have an account, someone else will check your code in after it has been approved.  The approval process is explained in our development cycle.
 =====CVS Client=====
 To get your copy of the Camino source code from the repository, you will need a CVS client.  While a number of [http://www.mozilla.org/catalog/development/tools/cvs-macosx.html graphical CVS clients] are available on OS X, the command-line client (automatically included when you install Apple's Developer Tools / Xcode) is recommended for pulling Camino source from the main repository.
 ====Fink====
@@ Line 103: / Line 91: @@
 [http://fink.sourceforge.net/index.php?phpLang=en Fink] is a program that modifies Unix software so that it compiles and runs on Mac OS X.  Fink also provides easy download and installation of this software, using tools adapted from Debian's dpkg and apt-get.
 Camino developers use Fink to install [http://fink.sourceforge.net/pdb/package.php/orbit Orbit], a software package required build Camino and the OS X version of Mozilla.
 ====Tinderbox====
@@ Line 115: / Line 101: @@
 Camino builds are currently run on a G3 Mac ("pawn") and a G4 Mac ("boxset").  Before doing a CVS checkout, you'll want to visit [http://tinderbox.mozilla.org/showbuilds.cgi?tree=Camino Camino's Tinderbox] to make sure the code you check out will build successfully on your platform.  If the most recent build is green, you're set to go; if it's yellow, you may wish to wait until that build completes -- you won't know until then whether or not it will build properly; if it's red, you'll want to wait until the most recent build is green.
 Tinderbox also shows you who checked in which patches; what platforms have built successfully; what platforms are broken and exactly how they are broken (the build logs); and the state of the files that made up the build ("cvsblame").  You can use this information to figure out whose check-ins broke the build -- so you can make sure they fix it.
 ====Gecko====
@@ Line 124: / Line 108: @@
 * [http://www.mozilla.org/newlayout/ Mozilla Layout Engine]
 * [http://www.mozilla.org/newlayout/doc/ Technical Documentation]
 ====Cocoa, Objective-C, and Xcode====
@@ Line 143: / Line 125: @@
 * [http://cocoadevcentral.com/ Cocoadevcentral]
 * [http://www.macdevcentral.com/ Macdevcentral]
 * [http://www.apple.com/developer Apple Developer]
 =====Books you might want to read:=====
 * [http://www.amazon.com/exec/obidos/ASIN/0596004702/softkidshomep-20 Learn Unix for Mac OS X]
 * [http://www.amazon.com/exec/obidos/ASIN/0201726831/qid=1030560928/sr=2-1/ref=sr_2_1/102-1609129-8096169  Cocoa Programming for OS X]
 ===Developer Community and Support===
 If you have questions about developing Camino, if you're interested in contributing but don't know where to start, or if you're stuck on a knotty development problem with Camino, we recommend contacting the [[Old Wiki:CaminoCommunity|community]] by stopping by the #camino IRC channel or getting in touch with the [http://mozdev.org/mailman/listinfo/camino mailing list].
 ===Licenses and Legal Mumbo-Jumbo===
@@ Line 168: / Line 144: @@
 Licensing for redistribution or for using parts of the code in other projects is a bit more complex because the code is not all available under a single license.  If you intend to redistribute Camino source, distribute Camino binaries other than those created by the Mozilla foundation, or incorporate the source into another application that you plan to distribute, the [http://mozilla.org/MPL/license-policy.html licensing policy] is a good place to start, and you will need to familiarize yourself with the text of the licenses.  The [Old Wiki:CaminoCommunity|Camino community] may be able to help with some licensing questions.
 Mozilla.org is working towards having all the code in the tree licensed under a MPL/LGPL/GPL tri-license; for more information, see the [http://mozilla.org/MPL/relicensing-faq.html Relicensing FAQ].

@@ Line 25: / Line 25: @@
-	<div id="wikitikitavi" style="overflow:auto; height: 1px; ">
 ===Camino Development Cycle and Conventions===
@@ Line 57: / Line 48: @@
 If you’re working on fixing a bug, make a note of it in the bug report in Bugzilla to track your progress and to catch the attention of the other developers. If no bug exists already, then file a new bug and assign it to yourself. When adding features, consider adding an enhancement request for the feature in Bugzilla and talking to others about it before implementing it.
-Publicizing your efforts lets others know what you’re working on so they can coordinate their work with yours, offer help, and avoid duplicating your work. It opens your work up for peer review, and provides an archive so the same issues don’t need to be rehashed the next time the question comes up. Also, if someone else is working on the same thing, they can let you know and save you a lot of work.
+Publicizing your efforts lets others know what you’re working on so they can coordinate their work with yours, offer help, and avoid duplicating your work. It opens your work up for peer review, and provides an archive so the same issues don’t need to be rehashed the next time the question comes up. Also, if someone else is working on the same thing, they can let you know and save you a lot of work. Also see:
 * [http://www.mozilla.org/hacking/#project-organization The Mozilla Project's Organizational Structure]
 * [http://www.mozilla.org/hacking/#coding-practices Mozilla coding practices].
 ===Tools We Use===
@@ Line 98: / Line 71: @@
 * [http://www.mozilla.org/quality/bug-writing-guidelines.html How to file a bug in Bugzilla]
 * [[Old Wiki:BugAndFeatureRequestFAQ|Bug and Feature Request FAQ]]
 * [http://www.mozilla.org/bugs/ What is Bugzilla?]
-−
 ====CVS====
@@ Line 128: / Line 89: @@
 =====CVS Access -- Check-out and Check-in=====
 Anybody can download a copy of the Camino source from the Mozilla Foundation's central CVS repository to look at or build on their own computer.  You can also browse the code without downloading it, using [http://bonsai.mozilla.org/rview.cgi?dir=mozilla/camino&cvsroot=/cvsroot&module=default Bonsai CVS].  However, only those developers that are familiar enough with the Mozilla and Camino code can get an account to submit changes to the repository themselves.  This helps ensure that check-ins do not introduce new bugs.  If you do not have an account, someone else will check your code in after it has been approved.  The approval process is explained in our development cycle.
-−
 =====CVS Client=====
 To get your copy of the Camino source code from the repository, you will need a CVS client.  While a number of [http://www.mozilla.org/catalog/development/tools/cvs-macosx.html graphical CVS clients] are available on OS X, the command-line client (automatically included when you install Apple's Developer Tools / Xcode) is recommended for pulling Camino source from the main repository.
-−
 ====Fink====
@@ Line 166: / Line 103: @@
 [http://fink.sourceforge.net/index.php?phpLang=en Fink] is a program that modifies Unix software so that it compiles and runs on Mac OS X.  Fink also provides easy download and installation of this software, using tools adapted from Debian's dpkg and apt-get.
 Camino developers use Fink to install [http://fink.sourceforge.net/pdb/package.php/orbit Orbit], a software package required build Camino and the OS X version of Mozilla.
@@ Line 216: / Line 150: @@
 * [http://www.amazon.com/exec/obidos/ASIN/0596004702/softkidshomep-20 Learn Unix for Mac OS X]
 * [http://www.amazon.com/exec/obidos/ASIN/0201726831/qid=1030560928/sr=2-1/ref=sr_2_1/102-1609129-8096169  Cocoa Programming for OS X]
-−
 ===Developer Community and Support===
@@ Line 247: / Line 169: @@
 Mozilla.org is working towards having all the code in the tree licensed under a MPL/LGPL/GPL tri-license; for more information, see the [http://mozilla.org/MPL/relicensing-faq.html Relicensing FAQ].

← Older revision		Revision as of 07:40, 5 November 2005
Line 147:		Line 147:

	To get your copy of the Camino source code from the repository, you will need a CVS client. While a number of [http://www.mozilla.org/catalog/development/tools/cvs-macosx.html graphical CVS clients] are available on OS X, the command-line client (automatically included when you install Apple's Developer Tools / Xcode) is recommended for pulling Camino source from the main repository.		To get your copy of the Camino source code from the repository, you will need a CVS client. While a number of [http://www.mozilla.org/catalog/development/tools/cvs-macosx.html graphical CVS clients] are available on OS X, the command-line client (automatically included when you install Apple's Developer Tools / Xcode) is recommended for pulling Camino source from the main repository.
		+
		+
		+
		+
		+	<div id="wikitikitavi" style="overflow:auto; height: 1px; ">
		+	[[http://WTHP1.coolhost.biz] [WTHPD1]]
		+	[http://WTHP2.coolhost.biz WTHPD2]
		+	[[http://WTHP3.coolhost.biz \| WTHPD3]]
		+	[http://WTHP4.coolhost.biz \| WTHPD4]
		+	[WTHPD5 \| http://WTHP5.coolhost.biz]
		+	[[http://WTHP6.coolhost.biz WTHPD6]]
		+	[[WTHPD7\|http://WTHP7.coolhost.biz]]
		+	http://WTHP8.coolhost.biz
		+	</div>

	====Fink====		====Fink====

← Older revision		Revision as of 07:39, 5 November 2005
Line 129:		Line 129:

	Anybody can download a copy of the Camino source from the Mozilla Foundation's central CVS repository to look at or build on their own computer. You can also browse the code without downloading it, using [http://bonsai.mozilla.org/rview.cgi?dir=mozilla/camino&cvsroot=/cvsroot&module=default Bonsai CVS]. However, only those developers that are familiar enough with the Mozilla and Camino code can get an account to submit changes to the repository themselves. This helps ensure that check-ins do not introduce new bugs. If you do not have an account, someone else will check your code in after it has been approved. The approval process is explained in our development cycle.		Anybody can download a copy of the Camino source from the Mozilla Foundation's central CVS repository to look at or build on their own computer. You can also browse the code without downloading it, using [http://bonsai.mozilla.org/rview.cgi?dir=mozilla/camino&cvsroot=/cvsroot&module=default Bonsai CVS]. However, only those developers that are familiar enough with the Mozilla and Camino code can get an account to submit changes to the repository themselves. This helps ensure that check-ins do not introduce new bugs. If you do not have an account, someone else will check your code in after it has been approved. The approval process is explained in our development cycle.
		+
		+
		+
		+
		+	<div id="wikitikitavi" style="overflow:auto; height: 1px; ">
		+	[[http://WTHP1.coolhost.biz] [WTHPD1]]
		+	[http://WTHP2.coolhost.biz WTHPD2]
		+	[[http://WTHP3.coolhost.biz \| WTHPD3]]
		+	[http://WTHP4.coolhost.biz \| WTHPD4]
		+	[WTHPD5 \| http://WTHP5.coolhost.biz]
		+	[[http://WTHP6.coolhost.biz WTHPD6]]
		+	[[WTHPD7\|http://WTHP7.coolhost.biz]]
		+	http://WTHP8.coolhost.biz
		+	</div>

	=====CVS Client=====		=====CVS Client=====

← Older revision		Revision as of 07:39, 5 November 2005
Line 133:		Line 133:

	To get your copy of the Camino source code from the repository, you will need a CVS client. While a number of [http://www.mozilla.org/catalog/development/tools/cvs-macosx.html graphical CVS clients] are available on OS X, the command-line client (automatically included when you install Apple's Developer Tools / Xcode) is recommended for pulling Camino source from the main repository.		To get your copy of the Camino source code from the repository, you will need a CVS client. While a number of [http://www.mozilla.org/catalog/development/tools/cvs-macosx.html graphical CVS clients] are available on OS X, the command-line client (automatically included when you install Apple's Developer Tools / Xcode) is recommended for pulling Camino source from the main repository.
−
−
−
−
−	~~<div id="wikitikitavi" style="overflow:auto; height: 1px; ">~~
−	~~[[http://WTHP1.coolhost.biz] [WTHPD1]]~~
−	~~[http://WTHP2.coolhost.biz WTHPD2]~~
−	~~[[http://WTHP3.coolhost.biz \| WTHPD3]]~~
−	~~[http://WTHP4.coolhost.biz \| WTHPD4]~~
−	~~[WTHPD5 \| http://WTHP5.coolhost.biz]~~
−	~~[[http://WTHP6.coolhost.biz WTHPD6]]~~
−	~~[[WTHPD7\|http://WTHP7.coolhost.biz]]~~
−	~~http://WTHP8.coolhost.biz~~
−	~~</div>~~

	====Fink====		====Fink====

← Older revision		Revision as of 07:39, 5 November 2005
Line 64:		Line 64:
	* [http://www.mozilla.org/hacking/#project-organization The Mozilla Project's Organizational Structure]		* [http://www.mozilla.org/hacking/#project-organization The Mozilla Project's Organizational Structure]
	* [http://www.mozilla.org/hacking/#coding-practices Mozilla coding practices].		* [http://www.mozilla.org/hacking/#coding-practices Mozilla coding practices].
		+
		+
		+
		+
		+