[RFC] Reorganize ray repo
See original GitHub issueCurrently, the top organization of the Ray repo is pretty hard to navigate. Something like the following would be more clear:
build/
core/
docs/
deploy/
rllib/
tune/
BUILD.bazel
CONTRIBUTING.rst
LICENSE
README.rst
Ideally, we’d also refactor core
, tune
and rllib
to have separate setup.py scripts, so that they can be developed without needing to recompile ray core by default.
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (6 by maintainers)
Top Results From Across the Web
[RFC] Mr Phelps - a distributed workflow orchestrator
Make a GitHub “organization” - they're free for open source projects and one can manage individual repos and permissions. A lot of Julia ......
Read more >EPA March 2022 Denial Letter of RFC 21005 Exhibits
Dear Mr. Walsh,. This letter is in response to the Request for Correction (RFC} received by the U.S.. Enviranrnental Protection Agency (EPA) ...
Read more >main - Anaconda repo
Package Latest Version Doc Dev License linux‑64 osx‑64 win‑64
7za 920 doc LGPL X
7zip 19.00 dev LGPL‑2.1‑or‑later X
_anaconda_depends 2022.05 doc dev BSD X X...
Read more >Model Zoo - Deep learning code and pretrained models for ...
ModelZoo curates and provides a platform for deep learning researchers to easily find code and pre-trained models for a variety of platforms and...
Read more >Enterprise Edition - CodeScene Enterprise Edition Documentation
Using X-Ray's inter-repo analysis lets you uncover expensive change ... organize your codebase by moving source code files to different folders, ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’m in general biased towards having a single repo, due to the need to maintain build and release processes and infrastructure (especially if we start adding larger scale tests). There are some benefits of a separate repo, but it would be substantial overhead to maintain I think.
@ericl I think it is done? Please reopen if it doesn’t!