Hi Guix! sorry if I'm going to reinvent some wheels but I've not found previous discussions nor documentation about what I'm writing what about reusing work already done from the Debian JavaScript Maintainers team [1]? they set up some interesting policies we could adapt to Guix needs and pusblish somewhere (where?) I mean pages like: - https://wiki.debian.org/Javascript/Policy - https://wiki.debian.org/Javascript/Nodejs they have an npm2deb importer https://wiki.debian.org/Javascript/Nodejs/Npm2Deb ... we could import what they import :-) I see in Apr 2016 a brief discussion on a .deb importer was done https://lists.gnu.org/archive/html/guix-devel/2016-04/msg01053.html what is the updated situation today? Brett Gilio writes: [...] > Thank you for taking the initiative on this, swedebugia. I tend to agree > with your licensee approach, but I think this will require an undoubted > good deal of man power before we are able to sufficiently move forward > on npm imports with a decent velocity. could a .deb importer help us to manage this *very big* workload, sharing this burden with Debian JavaScript maintainers? I found this project as a starting point https://gitlab.digitalcourage.de/htgoebel/guix-import-debian [...] > I guess one could argue that we should be wanting to bring them to us, > but I also know how disuasive "a lack of convenience" can be to those > who are not as freedom and ethicality conscious as the rest of us. should we ignore/deprecate npm packages with licensing issues and work with the ethically conscious like Debian JavaScript Maintainers? having a fully free software _and_ reproducible [3] nodejs/javascript dev environment would benefit a **huge** amount of web developers... they will be so happy to be guixified! :-) [...] ciao Giovanni [1] https://wiki.debian.org/Javascript [2] https://packages.debian.org/stretch/libjs-jquery [3] and bootstrappable? -- Giovanni Biscuolo Xelera IT Infrastructures