3.0 KiB
3.0 KiB
GNU Guix Beyond 1.0—A Road Map
- ‘guix pull’
- UI/UX
- grafts and profile hooks run as “build continuations” <https://bugs.gnu.org/28310>
- ‘package-derivation’ made faster
- (gnu installer) UI can be used to edit config.scm
- ‘guix system status’ shows info about the current status
- packages can be parameterized
- web application to [re]configure a Guix System
- ‘guix environment’ uses sane defaults and conventions
- GNOME Software backend written (or some other GUI implemented)
- packages made more lightweight (only necessary files are included)
- core
- substitutes can be published and fetched over IPFS <https://issues.guix.gnu.org/issue/33899>
- ‘wip-build-systems-gexp’ branch updated & merged
- labels removed from the inputs fields of packages
- Gash used instead of Bash during bootstrap
- shepherd uses Fibers, logs correctly, can do “socket activation”
- (guix record) provides optional static type checking
- architectures
- build daemon
- devops
- miscellaneous
- infrastructure
- web site officially available at https://guix.gnu.org
- web site includes a package and service browser
- Guix Data Service deployed
- code and services shared between Guix Data Service and Cuirass
- package sources are always archived on Software Heritage
- web site translated in other languages
- official channel registry service available
This is a roadmap of high-level, medium- to long-term tasks that we’d like to tackle for Guix in the comings months or years. You’re welcome to discuss it on guix-devel@gnu.org!
‘guix pull’
TODO 'guix pull' & commit authentication <https://bugs.gnu.org/22883>
TODO build-self.scm trampoline runs faster
UI/UX
TODO grafts and profile hooks run as “build continuations” <https://bugs.gnu.org/28310>
TODO ‘package-derivation’ made faster
TODO (gnu installer) UI can be used to edit config.scm
Maybe leave the possibility to specify a file, or even a URL?