paritytech / paritytech/jamtart

Improve naming in Bottlenecks section of TART Cores page

Open Beginner friendly
#41 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
18
Forks
3
Avg merge
3d 15h
Merged PRs (30d)
3

Description

Authorize and Refine are clear enough. That said Refine is not amazing because it includes transfer of the extrinsic data and fetching of imports at the moment. We should probably just add extra stages for these (there are JIP-3 events, so adding stages is just a TART thing).

It looks like "Report" means "Build Report", this is kind of confusing as "Report" as a verb is used to mean including the report on-chain. So I would expand this to "Build Report".

"Guarantee" means the time from "Built Report" to "Built Guarantee". This is going to be 99% waiting for signatures from other guarantors. Perhaps "Build Guarantee" with a note about that would be fine.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Find the source for the TART Cores page and its Bottlenecks section. Review the current stage labels, change “Report” to “Build Report,” clarify “Guarantee” as “Build Guarantee” with the waiting note, and consider separate stages for extrinsic-data transfer and import fetching; verify the rendered page.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
1/5
Estimated time
Under an hour
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
76/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.