Category: opensource

OpenSearch shouldn’t exist. The open source alternative to Elasticsearch started off as Amazon Web Services’ (AWS) answer to getting outflanked by Elastic’s change in Elasticsearch’s license, which was in turn sparked by AWS building a successful Elasticsearch service but contributing little back. In 2019 when AWS launched its then Open Distro for Elasticsearch, I thought its reasons rang hollow and, frankly, sounded sanctimonious. This was, after all, a company that used more open source than it contributed. Two years later, AWS opted to fork Elasticsearch to create OpenSearch, committing to a “long-term investment” in OpenSearch.

I worked at AWS at the time. Privately, I didn’t think it would work.

Rather, I didn’t feel that AWS really understood just how much work was involved in running a successful open source project, and the company would fail to invest the time and resources necessary to make OpenSearch a viable competitor to Elasticsearch. I was wrong. Although OpenSearch has a long way to go before it can credibly claim to have replaced Elasticsearch in the minds and workloads of developers, it has rocketed up the search engine popularity charts, with an increasingly diverse contributor population. In turn, the OpenSearch experience is adding a new tool to AWS’ arsenal of open source strengths….

As part of the AWS OpenSearch team, David Tippett and Eli Fisher laid out a few key indicators of OpenSearch’s success as they gave their 2022 year in review. They topped more than 100 million downloads and gathered 8,760 pull requests from 496 contributors, a number of whom don’t work for AWS. Not stated were other success factors, such as Adobe’s earlier decision to replace Elasticsearch with OpenSearch in its Adobe Commerce suite, or its increasingly open governance with third-party maintainers for the project. Nor did they tout its lightning-fast ascent up the DB-Engines database popularity rankings, hitting the Top 50 databases for the first time.

OpenSearch, in short, is a bonafide open source success story. More surprisingly, it’s an AWS open source success story. For many who have been committed to the “AWS strip mines open source” narrative, such success stories aren’t supposed to exist. Reality bites.
The article notes that OpenSearch’s success “doesn’t seem to be blunting Elastic’s income statement.” But it also points out that Amazon now has many employees actively contributing to open source projects, including PostgreSQL and MariaDB. (Although “If AWS were to turn forking projects into standard operating procedure, that might get uncomfortable.”)

“Fortunately, not only has AWS learned how to build more open source, it has also learned how to partner with open source companies.”

Young was a 40-year-old Canadian computer equipment salesperson with a software catalog when he noticed what Marc Ewing was doing. [Ewing was a recent college graduate bored with his two-month job at IBM, selling customized Linux as a side hustle.] It’s pretty primitive, but it’s going in the right direction, Young thought. He began reselling Ewing’s Red Hat product. Eventually, he called Ewing, and the two met at a tech conference in New York City. “I needed a product, and Marc needed some marketing help,” said Young, who was living in Connecticut at the time. “So we put our two little businesses together.”

Red Hat incorporated in March 1993, with the earliest employees operating the nascent business out of Ewing’s Durham apartment. Eventually, the landlord discovered what they were doing and kicked them out.
The four articles capture the highlights. (“A visual effects group used its Linux 4.1 to design parts of the 1997 film Titanic.”) And it doesn’t leave out Red Hat’s skirmishes with Microsoft. (“Microsoft was owned by the richest person in the world. Red Hat engineers were still linking servers together with extension cords. “) “We were changing the industry and a lot of companies were mad at us,” says Michael Ferris, Red Hat’s VP of corporate development/strategy. Soon there were corporate partnerships with Netscape, Intel, Hewlett-Packard, Compaq, Dell, and IBM — and when Red Hat finally goes public in 1999, its stock sees the eighth-largest first-day gain in Wall Street history, rising in value in days to over $7 billion and “making overnight millionaires of its earliest employees.”

But there’s also inspiring details like the quote painted on the wall of Red Hat’s headquarters in Durham: “Every revolution was first a thought in one man’s mind; and when the same thought occurs to another man, it is the key to that era…” It’s fun to see the story told by a local newspaper, with subheadings like “It started with a student from Finland” and “Red Hat takes on the Microsoft Goliath.”

Something I’d never thought of. 2001’s 9/11 terrorist attack on the World Trade Center “destroyed the principal data centers of many Wall Street investment banks, which were housed in the twin towers. With their computers wiped out, financial institutions had to choose whether to rebuild with standard proprietary software or the emergent open source. Many picked the latter.” And by the mid-2000s, “Red Hat was the world’s largest provider of Linux…’ according to part two of the series. “Soon, Red Hat was servicing more than 90% of Fortune 500 companies.”
By then, even the most vehement former critics were amenable to Red Hat’s kind of software. Microsoft had begun to integrate open source into its core operations. “Microsoft was on the wrong side of history when open source exploded at the beginning of the century, and I can say that about me personally,” Microsoft President Brad Smith later said.
In the 2010s, “open source has won” became a popular tagline among programmers. After years of fighting for legitimacy, former Red Hat executives said victory felt good. “There was never gloating,” Tiemann said.

“But there was always pride.”
In 2017 Red Hat’s CEO answered questions from Slashdot’s readers.

Organizations on PyPI are self-managed teams, with their own exclusive branded web addresses. Our goal is to make PyPI easier to use for large community projects, organizations, or companies who manage multiple sub-teams and multiple packages.

We’re making organizations available to community projects for free, forever, and to corporate projects for a small fee. Additional priority support agreements will be available to all paid subscribers, and all revenue will go right back into PyPI to continue building better support and infrastructure for all our users… Having more people using and contributing to Python every year is an fantastic problem to have, but it is one we must increase organizational capacity to accommodate. Increased revenue for PyPI allows it to become a staffed platform that can respond to support requests and attend to issues in a timeframe that is significantly faster than what our excellent (but thinly spread) largely volunteer team could reasonably handle.

We want to be very clear — these new features are completely optional. If features for larger projects don’t sound like something that would be useful to you as a PyPI maintainer, then there is no obligation to create an organization and absolutely nothing about your PyPI experience will change for you.

We look forward to discussing what other features PyPI users would like to see tackled next…

The Godot build you can download from EGS is the exact same open source release as on other platforms. Being present on more storefronts opens a new convenient avenue for more users to find the engine and begin their game development journey. You can of course still download Godot Engine from other platforms, or clone its source code from the Git repository and build it yourself. And if you do, you are more than welcome to contribute to Godot’s development too!

From the README: “MoonRay was developed at DreamWorks and is in continuous active development and includes an extensive library of production-tested, physically based materials, a USD Hydra render delegate, multi-machine and cloud rendering via the Arras distributed computation framework.”

More details can be found via OpenMoonRay.org.

This is an interesting home-brew project which seems like it might someday make a pleasant, expected feature in kits.

Hackaday is impressed by the possibilities too:
Surface mount components have been a game changer for the electronics hobbyist, but doing reflow soldering right requires some way to evenly heat the board. You might need to buy a commercial reflow oven — you can cobble one together from an old toaster oven, after all — but you still need something, because it’s not like a PCB is going to solder itself. Right?

Wrong. At least if you’re Carl Bugeja, who came up with a clever way to make his PCBs self-soldering…. The quality of the soldering seems very similar to what you’d see from a reflow oven…. After soldering, the now-useless heating element is converted into a ground plane for the circuit by breaking off the terminals and soldering on a couple of zero ohm resistors to short the coil to ground.

It’s an open source project, with all files available on GitHub. “This is really clever,” tweeted Adrian Bowyer, inventor of the open source 3D printer the RepRap Project.

In the video Bugeja compares reflow soldering to pizza-making. (If the circuit board is the underlying dough, then the electronics on top are the toppings, with the solder paste representing the sauce that keeps them in place. “The oven’s heat is what bonds these individual items together.”)

But by that logic making a self-soldering circuit is “like putting the oven in the dough and making it edible.”

So while “GitHub and our community have benefited tremendously from those who have filed issues, created extensions, fixed bugs, and built new features on Atom,” this now means that:

– Atom package management will stop working
– No more security updates
– Teletype will no longer work
– Deprecated redirects that supported downloading Electron symbols and headers will no longer work
– Pre-built Atom binaries can continue to downloaded from the atom repository releases

Fortunately, in 2014 GitHub open sourced the code for Atom. And according to It’s FOSS News:

A community build for it is already available; however, there seems to be a new version (Pulsar) that aims to bring feature parity with the original Atom and introduce modern features and updated architecture….

The reason why they made a separate fork is because of different goals for the projects. Pulsar wants to modernize everything to present a successor to Atom. Of course, the user interface is much of the same. Considering Pulsar hasn’t had a stable release yet, the branding could sometimes seem all over the place. However, the essentials seem to be there with the documentation, packages, and features like the ability to install packages from Git repositories….

As of now, it is too soon to say if Pulsar will become something better than what the Atom community version offers. However, it is something that we can keep an eye on…. You can head to its official download page to get the package required for your system and test it out.

Like Atom, Pulsar is cross-platform support (supporting Linux, macOS, and Windows).

The effort to make voting machines more transparent is the work of a group called VotingWorks. […] On November 8, VotingWorks machines will be used in a real election in real time. New Hampshire is the second state to use the open-source machines after Mississippi first did so in 2019. Some 3,000 voters will run their paper ballots through the new machines, and then, to ensure nothing went awry, those same votes will be hand counted in a public session in Concord, N.H. Anyone who cares to will be able to see if the new machines recorded the votes correctly. The idea is to make clear there is nothing to hide. If someone is worried that a voting machine is programmed to flip a vote to their opponent, they can simply hire a computer expert to examine it and see, in real time.