ipfs/kubo

Carve out namesys into a separate repo

Open

#3732 opened on Feb 28, 2017

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Go (13,906 stars) (2,725 forks)batch import
help wantedkind/enhancement

Description

I am finding myself go getting all of go-ipfs just to import "github.com/ipfs/go-ipfs/namesys/pb". Would it make sense to carve out namesys into a separate repo?

Contributor guide

Tech stack
go
Domain
developer experience
Issue type
refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Go programmingGo modulesGit repository managementIPFS project understanding
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
Examine the namesys package in the go ipfs repository to understand its dependencies and exported API. Review the two comments on the issue for any additional context or concerns. Determine the steps needed to create a new repository, move the package, and update import paths across the codebase.