-
Notifications
You must be signed in to change notification settings - Fork 154
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
Add Developer Guides, replace internal.md, CONTRIBUTING.md #625
Conversation
…into docs/libdesign
@isVoid did you want help adding to this doc? |
That would be awesome. Let's chat about this soon. |
…into docs/libdesign
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for doing this. I made lots of edits -- mostly for grammar / readability and typos, but also for line length. There are also a few questions mixed in with the edit suggestions.
Co-authored-by: Mark Harris <mharris@nvidia.com>
Co-authored-by: Mark Harris <mharris@nvidia.com>
Co-authored-by: Mark Harris <mharris@nvidia.com>
Co-authored-by: Mark Harris <mharris@nvidia.com>
Therefore the wrapper should not contain additional components besides | ||
the above. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Therefore the wrapper should not contain additional components besides | |
the above. | |
Therefore, the wrapper should avoid further data processing and be as | |
simple as possible. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The only change I saw worth noting is that you appear to go back and forth
in your line length selection. For the user docs I am setting all of the lines to
(provisionally) 96 chars wide, and using the double space
as a CRLF
delimiter to instruct markdown to always start a new line where I suggest.
It's my opinion that this improves readability by giving a limited column width
in HTML, and giving a consistent column width when reading in .md
.
rerun tests |
@gpucibot merge |
This PR introduces 3 documents for developer guides. The overall goal for these docs is to provide a place to centralize best practices and provide guidance to developers of all levels to bootstrap development for cuspatial.
This PR deprecates internals.md. The design of geocolumn has improved dramatically since #585 , rendering many of the description obsolete. Further, examples of geoarrow and detail description of geoarrow should be hosted in geoarrow specification.
library_design.md
replacesinternal.md
.CONTRIBUTING.md
is deprecated and only leaves a pointer tocontributing_guide.md
. The contents are highly identical to the overall RAPIDS contribution guide: https://docs.rapids.ai/contributing. This link is included in the contributing guide and is thus removed to maintain a single source of truth.