ovirt-engine repo up in gerrit.ovirt.org!
Here we go... - gerrit is up. - ovirt-engine git repo is there. - will upload the other repositories soon. below you can find the steps on how to get the code (yes, coming to you in wiki soon). a link to the wiki on how to build oVirt will be sent soon by Livnat. It's exciting to see everyone coming together to build a community, and I'm looking forward to working together on oVirt. Welcome everyone, Itamar How to use: 1. registering as a user: - you can use any OpenID provider for now[1] - login page shows google and yahoo - any fedora FAS account can login as well via https://admin.fedoraproject.org/accounts/openid/id/<username> 2. set ssh keys in gerrit settings - on your local machine, create a set of ssh keys if you don't have one via 'ssh-keygen -t rsa' - update via gerrit settings the ssh public key to allow ssh to gerrit 3. define gerrit in ~/.ssh/config Host gerrit.ovirt.org HostName gerrit.ovirt.org Port 29418 User <username> 4. check ssh works correctly, verify and ack the host fingerprint: ssh gerrit.ovirt.org if you get this, it is fine: *** Welcome to Gerrit Code Review **** 5. cloning the repo git clone gerrit.ovirt.org:ovirt-engine this can be done without registering to gerrit using: git clone git://gerrit.ovirt.org/ovirt-engine 6. install the change-Id hook - you must do this before you commit anything: scp -p gerrit.ovirt.org:hooks/commit-msg .git/hooks/ 7. do some work/commit/etc. wiki link on how to build/run ovirt will be sent by Livnat soon. 8. rebase: git fetch gerrit.ovirt.org:ovirt-engine master 9. push your patch for review: git push gerrit.ovirt.org:ovirt-engine HEAD:refs/for/master 10. track patch review process the review process is comprised of: - anyone can send a patch - anyone can code review and comment on the patch and +1/-1. This helps maintainers in reviewing the patches. - a maintainer can code review it with +2 it, which is required to commit (submit) it. - someone (anyone) needs to confirm they checked the patch works and flag it as verified +1 - a maintainer can submit (commit) the patch when it has: Code Review: +2 Verified: +1 - nacked (-1) patches should not be submitted - a submitted patch is merged to the git TODOs: - emails to mailing list on patches/commits[2] - upload repos of more projects - have gerrit add acked-by/verified-by based on the gerrit reviewes? - mirror to github [1] if anyone provides a reason to limit to specific OpenID providers that's an option as well. [2] basic emails until we merge the gerrit patches sending them inline - we are working on sending them to upstream gerrit.
On 10/27/2011 11:51 PM, Itamar Heim wrote:
Here we go...
- gerrit is up. - ovirt-engine git repo is there. - will upload the other repositories soon.
below you can find the steps on how to get the code (yes, coming to you in wiki soon). a link to the wiki on how to build oVirt will be sent soon by Livnat.
It's exciting to see everyone coming together to build a community, and I'm looking forward to working together on oVirt.
Welcome everyone, Itamar
Welcome indeed, A link to a wiki with info for setting development environment - http://www.ovirt.org/wiki/Building_Ovirt_Engine Livnat
How to use: 1. registering as a user: - you can use any OpenID provider for now[1] - login page shows google and yahoo - any fedora FAS account can login as well via https://admin.fedoraproject.org/accounts/openid/id/<username>
2. set ssh keys in gerrit settings - on your local machine, create a set of ssh keys if you don't have one via 'ssh-keygen -t rsa' - update via gerrit settings the ssh public key to allow ssh to gerrit
3. define gerrit in ~/.ssh/config Host gerrit.ovirt.org HostName gerrit.ovirt.org Port 29418 User <username>
4. check ssh works correctly, verify and ack the host fingerprint: ssh gerrit.ovirt.org if you get this, it is fine: *** Welcome to Gerrit Code Review ****
5. cloning the repo git clone gerrit.ovirt.org:ovirt-engine this can be done without registering to gerrit using: git clone git://gerrit.ovirt.org/ovirt-engine
6. install the change-Id hook - you must do this before you commit anything: scp -p gerrit.ovirt.org:hooks/commit-msg .git/hooks/
7. do some work/commit/etc. wiki link on how to build/run ovirt will be sent by Livnat soon.
8. rebase: git fetch gerrit.ovirt.org:ovirt-engine master
9. push your patch for review: git push gerrit.ovirt.org:ovirt-engine HEAD:refs/for/master
10. track patch review process the review process is comprised of: - anyone can send a patch - anyone can code review and comment on the patch and +1/-1. This helps maintainers in reviewing the patches. - a maintainer can code review it with +2 it, which is required to commit (submit) it. - someone (anyone) needs to confirm they checked the patch works and flag it as verified +1 - a maintainer can submit (commit) the patch when it has: Code Review: +2 Verified: +1 - nacked (-1) patches should not be submitted - a submitted patch is merged to the git
TODOs: - emails to mailing list on patches/commits[2] - upload repos of more projects - have gerrit add acked-by/verified-by based on the gerrit reviewes? - mirror to github
[1] if anyone provides a reason to limit to specific OpenID providers that's an option as well. [2] basic emails until we merge the gerrit patches sending them inline - we are working on sending them to upstream gerrit. _______________________________________________ Board mailing list Board@ovirt.org http://lists.ovirt.org/mailman/listinfo/board
On Friday 28 October 2011 02:09:41 Livnat Peer wrote:
On 10/27/2011 11:51 PM, Itamar Heim wrote:
Here we go...
- gerrit is up. - ovirt-engine git repo is there. - will upload the other repositories soon.
below you can find the steps on how to get the code (yes, coming to you in wiki soon). a link to the wiki on how to build oVirt will be sent soon by Livnat.
It's exciting to see everyone coming together to build a community, and I'm looking forward to working together on oVirt.
Welcome everyone,
Itamar
Welcome indeed,
A link to a wiki with info for setting development environment - http://www.ovirt.org/wiki/Building_Ovirt_Engine
refering to the wiki above, what about the ovirt-jboss rpm, we need a repo to pulish it (somewhere in ovirt.org) and update the above wiki. I assume much more rpms will follow since none are Fedora packages yet. Barak
Livnat
How to use: 1. registering as a user: - you can use any OpenID provider for now[1] - login page shows google and yahoo - any fedora FAS account can login as well via https://admin.fedoraproject.org/accounts/openid/id/<username>
2. set ssh keys in gerrit settings - on your local machine, create a set of ssh keys if you don't have one via 'ssh-keygen -t rsa' - update via gerrit settings the ssh public key to allow ssh to gerrit
3. define gerrit in ~/.ssh/config Host gerrit.ovirt.org
HostName gerrit.ovirt.org Port 29418 User <username>
4. check ssh works correctly, verify and ack the host fingerprint: ssh gerrit.ovirt.org if you get this, it is fine: *** Welcome to Gerrit Code Review ****
5. cloning the repo git clone gerrit.ovirt.org:ovirt-engine this can be done without registering to gerrit using: git clone git://gerrit.ovirt.org/ovirt-engine
6. install the change-Id hook - you must do this before you commit anything: scp -p gerrit.ovirt.org:hooks/commit-msg .git/hooks/
7. do some work/commit/etc. wiki link on how to build/run ovirt will be sent by Livnat soon.
8. rebase: git fetch gerrit.ovirt.org:ovirt-engine master
9. push your patch for review: git push gerrit.ovirt.org:ovirt-engine HEAD:refs/for/master
10. track patch review process the review process is comprised of: - anyone can send a patch - anyone can code review and comment on the patch and +1/-1. This helps maintainers in reviewing the patches. - a maintainer can code review it with +2 it, which is required to commit (submit) it. - someone (anyone) needs to confirm they checked the patch works and flag it as verified +1
- a maintainer can submit (commit) the patch when it has: Code Review: +2 Verified: +1
- nacked (-1) patches should not be submitted - a submitted patch is merged to the git
TODOs: - emails to mailing list on patches/commits[2] - upload repos of more projects - have gerrit add acked-by/verified-by based on the gerrit reviewes? - mirror to github
[1] if anyone provides a reason to limit to specific OpenID providers that's an option as well. [2] basic emails until we merge the gerrit patches sending them inline - we are working on sending them to upstream gerrit. _______________________________________________ Board mailing list Board@ovirt.org http://lists.ovirt.org/mailman/listinfo/board
_______________________________________________ Board mailing list Board@ovirt.org http://lists.ovirt.org/mailman/listinfo/board
From: infra-bounces@ovirt.org [mailto:infra-bounces@ovirt.org] On Behalf Of Barak Azulay ...
A link to a wiki with info for setting development environment - http://www.ovirt.org/wiki/Building_Ovirt_Engine
refering to the wiki above, what about the ovirt-jboss rpm, we need a repo to pulish it (somewhere in ovirt.org) and update the above wiki. I assume much more rpms will follow since none are Fedora packages yet.
Barak
Karsten - we need a place to host rpms: - for something like ovirt-jboss-5-as which provides jboss 5 in rpm to consume in fedora until we move to jboss as 7 and their rpms for fedora/whatever. - to publish nightly/weekly/versioned rpm builds of the different components Thanks, Itamar
--6h64vBu9tReNbGLX Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Oct 28, 2011 at 05:56:55PM -0400, Itamar Heim wrote:
=20 Karsten - we need a place to host rpms: - for something like ovirt-jboss-5-as which provides jboss 5 in rpm to consume in fedora until we move to jboss as 7 and their rpms for fedora/whatever. - to publish nightly/weekly/versioned rpm builds of the different components
What directory structure makes sense? Whatever we put in will supercede Wordpress owning the sub-directory structure. Maybe we should just put up a yum repository, which serves RPMs via HTTP but also has repository metadata. Anyone want to help setup the yum repo? I'll have to refresh my memory more if I have to do it myself. :) - Karsten --=20 name: Karsten 'quaid' Wade, Sr. Community Gardener team: Red Hat Community Architecture & Leadership uri: http://communityleadershipteam.org http://TheOpenSourceWay.org gpg: AD0E0C41 --6h64vBu9tReNbGLX Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iD8DBQFOrcbj2ZIOBq0ODEERAj+UAJ9HgHl6GdwAHc8t/FbORZ8/suT64QCghdTE Fw6Y96vCswove21SnvACBJ8= =b8X+ -----END PGP SIGNATURE----- --6h64vBu9tReNbGLX--
On Thu, 2011-10-27 at 23:51 +0200, Itamar Heim wrote:
Here we go...
- gerrit is up. - ovirt-engine git repo is there. - will upload the other repositories soon.
This is terrific. Any pointers on setting up additional projects? I'd love to get ovirt-node uploaded. Thanks Mike
below you can find the steps on how to get the code (yes, coming to you in wiki soon). a link to the wiki on how to build oVirt will be sent soon by Livnat.
It's exciting to see everyone coming together to build a community, and I'm looking forward to working together on oVirt.
Welcome everyone, Itamar
How to use: 1. registering as a user: - you can use any OpenID provider for now[1] - login page shows google and yahoo - any fedora FAS account can login as well via https://admin.fedoraproject.org/accounts/openid/id/<username>
2. set ssh keys in gerrit settings - on your local machine, create a set of ssh keys if you don't have one via 'ssh-keygen -t rsa' - update via gerrit settings the ssh public key to allow ssh to gerrit
3. define gerrit in ~/.ssh/config Host gerrit.ovirt.org HostName gerrit.ovirt.org Port 29418 User <username>
4. check ssh works correctly, verify and ack the host fingerprint: ssh gerrit.ovirt.org if you get this, it is fine: *** Welcome to Gerrit Code Review ****
5. cloning the repo git clone gerrit.ovirt.org:ovirt-engine this can be done without registering to gerrit using: git clone git://gerrit.ovirt.org/ovirt-engine
6. install the change-Id hook - you must do this before you commit anything: scp -p gerrit.ovirt.org:hooks/commit-msg .git/hooks/
7. do some work/commit/etc. wiki link on how to build/run ovirt will be sent by Livnat soon.
8. rebase: git fetch gerrit.ovirt.org:ovirt-engine master
9. push your patch for review: git push gerrit.ovirt.org:ovirt-engine HEAD:refs/for/master
10. track patch review process the review process is comprised of: - anyone can send a patch - anyone can code review and comment on the patch and +1/-1. This helps maintainers in reviewing the patches. - a maintainer can code review it with +2 it, which is required to commit (submit) it. - someone (anyone) needs to confirm they checked the patch works and flag it as verified +1 - a maintainer can submit (commit) the patch when it has: Code Review: +2 Verified: +1 - nacked (-1) patches should not be submitted - a submitted patch is merged to the git
TODOs: - emails to mailing list on patches/commits[2] - upload repos of more projects - have gerrit add acked-by/verified-by based on the gerrit reviewes? - mirror to github
[1] if anyone provides a reason to limit to specific OpenID providers that's an option as well. [2] basic emails until we merge the gerrit patches sending them inline - we are working on sending them to upstream gerrit. _______________________________________________ Board mailing list Board@ovirt.org http://lists.ovirt.org/mailman/listinfo/board
-----Original Message----- From: Mike Burns [mailto:mburns@redhat.com] Sent: Friday, October 28, 2011 3:13 AM To: Itamar Heim Cc: engine-devel@ovirt.org; infra@ovirt.org; board@ovirt.org Subject: Re: ovirt-engine repo up in gerrit.ovirt.org!
On Thu, 2011-10-27 at 23:51 +0200, Itamar Heim wrote:
Here we go...
- gerrit is up. - ovirt-engine git repo is there. - will upload the other repositories soon.
This is terrific. Any pointers on setting up additional projects? I'd love to get ovirt-node uploaded.
You just need to ask... Timing wise - since once it is up there it is the master git and workflow is through it, so if the maintainers are not familiar with gerrit, may I suggest we do this the week after the workshop so will be easier to help with any issues? If the maintainers are already familiar with gerrit, we can go right ahead. In the meantime, please ask the maintainers to login to gerrit.ovirt.org with an OpenID account so I can setup the ovirt-node-maintainers group.
Thanks
Mike
below you can find the steps on how to get the code (yes, coming to you in wiki soon). a link to the wiki on how to build oVirt will be sent soon by Livnat.
It's exciting to see everyone coming together to build a community, and I'm looking forward to working together on oVirt.
Welcome everyone, Itamar
How to use: 1. registering as a user: - you can use any OpenID provider for now[1] - login page shows google and yahoo - any fedora FAS account can login as well via https://admin.fedoraproject.org/accounts/openid/id/<username>
2. set ssh keys in gerrit settings - on your local machine, create a set of ssh keys if you don't have one via 'ssh-keygen -t rsa' - update via gerrit settings the ssh public key to allow ssh to gerrit
3. define gerrit in ~/.ssh/config Host gerrit.ovirt.org HostName gerrit.ovirt.org Port 29418 User <username>
4. check ssh works correctly, verify and ack the host fingerprint: ssh gerrit.ovirt.org if you get this, it is fine: *** Welcome to Gerrit Code Review ****
5. cloning the repo git clone gerrit.ovirt.org:ovirt-engine this can be done without registering to gerrit using: git clone git://gerrit.ovirt.org/ovirt-engine
6. install the change-Id hook - you must do this before you commit anything: scp -p gerrit.ovirt.org:hooks/commit-msg .git/hooks/
7. do some work/commit/etc. wiki link on how to build/run ovirt will be sent by Livnat soon.
8. rebase: git fetch gerrit.ovirt.org:ovirt-engine master
9. push your patch for review: git push gerrit.ovirt.org:ovirt-engine HEAD:refs/for/master
10. track patch review process the review process is comprised of: - anyone can send a patch - anyone can code review and comment on the patch and +1/-1. This helps maintainers in reviewing the patches. - a maintainer can code review it with +2 it, which is required to commit (submit) it. - someone (anyone) needs to confirm they checked the patch works and flag it as verified +1 - a maintainer can submit (commit) the patch when it has: Code Review: +2 Verified: +1 - nacked (-1) patches should not be submitted - a submitted patch is merged to the git
TODOs: - emails to mailing list on patches/commits[2] - upload repos of more projects - have gerrit add acked-by/verified-by based on the gerrit reviewes? - mirror to github
[1] if anyone provides a reason to limit to specific OpenID providers that's an option as well. [2] basic emails until we merge the gerrit patches sending them inline - we are working on sending them to upstream gerrit. _______________________________________________ Board mailing list Board@ovirt.org http://lists.ovirt.org/mailman/listinfo/board
On Fri, 2011-10-28 at 02:47 -0400, Itamar Heim wrote:
-----Original Message----- From: Mike Burns [mailto:mburns@redhat.com] Sent: Friday, October 28, 2011 3:13 AM To: Itamar Heim Cc: engine-devel@ovirt.org; infra@ovirt.org; board@ovirt.org Subject: Re: ovirt-engine repo up in gerrit.ovirt.org!
On Thu, 2011-10-27 at 23:51 +0200, Itamar Heim wrote:
Here we go...
- gerrit is up. - ovirt-engine git repo is there. - will upload the other repositories soon.
This is terrific. Any pointers on setting up additional projects? I'd love to get ovirt-node uploaded.
You just need to ask... Timing wise - since once it is up there it is the master git and workflow is through it, so if the maintainers are not familiar with gerrit, may I suggest we do this the week after the workshop so will be easier to help with any issues? If the maintainers are already familiar with gerrit, we can go right ahead. In the meantime, please ask the maintainers to login to gerrit.ovirt.org with an OpenID account so I can setup the ovirt-node-maintainers group.
Probably a good idea to wait until after the workshop to get it setup. I've played around with gerrit a bit previously, but not enough to be completely comfortable. I'm already setup there. My username is mburns.
Thanks
Mike
below you can find the steps on how to get the code (yes, coming to you in wiki soon). a link to the wiki on how to build oVirt will be sent soon by Livnat.
It's exciting to see everyone coming together to build a community, and I'm looking forward to working together on oVirt.
Welcome everyone, Itamar
How to use: 1. registering as a user: - you can use any OpenID provider for now[1] - login page shows google and yahoo - any fedora FAS account can login as well via https://admin.fedoraproject.org/accounts/openid/id/<username>
2. set ssh keys in gerrit settings - on your local machine, create a set of ssh keys if you don't have one via 'ssh-keygen -t rsa' - update via gerrit settings the ssh public key to allow ssh to gerrit
3. define gerrit in ~/.ssh/config Host gerrit.ovirt.org HostName gerrit.ovirt.org Port 29418 User <username>
4. check ssh works correctly, verify and ack the host fingerprint: ssh gerrit.ovirt.org if you get this, it is fine: *** Welcome to Gerrit Code Review ****
5. cloning the repo git clone gerrit.ovirt.org:ovirt-engine this can be done without registering to gerrit using: git clone git://gerrit.ovirt.org/ovirt-engine
6. install the change-Id hook - you must do this before you commit anything: scp -p gerrit.ovirt.org:hooks/commit-msg .git/hooks/
7. do some work/commit/etc. wiki link on how to build/run ovirt will be sent by Livnat soon.
8. rebase: git fetch gerrit.ovirt.org:ovirt-engine master
9. push your patch for review: git push gerrit.ovirt.org:ovirt-engine HEAD:refs/for/master
10. track patch review process the review process is comprised of: - anyone can send a patch - anyone can code review and comment on the patch and +1/-1. This helps maintainers in reviewing the patches. - a maintainer can code review it with +2 it, which is required to commit (submit) it. - someone (anyone) needs to confirm they checked the patch works and flag it as verified +1 - a maintainer can submit (commit) the patch when it has: Code Review: +2 Verified: +1 - nacked (-1) patches should not be submitted - a submitted patch is merged to the git
TODOs: - emails to mailing list on patches/commits[2] - upload repos of more projects - have gerrit add acked-by/verified-by based on the gerrit reviewes? - mirror to github
[1] if anyone provides a reason to limit to specific OpenID providers that's an option as well. [2] basic emails until we merge the gerrit patches sending them inline - we are working on sending them to upstream gerrit. _______________________________________________ Board mailing list Board@ovirt.org http://lists.ovirt.org/mailman/listinfo/board
This is a multi-part message in MIME format. --------------040700000909070908080508 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit on some of the links gerrit is doing this: Application Error Server Error org.eclipse.jgit.errors.MissingObjectException: Missing unknown 2444e06de5139c2205849ff6a1ff903b12535321 --------------040700000909070908080508 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit <html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> <br> on some of the links gerrit is doing this:<br> <br> <div class="GCLMTUVDAF">Application Error</div> <div> <div class="GCLMTUVDOE">Server Error</div> <div style="white-space: pre;" class="gwt-Label">org.eclipse.jgit.errors.MissingObjectException: Missing unknown 2444e06de5139c2205849ff6a1ff903b12535321</div> </div> <br> </body> </html> --------------040700000909070908080508--
-----Original Message----- From: Carl Trieloff [mailto:cctrieloff@redhat.com] Sent: Friday, October 28, 2011 15:33 PM To: Itamar Heim Cc: engine-devel@ovirt.org; infra@ovirt.org; board@ovirt.org Subject: Issue with gerrit
on some of the links gerrit is doing this:
What's the link / how you got to it? If this is the commit by Oved - it is a merge from a test removed later - it is only in the UI. I'll clean it later.
Application Error Server Error org.eclipse.jgit.errors.MissingObjectException: Missing unknown
2444e06de5139c2205849ff6a1ff903b12535321
On 10/28/2011 09:45 AM, Itamar Heim wrote:
What's the link / how you got to it? If this is the commit by Oved - it is a merge from a test removed later - it is only in the UI. I'll clean it later. http://gerrit.ovirt.org/3
-----Original Message----- From: Carl Trieloff [mailto:cctrieloff@redhat.com] Sent: Friday, October 28, 2011 15:45 PM To: Itamar Heim Cc: engine-devel@ovirt.org; infra@ovirt.org; board@ovirt.org Subject: Re: Issue with gerrit
On 10/28/2011 09:45 AM, Itamar Heim wrote:
What's the link / how you got to it? If this is the commit by Oved - it is a merge from a test removed later - it is only in the UI. I'll clean it later. http://gerrit.ovirt.org/3
Yes - that's the known one from the test ovirt-engine-git
On 10/28/2011 10:10 AM, Itamar Heim wrote:
-----Original Message----- From: Carl Trieloff [mailto:cctrieloff@redhat.com] Sent: Friday, October 28, 2011 15:45 PM To: Itamar Heim Cc: engine-devel@ovirt.org; infra@ovirt.org; board@ovirt.org Subject: Re: Issue with gerrit
On 10/28/2011 09:45 AM, Itamar Heim wrote:
What's the link / how you got to it? If this is the commit by Oved - it is a merge from a test removed later - it is only in the UI. I'll clean it later. http://gerrit.ovirt.org/3 Yes - that's the known one from the test ovirt-engine-git
ok, good. The last one seemed fine. Carl.
Is there also a plan (or maybe already in place, but I missed it) to have a git.ovirt.org that lets us browse the git repos used by gerrit? Thanks Mike On Thu, 2011-10-27 at 23:51 +0200, Itamar Heim wrote:
Here we go...
- gerrit is up. - ovirt-engine git repo is there. - will upload the other repositories soon.
below you can find the steps on how to get the code (yes, coming to you in wiki soon). a link to the wiki on how to build oVirt will be sent soon by Livnat.
It's exciting to see everyone coming together to build a community, and I'm looking forward to working together on oVirt.
Welcome everyone, Itamar
How to use: 1. registering as a user: - you can use any OpenID provider for now[1] - login page shows google and yahoo - any fedora FAS account can login as well via https://admin.fedoraproject.org/accounts/openid/id/<username>
2. set ssh keys in gerrit settings - on your local machine, create a set of ssh keys if you don't have one via 'ssh-keygen -t rsa' - update via gerrit settings the ssh public key to allow ssh to gerrit
3. define gerrit in ~/.ssh/config Host gerrit.ovirt.org HostName gerrit.ovirt.org Port 29418 User <username>
4. check ssh works correctly, verify and ack the host fingerprint: ssh gerrit.ovirt.org if you get this, it is fine: *** Welcome to Gerrit Code Review ****
5. cloning the repo git clone gerrit.ovirt.org:ovirt-engine this can be done without registering to gerrit using: git clone git://gerrit.ovirt.org/ovirt-engine
6. install the change-Id hook - you must do this before you commit anything: scp -p gerrit.ovirt.org:hooks/commit-msg .git/hooks/
7. do some work/commit/etc. wiki link on how to build/run ovirt will be sent by Livnat soon.
8. rebase: git fetch gerrit.ovirt.org:ovirt-engine master
9. push your patch for review: git push gerrit.ovirt.org:ovirt-engine HEAD:refs/for/master
10. track patch review process the review process is comprised of: - anyone can send a patch - anyone can code review and comment on the patch and +1/-1. This helps maintainers in reviewing the patches. - a maintainer can code review it with +2 it, which is required to commit (submit) it. - someone (anyone) needs to confirm they checked the patch works and flag it as verified +1 - a maintainer can submit (commit) the patch when it has: Code Review: +2 Verified: +1 - nacked (-1) patches should not be submitted - a submitted patch is merged to the git
TODOs: - emails to mailing list on patches/commits[2] - upload repos of more projects - have gerrit add acked-by/verified-by based on the gerrit reviewes? - mirror to github
[1] if anyone provides a reason to limit to specific OpenID providers that's an option as well. [2] basic emails until we merge the gerrit patches sending them inline - we are working on sending them to upstream gerrit. _______________________________________________ Board mailing list Board@ovirt.org http://lists.ovirt.org/mailman/listinfo/board
--BI5RvnYi6R4T2M87 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Oct 28, 2011 at 10:47:37AM -0400, Mike Burns wrote:
Is there also a plan (or maybe already in place, but I missed it) to have a git.ovirt.org that lets us browse the git repos used by gerrit?
Yes, it's on my personal list that may not be on the Infrastructure wiki yet. :) I know pepole want GitHub, Gitorious, and other mirroring sites to get pretty views, but we should host a simple web source view at git.ovirt.org. That is already a CNAME to the same host as gerrit.ovirt.org. That said, my personal list is NOT vetted by the infra@ovirt.org team, since every idea has an ongoing management cost. - Karsten --=20 name: Karsten 'quaid' Wade, Sr. Community Gardener team: Red Hat Community Architecture & Leadership uri: http://communityleadershipteam.org http://TheOpenSourceWay.org gpg: AD0E0C41 --BI5RvnYi6R4T2M87 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iD8DBQFOqvbX2ZIOBq0ODEERAuxVAJ9ltDjd2gitu36j5mn4h0HlLf2FYgCffln2 eKTtKPGWTS92UpUB27Lca3c= =BdkW -----END PGP SIGNATURE----- --BI5RvnYi6R4T2M87--
participants (6)
-
Barak Azulay -
Carl Trieloff -
Itamar Heim -
Karsten Wade -
Livnat Peer -
Mike Burns