Post ApTG5RxuDkblGThPn6 by bzg@fosstodon.org
 (DIR) More posts by bzg@fosstodon.org
 (DIR) Post #ApTG5RxuDkblGThPn6 by bzg@fosstodon.org
       2024-12-16T17:24:32Z
       
       1 likes, 1 repeats
       
       "States should also subsidize the development and maintenance of free software solutions where they do not currently exist that should run on the public-led cloud."Well said!👀  https://www.ucl.ac.uk/bartlett/public-purpose/sites/bartlett_public_purpose/files/reclaiming-digital-sovereignty.pdfThe whole document is title "Reclaiming Digital Sovereignty - A roadmap to build a digital stack for people and the planet" and it seems worth reading.
       
 (DIR) Post #ApTG5YAt8OYeWTorrM by grendel84@tiny.tilde.website
       2024-12-17T18:58:51Z
       
       0 likes, 0 repeats
       
       @bzgIf nothing else it would be a huge improvement for them to simply open source their in-house apps they've built.That would cost very little and do a lot of good.(if they cry about security, point out that if viewing the source leads to a compromise they've already failed)
       
 (DIR) Post #ApTG5ZZjvU1yrqSEEa by bzg@fosstodon.org
       2024-12-17T21:54:49Z
       
       1 likes, 0 repeats
       
       @grendel84 I take it that "they" means the States?  It's part of my current job to help public sector organisations release their source code under a Free Software licence, and I can tell you: the cost is not "very little" 😶  But yeah, agreed on the security argument.We're slowly getting there:🇳🇱 https://developer.overheid.nl/repositories🇮🇹  https://developers.italia.it/en/search.html?type=software_open&sort_by=release_date&page=0🇩🇪  https://opencode.de/en🥖  https://code.gouv.fr/sources/
       
 (DIR) Post #ApTG6EatQ6Ja5IJEDw by grendel84@tiny.tilde.website
       2024-12-17T22:00:00Z
       
       0 likes, 0 repeats
       
       @bzgYeah sorry I should have specified the country.That's a cool job! I'm really curious about what drives the cost? Is it from stripping out sensative info?
       
 (DIR) Post #ApTG6FhfIPKHWaU9Q0 by bzg@fosstodon.org
       2024-12-18T08:50:46Z
       
       1 likes, 0 repeats
       
       @grendel84 - Git training for the teams- Security checks in the Git history- Time spent choosing a forge- Time spent choosing a license- Time spent defining the reasonable commitment of the team- ... and other time/money costs, depending on the public organisation.
       
 (DIR) Post #ApTG6Ggddi6CZh0qSO by clacke@libranet.de
       2024-12-22T11:10:42Z
       
       0 likes, 0 repeats
       
       @bzg @grendel84 "[one does not] simply open source [one's] in-house apps" 😁
       
 (DIR) Post #ApTG6JW77ISlLv6yy8 by clacke@libranet.de
       2024-12-22T11:18:41Z
       
       0 likes, 0 repeats
       
       As someone who writes or leads the writing of in-house apps, I can say that making an in-house app fit for reuse even by another department or division *within the same company* may involve a lot of refactoring and reengineering to remove assumptions and dependencies, especially the assumption that this is the one deployment in the world.@bzg @grendel84
       
 (DIR) Post #ApUwewWOzlJ5OzOwoi by bzg@fosstodon.org
       2024-12-26T07:32:31Z
       
       1 likes, 1 repeats
       
       @clacke @grendel84 This is why Open Source Programme Offices are important IMHO: they help teams within the same company understand what they can/should share in terms of FLOSS skills, usage tips and upstream contributions.And sometimes it even leads to the release of Free Software (libraries or standalone apps) that is generic and useful to others - but that's more like the icing on the cake.