Re: Guix Documentation Meetup
Ryan Prior writes: > I've found the Guile IRC channel to be polite and encouraging, but also very > self-satisfied, which makes it hard to feel heard as a Guile hacker who's > struggling. Consider reaching out to Andy Wingo (wingo in IRC in #guile). I hope I am not laying this issue at his feet by suggesting this, but I have interacted with him a handful of times, and he is a genuinely nice and helpful person, and also a guile maintainer. I am pretty confident he would want to help make this problem better -- especially if there are those willing to do some work. Good luck! I have also found myself hunting around for basic functionality, and not being a guiler, nor even a schemer (I love lisps, but I mostly write emacs-lisp and common-lisp), wondering why things are fragmented into weird modules. It's a shame, because I feel like I would be contributing bigger features to Guix if I could stop bouncing off the language. -- Katherine
Re: bluetooth-service: addition config vaules
On 2021-12-11 14:57, Josselin Poiret wrote: > I think this is pretty approachable, especially given the fact that you > don't need to write the whole service from scratch. > > All of the following takes place in gnu/services/desktop.scm: the > options given to the service via the bluetooth-configuration record end > up being inserted into the gexp that the bluetooth-directory procedure > returns, which is itself used to build the actual /etc/bluetooth/ > directory for the system (see "G-Expressions" in the manual if you want > more info about gexps, although you won't need to manipulate them for > this). The contents of the main.conf file are generated with the > bluetooth-configuration-file procedure, which contains only basic string > manipulation. > > So, in order to add new options to the bluetooth service, > you would need to only modify the bluetooth-configuration record to add > them, with proper defaults, as well as add the relevant lines in > bluetooth-configuration-file. As to testing, you could simply run `guix > system build some-test-system-conf.scm` and check that the resulting > /gnu/store/-system/etc/bluetooth/ folder contains the proper > configuration file. Ideally, you would also test if the features > themselves end up working properly, but I am hopeful that bluetoothd > will handle them just as well. > > Good luck! > > Best, > Josselin Poiret Hello Josselin, I should have been more clear with my last message. Indeed I would be able to add the additional config values to the service. I haven't done so because I was told in order to get a service merged into Guix, one has to provide a "test marionette" (I don't even know what that is since it's not documented in the manual). That's what was holding me back. But if that's not the case I'll gladly submit a patch in the upcoming days. -- Best regards / Mit freundlichen Grüßen, Demis Balbach signature.asc Description: PGP signature
Re: bluetooth-service: addition config vaules
Hello, Demis Balbach writes: > If someone can explain to me how to test and submit it myself, I'll do > it. But I head that it's not as easy as submitting a patch for a > package. I believe a seasoned contributer could submit something way > faster. > > In any case, > > Best regards / Mit freundlichen Grüßen, > Demis Balbach I think this is pretty approachable, especially given the fact that you don't need to write the whole service from scratch. All of the following takes place in gnu/services/desktop.scm: the options given to the service via the bluetooth-configuration record end up being inserted into the gexp that the bluetooth-directory procedure returns, which is itself used to build the actual /etc/bluetooth/ directory for the system (see "G-Expressions" in the manual if you want more info about gexps, although you won't need to manipulate them for this). The contents of the main.conf file are generated with the bluetooth-configuration-file procedure, which contains only basic string manipulation. So, in order to add new options to the bluetooth service, you would need to only modify the bluetooth-configuration record to add them, with proper defaults, as well as add the relevant lines in bluetooth-configuration-file. As to testing, you could simply run `guix system build some-test-system-conf.scm` and check that the resulting /gnu/store/-system/etc/bluetooth/ folder contains the proper configuration file. Ideally, you would also test if the features themselves end up working properly, but I am hopeful that bluetoothd will handle them just as well. Good luck! Best, Josselin Poiret
Re: Organising Guix Days
Hello Julien, Julien Lepiller ezt írta (időpont: 2021. dec. 11., Szo, 2:37): > Hi Guix! > > I think it's time to start organising the Guix Days, traditionally held > around Fosdem. > Super good initiative. > During our guix-europe assembly, we discussed some options and everyone > agreed they wanted a two-day event, online just as Fosdem. I attached a > proposed blog post that we should put on the website as soon as we > agree on the first details. > > I suggest that we have these days right after Fosdem, Monday and > Tuesday. This should give us just a few more days to prepare, as I think > we're starting pretty late already. If you prefer to have them before > fosdem, I can change the blog post of course. > Sounds good to me. > As for how it'll be organised. I propose to do something similar to > what we need in November 2020. I'd love to get some talks from people > outside the usual maintainers and commiters, to have an overview of the > diversity of people and usage around Guix. > > Last year, we asked speakers to prepare a video in advance, and they > would only have an extended Q&A/discussion session. I think this year > we should have the same process, but ask for a short (3-5 minutes) talk > at the start of the session to refresh our minds on the main points of > the presentation before discussions start. > > Of course, one of our co-maintainers should have a session on a > retrospective (what happened last year in Guix) and lead discussions on > the future of Guix. We should reserve plenty of time for this session. > > In addition, I'd like to invite people to submit discussion ideas and > be free of having to make a presentation if they prefer (BoF). I'd also > like to "innovate" and have a session of lightning talks, where people > would only have to give a short, live presentation on any topic related > to Guix (I'm thinking short presentation of a project where you use > guix, of something you're doing with guix, how you found guix, a story > of your first days with guix, ...). We can also replace that with a > presentation round at the beginning of the conference if we don't have > enough lightning talks. > > The Guix Days have never been a "real" conference, and always had a lot > of room for discussions that start on the spot. I'd like to emulate > this by keeping a lot of time out of the talk sessions to discuss > whatever comes up naturally during our discussions. > > Also, we need to secure a BBB instance :) > Should you need any help in organizing, feel free to reach out to me, I will try to do my best. > WDYT? > Thanks for the effort that went into this so far, I am looking forward to participating. Best regards, g_bor