FOSDEM 2023 - Declarative and Minimalistic Computing - Call for Participation
We are excited to announce a devroom on Declarative and Minimalistic Computing at FOSDEM on 4th of February, 2023! FOSDEM is one of the most important free software conferences and is hosted annually at Université libre de Bruxelles in Brussels, Belgium. This year FOSDEM will be a physical conference. Talks will be done in person and we will also have virtual talks! We accept talks from languages that attempt to minimize use of hardware and software while trying to make systems simpler, more robust and more secure. If you are working on improving today's systems taking declarative/minimalistic approaches feel free to submit a talk proposal. Examples include the Scheme/Lisp family of programmings languages. In past editions, this devroom has received presentations from a varied number of language communities, including Forth, Guile, Lua, Nim, Racket, Raku and Tcl as well as several experimental projects that push minimalism in new directions. Minimalism and declarative programming are two important topics for this devroom. Minimalism matters. Minimalism allows for smaller systems that take less resources and consume less energy. More importantly, free and open source minimalism allows for secure systems that are easy to understand. Declarative programming is a programming paradigm that expresses the logic of a computation without describing its control flow. Many languages that apply this style attempt to minimize or eliminate side effects by describing what the program must accomplish in terms of the problem domain, rather than describe how to accomplish it as a sequence of the programming language primitives. Finally, in this year's virtual conference we will honour the late Professor [https://en.wikipedia.org/wiki/Dennis_Ritchie Dennis Ritchie] the creator of the C programming language and the Unix operating system. C was designed as a minimal language that reflects the underlying CPU architecture closely, i.e., a high-level assembler. C is very popular today and the Linux kernel is almost completely written in C. In this edition we will also invite speakers that are working on new projects and minimalistic languages in the spirit of C. We want to invite you to submit a talk on declarative and minimalistic computing that fits that description. We are especially happy to receive talk submissions from members of groups underrepresented in free software. If you have something you’d like to share with your fellow developers, please E-mail us! Talks considered for the devroom will have to be entered in - https://penta.fosdem.org/submission/FOSDEM23 The deadline for submission is December 3rd. If you have a FOSDEM pentabarf account from a previous year, please use that account. Otherwise add one on https://penta.fosdem.org/user/new_account. Reach out to pjotr.public...@thebird.nl or manolis...@gmail.com if you run into any trouble. When submitting your talk make doubly sure to select "Declarative and Minimalistic Computing devroom" as track (if you don't we won't find it), and include the following information: * The title and subtitle of your talk * A short abstract of one paragraph * A longer description if you wish to do so * Links to related websites/blogs etc To see what a final talk looks like see https://archive.fosdem.org/2021/schedule/event/gnumes/ Let's make this a fun day! = Organizers = Pjotr Prins, Manolis Ragkousis, Jonhathan McHugh, Bonface Munyoki, Arun Isaac, Ludovic Courtès, Amirouche Boubekki, Hisham Muhammad, Jan Nieuwenhuizen, Ricardo Wurmus, Alex Sassmannshausen, William Byrd, Oliver Propst, Efraim Flashner, Julien Lepiller = Code of conduct = - https://fosdem.org/2023/practical/conduct/ = Original proposal = - https://libreplanet.org/wiki/FOSDEM2023-devroom-proposal = Important dates: = - Dec 3rd 2022: submission deadline for talk proposals - Dec 15th 2022: announcement of the final schedule - Feb 4th 2023: FOSDEM! https://libreplanet.org/wiki/FOSDEM2023-devroom-declarative-and-minimalistic-computing-cfp
gwl-0.5.1 released [stable]
We are pleased to announce the release of the GNU Guix Workflow Language version 0.5.1, representing 17 commits by two people, incorporating the results of productive discussions among a number of helpful people on the #guix and #guix-hpc IRC channels on libera.chat and on the gwl-de...@gnu.org mailing list. This is a maintenance release with a number of bug fixes. For details see the NEWS excerpt below. See also the manual: https://workflows.guix.info/manual/ • About The Guix Workflow Language (GWL) provides an extension to GNU Guix's declarative language for package management to automate the execution of programs in scientific workflows. The GWL can use process engines to integrate with various computing environments. • Download Here are the compressed sources and a GPG detached signature[*]: https://ftpmirror.gnu.org/gwl/gwl-0.5.1.tar.gz https://ftpmirror.gnu.org/gwl/gwl-0.5.1.tar.gz.sig Use a mirror for higher download bandwidth: https://www.gnu.org/order/ftp.html [*] Use a .sig file to verify that the corresponding file (without the .sig suffix) is intact. First, be sure to download both the .sig file and the corresponding tarball. Then, run a command like this: gpg --verify gwl-0.5.1.tar.gz.sig If that command fails because you don't have the required public key, then run this command to import it: gpg --keyserver keys.gnupg.net --recv-keys BCA689B636553801C3C62150197A5888235FACAC and rerun the 'gpg --verify' command. This release was bootstrapped with the following tools: Autoconf 2.69 Automake 1.16.3 Gnulib v0.1-3269-g03d7a6b1f NEWS * Changes in 0.5.1 (since 0.5.0) ** Package handling - Packages are now handled as Guix manifests instead of plain lists. This makes handling of package outputs nondestructive. It also fixes an unrelated issue in the ordering of process packages – the implicit bash-minimal is now ordered last. ** Bug fixes - Fix argument parsing handler for =max-file-size= option. - Fix argument paring validation for =workflow-directory= option. - Fix secondary argument parsing for input mapping. This was likely broken by commit 2a5a34bc2062ccd04d33d61530a1e9ed03140d82 that causes “--” to be passed as an argument to the GWL entry point. - Use an identity comparison for all lookups of processes in hash tables. This is a continuation of work done in 0.5.0. - Remove over-zealous caching of processes based on identical procedures. This would ignore differences in the execution environment. ** Miscellaneous - The contents of input files are now hashed instead of just their metadata. -- Ricardo signature.asc Description: PGP signature
More rebuilds might be required under some circumstances.
hi ludo, Hope all is well! In the manual (guix.texi), you mentioned that "More rebuilds might be required under some circumstances" when running --list-dependent. What are those circumstances? Could you help us document the circumstances so we can have the background context/more explanations on that? If you reply to this I can make a patch to provide more context there from what you explained here. all best, jgart
Re: [Guix Website] A Search Page for Packages
Luis Felipe writes: >> > What Danjela produced in terms of the search is probably fine as >> > something to go with, maybe the additional thing that needs writing is >> > pages for the individual packages that the search can link to (they can >> > just be very simple initially). >> >> > But yeah, are you (or anyone else who's reading) up for hacking on this? >> >> Yeah, I'm willing to work on that. I'll start by adding support for handling >> requests for package detail pages. > > I have a working package browser now and will be styling it next. I'll link > to a public repository later. > > However, I have some questions about the Data Service: Hey! Sorry for the slow reply. > 1. Is there any way to page through the data > (e.g. https://dev.socrata.com/docs/paging.html#2.1)? For most bits of data, yes. Although I haven't used limit/offset style pagination as that doesn't perform particularly well. The Guix Data Service web pages should help with how to use the API, so you can look at how the packages page handles pagination for example: https://data.guix.gnu.org/revision/c4025af8c11c3e9ea0c2747b6c475c916fb61d80/packages > 2. What would be an efficient way to get the total count of packages? > (to be used as in https://guix.gnu.org/en/packages/) You can get a count here for example [1], that also works with the latest-processed-revision URL [2]. I think the counting methadolody is a bit different to what's currently used though. 1: https://data.guix.gnu.org/revision/c4025af8c11c3e9ea0c2747b6c475c916fb61d80.json 2: https://data.guix.gnu.org/repository/1/branch/master/latest-processed-revision.json > 3. Is there any way to get the "supported-systems" info of a package? The value of that specific field isn't recorded, but you could look at the derivations of the package, then just find the systems, that should be pretty close: https://data.guix.gnu.org/revision/c4025af8c11c3e9ea0c2747b6c475c916fb61d80/package/0ad/0.0.26-alpha.json Thanks, Chris signature.asc Description: PGP signature
