Looking over the guidelines I'd guess the trick is probably in setting the requirements such that only Windows/MS Office/AutoCAD/etc can meet them?
Very interesting document though, they have decision making flow charts and everything:
Looking over the guidelines I'd guess the trick is probably in setting the requirements such that only Windows/MS Office/AutoCAD/etc can meet them?
Very interesting document though, they have decision making flow charts and everything:
In the section about requirements it says you need to take "cost of data migration, installation, personalization, training staff" etc. into account.
I guess with that you can basically always make a case to just keep the current thing?
@gubi @maymage @fsfe So in theory someone could sue over the fact that e.g. Windows was chosen in a specific procurement decision, it's just that nobody has tried?
I recently learned that the Italian government is only allowed to buy proprietary software after it has determined that there isn't a free software option. IIUC they're also required to publish any code they write (or commission to be written) under a free license.
However, at least as far as I know Windows, Office, et al are being used everywhere in public administration, and even e.g. public transport apps are proprietary. What gives?
Hold on, there's another even better one https://www.theverge.com/news/623765/xiaomi-realme-camera-concepts-modular-lens-mwc-2025
Called it 5 years ago: The future of phones is all-screen front, all-camera back, ugly all around 🌈
My 2019 posts:
Cool to see this new effort by @niccolove! There's way too much misinformation out there as a result of the general disconnect between developers and free software "media". Kudos for seizing the means of communication o/
Drum Machine has been accepted into Circle! It's a delightful little app to play with drum patterns and prototype track ideas. Give it a try, I had a lot of fun playing with it during review 🥁 ✨
The Disks GTK4/Libadwaita port landed in GNOME OS Nightly, looking fantastic 🙌
We're starting off the new year with an exciting new edition of Unboiling The Ocean! Join us for a discussion about peer-to-peer UX and threat models.
We have some special guests and questions to discuss, but mostly the plan is to have an open discussion around these topics to inform the design and development of the Aardvark text editor project.
Join us on Monday January 27 at 19:00 at @offline in Neukölln!
PSA: I'm stepping down from putting together an STF application for 2025.
Reflecting on our experiences with the STF project last year, I no longer think the GNOME Foundation is a good venue to organize development collectively. Even if the Foundation's current issues are fixed, we've seen how risky it is to centralize development in a single structure.
My hope is that we'll learn from this and find more sustainable, decentralized ways of organizing going forward.
https://blogs.gnome.org/tbernard/2025/01/07/re-decentralizing
I blogged about our recent Aardvark hackfest with the @p2panda crew!
It (somewhat) works!!!
Doing some software archaeology with @jimmac today, looking at webOS on the Touchpad and Palm Pre.
It's very cool to see how far ahead of its time this was, and also how many elements from it survived in GNOME in some form! And of course, the multitasking is still unmatched by any more recent mobile platform :)
🎅🐼 Save the date 🐼🎅
We're having a release event for the new @p2panda stack, and a hackfest to start working on a new native GTK local-first collaborative text editor!
Join us December 7-8 in Berlin (location and details TBA)
Update: Here's a quick draft for a pre-review checklist https://gitlab.gnome.org/Teams/Circle/-/merge_requests/116
I've been trying to do more Circle reviews lately, and I've noticed that a lot of apps have very similar papercuts. Some of the classics are:
- Not using the standard keyboard shortcuts (e.g. Ctrl+, for opening preferences) https://developer.gnome.org/hig/reference/keyboard.html
- Missing a11y labels on buttons
- Longer blocks of text not being screen reader accessible
- Focus borders being weirdly shaped/glitchy
Maybe having a little checklist for app devs to do themselves before applying could catch some of these?
@bragefuglseth Do it, that's a great idea! Happy to look over drafts :)
That said, I was thinking maybe we could also just include a few of these things in the actual issue template for applying?
@forteller We've had mockups for this for like 5 years, just needs someone to implement the plumbing for scoped, global app actions 😅
Manuel is working hard on a new version of Apostrophe! It's the long-awaited port to GTK4, Libadwaita, and the other awesome new stuff ✨
The new version is a significant overhaul, so testing and filing bugs is appreciated!
Install the beta by adding the Flathub Beta repo:
flatpak remote-add --if-not-exists flathub-beta https://flathub.org/beta-repo/flathub-beta.flatpakrepo
And then install the app:
flatpak install flathub-beta org.gnome.gitlab.somas.Apostrophe
We'll burn that bridge when we get to it.he/they • Berlin • https://blogs.gnome.org/tbernard
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.