Tag open-source

 Like

Liked How to create an open source program office
Post details
A central open source program office is a designated place where open source is supported, nurtured, shared, explained, and grown inside a company. With such an office in place, businesses can establish and execute on their open source strategies in clear terms, giving their leaders, developers, marketers, and other staff the tools they need to make open source a success within their operations. This guide aims to help you figure out why and how to establish a program to manage the open source use and creation inside your company, as well as to show how your developers can make their own contributions to open source projects outside your operations.

 Like

Liked Sentry: From the Beginning
Post details
I've been trying to invest more and more of my free time interacting with founders. I genuinely feel we've been through a lot with Sentry and I can provide some useful value to others. More so, I believe most people in this industry, most successful people, do others a disservice but not having honest conversations about the hardships and endurance it takes to succeed. As part of that I thought it'd be interesting, or at least therapeutic, to talk about some of the history in written form. I previously wrote about Sentry's Seed Funding, but I want to go deeper on some other topics this time around. I'm not entirely sure what future topics I'll cover, but hopefully you'll find some value in it.

 Repost

Reposted calcifer (@calcifer@hackers.town)
Post details
People seem to really have bought into the capitalist version of open source where software is still a product that requires support and marketing and a roadmap and exists to serve a user community separate and apart from the project. But a whole lot of open source is really just a sharing economy. It’s devs doing something they found useful and deciding to share it rather than hoard it. Those devs don’t owe anyone extra labor just because they chose to share.

 Like

Liked Chris Siebenmann (@cks@mastodon.social)
Post details
IMHO, an underappreciated aspect of 'filing bug reports is (hard) work for people' is that it's hard work that often has no particularly immediate payoff. Filing a bug report will mostly not get the problem fixed immediately the way you want; at best it may get you a fix in the next release, which will arrive who knows when. Sparked by: https://hachyderm.io/@funnelfiasco/110344473863227729

 Like

Liked Getting to know the Open Source Vulnerability (OSV) format - Open Source Security Foundation by Jennifer Bly 
Post details
To keep the modern technological world of open source software safe, it is critical to efficiently and accurately communicate information about open source vulnerabilities. The OSV Schema, created through the collaboration between OpenSSF members and housed within the Vulnerability Disclosures Working Group, provides a minimal, easy-to-use first class JSON format for describing vulnerabilities in open source software.

 Like

Liked geraldew (@geraldew@fosstodon.org)
Post details
FOSS licenses come in two approaches. The distinction is _who_ is granted the most freedom: - in "copyleft" licenses the emphasis is on the end-user, ensuring that they are _always_ passed the four freedoms; - in "permissive" licenses, the emphasis is on other developers/programmers, including allowing them to _not_ pass on the four freedoms. Is disappointing people still mistake this as being a difference between #FreeSoftware and #OpenSource because each has always supported both types.

 Bookmark

Bookmarked Entitlement in Open Source by Mike McQuaid 
Post details
There have been discussions in the aftermath of the log4j vulnerability about whether or not open source is broken or sustainable, what we can do to improve the sustainability of the open source ecosystem moving forwards, and the entitlement of users and companies in expecting maintainers to fix their problems.