RS can be used freely and without permission to indicate that software or a project is derived from or based on Rust, compatible with Rust, inspired by Rust, or can be used for the same purpose as Rust. We recommend using RS instead of ‘Rust’ if you have any concerns about your use falling outside of this policy, for example, naming your crate foo-rs instead of rust-foo.
Some discussion can be found in this Reddit post.
Update: there has since been a followup note posted on the process being followed in the creation and consideration of this draft policy.
We want to thank the community for participating in this process, and for your patience as we learn the best way to navigate it. We recognize that the process and communication around it could have been better. Notably, the wider project was insufficiently included in the process. We were responsible for that and apologize.
We are pleased to announce the Call for Papers (CFP) for Microconferences at the Linux Plumbers Conference (LPC) 2023.
LPC 2023 is currently planned to take place in Richmond, VA, USA from 13 November to 15 November. For details about the location, co-location with other events see our website and social media for updates.
Like in 2022, Linux Plumbers Conference will be a hybrid event but still, ideally microconference runners should be willing and able to attend in person.
As the name suggests, LPC is about Linux plumbing encompassing topics from kernel and userspace. A microconference is a set of sessions organized around a particular topic. The topic can be a kernel subsystem or a specific problem area in either kernel or userspace.
A microconference is supposed to be research and development in action and an abstract for a Microconference should be thought of as a set of research questions and problem statements.
The sessions in each microconference are expected to address specific problems and should generate new ideas, solutions, and patches. Sessions should be focused on discussion. Presentations should always aim to aid or kick off a discussion. If your presentation feels like a talk we would recommend to consider submitting to the LPC refereed track.
In the past years microconferences were organized around topics such as security, scalability, energy efficiency, toolchains, containers, printing, system boot, Android, scheduling, filesystems, tracing, or real-time. The LPC microconference track is open to a wide variety of topics as long as it is focused, concerned with interesting problems, and is related to open source and the wider Linux ecosystem. We are happy about a wide range of topics!
A microconference submission should outline the overall topic and list key people and problems which can be discussed. The list of problems and specific topics in a microconference can be continuously updated until fairly late. This will allow microconferences to cover topics that pop up after submission and to address new developments or problems.
Microconferences that have been at previous LPCs should list results and accomplishments in the submission and should make sure to cover follow-up work and new topics.
Submissions are due on or before 11:59PM UTC on Sunday, June 1, 2023.
Calgary and elsewhere, 2023-04-10: The OpenBSD project today announced the release and general availability of its latest stable version, OpenBSD 7.3.
Eagerly anticipated by users, engineers, enthusiasts and industry pundits all over the world, this release contains a number of improvements over earlier versions, including but not limited to
You may notice that the list of OpenBSD Innovations has grown a bit too, while the detailed changelog offers more detail.
All reasonably modern architectures had install sets and complete binary packages available on the mirrors at the time of the announcements.
Some slower (historic or just weird) architectures are still building but OpenBSD still supports 14 architectures.
While you are waiting for your downloads, installs or upgrades to complete (or even before starting either), please remember to visit the donations page and/or buy OpenBSD swag to support the project financially.
And finally, this release is the first since OpenBSD 7.0 to feature a release song. The Wizard and the Fish is the new obligatory addition to your hacking playlist.
But before the festivities can begin, we still need to take care of business: Sunday still means another release candidate. Those rascally (and biologically confused) egg-laying rabbits must not distract us from kernel development.
Subject: LibreSSL 3.7.2 Released From: Brent Cook <busterb () gmail ! com> Date: 2023-04-08 11:59:41 We have released LibreSSL 3.7.2, which will be arriving in the LibreSSL directory of your local OpenBSD mirror soon. This is the first stable release for the 3.7.x branch, also available with OpenBSD 7.3 It includes the following changes from the 3.6.x series * Portable changes - Moved official Github project to https://github.com/libressl/. - Build support for Apple Silicon. - Installed opensslconf.h is now architecture-specific. - Removed internal defines from opensslconf.h. - Support reproducible builds on tagged commits in main branch.
While it shares some commonalities with other build systems (like Buck1 and Bazel), Buck2 is a from-scratch rewrite. Buck2 features a complete separation of the core and language-specific rules, with increased parallelism, integration with remote execution and virtual file systems, and a redesigned console output. All of these changes are aimed at helping engineers and developers spend less time waiting, and more time iterating on their code.
There seems to be broad support for paying people who are already involved as Debian contributors, but very little support for hiring contractors, that is to say, those who are not already Debian contributors in some way. Members of the Security Team were by far the most supportive towards the idea of paying Debian contributors.
The full report is available for those wanting all the details and pie charts.