Merge pull request #2158 from antoninbas/website-update

[Website] Update main docs and add blog post

.gitignore

@@ -14,3 +14,4 @@ bin
 
 .idea/
 .vscode/
+vendor

ADOPTERS.md

@@ -3,9 +3,6 @@
 <a href="http://glasnostic.com" border="0" target="_blank">
 <img alt="glasnostic.com" src="docs/assets/adopters/glasnostic-logo.png"
 height="50"></a>&nbsp; &nbsp; &nbsp;
-<a href="http://infrabuilder.com" border="0" target="_blank">
-<img alt="infrabuilder.com" src="docs/assets/adopters/infrabuilder-logo.png"
-height="50"></a>&nbsp; &nbsp; &nbsp;
 
 ## Success Stories
 
@@ -14,7 +11,11 @@ of how they use it.
 
 **[Glasnostic](https://glasnostic.com)**
 
-**[Infrabuilder](https://infrabuilder.com)**
+Glasnostic makes modern cloud operations resilient. It does this by shaping how
+systems interact, automatically and in real-time. As a result, DevOps and SRE
+teams can deploy reliably, prevent failure and assure the customer experience.
+We use Antrea's Open vSwitch support to tune how services interact in Kubernetes
+clusters. We are @glasnostic on Twitter.
 
 ## Adding yourself as an Adopter
 
@@ -32,7 +33,8 @@ add your success story and logo.
 your web site like this: `**[Example](https://example.com)**`
 
 3. Below your name, describe your organization or yourself and how you make
-use of Antrea. Optionally, list the features of Antrea you are using.
+use of Antrea. Optionally, list the features of Antrea you are using. Please
+keep the line width at 80 characters maximum, and avoid trailing spaces.
 
 4. If you are willing to share contact details, e.g. your Twitter handle, etc.
 add a line where people can find you.

CONTRIBUTING.md

@@ -5,21 +5,23 @@ Thank you for taking the time out to contribute to project Antrea!
 This guide will walk you through the process of making your first commit and how
 to effectively get it merged upstream.
 
-- [Developer Guide](#developer-guide)
-  - [Getting Started](#getting-started)
-    - [CLA](#cla)
-    - [Accounts Setup](#accounts-setup)
-  - [Contribute](#contribute)
-    - [GitHub Workflow](#github-workflow)
-    - [Getting reviewers](#getting-reviewers)
-    - [Inclusive Naming](#inclusive-naming)
-    - [Building and testing your change](#building-and-testing-your-change)
-    - [CI testing](#ci-testing)
-    - [Reverting a commit](#reverting-a-commit)
-  - [Issue and PR Management](#issue-and-pr-management)
-    - [Filing An Issue](#filing-an-issue)
-    - [Issue Triage](#issue-triage)
-    - [Issue and PR Kinds](#issue-and-pr-kinds)
+<!-- toc -->
+- [Getting Started](#getting-started)
+  - [CLA](#cla)
+  - [Accounts Setup](#accounts-setup)
+- [Contribute](#contribute)
+  - [GitHub Workflow](#github-workflow)
+  - [Getting reviewers](#getting-reviewers)
+  - [Cherry-picks to release branches](#cherry-picks-to-release-branches)
+  - [Inclusive Naming](#inclusive-naming)
+  - [Building and testing your change](#building-and-testing-your-change)
+  - [CI testing](#ci-testing)
+  - [Reverting a commit](#reverting-a-commit)
+- [Issue and PR Management](#issue-and-pr-management)
+  - [Filing An Issue](#filing-an-issue)
+  - [Issue Triage](#issue-triage)
+  - [Issue and PR Kinds](#issue-and-pr-kinds)
+<!-- /toc -->
 
 ## Getting Started
 
@@ -146,6 +148,14 @@ cases to our [automated test suite](ci/README.md) to guarantee enough
 coverage. A PR that makes significant code changes without contributing new test
 cases will be flagged by reviewers and will not be accepted.
 
+### Cherry-picks to release branches
+
+If your PR fixes a critical bug, it may need to be backported to older release
+branches which are still maintained. If this is the case, one of the Antrea
+maintainers will let you know once your PR is approved. Please refer to the
+documentation on [cherry-picks](docs/contributors/cherry-picks.md) for more
+information.
+
 ### Inclusive Naming
 
 For symbol names and documentation, do not introduce new usage of harmful

README.md

@@ -58,11 +58,11 @@ Your feedback is more than welcome!
 * Check the [Antrea Team Calendar](https://calendar.google.com/calendar/embed?src=uuillgmcb1cu3rmv7r7jrhcrco%40group.calendar.google.com)
   and join the developer and user communities!
   + The [Antrea community meeting](https://VMware.zoom.us/j/823654111?pwd=MEV6blNtUUtqallVSkVFSGZtQ1kwUT09),
-every two weeks on Tuesday at 5AM GMT.
+every two weeks on Tuesday at 5AM GMT+1 (United Kingdom time). See Antrea team calendar for localized times.
     - [Meeting minutes](https://github.com/vmware-tanzu/antrea/wiki/Community-Meetings)
     - [Meeting recordings](https://www.youtube.com/playlist?list=PLH5zTfQ3otSA6EOYDNb-MvcQRXACdCbQw)
   + [Antrea office hours](https://VMware.zoom.us/j/94245798791?pwd=RzRNVXYxdDJnNjZnNjBiUVFHZGlXdz09),
-every two weeks on Tuesday at 10PM GMT.
+every two weeks on Tuesday at 10PM GMT+1 (United Kingdom time). See Antrea team calendar for localized times.
 * Join our mailing lists to always stay up-to-date with Antrea development:
   + [projectantrea-announce](https://groups.google.com/forum/#!forum/projectantrea-announce)
 for important project announcements.