2 comments (2 comments)5 reactions (5 reactions)0 assignees (0 assignees)Shell19,151 stars (19,151 stars)323 forks (323 forks)batch import
help wanted
Description
See title. Ideally on per-font-basis.
Contributor guide
- Tech stack
- shell
- Domain
- devops
- Issue type
- feature
- 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.
- fresh
- ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
- clear
- Prerequisites
- Chocolatey packagingWindows environmentPowerShell basicsMonaspace font structure
- Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
- 65
- Research direction
- To implement, first review the Monaspace repository structure to understand font files and licensing. Then examine existing Chocolatey packages for fonts (e.g., on chocolatey.org) for patterns. Create a package with install script that optionally allows per font installation. Test on Windows. No linked PRs or maintainer clarification needed.