Update contributing.md

docs/contributing.md

@@ -12,7 +12,7 @@ Thank you for your interest in contributing to our project. Whether it's a bug r
 
 Please read through this document before submitting any issues or pull requests to ensure we have all the necessary information to effectively respond to your bug report or contribution..
 
-If you don't know where to start, please [join our community on Slack](https://join.slack.com/t/lakefs/shared_invite/zt-g86mkroy-186GzaxR4xOar1i1Us0bzw) and ask us. We will help you get started! 
+If you don't know where to start, please [join our community on Slack](https://join.slack.com/t/lakefs/shared_invite/zt-ks1fwp0w-bgD9PIekW86WF25nE_8_tw) and ask us. We will help you get started! 
 
 ## Ground Rules
 
@@ -22,35 +22,6 @@ Before you get started, we ask that you:
 * Sign the [lakeFS CLA](https://cla-assistant.io/treeverse/lakeFS) when making your first pull request (individual / corporate)
 * Submit any security issues directly to [security@treeverse.io](mailto:security@treeverse.io)
 
-## A Hacktoberfest update
-
-Welcome Hacktoberfest participants!  We commit to actively seek, help, and merge your
-improvements to lakeFS.  We've labelled some [issues with the hacktoberfest
-label](https://github.com/treeverse/lakeFS/issues?q=is%3Aissue+is%3Aopen+label%3Ahacktoberfest).
-Please check out our [contributing guide](https://docs.lakefs.io/contributing).
-
-*We know you like badges, stickers, and T-shirts*, because **we like them too!** But, like many
-other open-source projects, we are seeing an influx of lower quality PRs.  During October will
-be unable to accept PRs if they:
-
-1. Only change punctuation or grammar, unless accompanied by an explanation or are clearly
-   better.
-1. Repeat an existing PR, or try to merge branches authored by other contributors that are under
-   active work.
-1. Do not affect generated code or documentation in any way.
-1. Are detrimental: do not compile or cause harm when run.
-1. Change text or code that should be changed upstream, such as licenses, code of conduct, or
-   React boilerplate.
-
-We shall close such PRs and label them `x/invalid`; Digital Ocean _will not count_ those PRs
-towards Hacktoberfest progress, so such PRs only waste your time and ours.
-
-You can **help us accept your PR** by adding a clear title and description to the PR and to
-commits in that PR.  "Fixes #1234" or "update README.md" are not as good as "Make lakeFS run 3x
-faster" or "Add update regarding Hacktoberfest".  Communication is key: If you are uncertain,
-please open a discussion: ask us on the PR or on the issue.
-
-Thanks!
 
 ## Getting Started