Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added the new CNCF slack channel to README.md #2062

Conversation

vikas-saxena02
Copy link
Contributor

@vikas-saxena02 vikas-saxena02 commented Jun 14, 2024

🛑 Important:

This PR is for the change proposed in #2061

Purpose of this PR

The PR aims at providing the new CNCF slack Channel details so that new users can go to new slack channel instead of old slack channel which is going to be archived soon. See details here (#2061)

Proposed changes:

  • Update slack channel to CNCF Slack channel

Change Category

Indicate the type of change by marking the applicable boxes:

  • Bugfix (non-breaking change which fixes an issue)
  • Feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that could affect existing functionality)
  • Documentation update

Rationale

Users are currentl joining the old slack channel instead of the new one

Checklist

Before submitting your PR, please review the following:

  • I have conducted a self-review of my own code.
  • I have updated documentation accordingly.
  • I have added tests that prove my changes are effective or that my feature works.
  • Existing unit tests pass locally with my changes.

Signed-off-by: Vikas Saxena <Vikas.Saxena.2006@gmail.com>
Signed-off-by: Vikas Saxena <Vikas.Saxena.2006@gmail.com>
@vikas-saxena02 vikas-saxena02 force-pushed the Issue2061_add_new_slack_channel_details branch from 37880b0 to 9d992e6 Compare June 14, 2024 18:56
@vikas-saxena02 vikas-saxena02 changed the title Added the link of Slack channel to new CNCF slack channel Added the new CNCF slack channel to README.md Jun 14, 2024
Copy link
Member

@andreyvelich andreyvelich left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for this @vikas-saxena02!
I would appreciate if you could also update the blog post: https://github.com/kubeflow/blog/blob/master/_posts/2024-04-15-kubeflow-spark-operator.md

README.md Outdated
@@ -91,5 +91,5 @@ Please check [CONTRIBUTING.md](CONTRIBUTING.md) and the [Developer Guide](docs/d

## Community

* Join our [Kubeflow Slack Channel](https://kubeflow.slack.com/archives/C06627U3XU3)
* Join our [Kubeflow Slack Channel](https://cloud-native.slack.com/archives/C074588U7EG)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please can you link this page: https://www.kubeflow.org/docs/about/community/#kubeflow-slack-channels ?
Since folks need to join CNCF Slack before joining the #kubeflow-spark-operator channel.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

on to it... will update by my EOD today

Copy link
Contributor Author

@vikas-saxena02 vikas-saxena02 Jun 15, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@andreyvelich @yuchaoran2011 I have incorporated both the review points in PR.

…oining slack channel to point to kubeflow website

Signed-off-by: Vikas Saxena <Vikas.Saxena.2006@gmail.com>
Signed-off-by: Vikas Saxena <Vikas.Saxena.2006@gmail.com>
@andreyvelich
Copy link
Member

Thanks @vikas-saxena02!
Please can you open another PR to update the Slack channel in kubeflow/blog here: https://github.com/kubeflow/blog/blob/master/_posts/2024-04-15-kubeflow-spark-operator.md#join-the-movement.

Copy link
Contributor

@vara-bonthu vara-bonthu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

README.md Outdated
@@ -91,5 +91,6 @@ Please check [CONTRIBUTING.md](CONTRIBUTING.md) and the [Developer Guide](docs/d

## Community

* Join our [Kubeflow Slack Channel](https://kubeflow.slack.com/archives/C06627U3XU3)
* Join [CNCF Slack Channel](https://www.kubeflow.org/docs/about/community/#kubeflow-slack-channels)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it's better provide the direct link to CNCF Kubeflow Spark Operator channel
replace the link with this one https://cloud-native.slack.com/archives/C074588U7EG

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Previously, we got a feedback that if we provide this link and user is not member of CNCF slack, they can't join it: kubeflow/katib#2343

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, just checked the comment from Andrey on this. Maybe we can rephrase it as:

Join the CNCF Slack Channel #kubeflow-spark-operator for collaboration on the Spark Operator.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

that sounds good

Copy link
Contributor Author

@vikas-saxena02 vikas-saxena02 Jun 16, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@vara-bonthu @andreyvelich please take a look again, I have updated the same. Happy to put a link to kubeflow-spark-operator as well if you think it would make more sense. I am double minded about it as it may confuse users and they may not end up clicking on first link to join the CNCF Slack Workspace

README.md Outdated
@@ -91,5 +91,6 @@ Please check [CONTRIBUTING.md](CONTRIBUTING.md) and the [Developer Guide](docs/d

## Community

* Join our [Kubeflow Slack Channel](https://kubeflow.slack.com/archives/C06627U3XU3)
* Join [CNCF Slack Channel](https://www.kubeflow.org/docs/about/community/#kubeflow-slack-channels)
* Check out our blog post [Announcing the Kubeflow Spark Operator: Building a Stronger Spark on Kubernetes Community](https://github.com/kubeflow/blog/blob/master/_posts/2024-04-15-kubeflow-spark-operator.md)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@vara-bonthu
Copy link
Contributor

/hold

Signed-off-by: Vikas Saxena <Vikas.Saxena.2006@gmail.com>
Copy link
Contributor

New changes are detected. LGTM label has been removed.

@google-oss-prow google-oss-prow bot removed the lgtm label Jun 16, 2024
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from vara-bonthu. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Signed-off-by: Vikas Saxena <Vikas.Saxena.2006@gmail.com>
@vikas-saxena02
Copy link
Contributor Author

vikas-saxena02 commented Jun 16, 2024

https://github.com/kubeflow/blog/blob/master/_posts/2024-04-15-kubeflow-spark-operator.md#join-the-movement

@andreyvelich please take a look at the change made in this PR and I will make an identical change in kubeflow/blog repository as mentioned by you.

Signed-off-by: Vikas Saxena <Vikas.Saxena.2006@gmail.com>
@vikas-saxena02
Copy link
Contributor Author

@vara-bonthu I am getting the following error ✖︎ spark-operator => (version: "1.4.1", path: "charts/spark-operator-chart") > chart version not ok. Needs a version bump! from Pre-commit check/build-helm-chart doI need to bump the operator version?

@@ -1,6 +1,6 @@
# spark-operator

![Version: 1.4.0](https://img.shields.io/badge/Version-1.4.0-informational?style=flat-square) ![AppVersion: v1beta2-1.6.0-3.5.0](https://img.shields.io/badge/AppVersion-v1beta2--1.6.0--3.5.0-informational?style=flat-square)
![Version: 1.4.1](https://img.shields.io/badge/Version-1.4.1-informational?style=flat-square) ![AppVersion: v1beta2-1.6.0-3.5.0](https://img.shields.io/badge/AppVersion-v1beta2--1.6.0--3.5.0-informational?style=flat-square)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you don't have to change the version in your PR

@@ -110,7 +110,7 @@ See [helm uninstall](https://helm.sh/docs/helm/helm_uninstall) for command docum
| podMonitor.labels | object | `{}` | Pod monitor labels |
| podMonitor.podMetricsEndpoint | object | `{"interval":"5s","scheme":"http"}` | Prometheus metrics endpoint properties. `metrics.portName` will be used as a port |
| podSecurityContext | object | `{}` | Pod security context |
| priorityClassName | string | `""` | Priority class to be used for running spark-operator pod. This helps in managing the pods during preemption. |
| priorityClassName | string | `""` | A priority class to be used for running spark-operator pod. |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you can exclude these changes

… "fixed Typos in README.md"

This reverts commit 6d7eb4d.
Signed-off-by: Vikas Saxena <Vikas.Saxena.2006@gmail.com>
@vikas-saxena02
Copy link
Contributor Author

@vara-bonthu @andreyvelich I think I have screwed up my branch. i will do a new PR soon

@vikas-saxena02 vikas-saxena02 deleted the Issue2061_add_new_slack_channel_details branch June 18, 2024 08:45
vikas-saxena02 added a commit to vikas-saxena02/spark-operator that referenced this pull request Jun 18, 2024
Signed-off-by: Vikas Saxena <Vikas.Saxena.2006@gmail.com>
google-oss-prow bot pushed a commit that referenced this pull request Jun 18, 2024
Signed-off-by: Vikas Saxena <Vikas.Saxena.2006@gmail.com>
jacobsalway pushed a commit to jacobsalway/spark-operator that referenced this pull request Jul 25, 2024
…w#2066)

Signed-off-by: Vikas Saxena <Vikas.Saxena.2006@gmail.com>
sigmarkarl pushed a commit to spotinst/spark-on-k8s-operator that referenced this pull request Aug 7, 2024
…w#2066)

Signed-off-by: Vikas Saxena <Vikas.Saxena.2006@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants