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.

Sign up for GitHub

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

[review] MD-91: Define the Move Stack #91

Merged
merged 7 commits into from
Jan 21, 2025
Merged

[review] MD-91: Define the Move Stack #91

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
aefaa8a
init
apenzk Jan 17, 2025
a9550c8
add content
apenzk Jan 17, 2025
0dd905f
add another desiderata
apenzk Jan 17, 2025
b57d3a7
change folder
apenzk Jan 17, 2025
5029438
file removal
apenzk Jan 17, 2025
773ecd9
codeowners
apenzk Jan 17, 2025
684ef62
update MD number
apenzk Jan 17, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions .github/CODEOWNERS
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,3 +13,4 @@
/MIP/mip-39/ @franck44
/MIP/mip-53/ @l-monninger
/MIP/mip-58/ @primata @apenzk
/MIP/mip-91/ @apenzk
42 changes: 42 additions & 0 deletions MD/md-91/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,42 @@
# MD-91: Define Move Stack and Movement SDK

- **Description**: Define the Move Stack and the Movement SDK to provide clear categorization of our software components and standardize language around the Movement technologies.
- **Authors**: Andreas Penzkofer

## Overview

The Move Stack and Movement SDK are foundational components for Movement technologies, aimed at empowering developers with standardized tools, interfaces, and services for building, interacting with, and maintaining Movement Labs' networks and dApps.

## Desiderata

### D1: Standardization of Development Stack

**User Journey**: Developers can utilize a well-documented stack to build and maintain Movement Labs' networks and dApps.

**Justification**: Ensures high quality of documentation.

### D2: Create Categories for Move Stack components

**User Journey**: Developers are able to have an easy access to which category is relevant to them.

**Justification**: The Move Stack may be extensive and complex, so categorization is necessary. It will accelerate for developers to find their way within the stack.

### D2: Categorization of Software Components

**User Journey**: Software components are clearly categorized and associated with categories within the Move Stack.

**Justification**: Categorization of Software components helps to provide consistent documentation and may aid in framing the documentation. It also provides a clear and consistent language for discussing Movement technologies.

### D3: Vizualization of the Move Stack

**User Journey**: Developers can easily understand the Move Stack and its components.

**Justification**: Visualization of the Move Stack will help developers to understand the components and their relationships.

### D4: Reduce confusion between SDK and Stack

**User Journey**: Developers are able to understand what the SDK implies.

**Justification**: There has been much confusion about what the SDK constitutes. There is great need for clarification to align language in the ecosystem.

## Changelog
Loading