Guix Social just welcomed our 105th member to the meetup group! It's been a really fun year of chat and talks about Guix, the declarative approach to Linux, as well as Guile, Scheme and Lisp.
Next week we have another really interesting talk. If you're interested in hanging out with a friendly group - find out more on the Meetup or Wiki pages!
Guix Social next Thursday (January 16th). There will be a talk by @abcdw about his Guile Scheme IDE for Emacs, and the underlying Nrepl project that can be used by any editor. For all the details:
Guix Social online meetup this Thursday with a talk by @cwebber of the @spritely
Interested in distributed communities and #socialmedia ? Or #guile#lisp and their futures in the web browser due to #WASM ! Or how about #guix / #nix and the future of the OS with distributed Shepherd? Christine is always curious, interesting and creative - so don't miss this one!
@jakehamilton@luis_felipe I think it's going to make it difficult at #fossdem. How do we differentiate one group of "Geeks" from the other sets, groups etc.
Online #guix social this Friday 22nd. We'll do patch reviews and general Guix chat. Want to learn more about the #nix approach, but love #scheme and #lisp - this is the #linux#distro meetup for you!
See the #libreplanet wiki for details and links to the Meetup:
Guix solves the technical issue. Real transactions.
At scale and with general users any form of state will kill you eventually. Push an upgrade out to 50 million users and you'll always see a percentage that goes bad. If the user can't reverse out you're screwed.
Deb/RPM weren't designed for that kind of use-case. For their users "ssh and fix it" is fine. Not for the general public 'user' - who need a big UNDO button.
SUSE simulate transactions with btrfs snapshots but it's icky
The projects never done this before so it be great to get input from across the community! Both users and contributors.
There's also a section for people who previously used #guix to understand their experiences adopting Guix. So if you came from #nix#emacs#scheme#guile - whether just for a bit or a long time - we'd love to gather your experiences as well.
#foss#freesoftware#gnu#fsf#libre Hello! please help us promote the Guix user and contributor survey. We're gathering the views of anyone who's used #Guix or contributed to it:
If someone asked you how to get their first job in #software as a #developer what would you say? Non-traditional background but very bright, ideally #FOSS work. Any tips you'd give?
I've been using #virtiofs to access the host filesystem in my #guix#kvm#libvirt#VMs - it's very nice. I have it mount the directory automatically in my guix-system definition:
In the conversation about #guix sustainability I've talked a few times about Clojure Together which I think is a great example of "making things happen" (originally by just one person Daniel Compton) in a small community. Clojure is a small community compared to Python/Rust or whatever - but this project has been great for the Clojure community - recognising, supporting and sustaining improvements. Could equally apply to #guile#scheme
The original question was about whether users MUST make config "Free Software"
Guile says:
"Scheme level code written to be run by Guile (but not derived from Guile itself) is not restricted in any way, and may be published on any terms. We encourage authors to publish on Free terms."
Seems clear to me. There is no **requirement** on users to make their #guix config "Free Software" - users can choose what they want - freedom of choice.