[
https://issues.apache.org/jira/browse/RATIS-220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tsz-wo Sze updated RATIS-220:
-----------------------------
Parent: RATIS-75
Issue Type: Sub-task (was: Improvement)
> Overall project design document
> -------------------------------
>
> Key: RATIS-220
> URL: https://issues.apache.org/jira/browse/RATIS-220
> Project: Ratis
> Issue Type: Sub-task
> Components: documentation
> Affects Versions: 0.1.0-alpha
> Reporter: Vinay Banakar
> Assignee: Tsz-wo Sze
> Priority: Major
> Labels: documentation
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> Although the code is well documented, the project's design is nowhere to be
> found. Each of the listed components can have their own documentation page
> delineating its purpose and dependencies. Have one master design document
> which portrays overall system design and interaction between components.
> To begin with, let's not be scrupulous about flowcharts and UML diagrams. A
> simple high level diagram would do.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
