Today, DreamWorks published the open-source code for MoonRay, their production renderer used for films like The Bad Guys, Puss in Boots: The Last Wish, and other animation films. “OpenMoonRay is available via DreamWorks Animation’s GitHub,” reports Phoronix. “This professional-grade renderer is available under an Apache 2.0 license.”

From the README: “MoonRay was developed at DreamWorks and is in continuous active development and includes an extensive library of production-tested, physically based materials, a USD Hydra render delegate, multi-machine and cloud rendering via the Arras distributed computation framework.”

More details can be found via OpenMoonRay.org.

Read more of this story at Slashdot.

L.Kynes shares a report from CSO Online: At a time when almost all software contains open source code, at least one known open source vulnerability was detected in 84% of all commercial and proprietary code bases examined by researchers at application security company Synopsys. In addition, 48% of all code bases analyzed by Synopsys researchers contained high-risk vulnerabilities, which are those that have been actively exploited, already have documented proof-of-concept exploits, or are classified as remote code execution vulnerabilities. The vulnerability data — along with information on open source license compliance — was included in Synopsys’ 2023 Open Source Security and Risk Analysis (OSSRA) report (PDF), put together by the company’s Cybersecurity Research Center (CyRC). “Of the 1,703 codebases that Synopsys audited in 2022, 96% of them contained open source,” adds L.Kynes, citing the report. “Aerospace, aviation, automotive, transportation, logistics; EdTech; and Internet of Things are three of the 17 industry sectors included in the report that had open source in 100% of their audited codebases. In the remaining verticals, over 92% of the codebases contained open source.”

Read more of this story at Slashdot.

Long-time Slashdot reader wonkavader found a video on YouTube where, at the 2:50 mark, there’s time-lapse footage of soldering paste magically melting into place. The secret?
Many circuit boards include a grounded plane as a layer. This doesn’t have to be a big unbroken expanse of copper — it can be a long snake to reduce the copper used. Well, if you run 9 volts through that long snake, it acts as a resistor and heats up the board enough to melt solder paste. Electronics engineer Carl Bugeja has made a board which controls the 9 volt input to keep the temperature on the desired curve for the solder.

This is an interesting home-brew project which seems like it might someday make a pleasant, expected feature in kits.

Hackaday is impressed by the possibilities too:
Surface mount components have been a game changer for the electronics hobbyist, but doing reflow soldering right requires some way to evenly heat the board. You might need to buy a commercial reflow oven — you can cobble one together from an old toaster oven, after all — but you still need something, because it’s not like a PCB is going to solder itself. Right?

Wrong. At least if you’re Carl Bugeja, who came up with a clever way to make his PCBs self-soldering…. The quality of the soldering seems very similar to what you’d see from a reflow oven…. After soldering, the now-useless heating element is converted into a ground plane for the circuit by breaking off the terminals and soldering on a couple of zero ohm resistors to short the coil to ground.

It’s an open source project, with all files available on GitHub. “This is really clever,” tweeted Adrian Bowyer, inventor of the open source 3D printer the RepRap Project.

In the video Bugeja compares reflow soldering to pizza-making. (If the circuit board is the underlying dough, then the electronics on top are the toppings, with the solder paste representing the sauce that keeps them in place. “The oven’s heat is what bonds these individual items together.”)

But by that logic making a self-soldering circuit is “like putting the oven in the dough and making it edible.”

Read more of this story at Slashdot.

In June GitHub announced they’d retire their customizable text editor Atom on December 15th — so they could focus their development efforts on the IDEs Microsoft Visual Studio Code and GitHub Codespaces. “As new cloud-based tools have emerged and evolved over the years, Atom community involvement has declined significantly,” according to a post on GitHub’s blog.

So while “GitHub and our community have benefited tremendously from those who have filed issues, created extensions, fixed bugs, and built new features on Atom,” this now means that:

– Atom package management will stop working
– No more security updates
– Teletype will no longer work
– Deprecated redirects that supported downloading Electron symbols and headers will no longer work
– Pre-built Atom binaries can continue to downloaded from the atom repository releases

Fortunately, in 2014 GitHub open sourced the code for Atom. And according to It’s FOSS News:

A community build for it is already available; however, there seems to be a new version (Pulsar) that aims to bring feature parity with the original Atom and introduce modern features and updated architecture….

The reason why they made a separate fork is because of different goals for the projects. Pulsar wants to modernize everything to present a successor to Atom. Of course, the user interface is much of the same. Considering Pulsar hasn’t had a stable release yet, the branding could sometimes seem all over the place. However, the essentials seem to be there with the documentation, packages, and features like the ability to install packages from Git repositories….

As of now, it is too soon to say if Pulsar will become something better than what the Atom community version offers. However, it is something that we can keep an eye on…. You can head to its official download page to get the package required for your system and test it out.

Like Atom, Pulsar is cross-platform support (supporting Linux, macOS, and Windows).

Read more of this story at Slashdot.

Amazon and Amazon Web Services (AWS) have joined the Open Invention Network (OIN) — the world’s largest patent non-aggression consortium. ZDNet reports: OIN has long protected Linux and Linux-related software from patent aggression by rival companies. With the recent increase in patent troll attacks, the OIN is also defending companies from these assaults. This is a natural move for Amazon. Besides relying on Linux and open-source software both for its retail and cloud businesses, Amazon has a strict policy against patent infringement, and users who engage in this behavior can have their listings removed or accounts deleted. Nevertheless, like all large companies, Amazon has also been sued for patent violations. Joining the OIN simply makes good business sense. Nithya Ruff, the Amazon Open Source Program Office director, added: “Linux and open source are essential to many of our customers and a key driver of innovation across Amazon. We are proud to support a broad range of open-source projects, foundations, and partners, and we are committed to the long-term success and sustainability of open source as a whole. By joining OIN, we are continuing to strengthen open source communities and helping to ensure technologies like Linux remain thriving and accessible to everyone.”

Read more of this story at Slashdot.

According to The Record, New Hampshire will pilot a new kind of voting machine that will use open-source software to tally the votes. The Record reports: The software that runs voting machines is typically distributed in a kind of black box — like a car with its hood sealed shut. Because the election industry in the U.S. is dominated by three companies — Dominion, Election Systems & Software and Hart InterCivic — the software that runs their machines is private. The companies consider it their intellectual property and that has given rise to a roster of unfounded conspiracy theories about elections and their fairness. New Hampshire’s experiment with open-source software is meant to address exactly that. The software by its very design allows you to pop the hood, modify the code, make suggestions for how to make it better, and work with other people to make it run more smoothly. The thinking is, if voting machines run on software anyone can audit and run, it is less likely to give rise to allegations of vote rigging.

The effort to make voting machines more transparent is the work of a group called VotingWorks. […] On November 8, VotingWorks machines will be used in a real election in real time. New Hampshire is the second state to use the open-source machines after Mississippi first did so in 2019. Some 3,000 voters will run their paper ballots through the new machines, and then, to ensure nothing went awry, those same votes will be hand counted in a public session in Concord, N.H. Anyone who cares to will be able to see if the new machines recorded the votes correctly. The idea is to make clear there is nothing to hide. If someone is worried that a voting machine is programmed to flip a vote to their opponent, they can simply hire a computer expert to examine it and see, in real time.

Read more of this story at Slashdot.

The Godot Engine now has its own foundation to continue funding themselves. Previously, they teamed up with the Software Freedom Conservancy to handle fiscal sponsorship duties. Phoronix reports: The Godot engine developers and Software Freedom Conservancy mutually agreed to move the open-source game engine project to its own foundation. The Godot Foundation has been setup in the Netherlands as its own organization modeled after the policies of the SFC. The Godot Foundation is to help this game engine achieve its next level of growth and project a stronger image for the project. “We have just started the process of moving to the Foundation,” writes Godot Engine lead developer, Juan Linietsky, in a blog post. “For now all of Godot’s funding and contractors are still managed by the SFC. The SFC will gradually reduce its work for Godot and the new foundation will slowly ramp up. Stay tuned for announcements in the future as we finalize the Foundation’s organizational structure and officially begin operations.”

More details can be found via the Godot Engine blog.

Read more of this story at Slashdot.

The Clearing House, a banking association and payments company owned by the largest commercial banks in the U.S., has joined the Open Invention Network (OIN) — the world’s largest patent nonaggression consortium. ZDNet reports: The OIN has long protected Linux and Linux-related software from patent aggression by rival companies. With the increase in patent troll attacks, the OIN is also defending companies from these assaults. You may not think financial companies and banks are subject to such attacks. I mean, TCH’s roots go all the way back to 1853. Think again.

As Keith Bergelt, CEO of OIN, said in June, “The most sophisticated and compelling global banking and fintech companies have essentially become technology companies that employ open-source software to deliver their services at scale.” Further, patent trolls “appear to be targeting them for this reason, along with the fact that financial services companies have not historically been active patent filers.” That’s because, historically, they’ve purchased most of their tech from third-party vendors.

That was then. This is now. Today, financial institutions generate more tech in-house, so they’re more concerned about being granted patents, building patent portfolios, and related patent issues. Indeed, these days fintech businesses have their own Fintech Open Source Foundation (FINOS), the financial sector branch of the Linux Foundation. So, Bergelt said in a release Wednesday, “Advancements in financial services and fintech increasingly rely on open-source technologies. As the most experienced payment company in the US, and a keystone for the financial services industry, we are pleased that The Clearing House is committed to patent nonaggression in core Linux and adjacent open-source technologies.”

Read more of this story at Slashdot.

An anonymous reader quotes a report from Ars Technica: A stable version of Linux 6.0 is out, with 15,000 non-merge commits and a notable version number for the kernel. And while major Linux releases only happen when the prior number’s dot numbers start looking too big — there is literally no other reason” — there are a lot of notable things rolled into this release besides a marking in time. Most notable among them could be a patch that prevents a nearly two-decade slowdown for AMD chips, based on workaround code for power management in the early 2000s that hung around for far too long. […]

Intel’s new Arc GPUs are supported in their discrete laptop form in 6.0 (though still experimental). Linux blog Phoronix notes that Intel’s ARC GPUs all seem to run on open source upstream drivers, so support should show up for future Intel cards and chipsets as they arrive on the market. Linux 6.0 includes several hardware drivers of note: fourth-generation Intel Xeon server chips, the not-quite-out 13th-generation Raptor Lake and Meteor Lake chips, AMD’s RDNA 3 GPUs, Threadripper CPUs, EPYC systems, and audio drivers for a number of newer AMD systems. One small, quirky addition points to larger things happening inside Linux. Lenovo’s ThinkPad X13s, based on an ARM-powered Qualcomm Snapdragon chip, get some early support in 6.0. ARM support is something Linux founder Linus Torvalds is eager to see […].

Among other changes you can find in Linux 6.0, as compiled by LWN.net (in part one and part two): – ACPI and power management improvements for Sapphire Rapids CPUs – Support for SMB3 file transfer inside Samba, while SMB1 is further deprecated – More work on RISC-V, OpenRISC, and LoongArch technologies – Intel Habana Labs Gaudi2 support, allowing hardware acceleration for machine-learning libraries – A “guest vCPU stall detector” that can tell a host when a virtual client is frozen Ars’ Kevin Purdy notes that in 2022, “there are patches in Linux 6.0 to help Atari’s Falcon computers from the early 1990s (or their emulated descendants) better handle VGA modes, color, and other issues.”

Not included in this release are Rust improvements, but they “are likely coming in the next point release, 6.1,” writes Purdy.

Read more of this story at Slashdot.

Greg Lavender, CTO of Intel, spoke to VentureBeat about the company’s efforts to help developers build applications that can run on any operating system. From the report: “Today in the accelerated computing and GPU world, you can use CUDA and then you can only run on an Nvidia GPU, or you can go use AMD’s CUDA equivalent running on an AMD GPU,â Lavender told VentureBeat. “You can’t use CUDA to program an Intel GPU, so what do you use?” That’s where Intel is contributing heavily to the open-source SYCL specification (SYCL is pronounced like “sickle”) that aims to do for GPU and accelerated computing what Java did decades ago for application development. Intel’s investment in SYCL is not entirely selfless and isn’t just about supporting an open-source effort; it’s also about helping to steer more development toward its recently released consumer and data center GPUs. SYCL is an approach for data parallel programming in the C++ language and, according to Lavender, it looks a lot like CUDA.

To date, SYCL development has been managed by the Khronos Group, which is a multi-stakeholder organization that is helping to build out standards for parallel computing, virtual reality and 3D graphics. On June 1, Intel acquired Scottish development firm Codeplay Software, which is one of the leading contributors to the SYCL specification. “We should have an open programming language with extensions to C++ that are being standardized, that can run on Intel, AMD and Nvidia GPUs without changing your code,” Lavender said. Lavender is also a realist and he knows that there is a lot of code already written specifically for CUDA. That’s why Intel developers built an open-source tool called SYCLomatic, which aims to migrate CUDA code into SYCL. Lavender claimed that SYCLomatic today has coverage for approximately 95% of all the functionality that is present in CUDA. He noted that the 5% SYCLomatic doesn’t cover are capabilities that are specific to Nvidia hardware.

With SYCL, Lavender said that there are code libraries that developers can use that are device independent. The way that works is code is written by a developer once, and then SYCL can compile the code to work with whatever architecture is needed, be it for an Nvidia, AMD or Intel GPU. Looking forward, Lavender said that he’s hopeful that SYCL can become a Linux Foundation project, to further enable participation and growth of the open-source effort. […] “We should have write once, run everywhere for accelerated computing, and then let the market decide which GPU they want to use, and level the playing field,” Lavender said.

Read more of this story at Slashdot.