mtca: Start using trees/cosginature in mtca
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
Research direction
The issue has no description, files, tests, or entry points to guide implementation. First clarify what “trees/cosignature” means in mtca, identify the affected Boulder components and expected behavior, then define tests that demonstrate when the feature is complete.
Written by the indexing model from the issue text.
Description
This issue has no description.
- Dominant language
- Go
- Stars
- 5.8k
- Forks
- 649
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 24
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.
More from letsencrypt/boulder
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
letsencrypt/boulder#8979 · 1 reaction ·
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
letsencrypt/boulder#9022 ·
-
letsencrypt/boulder#9021 · 1 assignee ·
-
Difficulty 5/5 Over a week Newbie friendliness 39/100
letsencrypt/boulder#9020 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
letsencrypt/boulder#9018 ·
All issues in letsencrypt/boulder
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
enhancement needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
kind/cleanup
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
kubernetes-sigs/kueue#15947 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sympozium-ai/sympozium#627 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100