#opensource

65 bookmarks tagged with #opensource · RSS Feed · ← All Tags

a new model for open source: closed to pull requests, open to remix.

https://ghuntley.com/remix/
For what's the point of reading a pull request that's been generated by code? All I want is to read and understand the core idea. If it's a good idea, I might incorporate it back upstream, but there should be no expectation that I will. You see, open source software is open source by definition because the license says that it's as is, and that as is permits you to remix software.

My answers to the questions I posed about porting open source code with LLMs

https://simonwillison.net/2026/Jan/11/answers/#atom-everything
What’s important here is making it very clear to potential users what they should expect from that software. I’ve started publishing my AI-generated and not 100% reviewed libraries as alphas, which I’m tentatively thinking of as “alpha slop”. I’ll take the alpha label off once I’ve used them in production to the point that I’m willing to stake my reputation on them being decent implementations, and I’ll ship a 1.0 version when I’m confident that they are a solid bet for other people to depend on. I think that’s the responsible way to handle this.

Open Source is one person | Open Source Security

https://opensourcesecurity.io/2025/08-oss-one-person/
Open source, the thing that drives the world, the thing Harvard says has an economic value of 8.8 trillion dollars (also a big number). Most of it is one person. And I can promise you not one of those single person projects have the proper amount of resources they need. If you want to talk about possible risks to your supply chain, a single maintainer that’s grossly underpaid and overworked. That’s the risk. The country they are from is irrelevant.

Open code != working open

https://anna.flourishing.stream/2018/09/04/open-code-is-not-working-open/
Free software can’t solve the power imbalance between users and software makers alone by giving to the former the possibility to run, study, and distribute both original and modified copies. Such approach fails to acknowledge that the problems we face with proprietary software go beyond technological aspects, and that is possible to easily reproduce toxic patterns within open projects. Collaborative efforts take a lot more than just making the code available to anyone, being primarily based on human interactions and emotional labor.

Open-Source LLMs - Schneier on Security

https://www.schneier.com/blog/archives/2023/06/open-source-llms.html
We have entered an era of LLM democratization. By showing that smaller models can be highly effective, enabling easy experimentation, diversifying control, and providing incentives that are not profit motivated, open-source initiatives are moving us into a more dynamic and inclusive AI landscape. This doesn’t mean that some of these models won’t be biased, or wrong, or used to generate disinformation or abuse. But it does mean that controlling this technology is going to take an entirely different approach than regulating the large players.

BrewPony Coffee Powers The Interwebs | BrewPony

http://brewpony.com/brewpony-coffee-powers-the-interweb/
If you’re in the United States and have ever contributed to a Free/Open Source project in any way, please email our hospitality Ponies telling them to which project(s) you’ve contributed and how and we’ll email you back with a coupon code worth 10% off any BrewPony product. For as long as you (or we) live.

Open Source (Almost) Everything

http://tom.preston-werner.com/2011/11/22/open-source-everything.html
Should we open source Grit or keep it proprietary? Keeping it private would provide a higher hurdle for competing Ruby-based Git hosting sites, giving us an advantage. Open sourcing it would mean thousands of people worldwide could use it to build interesting Git tools, creating an even more vibrant Git ecosystem. After a small amount of debate we decided to open source Grit. I don't recall the specifics of the conversation but that decision nearly four years ago has led to what I think is one of our most important core values: open source (almost) everything.

Public Open Source Services / FrontPage

http://poss.gliderlab.com
"You use the same Google Merchant account that App Engine debits as the one that accepts donations. This way no bank account is involved. Then you track the money that goes into the account (using the Google Merchant IPN equivalent). Then you look at your usage stats from the App Engine panel and predicate future usage trends. Then calculate the cost per month. Then divide the cash in the account by that and you have how long the service will run. You make this visible on all pages (at the bottom, say) that this service will run for X months, "Pay now to keep it running." You accept any amount, but you are completely clear about what the costs are. And this is all automated."

Dreamwidth Studios

http://www.dreamwidth.org
"Dreamwidth Studios is an Open Source social networking, content management, and personal publishing platform. Our mission in life is to make it easy for you to share the things you make, and easy to find the people who are making the things you want to enjoy. ... Dreamwidth Studios is based upon the LiveJournal codebase offered by LiveJournal, Inc. We've taken the LiveJournal server code and updated, modernized, and streamlined it -- and we make all of our changes available under an Open Source license."

Eucalyptus

http://eucalyptus.cs.ucsb.edu
"Elastic Utility Computing Architecture for Linking Your Programs To Useful Systems - is an open-source software infrastructure for implementing "cloud computing" on clusters. The current interface to EUCALYPTUS is compatible with Amazon's EC2 interface, but the infrastructure is designed to support multiple client-side interfaces. EUCALYPTUS is implemented using commonly available Linux tools and basic Web-service technologies making it easy to install and maintain"

Quetzalcoatal: A public service announcement

http://quetzalcoatal.blogspot.com/2008/11/public-service-announcement.html
"If your code will be seen by the world at large, one of your first tasks should be to write documentation. Document all functions as soon as you write them (before is also helpful). Provide samples on how to use code as soon as you finish a module (or earlier, if possible). Do not wait until your 5.0 release. Do not wait until your 1.0 release. Do not even wait until your 0.5 release. Do it as you write your code. The sooner, the better."

-=SUbWAY=- » Blog Archive » TWiki is dead, long live TWiki!

http://wordpress.metro.cx/2008/10/28/twiki-is-dead-long-live-twiki
"Although the events are sad in one way, it is refreshing to finally see twiki.net take a definitive stand against the community, making explicit what has been implicit in their behaviour. The project can now be taken out of limbo. Most (if not all) of the active contributors have jumped ship and gotten on the fork bandwagon. There’s a great number of features lined up that people didn’t commit during the governance crisis, for fear of being taken advantage over by TWiki.net. They have proven again and again that marketing the hard work of community volunteers as their own is not below them."

Cross-Browser.com

http://cross-browser.com
Wow, "X" - what an unsearchably-named framework. "X is a collection of loosely-bound, cross-browser, Javascript functions and objects. It is intended to be a resource from which you pick and choose - you do not have to include the entire library in your application. It contains core DOM/Style functions, unobtrusive enhancements, utility functions, objects such as menus and tab panels, and also has some experimental stuff. I've been developing this library since 2001 (I started its predecessor around 1999). Thanks to thousands of people like yourself X has been extensively tested on a wide range of operating systems and browsers. Thanks to your contributions X continues to improve, grow and evolve."

Ma.gnolia Blog: The Open Road Ahead

http://ma.gnolia.com/blog/2008/08/22/the-open-road-ahead
At one point, I thought something like this would've been a good idea for Delicious. But, I never took time to think it through or make a case for it. Could be a horrible idea for all I know. It'll be interesting to see where and how far this goes: "As we develop M2, it means we’ll be posting the code for most pieces in the open and having regular discussions on both technical and non-technical subjects to get input from the community and to share our progress. ... Once M2 is launched, the open source aspects can be downloaded and run as a self-administered installation that can be independent or federated with other installations, including Ma.gnolia.com."

Flex:Open Source - Adobe Labs

http://labs.adobe.com/wiki/index.php/Flex:Open_Source
"Adobe is announcing plans to open source Flex under the Mozilla Public License (MPL). This includes not only the source to the ActionScript components from the Flex SDK, which have been available in source code form with the SDK since Flex 2 was released

On a Wing and a Wiki

http://www.eweek.com/article2/0,1759,1584630,00.asp
"When burglars brought down the Internet link to Ziff Davis' Manhattan offices, open-source software—and Sean Gallagher's personal Web server—kept eWEEK.com's stories flowing."

NanoBlogger

http://home.columbus.rr.com/n1xt3r/nanoblogger
"NanoBlogger is a small weblog engine written in Bash, that uses common unix tools, such as cat, grep and sed." Looks like Blosxom has some competition in the Unix-philosophy-of-blogging category