My favorites | Sign in
Project Home Downloads Wiki Issues Source
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 1369: Instructions for Installing Gerrit Under Tomcat, Install Guide Updates
4 people starred this issue and may be notified of changes. Back to list
Status:  New
Owner:  ----


Sign in to add a comment
 
Reported by oneprem...@gmail.com, May 1, 2012
I actually placed together instructions for installing Gerrit under Tomcat on serverfault.com. I would also like to make them available to the Gerrit project. Please feel free to take any sections of my tutorial and contribute the to your install doc, where needed. Hopefully, it will save time for other developers seeking to deploy Gerrit under a Windows/Tomcat environment. If you decide you would like to contribute sections, and would like help, don't hesitate to ask.

Here they are:

http://serverfault.com/questions/383573/how-do-i-install-gerrit-under-tomcat-with-ldap/385076#385076

Thanks!
May 2, 2012
Project Member #1 bklarson@gmail.com
Thank you for your work on this.  To get this in Gerrit's official docs we will need you to make a commit and push it to Gerrit for review.  This ensures that you have filled out the proper contributor agreement and are donating the work to the project.
May 2, 2012
#2 oneprem...@gmail.com
Ok, I've cloned an instance and looking at the documentation now. I'll see what I can come up with and merge it to gerrit for review. Let me know if there's any area you would like me to focus in on. Thanks!
May 2, 2012
#3 sop@google.com
Donating isn't the right word. The contributor agreement doesn't require you to make a donation to the project, it requires you to license the content to the project under the project's license (Apache License 2.0). Authors retain copyright.
May 2, 2012
Project Member #4 bklarson@gmail.com
Sorry Shawn, thank you for the clarification.  I'll be more careful in the future :)
May 2, 2012
#5 oneprem...@gmail.com
license, donate, contribute, submit... It's just a choice of words. If you prefer license, that's fine. I understand.
May 2, 2012
#6 oneprem...@gmail.com
Is there a location i can test the ascii markup before submitting the doc? I would like to make sure it displays correctly.
May 2, 2012
Project Member #7 bklarson@gmail.com
You can run the Makefile inside the Documentation folder to generate the html.  It can also be done as part of the mvn build, but this is probably fastest.
Aug 8, 2012
#8 oneprem...@gmail.com
If any of you get a chance, please review the doc updates. This original change, Change-Id: I91dae81f8dc7ad361a40f7a76ec74ec69aaa4250, has been broken down further into smaller changes. Now resulting in 4 smaller changes:
 
Change-Id: I91dae81f8dc7ad361a40f7a76ec74ec69aaa4250 - Database Setup Instructions
Change-Id: I52b30c0d3c0edd515cf1b2f66eff7b85173b724c - Gitweb Instruction Updates
Change-Id: Iec0af0325ca59b9c9cc7fc178155e58dda6274ba - Initial Login Doc Updates
Change-Id: I63409a6746eb3892643b6f92acb821a025fdb6ed - This change.
Sep 27, 2013
#9 oneprem...@gmail.com
I haven't had a whole lot of time to keep this effort going and it has since been abandoned. However, it's still a good reference:

https://gerrit-review.googlesource.com/#/c/37072

If anybody ever would like to pick this up and finish, please be my guest. I don't know what the policy is here bringing abandoned patches back to life, but if I can, i might bring it back.
Sep 27, 2013
Project Member #10 edwin.ke...@gmail.com
It depends on the reason for abandoning. If it was just abandoned because there was no further progress (like in this case) anyone who wants to continue working on it can simply restore the change and push a new patch set.
Sign in to add a comment

Powered by Google Project Hosting