Publish the vdir specification as a standalone spec #30
Conversation
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
Verbatim copy from the vdirsyncer documentation, adapted from ReStructuredText to Markdown. See: https://github.com/pimutils/vdirsyncer/blob/41b48857ebd7ad6d7b818295b86677fc84c13dae/docs/vdir.rst
|
I'd also like to append a list of Authors at the end. @dilyanpalauzov, @untitaker: are you okay with me using the same name/email as in the commits made to the original file? |
|
My input is so little on this, that you can skip mentioning me. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Publish the vdir specification as a standalone spec, to clearly reflect that it is not merely an internal implementation detail of vdirsyncer/pimsync.
This is based on the original spec from vdirsyncer's documentation with a few extra clarifications.
Fixes: #20