boot-clj/boot

split boot kernel and stdlib

Open

#423 opened on Mar 2, 2016

View on GitHub
 (0 comments) (1 reaction) (0 assignees)Clojure (1,748 stars) (178 forks)batch import
help wanted

Description

The suggestion is to break boot into two parts the better to support tool makers who just want the boot kernel without the builtins and utils. A boot.kernel project would contain just boot.core, boot.pod, boot.aether, and whatever else is needed to make a minimal kernel for developers. Then boot.stdlib would contain boot.task.built-in and boot.utils, although you could make the argument that boot.utils should be in the kernel, or in a separate project. You could package both the kernel and the stdlib in a standard boot package for users, but developers could still use just boot.kernel.

Contributor guide

Tech stack
None
Domain
build systemdeveloper experience
Issue type
refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
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.
mostly clear
Prerequisites
Clojureboot project architecturemodularization concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
15
Research direction
Investigate the current structure of the boot project to identify which namespaces belong to boot.core, boot.pod, boot.aether, boot.task.built in, and boot.utils. Propose a detailed plan for splitting the repository into kernel and stdlib, considering dependencies and backward compatibility. Assess the impact on existing users and developers.