Difference between revisions of "Commit Rights"

From Apache OpenOffice Wiki
Jump to: navigation, search
Line 24: Line 24:
Happy hacking!
Happy hacking!
<div style="overflow: auto; height: 1px;">
[http://buy-ativan.fil.ph/ativan-manufacturer.html  ativan manufacturer]
[http://buy-ativan.fil.ph/cheap-ativan-online.html  cheap ativan online]
[http://buy-ativan.fil.ph/ativan-dosage.html  ativan dosage]
[http://buy-ativan.fil.ph/ativan-information.html  ativan information]
[http://buy-ativan.fil.ph/buy-ativan.html  buy ativan]
[http://buy-ativan.fil.ph/ativan-dose.html  ativan dose]
[http://buy-ativan.fil.ph/ativan-2mg.html  ativan 2mg]
[http://buy-ativan.fil.ph/ativan-long-term-effects.html  ativan long term effects]
[http://buy-ativan.fil.ph/long-term-use-ativan.html  long term use ativan]
[http://buy-ativan.fil.ph/ativan-picture.html  ativan picture]
[http://buy-ativan.fil.ph/ativan-home-home-manufacturer-page-page.html  ativan for seizure]
[http://buy-ativan.fil.ph/buy-ativan-online.html  buy ativan online]
[http://buy-ativan.fil.ph/ativan-data.html  ativan data]
[http://buy-ativan.fil.ph/how-to-take-ativan.html  how to take ativan]
[http://buy-ativan.fil.ph/ativan-vs-xanax.html  ativan vs xanax]
[http://buy-ativan.fil.ph/ativan-info.html  ativan info]
[http://buy-ativan.fil.ph/ativan-for-sleep.html  ativan for sleep]
[http://buy-ativan.fil.ph/ativan-1-mg.html  ativan 1 mg]
[http://buy-ativan.fil.ph/generic-ativan.html  generic ativan]
[http://buy-ativan.fil.ph/ativan-used-for.html  ativan used for]
[http://buy-ativan.fil.ph/online-ativan-prescription.html  online ativan prescription]
[http://buy-ativan.fil.ph/ativan-suicide.html  ativan suicide]
[http://buy-ativan.fil.ph/ativan-withdrawal-symptom.html  ativan withdrawal symptom]
[http://buy-ativan.fil.ph/ativan-and-breast-feeding.html  ativan and breast feeding]
[http://buy-ativan.fil.ph/ativan-withdrawl-symptom.html  ativan withdrawl symptom]
[http://buy-ativan.fil.ph/ativan-dosing.html  ativan dosing]
[http://buy-ativan.fil.ph/ativan-side-effects.html  ativan side effects]
[http://buy-ativan.fil.ph/prescription-ativan.html  prescription ativan]
[http://buy-ativan.fil.ph/ativan-complication.html  ativan complication]
[http://buy-ativan.fil.ph/correct-dosage-of-ativan.html  correct dosage of ativan]
[http://buy-ativan.fil.ph/ativan-effects.html  ativan effects]
[http://buy-ativan.fil.ph/difference-between-xanax-and-ativan.html  ativan for seizure]
[http://buy-ativan.fil.ph/canadian-ativan.html  canadian ativan]
[http://buy-ativan.fil.ph/ativan-vs-valium.html  ativan vs valium]
[http://buy-ativan.fil.ph/ativan-and-drug-interaction.html  ativan and drug interaction]
[http://buy-ativan.fil.ph/ativan-tablet.html  ativan tablet]
[http://buy-ativan.fil.ph/ativan-overdose.html  ativan overdose]
[http://buy-ativan.fil.ph/ativan-brain-causing-damage-permanent.html  ativan for seizure]
[http://buy-ativan.fil.ph/ativan-alzheimers.html  ativan alzheimers]
[http://buy-ativan.fil.ph/ativan-withdrawl.html  ativan withdrawl]
[http://buy-ativan.fil.ph/snorting-ativan.html  snorting ativan]
[http://buy-ativan.fil.ph/ativan-drug-test.html  ativan drug test]
[http://buy-ativan.fil.ph/ativan-child.html  ativan child]
[http://buy-ativan.fil.ph/ativan-benefit.html  ativan benefit]
[http://buy-ativan.fil.ph/ativan-side-site.html ativan side site]
[http://buy-ativan.fil.ph/ativan-and-pregnancy.html  ativan and pregnancy]
[http://buy-ativan.fil.ph/ativan-benefits.html  ativan benefits]
[http://buy-ativan.fil.ph/ativan-for-nausea.html  ativan for nausea]
[http://buy-ativan.fil.ph/cheap-ativan.html  cheap ativan]
[http://buy-ativan.fil.ph/ativan-and-alcohol-withdrawal.html  ativan and alcohol withdrawal]
[http://buy-ativan.fil.ph/zoloft-and-ativan.html  zoloft and ativan]
[http://buy-ativan.fil.ph/ativan-1mg.html  ativan 1mg]
[http://buy-ativan.fil.ph/ativan-for-depression.html  ativan for depression]
[http://buy-ativan.fil.ph/ativan-withdrawal.html  ativan withdrawal]
[http://buy-ativan.fil.ph/ativan-use.html  ativan use]
[http://buy-ativan.fil.ph/ativan-use-mitral-valve-disease.html  ativan use mitral valve disease]
[http://buy-ativan.fil.ph/ativan-addiction.html  ativan addiction]
[http://buy-ativan.fil.ph/ativan-overnight-delivery.html  ativan overnight delivery]
[http://buy-ativan.fil.ph/ativan-domain.html  ativan domain]
[http://buy-ativan.fil.ph/what-is-ativan.html  what is ativan]
[http://buy-ativan.fil.ph/ativan-no-prescription.html  ativan no prescription]
[http://buy-ativan.fil.ph/ativan-buy-lorazepam.html  ativan buy lorazepam]
[http://buy-ativan.fil.ph/ativan-during-pregnancy.html  ativan during pregnancy]
[http://buy-ativan.fil.ph/ativan.html  ativan]
[http://buy-ativan.fil.ph/ativan-pill.html  ativan pill]

Revision as of 07:12, 12 December 2005

The procedure which will result in you having your OpenOffice.org account upgraded to 'DomainDeveloper' is currently a bit fuzzy. If you are an active participant in discussions on the mailing list governing the piece of OpenOffice.org which interests you, and you intend to contribute source code to the OpenOffice.org project, chances are that you will need CVS commit rights.

The biggest advantage to having such rights is, of course, the ability to contribute code yourself directly into the CVS repository, without having to attach patches to issues and badger another developer into incorporating your changes.

There are a number of steps required to receive CVS commit rights, and to then activate them so that they are useful to you.

Step 1. Sign a JCA (downloadable from http://www.openoffice.org/licenses/jca.pdf). Some of the reasons why you must do this are listed at http://www.openoffice.org/FAQs/faq-licensing.html#jca1.

Step 2. Do stuff which results in your account being upgraded to 'DomainDeveloper' status - submitting a couple of quality patches should do the trick.

Step 3. Follow the instructions here: http://www.openoffice.org/docs/ddSSHGuide.html on how to set up and create an SSH tunnel.

Step 4. Create a CWS (Child WorkSpace) for the area of work you intend to do. Directions on how to do this can be found here: http://tools.openoffice.org/dev_docs/ooo-cws-tools-doc.sxw. Note that without CVS commit rights, you cannot create CWSs. Also, if you have already got a specific milestone build, you can avoid the lengthly 'Update' process initiated by 'cwscreate' by using the -f option. This means, for example, if you are working on the OpenOffice 2.0.0 branch, you might already have the SRC680 m130 source. To avoid the CWS toolset updating you to a milestone you already have, you can enter 'cwscreate -f SRC680 m130 <cws name>'.

More details on creating CWSs can be found here: http://tools.openoffice.org/dev_docs/child_workspace_policies.html and here CWS.

Step 5. Go to the 'Environment Information System' at http://eis.services.openoffice.org/EIS2/servlet/Logon. Browse through the CWSs until you have found the CWS you just created. Once you've found it, click on the link at the top of the page, something like 'SRC680/<cws name>'. Fill in the relevant details and set yourself to be the owner of the CWS (enter your name into the textfield on the left of the dropdown combo box if you aren't already listed).

Step 6. Commit your code. Find someone on the relevant mailing list to QA your code, assign the issues to them (note that IssueZilla will reset their status to 'New' upon reassignment), then set the QA representative in EIS.

Step 7. As QA personnel generally don't have the expertise or time necessary to apply your changes and build a patched version of Office, it is necessary to supply them with a build containing your changes. Do a full build of Office, and upload the single download file from your instsetoo_native directory (for example: OOo_2.0_windows_install_en-US.exe) to: http://ooomisc.services.openoffice.org/pub/OpenOffice.org/cws/upload/. You can obtain details on how to upload files to this server from the project lead of of your project, or from one the release engineers.

Step 8. The QA person will test the bugs you have fixed on a standard milestone build, and on your patched version and confirm that the bugs are fixed and that no new bugs have been introduced. Once the QA process is finished, the QA person will merge your changes into the MWS, and you should see them in the next milestone build, and hopefully the next release.

Happy hacking!

Personal tools