doc: update slack links to https

README.md

@@ -32,7 +32,7 @@ HOSTED_DOCS_ONLY-->
 [![Version](https://img.shields.io/github/v/release/linkedin/datahub?include_prereleases)](https://github.com/linkedin/datahub/releases/latest)
 [![build & test](https://github.com/linkedin/datahub/workflows/build%20&%20test/badge.svg?branch=master&event=push)](https://github.com/linkedin/datahub/actions?query=workflow%3A%22build+%26+test%22+branch%3Amaster+event%3Apush)
 [![Docker Pulls](https://img.shields.io/docker/pulls/linkedin/datahub-gms.svg)](https://hub.docker.com/r/linkedin/datahub-gms)
-[![Slack](https://img.shields.io/badge/slack-join_chat-white.svg?logo=slack&style=social)](http://slack.datahubproject.io)
+[![Slack](https://img.shields.io/badge/slack-join_chat-white.svg?logo=slack&style=social)](https://slack.datahubproject.io)
 [![PRs Welcome](https://img.shields.io/badge/PRs-welcome-brightgreen.svg)](https://github.com/linkedin/datahub/blob/master/docs/CONTRIBUTING.md)
 [![GitHub commit activity](https://img.shields.io/github/commit-activity/m/linkedin/datahub)](https://github.com/linkedin/datahub/pulls?q=is%3Apr)
 [![License](https://img.shields.io/github/license/linkedin/datahub)](https://github.com/linkedin/datahub/blob/master/LICENSE)
@@ -109,7 +109,7 @@ Check out DataHub's [Features](docs/features.md) & [Roadmap](docs/roadmap.md).
 We welcome contributions from the community. Please refer to our [Contributing Guidelines](docs/CONTRIBUTING.md) for more details. We also have a [contrib](contrib) directory for incubating experimental features.
 
 ## Community
-Join our [slack workspace](http://slack.datahubproject.io) for discussions and important announcements. You can also find out more about our upcoming [town hall meetings](docs/townhalls.md) and view past recordings.
+Join our [slack workspace](https://slack.datahubproject.io) for discussions and important announcements. You can also find out more about our upcoming [town hall meetings](docs/townhalls.md) and view past recordings.
 
 ## Adoption
 Here are the companies that have officially adopted DataHub. Please feel free to add yours to the list if we missed it.

docs-website/docusaurus.config.js

@@ -24,7 +24,7 @@ module.exports = {
           position: "right",
         },
         {
-          href: "http://slack.datahubproject.io",
+          href: "https://slack.datahubproject.io",
           label: "Slack",
           position: "right",
         },
@@ -69,7 +69,7 @@ module.exports = {
           items: [
             {
               label: "Slack",
-              href: "http://slack.datahubproject.io",
+              href: "https://slack.datahubproject.io",
             },
             {
               label: "YouTube",

docs-website/src/pages/index.js

@@ -167,7 +167,7 @@ function Home() {
                     'button button--secondary button--outline button--lg',
                     styles.hero_button
                   )}
-                  to='http://slack.datahubproject.io'>
+                  to='https://slack.datahubproject.io'>
                   Join our Slack
             </Link>
               </div>

docs/CODE_OF_CONDUCT.md

@@ -70,7 +70,7 @@ members of the project's leadership.
 This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
 available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
 
-[Slack]: https://datahubspace.slack.com/join/shared_invite/zt-cl60ng6o-6odCh_I~ejZKE~a9GG30PA
+[Slack]: https://slack.datahubproject.io
 [homepage]: https://www.contributor-covenant.org
 
 For answers to common questions about this code of conduct, see

docs/faq.md

@@ -40,10 +40,10 @@ External parties who deploy / are actively evaluating DataHub:
 We welcome contributions from everyone in the community. Please read our [contributing guidelines](CONTRIBUTING.md). In general, we will review PRs with the same rigor as our internal code review process to maintain overall quality.
 
 ## How does LinkedIn plan to engage with the community?
-We plan to organize public town hall meetings at a monthly cadence, which may change depending on the interest from the community. Also we recently deprecated Gitter and start using [Slack](https://datahubspace.slack.com/join/shared_invite/zt-cl60ng6o-6odCh_I~ejZKE~a9GG30PA) as one of the main ways to support the community.
+We plan to organize public town hall meetings at a monthly cadence, which may change depending on the interest from the community. Also we recently deprecated Gitter and start using [Slack](https://slack.datahubproject.io) as one of the main ways to support the community.
 
 ## Should this be the platform we decide upon, we’d like to fully engage and work with LinkedIn and the community. What’s the best way and what level of engagement/involvement should we expect?
-The best way to engage is through the [Slack channel](https://datahubspace.slack.com/join/shared_invite/zt-cl60ng6o-6odCh_I~ejZKE~a9GG30PA). You’ll get to interact with the developers and the community. We are fairly response on Slack and plan to setup proper oncall support during normal business hours (Pacific Time). Sometimes we also create working groups with dedicated POC from the LinkedIn team to tackle specific use cases the community has.
+The best way to engage is through the [Slack channel](https://slack.datahubproject.io). You’ll get to interact with the developers and the community. We are fairly response on Slack and plan to setup proper oncall support during normal business hours (Pacific Time). Sometimes we also create working groups with dedicated POC from the LinkedIn team to tackle specific use cases the community has.
 
 For reproducible technical issues, bugs and code contributions, Github [issues](https://github.com/linkedin/datahub/issues) and [PRs](https://github.com/linkedin/datahub/pulls) are the preferred channel.
 

docs/roadmap.md

@@ -8,7 +8,7 @@ We publish only a short roadmap, because we are evolving very fast and want to a
 
 If you would like to suggest new items or request timeline changes to the existing items, please submit your request through this [form](https://docs.google.com/forms/d/1znDv7_CXXvUDcUsqzq92PgGqPSh_1yeYC3cl2xgizSE/) or submit a GitHub [feature request](https://github.com/linkedin/datahub/issues/new?assignees=&labels=feature-request&template=--feature-request.md&title=A+short+description+of+the+feature+request).
 
-Of course, you always have access to our community through [Slack](http://slack.datahubproject.io) or our [town halls](townhalls.md) to chat with us live!
+Of course, you always have access to our community through [Slack](https://slack.datahubproject.io) or our [town halls](townhalls.md) to chat with us live!
 
 ## Q1 2021 [Jan - Mar 2021]
 

docs/slack.md

@@ -2,8 +2,8 @@
 
 The DataHub team has an open source slack workspace to discuss development and support.
 
-[Sign up](http://slack.datahubproject.io) or [log in with an
-existing account](https://datahubspace.slack.com/) to `datahubspace` on Slack.
+[Sign up](https://slack.datahubproject.io) or [log in with an
+existing account](https://slack.datahubproject.io) to `datahubspace` on Slack.
 
 Here are some notable channels and their purposes