101010.pl is one of the many independent Mastodon servers you can use to participate in the fediverse.
101010.pl czyli najstarszy polski serwer Mastodon. Posiadamy wpisy do 2048 znaków.

Server stats:

474
active users

#OSPO

0 posts0 participants0 posts today

Thank you to Mary Grush of Campus Technology magazine for her interest in @apereo and the resurgence of #OpenSource in #HigherEd.

While institutions of #HigherEducation are now more dependent on #OSS than ever, their engagement with and support of both the projects and communities may be at an all-time low.

Several factors should prompt greater participation from campus leadership and IT departments: #SBOM, #CRA, the rise of academic #OSPO, grant/funding requirements (#OpenScience), etc.

Continued thread

🧵2/4 We ask the @ec.europa.eu to
- use open standards to facilitate cloud interoperability and switching
- look into anti-competitive bundling practices
- build institutional capacity by establishing #OpenSource Programme Offices #OSPO

Plongez dans l’univers de Lutèce, la solution open source développée par la Ville de Paris pour alimenter les services numériques dédiés aux citoyens !

Dans cet épisode, Magali Lemaire et Philippe Bareille nous racontent l’histoire de Lutèce, la création de Cité Libre, le produit basé sur Lutèce, ainsi que la gouvernance du projet, et le déploiement de leur OSPO.

👉 projets-libres.org/s3e11-de-lu

Bonne écoute 🎧

Here's another great pattern from a #CURIOSS member.

❓Is your university is trying to meet demand from students for #opensource activities with limited resources?

💡 Have a read of the ‘Co-hosting Student Events’ pattern: bit.ly/3XwwXHQ

A huge thanks to Emily Lovell, @slieggi and Yelena Martynovskaya from the CROSS / #OSPO @ucsc for sharing.

GitHubcurioss-patterns/cohosting-student-events.md at main · CURIOSSorg/curioss-patternsA public repository for the CURIOSS Patterns Practice - CURIOSSorg/curioss-patterns
Replied in thread

@apereo,

The key point here isn't that there is a policy promoting #Opensource—which is fantastic and has goals and values with which I wholly agree—but rather that the institution has taken the time to develop a policy.

One of the primary responsibilities for academic Open Source Program Offices (#OSPO) is to develop such policies.

I would be very interested in understanding how the need for this policy was identified and how it was developed within the institution.

Verslag #FOSDEM:

ibestuur.nl/artikel/nederland-

"Op deze informele manier is eerder bijvoorbeeld een samenwerking tussen de Franse, Duitse en Nederlandse overheden opgestart om gezamenlijk open source werkpleksoftware te ontwikkelen."

"Dit jaar is ook de Europese Commissie, voor de tweede keer, aanwezig om via sessies te informeren over en input op te halen voor Europese wet- en regelgeving."

Veel is al terug te zien via:

fosdem.org/2025/schedule/

iBestuurNederland moet flink been bijzetten als het gaat om open source - iBestuurNederlandse gemeenschap volgt de ontwikkelingen op internationaal open source conferentie FOSDEM.