Content Addressable Bundles
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 125
- PR merge metrics
- No merged PRs in 30d
Description
Let me file an issue to discuss a proposal: Resource Loading with Content Addressable Bundles.
This is a strawperson proposal at very early stage, and this can be positioned as "my personal proposal", as of now.
I've put it in explainer directory, however, if that is inappropriate and confusing, I'll move it to somewhere. Maybe we can have proposals directory, as WICG/webcomponenets has. I am not sure what is the best practice in this repository.
I hope we can use this issue to discuss and get early feedback.
I've observed that PRs are not a good place to discuss overall design and ideas because we are likely to lose the discussion history. An issue might be a better place to discuss.
cc: @littledan @jyasskin @yoavweiss
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading explainer/content-addressable-bundles.md and the issue discussion about whether it belongs in explainer or a proposals directory. No implementation entry point, test, or concrete acceptance criteria are identified; done would require an agreed proposal direction and repository placement.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100