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

Determine future of Distributed Workloads repo #25

Open
Tracked by #314
dimakis opened this issue Sep 27, 2023 · 3 comments
Open
Tracked by #314

Determine future of Distributed Workloads repo #25

dimakis opened this issue Sep 27, 2023 · 3 comments
Assignees

Comments

@dimakis
Copy link

dimakis commented Sep 27, 2023

No description provided.

@dimakis dimakis changed the title [Longer term] Determine future of Distributed Workloads repo Determine future of Distributed Workloads repo Oct 10, 2023
@KPostOffice KPostOffice self-assigned this Oct 16, 2023
@KPostOffice
Copy link

KPostOffice commented Oct 16, 2023

We should definitely get rid of the DW repo if possible, the question becomes what happens to the following:

@tedhtchang
Copy link

tedhtchang commented Oct 20, 2023

We have been referencing the DW repo in the open source community.

For installation and contribution, which repo are we going to direct the community to ?
Update:
Perhaps the ODH installation can go here.

@KPostOffice
Copy link

We have been referencing the DW repo in the open source community.

* The [kube mcad tutorial](https://github.com/ray-project/kuberay/blob/master/docs/guidance/kuberay-with-MCAD.md).

* The official DW [installation ](https://github.com/opendatahub-io/distributed-workloads/blob/main/Quick-Start.md) are also used referenced many place like [this](https://developer.ibm.com/tutorials/awb-codeflare-installation/).

For installation and contribution, which repo are we going to direct the community to ? Update: Perhaps the ODH installation can go here.

Because this repo is linked elsewhere, let's not delete the repo when it gets to that point. We can make some changes and let this live on as a link tree to the new documentation and explicitly encourage linking directly to the new documents. For installation, I lean towards having it live in the ODH docs (either explicitly or just as the general installation guide) and referencing it from the CFO

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants