Worker co-op for #guix and #guile jobs. Sounds interesting!

Guixotic | GNU Guix and Guile Worker Cooperative
https://guixotic.coop/

we're pleased to announce https://guixotic.coop, a new free software cooperative focused on gnu guix and guile cofounded by @podiki, maxim cournoyer and me. we offer services including training, commercial support, development, system administration (CI/CD, HPC), packaging -- in short, everything guix and guile.

our goal is to strengthen & expand the community, bringing in new people and organizations (our clients), supporting development work, and growing the network of organizations supporting these technologies.

could you or an organization you know of benefit from our services? email contact@guixotic.coop or contact us here!

full announcement: https://lists.gnu.org/r/guix-devel/2025-07/msg00113.html

Long-time contributors are launching a cooperative specializing in #Guix & #Guile: Guixotic
https://guixotic.coop/

A beautiful initiative; wishing them success!!

Just announced! Guixotic: a worker #Cooperative specializing in #GNU #Guix and #Guile #Scheme https://guixotic.coop/

Sorry, last quick reminder re tomorrow's #Guix #meetup, in meatspace, in #London.

Time: Tuesday 8th July at 6pm
Location: 20 Farringdon St, EC4A 4AB

Full info:
https://www.meetup.com/guix-social/events/308234219/

No need to use meetup.com if that's not your cup of tea or to avoid "account-fatigue". DM me in case.

I learned #scheme back in 1994 or so, at Iowa State University, where the CS dept was very progressive and theory rich. Used it a bit after, and I remember when #guile got adopted as a GNU scripting language around 1998 or something. Now 25+ years later #GUIX is pretty sweet, and I see guile has a byte code compiler and templating JIT. So guile is dramatically more capable than something like bash. The future is now!

Did you notice, that Guile moved to Codeberg?

https://codeberg.org/guile/guile

If I want to provide a "thing" that defines few bindings in a current module, can I write it as a procedure instead of a syntax-case macro? This:

(define (define-stuff)
(let ((m (current-module)))
(module-define! m 'foo 1)
(module-define! m 'bar 2)))

seems to work, however I am getting "possibly unbound variable" warnings (but the code seems to work). Is there a way around that? Or do I need use the syntax-case approach (with-syntax, and regular define)?

I wrote a #blog post on why #scheme (more specifically #guile) and #lisp are great for production and real-world #software and why more companies should adopt it, trying to debunk some illusions and fallacies. Enjoy:

https://jointhefreeworld.org/blog/articles/lisps/scheme-and-lisps-are-great-for-production/index.html

#guix is also a great part of why guile is so awesome

With the idea of promoting the usage of #guix and my favourite #programming language #guile #scheme I created a small project which is still in early stages, but I think with some more #love and #effort can be quite something.

https://jointhefreeworld.org/guile-show-hub/

The Guile ShowHub! Promoting all Guile projects out there! By reading from #foss Guix project source code we can tap into a plethora of information, and leverage the #homoiconicity of #lisp to directly analyze the source code and extract info.

@baleine and I have been messing around with Guile's Stack Traces and now they are freaking awesome.

https://trop.in/blog/actually-useful-stack-traces

I've just packed wayland-scm in #Guix. Sane multischeme (#guile, #chicken,
#gauche) #bindings for #wayland by Mal https://codeberg.org/kfu

See: https://codeberg.org/shegeley/wayland-scm/src/branch/guix

I was able to launch 'empty-window.scm' example. See 'make -f example.Makefile'.

I didn not yet tried it on other complex interfaces (from wlroots). It
might need few more changes to work with them.

Also see my post on existing wayland bindings in Lisps:
https://grigory.tech/posts/wayland-lisps.html

The Bechamel project now has a CoC and a Mediation Process [1] that is based on the Cooperative Software Development Guidelines. [2]

The governance work is done as part of @joinjabber. As a I mentioned in a previous post it will be a similar model to the one @bonfire has.

[1] https://codeberg.org/Bechamel_Guix/collective/src/branch/main/Governance/Circles/Mediation%20Circle/Code%20of%20Conduct.md

[2] https://codeberg.org/msavoritias/Cooperative_Development_Guidelines

Paris: Guix@Paris, Le jeudi 19 juin 2025 de 19h00 à 22h00. https://www.agendadulibre.org/events/32656 #guix #guile #linux #logicielsLibres #rencontreMensuelle

scheme@(guile-user)> 1234
$1 = 1234
scheme@(guile-user)> 12_34
$2 = 1234
scheme@(guile-user)> 123_456_789
$3 = 123456789

Hm, I wonder whether this would be accepted into #guile . Any opinions?

I sat down the other day to re-look through David Thompson guile-bstructs library, as a learning exercise.

I re-learnt a few things I didn't know before. Like how far it's possible to push syntax-rules/case. I've never quite seen anything like it before.

I've said it before, but scheme syntax-rule related stuff isn't the most intuitive thing. Fear of Macros is still the best explanation I've read; but doesn't show off the capability quite like that library does.