theupdateframework / theupdateframework/taps

Title: [GSoC] Interested in implementing TAP 16 - Snapshot Merkle Trees

Open
#191 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
37
Forks
23
PR merge metrics
No merged PRs in 30d

Description

Hi @lukpueh and @JustinCappos,

I hope you’re doing well! My name is Eeshani, and I’m interested in contributing to the implementation of TAP 16 for Snapshot Merkle Trees in the python-tuf project as part of Google Summer of Code (GSoC) 2025.

Before I start working on my proposal, I wanted to reach out and ask a few questions regarding the project:

-Starting the Implementation: Could you provide more detailed guidance on how to begin implementing Snapshot Merkle Trees for TAP 16 in the python-tuf repository? Are there any specific areas or files I should focus on first?

-Testing Strategies: What testing strategies or tools would you recommend for validating the implementation of Snapshot Merkle Trees? Are there existing tests in the repository I should be aware of, or should I create new tests?

-Proposal Expectations: Is there anything specific you would like to see in my GSoC proposal for the implementation of TAP 16 that I might have missed? Any particular focus areas or details that would help you evaluate my proposal more effectively?

I would greatly appreciate any guidance you can offer!

Best regards,
Eeshani (@ennie191)
ennie19105@gmail.com

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

The issue names TAP 16 Snapshot Merkle Trees and the python-tuf repository but no files, tests, or acceptance criteria. Start by reviewing TAP 16 and the relevant python-tuf implementation and tests; the issue does not define what completion should look like, so maintainer guidance is needed before work can begin.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
cryptography, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.