Our great sponsors
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
dependency-track
Dependency-Track is an intelligent Component Analysis platform that allows organizations to identify and reduce risk in the software supply chain.
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
As others have already commented:
The US government has added SBOMs to a proposed rule to update the Federal Acquisition Regulation. So if you want to sell to the US Government you'll have to provide SBOMs: https://www.federalregister.gov/documents/2023/10/03/2023-21...
Lots of large companies require SBOMs from their supplier.
In the EU we will get the Cyber Resilience Act which will make them mandatory as well in certain cases: https://data.consilium.europa.eu/doc/document/ST-12536-2023-...
And yes, there's bascially two technical standards to provide them: SPDX and CycloneDX: https://cyclonedx.org/
> I remember reading some rant by an open source developer
This one? https://github.com/gco/xee/blob/4fa3a6d609dd72b8493e52a68f31...
I have made a simple CLI utility[0] with this purpose in mind. It scans your entire filesystem for README.md and FUNDING.yml files for a set of donation/sponsor links and tag it with the associated repo (No HTTP calls, just the assumption that most repos link their support URL in either of these files). The output is a CSV sheet containing the open-source dependencies/libraries you use in your system that accepts donations.
I have plans to expand/plug this into a donation aggregator platform like you mentioned if time permits. But if there is an existing effort for the same, I am happy to contribute. :)
[0] - https://github.com/mufeedvh/paydept
https://dependencytrack.org/
You just need to use one of the various tools out there to scan.
I don't have a huge amount of experience with Krita's Wayland performance because the situation on Wayland is still sub-optimal for art in general. Tablet support has gotten much better, but configuration per-app or tied to the desktop environment still seems to be a big issue. The idea that my tablet configuration might stop working if I switch off of a desktop environment is kind of a non-starter to me. It stinks because I really want to use Wayland, but even as recently as a month ago I tried to see if I could make the switch and couldn't.
Truthfully, if someone has a lot of money to dump around, devoting a few full-time developers or dropping cash on https://github.com/OpenTabletDriver/OpenTabletDriver would probably go a long way towards encouraging Wayland adoption from artists.
As far as I can tell the issue is not that Wayland can't do tablet control on the same level as X11, it's that the tools built around those capabilities still seem immature. OpenTabletDriver looks very promising but seems to have limited device support, limited in no small part by what tablets the devs have access to (my Cintiq 32 is unlikely to get added any time soon because it is no longer being sold and was expensive and uncommon when it was on the market).
The NVIDIA situation is also a problem, but there's nothing anyone can do about that other than yell at NVIDIA more.
----
> The text tool is a joke.
The text tool should see considerable improvement soon; the entire text engine got rewritten in the last release, the devs just only had time to get it to feature parity with the existing tools.