feat: rfc-1102 tapplet registry #138
Conversation
src/RFC-1102_TappletsRegistry.md
Outdated
|
|
||
| ## Github Repository | ||
|
|
||
| Github repository is the solution which assumes that every tapplet's metadata is stored in a separate folder, each version in a subfolder. Tapplets themself are distributed az zip bundles, so the code is not stored in the folder. Tapplet Registry manifest file, named `tapplets-registry.manifest.json`, keeps metadata about verified and listed tapplets. |
There was a problem hiding this comment.
| Github repository is the solution which assumes that every tapplet's metadata is stored in a separate folder, each version in a subfolder. Tapplets themself are distributed az zip bundles, so the code is not stored in the folder. Tapplet Registry manifest file, named `tapplets-registry.manifest.json`, keeps metadata about verified and listed tapplets. | |
| Github repository is the solution which assumes that every tapplet's metadata is stored in a separate folder, each version in a subfolder. Tapplets themself are distributed as zip bundles, so the code is not stored in the folder. Tapplet Registry manifest file, named `tapplets-registry.manifest.json`, keeps metadata about verified and listed tapplets. |
src/RFC-1102_TappletsRegistry.md
Outdated
| tapplets-registry.manifest.json | ||
| ``` | ||
|
|
||
| ## Tari Blockchain |
There was a problem hiding this comment.
nit: Usually "Tari Blockchain" refers to the Layer 1, since the L2 is not a blockchain per sê. Tari Network, or L2, is more unambiguous.
src/RFC-1102_TappletsRegistry.md
Outdated
|
|
||
| ## Github Repository | ||
|
|
||
| Github repository is the solution which assumes that every tapplet's metadata is stored in a separate folder, each version in a subfolder. Tapplets themself are distributed az zip bundles, so the code is not stored in the folder. Tapplet Registry manifest file, named `tapplets-registry.manifest.json`, keeps metadata about verified and listed tapplets. |
There was a problem hiding this comment.
If I understand this right:
All curated tapplets' source code will be stored together in a single monolithic Github repo.
I guess this means that to add your app to the registry, you open a PR adding your code to the monolith. Is this right?
Edit: My question is answered below. I'll leave this comment in as an indication that it took a while to grok what this paragraph was saying.
| 1. Mark the version as “deprecated” - special optional tag like “status” can be used | ||
| 2. Update the Tapplet Registry and remove the tapplet from the list available ones |
There was a problem hiding this comment.
Ok, I asked about this in RFC-1101.
So, there's a high degree of trust being placed in the maintainers of the registry repo.
It would be good to make this trust model explicit somewhere.
karczuRF
force-pushed
the
feat/rfc-tapplets-registry
branch
from
914719a
to
48ba395
Compare
The Tapplets Registry is the fundamental part of the Tari Universe. This RFC propose the registry structure as well as manifest file as list of registered and verified tapplets.