The #LibreTexts team is happy to continue to support Mizzou Academy's efforts as part of our #LibreNet consortium! Thank you for helping ensure the future of #education is #open.
The #LibreTexts team is happy to continue to support Mizzou Academy's efforts as part of our #LibreNet consortium! Thank you for helping ensure the future of #education is #open.
@LibreTexts when you say "#open" what do you mean? Because you keep using that word...
I'd appreciate seeing your definition.
@lightweight thanks for asking. We use #open to primarily mean the 5R's codified via #CreativeCommons and #GNU licensing. We do have some content that doesn't follow this (e.g. content w/ an ND clause); in these cases #open
means #OpenAccess. Everything created on the #LibreTexts site is #OER open.
For code, we refer primarily to GNU and MIT licensed open-source content.
We hope this helps answer your question. Let us know if we can clarify anything else related to our greater #LibreVerse.
@LibreTexts the words #open and #libre are used in the software context to refer to code that is available under an OSI approved open source license, & libre more specifically refers to a #Copyleft (shared-alike) license. Is any of your software open source or Copyleft licensed? What about your flagship software?
I looked on your website and couldn't find any evidence of any open source code to download. Everything I found appeared to be proprietary, i.e. not at all '#open'.
It might be time for a broad (and thoughtful) conversation on the limits of openness, in the #OpenEcosystem? How do #OpenGovernment and #OpenData work within the #FreeSoftware framework? Do #OERs run the risk of promoting #fauxpen and #OpenWashing?
@enkerli As you can imagine, I'd certainly be keen to have that broader discussion.
@enkerli the almost compete erosion of value in the term "open source" (to mean 'weak open source licenses but, unlike its original meaning, *not* including #Copyleft or '#libre' licenses) thanks to bad corporate actors has forced the #FreeSoftware community to reinforce its long-time use of the term #libre to refer to share-alike #open licensing. #LibreWashing is an emerging insidious problem.
@lightweight It might be useful to focus on the phenomena themselves. Yes, including #LibreWashing, #Fauxpen, as well as the whole distinction between software freedom and open source development. There are diverse actors taking different postures which may or may not jibe with our values. Dispassionately, we can still describe the “Ecosystem of Open” with diverse initiatives taking root despite counteracting forces.
In other words, #HowMightWe design this ecosystem for the common good?
@lightweight Ditto.
What feels different, these days, is the power of #EcosystemThinking. While #OpenEducation and #OpenGovernment and #OpenData were largely inspired by #FreeSoftware, there’s a sense in which the puzzle pieces are finally realigning.
@lightweight @openedtech Good to know about OnlyOffice (our small association for Free Software in Higher Ed will be interested).
And I’ll soon be free to explore more options.
As for federation, my personal reactions tend to be very positive. Yet it’s clear that a lot of it depends on usage patterns and community relations (not to mention “governance models”). My guess is that @evan would agree.
@enkerli
Happy to provide access to one of our instances for you to try and compare. And I agree that (decentralised) federation, though technically more complex, is ab inherently better approach than (centralised) stand-alone, especially from a resilience and sovereignty perspective.
This is another update of my previous posts (installing NextCloud with Collabora Office Online on Ubuntu 16.04 and then NextCloud with OnlyOffice on Ubuntu 18.04). I'm updating it thanks to my colleague in edtech, Stephen Downes' heroic videos showing how he went through this process using my 18.04 instructions on 22.04, running into a few minor issues... this update seeks to remedy the problems he encountered with the older tutorial.