vmware
diff --git a/‎.github/PULL_REQUEST_TEMPLATE.md‎
Lines changed: 4 additions & 27 deletions b/‎.github/PULL_REQUEST_TEMPLATE.md‎
Lines changed: 4 additions & 27 deletions
diff --git a/‎.mailmap‎
Lines changed: 6 additions & 0 deletions b/‎.mailmap‎
Lines changed: 6 additions & 0 deletions
diff --git a/‎CONTRIBUTING.md‎
Lines changed: 35 additions & 10 deletions b/‎CONTRIBUTING.md‎
Lines changed: 35 additions & 10 deletions
diff --git a/‎CONTRIBUTORS‎
Lines changed: 17 additions & 0 deletions b/‎CONTRIBUTORS‎
Lines changed: 17 additions & 0 deletions
@@ -1,38 +1,15 @@
 ## Description
 
-Please include a summary of the change and which issue is fixed. Please also
-include relevant motivation and context. List any dependencies that are required
-for this change.
+Please include a summary of the change.
 
 Closes: #(issue-number)
 
-## Type of change
-
-Please mark options that are relevant:
-
-- [ ] Bug fix (non-breaking change which fixes an issue)
-- [ ] New feature (non-breaking change which adds functionality)
-- [ ] Breaking change (fix or feature that would cause existing functionality to
-  not work as expected)
-- [ ] This change requires a documentation update
-- [ ] Build related change
-
 ## How Has This Been Tested?
 
-Please describe the tests that you ran to verify your changes. Provide
-instructions so we can reproduce. If applicable, please also list any relevant
-details for your test configuration.
-
-- [ ] Test Description 1
-- [ ] Test Description 2
+Please describe any manual tests done to verify your changes.
 
-## Checklist:
+## Guidelines
 
-- [ ] My code follows the `CONTRIBUTION` [guidelines] of this project
-- [ ] I have commented my code, particularly in hard-to-understand areas
-- [ ] I have made corresponding changes to the documentation
-- [ ] I have added tests that prove my fix is effective or that my feature works
-- [ ] New and existing unit tests pass locally with my changes
-- [ ] Any dependent changes have been merged
+Please read and follow the `CONTRIBUTION` [guidelines] of this project.
 
 [guidelines]: https://github.com/vmware/govmomi/blob/main/CONTRIBUTING.md
@@ -57,3 +57,9 @@ Yun Zhou <yunz@vmware.com> <41678287+gh05tn0va@users.noreply.github.com>
 Zach G <zguan@vmware.com> zach96guan <zach96guan@users.noreply.github.com>
 Zach Tucker <ztucker@vmware.com> <jzt@users.noreply.github.com>
 Zee Yang <zeey@vmware.com> <zee.yang@gmail.com>
+Arunesh Pandey <parunesh@vmware.com> Arunesh Pandey <aruneshpa@gmail.com>
+Eric Cao <ecao@vmware.com> Eric Cao <32748317+ericvmw@users.noreply.github.com>
+Eric Cao <ecao@vmware.com> Eric Cao <eric.cao@broadcom.com>
+Ryan Johnson <johnsonryan@vmware.com> Ryan Johnson <ryan.johnson@broadcom.com>
+Stoyan Zhelyazkov <stoyan.zhelyazkov@broadcom.com> Stoyan Zhelyazkov <156204153+spacegospod@users.noreply.github.com>
+Yanlei Zhao <yanleizhao@vmware.com> Yanlei Zhao <136122252+yanleizhao-vmware@users.noreply.github.com>
@@ -1,5 +1,11 @@
 # Contributing to `govmomi`
 
+tl;dr
+
+- Sign your commits, unless you've signed the CLA
+- Include a component `prefix:` in your commit message, if applicable
+- Squash fixup commits and force push to your branch
+
 ## Getting started
 
 First, fork the repository on GitHub to your personal account.
@@ -27,6 +33,7 @@ This is a rough outline of what a contributor's workflow looks like:
 - Create an issue describing the feature/fix
 - Create a topic branch from where you want to base your work.
 - Make commits of logical units.
+- [Sign](#sign-off-your-work) your commits.
 - Make sure your commit messages are in the proper format (see below).
 - Push your changes to a topic branch in your fork of the repository.
 - Submit a pull request to `vmware/govmomi`.
@@ -38,12 +45,30 @@ and **supported prefixes**, e.g. `govc: <message>`.
 > my!](https://www.mgasch.com/2021/05/git-basics/) for more details on how to
 > successfully contribute to an open source project.
 
+### Sign-off Your Work
+
+Use the [Developer Certificate of Origin](https://developercertificate.org/) (DCO) on all Pull Requests.
+By adding this line to their commit messages, contributors *sign-off* that they adhere to the requirements of the DCO.
+
+Git provides the `-s` command-line option to append the required line
+automatically to the commit message:
+
+```bash
+git commit -s -m 'This is my commit message'
+```
+
+For an existing commit, you can also use this option with `--amend`:
+
+```bash
+git commit -s --amend
+```
+
 ### Example 1 - Fix a Bug in `govmomi`
 
 ```bash
 git checkout -b issue-<number> main
 git add <files>
-git commit -m "fix: ..." -m "Closes: #<issue-number>"
+git commit -s -m "fix: ..." -m "Closes: #<issue-number>"
 git push $USER issue-<number>
 ```
 
@@ -52,7 +77,7 @@ git push $USER issue-<number>
 ```bash
 git checkout -b issue-<number> main
 git add <files>
-git commit -m "Add API ..." -m "Closes: #<issue-number>"
+git commit -s -m "Add API ..." -m "Closes: #<issue-number>"
 git push $USER issue-<number>
 ```
 
@@ -61,26 +86,26 @@ git push $USER issue-<number>
 ```bash
 git checkout -b issue-<number> main
 git add <files>
-git commit -m "govc: Add feature ..." -m "Closes: #<issue-number>"
+git commit -s -m "govc: Add feature ..." -m "Closes: #<issue-number>"
 git push $USER issue-<number>
 ```
-**Note**:  
+**Note**:
 To register the new `govc` command package, add a blank `_` import to `govmomi/govc/main.go`.
 
 ### Example 4 - Fix a Bug in `vcsim`
 
 ```bash
 git checkout -b issue-<number> main
 git add <files>
-git commit -m "vcsim: Fix ..." -m "Closes: #<issue-number>"
+git commit -s -m "vcsim: Fix ..." -m "Closes: #<issue-number>"
 git push $USER issue-<number>
 ```
 
 ### Example 5 - Document Breaking (API) Changes
 
 Breaking changes, e.g. to the `govmomi` APIs, are highlighted in the `CHANGELOG`
 and release notes when the keyword `BREAKING:` is used in the commit message
-body. 
+body.
 
 The text after `BREAKING:` is used in the corresponding highlighted section.
 Thus these details should be stated at the body of the commit message.
@@ -89,7 +114,7 @@ Multi-line strings are supported.
 ```bash
 git checkout -b issue-<number> main
 git add <files>
-cat << EOF | git commit -F -
+cat << EOF | git commit -s -F -
 Add ctx to funcXYZ
 
 This commit introduces context.Context to function XYZ
@@ -127,7 +152,7 @@ directly instead.
 git add .
 
 # create a fixup commit which will be merged into your (original) <commit>
-git commit --fixup <commit>
+git commit -s --fixup <commit>
 git push $USER issue-<number>
 ```
 
@@ -162,7 +187,7 @@ e.g. `Closes: #<number>`.
 The [`CHANGELOG.md`](./CHANGELOG.md) and release page uses **commit message
 prefixes** for grouping and highlighting. A commit message that
 starts with `[prefix:] ` will place this commit under the respective
-section in the `CHANGELOG`. 
+section in the `CHANGELOG`.
 
 The following example creates a commit referencing the `issue: 1234` and puts
 the commit message in the `govc` `CHANGELOG` section:
@@ -186,7 +211,7 @@ is recommended to break up your commits using distinct prefixes.
 
 ### Running CI Checks and Tests
 You can run both `make check` and `make test` from the top level of the
-repository. 
+repository.
 
 While `make check` will catch formatting and import errors, it will not apply
 any fixes. The developer is expected to do that.
 
@@ -8,6 +8,7 @@ abrarshivani <abrarshivani@users.noreply.github.com>
 Adam Chalkley <atc0005@users.noreply.github.com>
 Adam Fowler <adam@adamfowler.org>
 Adam Shannon <adamkshannon@gmail.com>
+Adnan Baruni <badnan@vmware.com>
 Akanksha Panse <pansea@vmware.com>
 Al Biheiri <abiheiri@apple.com>
 Alessandro Cortiana <alessandro.cortiana@gmail.com>
@@ -24,6 +25,7 @@ Andrew <AndrewDi@users.noreply.github.com>
 Andrew Chin <andrew@andrewtchin.com>
 Andrew Kutz <akutz@vmware.com>
 Andrey Klimentyev <andrey.klimentyev@flant.com>
+aneesurrehman001 <55150455+aneesurrehman001@users.noreply.github.com>
 Anfernee Yongkun Gui <agui@vmware.com>
 angystardust <angystardust@users.noreply.github.com>
 aniketGslab <aniket.shinde@gslab.com>
@@ -32,6 +34,7 @@ Ankit Vaidya <vaidyaa@vmware.com>
 Ankur Huralikoppi <huralikoppia@vmware.com>
 Anna Carrigan <anna.carrigan@hpe.com>
 Antony Saba <awsaba@gmail.com>
+Anusha Ramineni <raminenia@vmware.com>
 Ariel Chinn <arielchinn@gmail.com>
 Arran Walker <arran.walker@zopa.com>
 Artem Anisimov <aanisimov@inbox.ru>
@@ -46,6 +49,7 @@ Ben Vickers <bvickers@pivotal.io>
 Benjamin Davini <davinib@vmware.com>
 Benjamin Peterson <benjamin@python.org>
 Benjamin Vickers <bvickers@vmware.com>
+Bernd Zeimetz <bernd@bzed.de>
 Bhavya Choudhary <bhavyac@vmware.com>
 Bob Killen <killen.bob@gmail.com>
 Brad Fitzpatrick <bradfitz@golang.org>
@@ -57,6 +61,7 @@ Bruno Meneguello <1322552+bkmeneguello@users.noreply.github.com>
 Bryan Venteicher <bryanventeicher@gmail.com>
 C S P Nanda <cspn@google.com>
 Carsten Grohmann <mail@carstengrohmann.de>
+Chebrolu <hchebrol@redhat.com>
 Cheng Cheng <chengch@vmware.com>
 Chethan Venkatesh <chethanv@vmware.com>
 Choudhury Sarada Prasanna Nanda <cspn@google.com>
@@ -82,6 +87,7 @@ Davide Agnello <dagnello@hp.com>
 Davinder Kumar <davinderk@vmware.com>
 Defa <zhoudefa666@163.com>
 demarey <christophe.demarey@inria.fr>
+Derek Beard <derek.beard@gmail.com>
 Deric Crago <deric.crago@gmail.com>
 Deyan Popov <deyan.popov@gmail.com>
 Dinesh Bhat <35480850+dbhat-arkin@users.noreply.github.com>
@@ -92,12 +98,14 @@ Doug MacEachern <dougm@vmware.com>
 East <60801291+houfangdong@users.noreply.github.com>
 Eloy Coto <eloy.coto@gmail.com>
 Eng Zer Jun <engzerjun@gmail.com>
+Eric Cao <ecao@vmware.com>
 Eric Edens <ericedens@google.com>
 Eric Graham <16710890+Pheric@users.noreply.github.com>
 Eric Gray <egray@vmware.com>
 Eric Yutao <eric.yutao@gmail.com>
 Erik Hollensbe <github@hollensbe.org>
 Erik Lund <info@erikjensen.it>
+Erim Erdal <erim.erdal@broadcom.com>
 Essodjolo KAHANAM <essodjolo@kahanam.com>
 Ethan Kaley <ethan.kaley@emc.com>
 Evan Chu <echu@vmware.com>
@@ -121,6 +129,7 @@ Hasan Mahmood <mahmoodh@vmware.com>
 Haydon Ryan <haydon.ryan@gmail.com>
 Heiko Reese <hreese@users.noreply.github.com>
 Henrik Hodne <henrik@travis-ci.com>
+Himanshu Ranjan <rhimanshu@vmware.com>
 hkumar <hkumar@vmware.com>
 Hrabur Stoyanov <hstoyanov@vmware.com>
 hui luo <luoh@vmware.com>
@@ -135,10 +144,12 @@ Jeremy Canady <jcanady@jackhenry.com>
 jeremy-clerc <jeremy@clerc.io>
 Jiatong Wang <wjiatong@vmware.com>
 jingyizPensando <jingyiz@pensando.io>
+jitinkumar94 <jitinkumar94@github.com>
 Jonas Ausevicius <jonas.ausevicius@virtustream.com>
 Jorge Sevilla <jorge.sevilla@rstor.io>
 Joseph LeBlanc <jsleblanc@users.noreply.github.com>
 João Pereira <joaodrp@gmail.com>
+Jukka Lehtniemi <ext-jukka.lehtniemi@vaisala.com>
 Julien PILLON <jpillon@lesalternatives.org>
 Justin J. Novack <jnovack@users.noreply.github.com>
 kayrus <kay.diam@gmail.com>
@@ -155,6 +166,7 @@ Liping Xue <lipingx@vmware.com>
 liron.levin <liron.levin@wiz.io>
 Louie Jiang <jiangl@vmware.com>
 Lubron Zhan <lzhan@vmware.com>
+Luis Davim <dluis@vmware.com>
 Luther Monson <luther.monson@gmail.com>
 Madanagopal Arunachalam <marunachalam@vmware.com>
 makelarisjr <8687447+makelarisjr@users.noreply.github.com>
@@ -209,16 +221,19 @@ Robin Watkins <robwatkins@gmail.com>
 Rowan Jacobs <rojacobs@pivotal.io>
 Roy Ling <royling0024@gmail.com>
 rsikdar <rsikdar@berkeley.edu>
+rubinthomasdev <rubinthomasdev@gmail.com>
 runner.mei <runner.mei@gmail.com>
 Ryan Johnson <johnsonryan@vmware.com>
 S R Ashrith <sashrith@vmware.com>
 S.Çağlar Onur <conur@vmware.com>
 Saad Malik <saad@spectrocloud.com>
+Sai Diliyaer <sai.diliyaer@gmail.com>
 Sam Zhu <zhusa@zhusa-a02.vmware.com>
 samzhu333 <45263849+samzhu333@users.noreply.github.com>
 Sandeep Pissay Srinivasa Rao <ssrinivas@vmware.com>
 schmikei <keith.schmitt@bluemedora.com>
 Scott Holden <scott@nullops.io>
+Sebastian Mitterle <smitterl@redhat.com>
 Sergey Ignatov <sergey.ignatov@jetbrains.com>
 serokles <timbo.alexander@gmail.com>
 shahra <shahra@vmware.com>
@@ -229,6 +244,7 @@ shylasrinivas <sshyla@vmware.com>
 sky-joker <sky.jokerxx@gmail.com>
 smaftoul <samuel.maftoul@gmail.com>
 smahadik <smahadik@vmware.com>
+Sreeja Acharya <acharyasreej@vmware.com>
 Sten Feldman <exile@chamber.ee>
 Stepan Mazurov <smazurov@gmail.com>
 Steve Purcell <steve@sanityinc.com>
@@ -264,6 +280,7 @@ xing-yang <xingyang105@gmail.com>
 xinyanw409 <wxinyan@vmware.com>
 Yang Yang <yangy@vmware.com>
 yangxi <yangxi@vmware.com>
+Yanlei Zhao <yanleizhao@vmware.com>
 Yann Hodique <yhodique@google.com>
 Yash Nitin Desai <desaiy@vmware.com>
 Yassine TIJANI <ytijani@vmware.com>