diff --git a/docs/internals/gsoc-2026.md b/docs/internals/gsoc-2026.md
index fd1c4ed9..62d5bbfc 100644
--- a/docs/internals/gsoc-2026.md
+++ b/docs/internals/gsoc-2026.md
@@ -385,34 +385,6 @@ filesystem restrictions, and resource limits for sandboxed execution.
 
 ---
 
-## Metadata service request improvements
-
-**Difficulty:** Easy
-
-**Duration:** 175 hours (Medium project)
-
-**Technologies:** Python, Docker, PostgreSQL
-
-**Mentors:** Sakari
-
-### Description
-
-The current metadata service for Metaflow does not provide paginated responses for its endpoints. Introducing pagination is required for some backfill-patterns that need to iterate over existing resources, in order to keep the resource requirements of these operations limited. Currently the payloads returned over the wire are not capped, and can be significant in size with more established deployments.
-
-Resources can also be filtered by tags in the Metaflow client. This is currently still happening in-memory over the response payload, as the API does not support filtering. Being able to apply filters on the request level would also cut down on the resource use.
-
-### Goals
-
-1. Being able to return filtered, paginated responses from metadata-service
-
-2. Backwards compatibility with older Metaflow clients that do not support pagination. Possibly by feature-gating via client version in request headers.
-
-3. Handling paginated responses in Metaflow client
-
-4. handling filtering by tag in Metaflow client on the request level, not in-memory.
-
----
-
 ## Jupyter-Native Metaflow
 
 **Difficulty:** Medium
@@ -590,7 +562,7 @@ This project aims to implement a `@nomad` decorator that executes Metaflow steps
 
 **Technologies:** Python, Metaflow Client API, Metaflow Metadata Service
 
-**Mentors:** Valay Dave
+**Mentors:** Valay Dave, Sakari Ikonen
 
 ### Description