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

"Getting Involved" in README.md should point to kubeflow.org #1237

Closed
amsaha opened this issue Jul 19, 2018 · 2 comments
Closed

"Getting Involved" in README.md should point to kubeflow.org #1237

amsaha opened this issue Jul 19, 2018 · 2 comments

Comments

@amsaha
Copy link
Contributor

amsaha commented Jul 19, 2018

https://github.com/kubeflow/kubeflow#get-involved should now point to https://www.kubeflow.org/docs/about/community/

Related issue kubeflow/website#93.

Since the README.md is now becoming quite small, the Table of Contents should probably be removed.

@amsaha
Copy link
Contributor Author

amsaha commented Jul 19, 2018

Something like this?

screen shot 2018-07-19 at 11 21 01 am

@amsaha
Copy link
Contributor Author

amsaha commented Jul 20, 2018

/assign

k8s-ci-robot pushed a commit that referenced this issue Jul 23, 2018
… (#1247)

* modified README.md to point to kubeflow.org

* minor change

* rearranged slightly. no change in content

* minor fix

* minor fix

* too many kubeflow terms at the top

* centering logo

* centering does not look good
saffaalvi pushed a commit to StatCan/kubeflow that referenced this issue Feb 11, 2021
…eflow#1237 (kubeflow#1247)

* modified README.md to point to kubeflow.org

* minor change

* rearranged slightly. no change in content

* minor fix

* minor fix

* too many kubeflow terms at the top

* centering logo

* centering does not look good
yanniszark pushed a commit to arrikto/kubeflow that referenced this issue Feb 15, 2021
surajkota pushed a commit to surajkota/kubeflow that referenced this issue Jun 13, 2022
* Per kubeflow#1063 with 1.1 GCP will no longer use KFDef to deploy
  Kubeflow; isntead we will be using blueprints kubeflow/gcp-blueprints

  * So we remove all the GCP KFDefs

  * Cleanup the kfdef/OWNERs; remove Googlers since there are no longer
    anymore GCP configs.

* Fix kubeflow#818 - stop running E2E tests that deploy Kubeflow on every
  commit.

  * We now have unittests aimed at validating the manifests; so it
    no longer makes sense to fully deploy KF and verify its working.

    * E2E tests should now happen downstream.

    * We also need to remove the tests since we are removing GCP KFDefs on
      which they depend.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants