413 private links
This is the project site for Evergreen, highly-scalable software for libraries that helps library patrons find library materials, and helps libraries manage, catalog, and circulate those materials, no matter how large or complex the libraries.
Evergreen is open source software, licensed under the GNU GPL, version 2 or later.
Get The World’s Most Popular Customer Support Software
We believe in helping you Make. Happy. Customers. Easily scale and streamline your customer service and drastically improve your customer’s experience.
that one in the corner
but no FOSS package ever dies
Oh yes they do - and have.
Nowadays, the bulk of FOSS is shoved into GitHub and will be available - for as long as GirHub bothers to run its servers[1].
Back in the day, Tarballs and Arc files were downloaded direct from the author's site and then you were expected to mirror it if it was important to you.
Then the Web was "discovered" by more and more people and for some reason the mirroring stopped and changed to just dropping in a link to "the" download location - and of course, we then learnt that URLs have a half-life.
As public version control servers came online - and people started to trust them - we saw materials on something safer than a personal site, or the pages of a company that vanished overnight (sometimes the entire company vanished, sometimes just the project)[2].
If you are lucky, the Internet Archive grabbed a copy and you can try one of the dead URLs there; patience can be required[4].
If you are really lucky, somebody has put a copy into GitHub[5] - although you can open yourself up to flames because your copy "doesn't compile for me"[6]
And what about the FOSS that is practically single-sourced by being published in that JavaScript compost heap? Was LeftPad() also available from GitLab? Some of it is handled properly (p5.js oooh, squiggly and probably safe from vanishing).
Of course, any FOSS that does fall through the cracks "is not important" - after all, all the Linux distros keep their own copies of source packages, "so we are not actually reliant on GitHub at all, Corner you fool."
Not important. Well, you never know. Literally, you never know, it has gone now.[7]
[1] Then we'll have to go back and pull the older version from SourceForge.
[2] As a few others did I like the old "Elegant" library & util from Philips Labs - good luck finding that, on the Philips site - or doing a web search for it available elsewhere[3]
[3] stop giving your projects names that are normal words!
[4] not being able to find something is, in all practical terms, the same as the thing no longer existing at all. Take note when organising your backup copies...
[5] really must put my compiling copy of Elegant up on GitHub
[6] so maybe I won't put Elegant up, as I only have Makefiles for My Own Build System and am fed up telling people how to write build scripts for their favoured build tools. Seriously.
[7] "Important" is a relative term[8]. Maybe it is really important to you to generate an awful lot of Elegantly laid out syntax diagrams in the next day or you can't pay for Tiny Tim's new clutches, he is growing so fast nowadays, at least the one leg is.
[8] see so very many commentards "well, my PC is ok so this is a non-issue" and the response to same
[9] Footnotes FTW. Be more Pterry!
Minimise
Proprietary code goes unpublished – but no FOSS package ever dies. //
Proprietary code goes unpublished: if its host company dies, it probably dies with it the moment the servers are wiped.
Open source's default mode is life. The code is published, cloned, archived by default. It may be abandoned to lie dormant, like a tardigrade sitting out a drought in suspended animation, but drop the water of attention on it and it's back in the game. At least, that's the theory. //
Ledru started the project for very personal reasons: as a director at Mozilla, he was surrounded by Rust creators in an entirely managerial job, and he wanted to learn Rust. Reinventing coreutils, for him, was primarily fun; he learned the thinking behind the beginning of modern computing. Plus, it seemed to be something worth doing.
Last year, the package started to get a reputation for robustness, and was finding its way into production in some significant places. It had attracted hundreds of contributors, it had some performance advantages, and it has a more permissive license – MIT in place of GPL. You can do that if you re-invent. //
The real joy of this is that it's been so organic. One person's itch to learn and code found its salve in a project that few thought needed to be done. But in ten or 20 years' time, it will need to have been done. None of the reasons for this have any place in the proprietary, metrics-driven goal world of closed source.
The end result is that an essential and massively used set of tools from 50 years ago will be just as essential and just as used 50 years hence. To the many freedoms FOSS grants, we can add that of looking ahead as far as you can see and quietly start the business of evolution to fit.
There's a core utility for you. ®
Speak Freely is a 100% software-based VoIP phone originally written in 1991 by John Walker, founder of Autodesk, and Brian C. Wiles. Over the years since, other VoIP applications popped up, but Speak Freely was the first VoIP application (or Internet telephone) released to the public.
Microsoft has open-sourced another bit of computing history this week: The company teamed up with IBM to release the source code of 1988's MS-DOS 4.00, a version better known for its unpopularity, bugginess, and convoluted development history than its utility as a computer operating system.
The MS-DOS 4.00 code is available on Microsoft's MS-DOS GitHub page along with versions 1.25 and 2.0, which Microsoft open-sourced in cooperation with the Computer History Museum back in 2014. All open-source versions of DOS have been released under the MIT License. //
The publicly released version of MS-DOS 4.00 is known less for its new features than for its high memory usage; the 4.00 release could consume as much as 92KB of RAM, way up from the roughly 56KB used by MS-DOS 3.31, and the 4.01 release reduced this to about 86KB. The later MS-DOS 5.0 and 6.0 releases maxed out at 72 or 73KB, and even IBM's PC DOS 2000 only wanted around 64KB.
These RAM numbers would be rounding errors on any modern computer, but in the days when RAM was pricey, systems maxed out at 640KB, and virtual memory wasn't a thing, such a huge jump in system requirements was a big deal. //
Microsoft has open-sourced some other legacy code over the years, including those older MS-DOS versions, Word for Windows 1.1a, 1983-era GW-BASIC, and the original Windows File Manager. While most of these have been released in their original forms without any updates or changes, the Windows File Manager is actually actively maintained. It was initially just changed enough to run natively on modern 64-bit and Arm PCs running Windows 10 and 11, but it's been updated with new fixes and features as recently as March 2024.
git-annex allows managing files with git, without checking the file contents into git. While that may seem paradoxical, it is useful when dealing with files larger than git can currently easily handle, whether due to limitations in memory, time, or disk space.
git-annex is designed for git users who love the command line. For everyone else, the git-annex assistant turns git-annex into an easy to use folder synchroniser.
Elevate Your Presentations with FreeShow
A dynamic, user-friendly, and open-source presenter built for all of your presentations. //
Every year churches spend hundreds of millions of dollars on the software needed to operate effectively and efficiently. We believe that within the Church the talent exists to create all the software that churches need and provide it free of charge.
So, there’s your quick background on open source software and why using these is not only great for your needs, but also for your budget!
Experience the power of open source in your church with worship presentation software designed to fit how you want to run your service. Fast, flexible and easy to use, you will have your service up and running in a few minutes. These features and a whole lot more at a price that can't be beat.
FreeShow is a free and open-source presentation program that makes it easy to show text on a big screen. It supports stage display, remote control, media, and many other advanced features. It is open-sourced meaning anyone can contribute.
Jellyfin is the volunteer-built media solution that puts you in control of your media. Stream to any device from your own server, with no strings attached. Your media, your server, your way.
Cyberduck is a libre server and cloud storage browser for Mac and Windows with support for FTP, SFTP, WebDAV, Amazon S3, OpenStack Swift, Backblaze B2, Microsoft Azure & OneDrive, Google Drive and Dropbox.
OpenWrt, the open source firmware that sprang from Linksys' use of open source code in its iconic WRT54G router and subsequent release of its work, is 20 years old this year. To keep the project going, lead developers have proposed creating a "fully upstream supported hardware design," one that would prevent the need for handling "binary blobs" in modern router hardware and let DIY router enthusiasts forge their own path. //
Failing an image of the proposed reference hardware by the OpenWrt group, let us gaze upon where this all started: inside a device that tried to quietly use open source software without crediting or releasing it.
Welcome to the CryptPad documentation.
CryptPad is a collaboration suite, encrypted and open-source.
This site contains 3 guides with information about using CryptPad, installing and administering the service, and contributing to the code.