I think telemetry could help in a lot of discussions around UI/UX.
Questions:
1. In which project should we create an issue about telemetry?
2. Where can I see current telemetry data?
3. How many users enabled telemetry, at what level?
Concerns:
4. Storing more data might raise concerns among use
Another thing I'd like to explore is to have some universal way to
programmatically change KDE settings.
Currently, I either change settings in KCMs, or manually edit a config
file then make a dbus "reconfigure" call. But the latter is mostly
undocumented. Perhaps we can gather all KConfig files i
Any example of "process an SVG document in a different way than to render it"?
Laura David Hurka 于2024年3月15日周五 05:57写道：
>
> On Thursday, March 14, 2024 2:04:45 PM CET Sune Vuorela wrote:
> > On 2024-03-14, Igor Mironchik wrote:
> > > Hello,
> > >
> > > What do you think about https://github.com/
The tree-id of a git commit is effectively a checksum of all files. So you
can ask packagers to pull a specific commit and verify either commit-id or
tree-id. No extra verification step needed.
Sune Vuorela 于 2024年4月4日周四 17:48写道：
> On 2024-04-03, Albert Vaca Cintora wrote:
> > What's the advant
Neal Gompa 于 2024年4月4日周四 22:09写道：
> and because Git has no immutability
guarantees, it's not exactly ideal as an input either.
Commits and trees in git are immutable. Refs like tags and branches are not.
Neal Gompa 于 2024年4月4日周四 22:19写道：
>
> That's fair, but they are not permanent and can be reaped when they're
> not referenced by anything anymore.
>
If you pull these release commits in a "download" server and restrict write
access to it, not giving everyone permission to delete a tag, just lik
One more option: Keep the old load code as a fallback to the new load
code. You can drop the old save code, but the old load code probably
has to be kept forever.
-Jin
Stefano Crocco 于2024年9月21日周六 14:39写道：
>
> Hello to everyone,
> I'd need an advice on how to proceed with a change I'm going to m
