Mozilla.org/How to Work with Site: Difference between revisions
(Updating Bugzilla information) |
(Adding CVS information) |
||
| Line 10: | Line 10: | ||
Phone: [[Mozilla.org:Planning#Planning_Meetings|Monthly planning meetings]] | Phone: [[Mozilla.org:Planning#Planning_Meetings|Monthly planning meetings]] | ||
==Bugzilla== | ==Bugzilla== | ||
| Line 24: | Line 23: | ||
* [https://bugzilla.mozilla.org/enter_bug.cgi Enter a new bug] | * [https://bugzilla.mozilla.org/enter_bug.cgi Enter a new bug] | ||
== | ==Staging== | ||
==Making Site Changes== | |||
There are two ways to update the site—have someone with access make the change or make the change yourself. | |||
===Submitting Changes=== | |||
The easiest way to make a change is to work with someone who already has access. You can send them the change in a variety of formats. Attaching a [https://developer.mozilla.org/En/Creating_a_patch patch] to a bug is the most common way to do that, but it is also possible to simply email a change to someone. How changes are submitted will vary on your technical experience and on who you are working with. | |||
===Checking In Changes=== | |||
''Note: You '''do not''' need to deal with CVS if you don't want to. This information is provided for anyone who does want to work directly with our repository.'' | |||
' | If you'd like to edit the site directly, you will need to be able to use CVS, get commit access and check out the site's repository. Documentation for each of those steps is below: | ||
* [http://ximbiot.com/cvs/cvshome/docs/blandy.html CVS tutorial] | * [http://ximbiot.com/cvs/cvshome/docs/blandy.html CVS tutorial] | ||
* [http://www.mozilla.org/hacking/committer/ Becoming A Mozilla Committer] | |||
* [http://www.mozilla.org/contribute/writing/cvs mozilla.org content and cvs] | * [http://www.mozilla.org/contribute/writing/cvs mozilla.org content and cvs] | ||
* [https://developer.mozilla.org/En/Mozilla_Source_Code_(CVS) Mozilla Source Code (CVS)] | * [https://developer.mozilla.org/En/Mozilla_Source_Code_(CVS) Mozilla Source Code (CVS)] | ||
Revision as of 21:25, 30 March 2009
Docs for people getting involved with site.
Asking Questions
The best way to learn about how to work with the www.mozilla.org site is to ask questions. Community members are happy to help, but it can be difficult to know who to talk to. Here are a few good places to go with questions:
Email: dev-mozilla-org
Chat: #siteplanning on irc.mozilla.org
Phone: Monthly planning meetings
Bugzilla
We use Bugzilla to track bugs as well as enhancements to the site. You can look through bugs without an account, but will need to log in to be able to update an existing bug or open a new one. Feel free to look through open bugs, comment or open a new one.
Staging
Making Site Changes
There are two ways to update the site—have someone with access make the change or make the change yourself.
Submitting Changes
The easiest way to make a change is to work with someone who already has access. You can send them the change in a variety of formats. Attaching a patch to a bug is the most common way to do that, but it is also possible to simply email a change to someone. How changes are submitted will vary on your technical experience and on who you are working with.
Checking In Changes
Note: You do not need to deal with CVS if you don't want to. This information is provided for anyone who does want to work directly with our repository.
If you'd like to edit the site directly, you will need to be able to use CVS, get commit access and check out the site's repository. Documentation for each of those steps is below: