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

Tracking: Developer Docs #1384

Closed
9 tasks done
fuyufjh opened this issue Mar 29, 2022 · 3 comments
Closed
9 tasks done

Tracking: Developer Docs #1384

fuyufjh opened this issue Mar 29, 2022 · 3 comments

Comments

@fuyufjh
Copy link
Member

fuyufjh commented Mar 29, 2022

In order to make it easier for community developers to understand the internals, we may migrate some design docs from Quip to this repo under the docs folder.

Unlike Quip, the docs selected is recommended to be relatively stabilized. Discussions should not be placed here.

Please make sure to check the docs before migrating here, including:

  • Revise the outdated descriptions
  • Clean or update the hyperlink to internal docs or resources
  • Complete or rewrite the motivation/context/background to help others to understand
  • Revise some inappropriate words (just in case)

The list below is not completed yet. Please feel free to add more or comment.

@fuyufjh fuyufjh pinned this issue Mar 29, 2022
@TennyZhuang
Copy link
Contributor

I’d like to move docs written by me. Next time for sure!

@skyzh
Copy link
Contributor

skyzh commented Apr 2, 2022

shall we have a ToC under docs folder?

@fuyufjh
Copy link
Member Author

fuyufjh commented Apr 2, 2022

shall we have a ToC under docs folder?

Yes, there is a TODO in the docs/README.md

@fuyufjh fuyufjh unpinned this issue Apr 14, 2022
@fuyufjh fuyufjh closed this as completed Jul 25, 2022
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