CIDT - Polywrap Go Client

Description

CIDT will deliver Polywrap Go Client

Backlog

Storyboard: StoriesOnBoard
Shapshot proposal: Snapshot

Epic User Story Estimation
General Project modules, interfaces, structures 2
General Example Applications 2
General End-to-end Tests 3
WebAssembly Runtime Wasmtime integration 3
WRAP Standard Data Types 1
WRAP Standard URI Resolver Interface 1
WRAP Standard MessagePack Generic Interface Support 3
Wrapper WebAssembly Wrapper 5
URI Resolver FileSystem 2
TOTAL SP 22

SP Team Roles & SP Cost

Proposed Dev Team specialties, along with estimated individual time commitment and cost per Story Point (SP)

Team Roles Time Commitment (Hrs/SP) Rate ($/Hr) Cost/SP
Program Manager, Scrum Master 1 $120 $120.00
Tech Lead, Lead Architect 2 $150 $300.00
Golang Developer 8 $120 $960.00
Total Team 1SP Cost $1,380.00
Total Story Points 22
Total Cost $30,360.00

Velocity & Estimated Timeline

Polywrap DAO uses Story Points (SP) to derive duration estimates for development projects. We define Baseline SP = as approximately 1 Day of Individua/Team effort.

Target Monthly Velocity Estimated Start Estimated Duration
20 SP/Month 1-Nov-22 ~1-1.5 Months

Sponsor Review

Sponsor:

  • Jordan
  • Nester

Terms

By submtting this proposal, I understand that the DAO and my sponsor will be evaluating whether my work meets the acceptance criteria. If it does not, the DAO will determine what percentage of the proposal cost to pay, if any.

I also understand that I may not begin work until it is confirmed that the Snapshot proposal has passed.

[ X ] I agree

Hey @ramil, why does “Wasmtime Integration” have 10 story points assigned to it? I’m not sure why this would take so much time.

Do you think you need the tech lead role? I think that core devs should be leading, but no strong opinion here

This is our typical process to have Tech lead do code reviews and provide technical direction.

Hi @dOrgJelli

Under Wasmtime integration story I allocated time for:

  • generate project structure with module breakdown, Go interfaces and structures
  • integration with Wasmtime library including general tests that verify wasm runtime works fine
  • example applications on Go that show how to use Polywrap Go Client
  • end-to-end tests

Maybe it makes sense rename this User Story to something more relevant describing work?

Okay this helps, I think breaking it apart into separate stories instead of having one large one would be helpful.

1 Like

@dOrgJelli will work for you following story break down:

Epic User Story Estimation
General Project modules, interfaces, structures 2
General Example Applications 2
General End-to-end Tests 3
WebAssembly Runtime Wasmtime integration 3
1 Like

Hey all, what’s the status on this? Can I put it up for proposal on snapshot?

@Jure @dOrgJelli

It was already posted, but not cross-linked: Snapshot