#softwarecommons — Public Fediverse posts

We need more experiments in what a #SoftwareCommons might look like. It's clear that non-copyleft #OpenSource isn't it, because it ignores the principles that Ostrom found in long-lived natural resource #commons (https://patternsofcommoning.org/uncategorized/eight-design-principles-for-successful-commons/). We shouldn't expect all of them to carry over, but we at least need enforceable rules to ensure that people profiting from a piece of software have to contribute to supporting it.

We should not expect these experiments to succeed quickly. It will take time to shift the Overton window.

We need more experiments in what a #SoftwareCommons might look like. It's clear that non-copyleft #OpenSource isn't it, because it ignores the principles that Ostrom found in long-lived natural resource #commons (https://patternsofcommoning.org/uncategorized/eight-design-principles-for-successful-commons/). We shouldn't expect all of them to carry over, but we at least need enforceable rules to ensure that people profiting from a piece of software have to contribute to supporting it.

We should not expect these experiments to succeed quickly. It will take time to shift the Overton window.

We need more experiments in what a #SoftwareCommons might look like. It's clear that non-copyleft #OpenSource isn't it, because it ignores the principles that Ostrom found in long-lived natural resource #commons (https://patternsofcommoning.org/uncategorized/eight-design-principles-for-successful-commons/). We shouldn't expect all of them to carry over, but we at least need enforceable rules to ensure that people profiting from a piece of software have to contribute to supporting it.

We should not expect these experiments to succeed quickly. It will take time to shift the Overton window.

We need more experiments in what a #SoftwareCommons might look like. It's clear that non-copyleft #OpenSource isn't it, because it ignores the principles that Ostrom found in long-lived natural resource #commons (https://patternsofcommoning.org/uncategorized/eight-design-principles-for-successful-commons/). We shouldn't expect all of them to carry over, but we at least need enforceable rules to ensure that people profiting from a piece of software have to contribute to supporting it.

We should not expect these experiments to succeed quickly. It will take time to shift the Overton window.

We need more experiments in what a #SoftwareCommons might look like. It's clear that non-copyleft #OpenSource isn't it, because it ignores the principles that Ostrom found in long-lived natural resource #commons (https://patternsofcommoning.org/uncategorized/eight-design-principles-for-successful-commons/). We shouldn't expect all of them to carry over, but we at least need enforceable rules to ensure that people profiting from a piece of software have to contribute to supporting it.

We should not expect these experiments to succeed quickly. It will take time to shift the Overton window.

Here we go. S1E1!

Chad Whitacre is head of open source at Sentry, an application and performance monitoring software maker that moved to a business source license for its products in 2019, and then to a functional source license in November 2023. In this episode, he discusses the #tragedyofthecommons vs #enclosure, open source vs open products, #BSL vs #FSL and the story of "The #Codecov kerfuffle." #OSS #softwarecommons #opensource #opensourcesustainability #podcast

https://itopsquery.podbean.com/e/chad-whitacre-sentry/

Here we go. S1E1!

Chad Whitacre is head of open source at Sentry, an application and performance monitoring software maker that moved to a business source license for its products in 2019, and then to a functional source license in November 2023. In this episode, he discusses the #tragedyofthecommons vs #enclosure, open source vs open products, #BSL vs #FSL and the story of "The #Codecov kerfuffle." #OSS #softwarecommons #opensource #opensourcesustainability #podcast

https://itopsquery.podbean.com/e/chad-whitacre-sentry/

Here we go. S1E1!

Chad Whitacre is head of open source at Sentry, an application and performance monitoring software maker that moved to a business source license for its products in 2019, and then to a functional source license in November 2023. In this episode, he discusses the #tragedyofthecommons vs #enclosure, open source vs open products, #BSL vs #FSL and the story of "The #Codecov kerfuffle." #OSS #softwarecommons #opensource #opensourcesustainability #podcast

https://itopsquery.podbean.com/e/chad-whitacre-sentry/

Here we go. S1E1!

Chad Whitacre is head of open source at Sentry, an application and performance monitoring software maker that moved to a business source license for its products in 2019, and then to a functional source license in November 2023. In this episode, he discusses the #tragedyofthecommons vs #enclosure, open source vs open products, #BSL vs #FSL and the story of "The #Codecov kerfuffle." #OSS #softwarecommons #opensource #opensourcesustainability #podcast

https://itopsquery.podbean.com/e/chad-whitacre-sentry/

Here we go. S1E1!

Chad Whitacre is head of open source at Sentry, an application and performance monitoring software maker that moved to a business source license for its products in 2019, and then to a functional source license in November 2023. In this episode, he discusses the #tragedyofthecommons vs #enclosure, open source vs open products, #BSL vs #FSL and the story of "The #Codecov kerfuffle." #OSS #softwarecommons #opensource #opensourcesustainability #podcast

https://itopsquery.podbean.com/e/chad-whitacre-sentry/

“Software Commons is a great name. But for what?”

Y’all, that already means something to a lot of very passionate people and communities… please don’t try to commendeer it for profit.

https://github.com/softwarecommons/softwarecommons.com/issues/3

#FreeSoftware #FreeKnowledge #OpenSource #FOSS #OSS #DigitalCommons #InformationCommons #SoftwareCommons

“Software Commons is a great name. But for what?”

Y’all, that already means something to a lot of very passionate people and communities… please don’t try to commendeer it for profit.

https://github.com/softwarecommons/softwarecommons.com/issues/3

#FreeSoftware #FreeKnowledge #OpenSource #FOSS #OSS #DigitalCommons #InformationCommons #SoftwareCommons

“Software Commons is a great name. But for what?”

Y’all, that already means something to a lot of very passionate people and communities… please don’t try to commendeer it for profit.

https://github.com/softwarecommons/softwarecommons.com/issues/3

#FreeSoftware #FreeKnowledge #OpenSource #FOSS #OSS #DigitalCommons #InformationCommons #SoftwareCommons

“Software Commons is a great name. But for what?”

Y’all, that already means something to a lot of very passionate people and communities… please don’t try to commendeer it for profit.

https://github.com/softwarecommons/softwarecommons.com/issues/3

#FreeSoftware #FreeKnowledge #OpenSource #FOSS #OSS #DigitalCommons #InformationCommons #SoftwareCommons

“Software Commons is a great name. But for what?”

Y’all, that already means something to a lot of very passionate people and communities… please don’t try to commendeer it for profit.

https://github.com/softwarecommons/softwarecommons.com/issues/3

#FreeSoftware #FreeKnowledge #OpenSource #FOSS #OSS #DigitalCommons #InformationCommons #SoftwareCommons

I’ve been bitten by the “last call” before…

I don’t have infinite free time to engage on these issues, especially when feedback isn’t reflected in a change.
#OpenSource #FreeSoftware #FOSS #OSS #SoftwareCommons #CreativeCommons

https://github.com/getsentry/fsl.software/issues/2#issuecomment-1976628352

I’ve been bitten by the “last call” before…

I don’t have infinite free time to engage on these issues, especially when feedback isn’t reflected in a change.
#OpenSource #FreeSoftware #FOSS #OSS #SoftwareCommons #CreativeCommons

https://github.com/getsentry/fsl.software/issues/2#issuecomment-1976628352

I’ve been bitten by the “last call” before…

I don’t have infinite free time to engage on these issues, especially when feedback isn’t reflected in a change.
#OpenSource #FreeSoftware #FOSS #OSS #SoftwareCommons #CreativeCommons

https://github.com/getsentry/fsl.software/issues/2#issuecomment-1976628352

I’ve been bitten by the “last call” before…

I don’t have infinite free time to engage on these issues, especially when feedback isn’t reflected in a change.
#OpenSource #FreeSoftware #FOSS #OSS #SoftwareCommons #CreativeCommons

https://github.com/getsentry/fsl.software/issues/2#issuecomment-1976628352

I’ve been bitten by the “last call” before…

I don’t have infinite free time to engage on these issues, especially when feedback isn’t reflected in a change.
#OpenSource #FreeSoftware #FOSS #OSS #SoftwareCommons #CreativeCommons

https://github.com/getsentry/fsl.software/issues/2#issuecomment-1976628352

#softwarecommons? "the two failure modes of a commons are the tragedy of the commons and enclosure. In the former, a majority of people overuses the common resource to the point of destruction, due to too few restrictions. In the latter, a minority of people gains control and excludes the majority, imposing too many restrictions. That is, same tension in commons management & software ecosystem: between user freedom and developer sustainability."
https://openpath.chadwhitacre.com/2024/towards-software-commons/

#softwarecommons? "the two failure modes of a commons are the tragedy of the commons and enclosure. In the former, a majority of people overuses the common resource to the point of destruction, due to too few restrictions. In the latter, a minority of people gains control and excludes the majority, imposing too many restrictions. That is, same tension in commons management & software ecosystem: between user freedom and developer sustainability."
https://openpath.chadwhitacre.com/2024/towards-software-commons/

#softwarecommons? "the two failure modes of a commons are the tragedy of the commons and enclosure. In the former, a majority of people overuses the common resource to the point of destruction, due to too few restrictions. In the latter, a minority of people gains control and excludes the majority, imposing too many restrictions. That is, same tension in commons management & software ecosystem: between user freedom and developer sustainability."
https://openpath.chadwhitacre.com/2024/towards-software-commons/

#softwarecommons? "the two failure modes of a commons are the tragedy of the commons and enclosure. In the former, a majority of people overuses the common resource to the point of destruction, due to too few restrictions. In the latter, a minority of people gains control and excludes the majority, imposing too many restrictions. That is, same tension in commons management & software ecosystem: between user freedom and developer sustainability."
https://openpath.chadwhitacre.com/2024/towards-software-commons/

#softwarecommons? "the two failure modes of a commons are the tragedy of the commons and enclosure. In the former, a majority of people overuses the common resource to the point of destruction, due to too few restrictions. In the latter, a minority of people gains control and excludes the majority, imposing too many restrictions. That is, same tension in commons management & software ecosystem: between user freedom and developer sustainability."
https://openpath.chadwhitacre.com/2024/towards-software-commons/

Beyond #opensource to sustainable software: Towards #SoftwareCommons ❧ Open Path by Chad Whitacre

https://openpath.chadwhitacre.com/2024/towards-software-commons/

Beyond #opensource to sustainable software: Towards #SoftwareCommons ❧ Open Path by Chad Whitacre

https://openpath.chadwhitacre.com/2024/towards-software-commons/

Beyond #opensource to sustainable software: Towards #SoftwareCommons ❧ Open Path by Chad Whitacre

https://openpath.chadwhitacre.com/2024/towards-software-commons/

Beyond #opensource to sustainable software: Towards #SoftwareCommons ❧ Open Path by Chad Whitacre

https://openpath.chadwhitacre.com/2024/towards-software-commons/

Looks like #SoftwareCommons is a candidate for a term of art to describe a “big tent” approach to open source https://openpath.chadwhitacre.com/2024/towards-software-commons/

cc @anthrocypher another one for us to discuss. I nodded my head strongly when reading.

Looks like #SoftwareCommons is a candidate for a term of art to describe a “big tent” approach to open source https://openpath.chadwhitacre.com/2024/towards-software-commons/

cc @anthrocypher another one for us to discuss. I nodded my head strongly when reading.

Looks like #SoftwareCommons is a candidate for a term of art to describe a “big tent” approach to open source https://openpath.chadwhitacre.com/2024/towards-software-commons/

cc @anthrocypher another one for us to discuss. I nodded my head strongly when reading.

Looks like #SoftwareCommons is a candidate for a term of art to describe a “big tent” approach to open source https://openpath.chadwhitacre.com/2024/towards-software-commons/

cc @anthrocypher another one for us to discuss. I nodded my head strongly when reading.

Looks like #SoftwareCommons is a candidate for a term of art to describe a “big tent” approach to open source https://openpath.chadwhitacre.com/2024/towards-software-commons/

cc @anthrocypher another one for us to discuss. I nodded my head strongly when reading.

Happy that our paper «Forking Without Clicking: on How to Identify Software Repository Forks» has been accepted at @msrconf #msr2020. Great example of how @swheritage allows tracking global relationships in the #SoftwareCommons. Preprint upcoming. Joint work w/ @seirl @g_rousseau

Happy that our paper «Forking Without Clicking: on How to Identify Software Repository Forks» has been accepted at @msrconf #msr2020. Great example of how @swheritage allows tracking global relationships in the #SoftwareCommons. Preprint upcoming. Joint work w/ @seirl @g_rousseau

Here are some good notes from a discussion on governing a shared resource, ie: treating #FOSS as the commons.

https://devsummit.aspirationtech.org/index.php?title=Governing_Shared_Resources

#FreeSoftware #OpenSource #SoftwareCommons #Commons

@mike_hales @Matt_Noyes @ntnsndr @natstein yeah I've been using the term #softwarecommons more and more over #freesoftware or #opensource as there is an open, collaboratively managed orientation there not necessarily present in FLOSS.

In Drupal, for example, there are many projects that while technically open source, are really the product of a single company who has no interest in real collaboration.

It's even worse in Wordpress.