How to Evaluate Open Source Software / Free Software (OSS/FS) Programshttps://dwheeler.com/oss_fs_eval.html
a case study on Course Management Systems" also provides an approach for evaluating OSS/FS, including a worked example that evaluated 36 systems. Interestingly, van den Berg surve
This paper describes how to evaluate open source software
Jose Explains Why Not Monohttp://techrights.org/o/2008/11/25/jose-on-mono/
blog entry), vs. legacy management of existing built Windows-based software (help existing msapps run on Linux). The FOSS dotnet "clones" market will develop automatically as one
Our reader Jose explains the dangers of embracing Novell's Mono
Home - ratfactorhttp://ratfactor.com/
to release our Learning Management System project under an open-source license. I think it’s a pretty great piece of software: single-page application based on mithril.js wi
CLI Club: Command-line Interface Tools & Alternativeshttps://cli.club/
automatic contact-list management, custom code insertion via a Ruby hook system, and more. If you’re the type of person who treats email as an extension of your long-term memory,
A collection of the best CLI
Linux Gazette Indexhttps://www.linuxdoc.org/LDP/LG/lg_index.html
Orr Simple Package Management With Stow , by Allan Peda Why I wrote Install Kernel (ik) and How It Works , by Justin Piszcz Writing Documentation, Part III: DocBook/XML , by Chris
Esoteric Operating Systemshttps://sgfault.com/post/2018/05/2018-05-31-esoteric-os/
scheduling, memory management, device drivers and little else. Everything else such as the network stack, input handling, the filesystem and every other component you may think of
Vita :: James Lyle Petersonhttp://www.jklp.org/profession/vita/vita.html
these classes of memory management algorithms, first to the weighted buddy system and then to more general buddy systems. The general algorithms, based on powers-of-two, Fibonacci
The Mailbag LG #115https://linuxgazette.net/115/lg_mail.html
overhead and a key-management problem. Jack Masters <jackm.abc(at)starplace(dot)com> wrote: Rick Moen wrote: > test <test(at)example(dot)com> wrote: > ^^^^^^^^^^
Find more...