Visualization for the docker-py codebase#3340
Open
ivanmilevtues wants to merge 1 commit intodocker:mainfrom
Open
Visualization for the docker-py codebase#3340ivanmilevtues wants to merge 1 commit intodocker:mainfrom
ivanmilevtues wants to merge 1 commit intodocker:mainfrom
Conversation
Signed-off-by: ivanmilevtues <ivanmilevtues@gmail.com>
Author
|
Hey, dropping by to announce that we are now also open-source: https://github.com/CodeBoarding/CodeBoarding |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Generated documentation to help new developers to get up to speed with the docker-py.
Hey all. Me and a friend have noticed that it is quite hard to get to know new codebases, so we are working on something which can help people get up to speed. We believe that it is always best to start with nice high-level visualization and then dig down into the interesting/relevant parts of the code i.e. first task/something one wants to contribute to. We would love to hear how you go about on-boarding in Docker in general, do you think that such diagrams can be part of your existing process? Further what is your opinion on diagram first documentation?
The generated diagrams are done via leveraging static analysis and LLM's. The generated one for the docker-py repo can be seen rendered here: https://github.com/CodeBoarding/GeneratedOnBoardings/blob/main/docker-py/on_boarding.md
Would love to hear your opinion on the diagram, any feedback is more than welcome!
Full disclosure: we're trying to turn this into a startup, but we're still in a very early stage and figuring out what will actually be useful for people.