Standard Notes is an easy-to-use encrypted note-taking app for digitalists and professionals. Capture your notes, documents, and life’s work all in one place. //

No matter your needs, we’ve got you covered. In addition to our forever-free plan, we offer different subscription plans that help you get the most out of Standard Notes.

Our free plan gives you access to Standard Notes’ basic features.

• End to end encryption
• Seamless sync on all devices
• Web and offline access
• Plain text note type
• Unlimited notes
• Unlimited devices

Bahmni is an easy to use, complete, open source Hospital Information System (HIS) and Electronic Medical Record (EMR) that aims to meet the needs of low resource environments by leveraging a tapestry of existing open source products. Bahmni is an OpenMRS Distro. Website: http://www.bahmni.org

Businesses are simply not in the business of fair dealing. Those prioritizing their own concerns are simply doing what the law or the software license allows. The problem is not payment; it is permission – many popular open-source licenses are extremely permissive while lacking the reciprocity requirements of copyleft licenses. Licenses like the Apache license and the MIT license offer a lot and ask very little.

"Open source maintainers create massive amounts of value and capture almost none of it," said Feross Aboukhadijeh, an open-source developer who runs Socket, in an email to The Register. "Many of the most important open source projects that power the Fortune 500 are maintained by volunteers in their spare time, after work hours.

"The software industry needs to find a way to help maintainers start capturing at least a portion of the value they create so they can continue to write new features, fix bugs, improve documentation, and most importantly, fix critical security issues in a timely manner.

Aboukhadijeh added that the Log4j incident also illustrates how almost no company using open-source code in their applications bothers to review it.

"At the end of the day, companies are responsible for ensuring the code they ship to production is safe, secure, and reliable," he said.

Understanding Projects
Understanding of project like how folders are arranged? how files are linked? which tech stack is used? is the most important thing before raising an issue or making a pull request in any project on GitHub. //

Making Pull Request
Your PR should do one thing. Always make a pull request for one part or section so that it would be easier for reviewers and maintainers to merge your pull request. If you are solving multiple issues in a project then open multiple PRs.

Enigma2Illusion - 2021-05-19

I think people tend to forget that Mounir as a fulltime job, family obligations and the data center fire that impacted his livelihood and the VeraCrypt project.

I think people should consider how much time it takes to work on VeraCrypt for three OS's including the various Linux variants.

Mounir Idrassi handling the many features of VeraCrypt across three OS platforms (Linux, Mac, Windows) by performing development, testing, bug fixes and releasing software during his free personal time after working a fulltime job and family commitments for little to no monetary compensation. Just to compile and perform a release takes two days for a release of the three OSs.

Beta software is released to the VeraCrypt community with the hope that users are willing to test new upcoming versions to find issues before the next version is released since it is impossible for the developer to have test machines from the various PC makers, various Windows, Linux, Mac OS versions and various disk partitioning configurations for testing.

Hence, the developer relies on the VeraCrypt user community to help test the beta releases.

As with many Open Source projects, the developers rely on the user community to help each other with issues due to the overwhelming requests for assistance.

TL:DR
Each VeraCrypt user should consider how much work effort is involved on an Open Source project supporting three OSs and their various versions for little financial gain by performing development, testing, bug fixes and releasing software during their free time after meeting their obligations of fulltime job and family obligations. Not to mention some VeraCrypt users feeling entitled to have their support issues and/or features worked on immediately. :)

Obsidian is a powerful knowledge base on top of
a local folder of plain text Markdown files.

Nonfree (proprietary) software is very often malware (designed to mistreat the user). Nonfree software is controlled by its developers, which puts them in a position of power over the users; that is the basic injustice. The developers and manufacturers often exercise that power to the detriment of the users they ought to serve.

This typically takes the form of malicious functionalities.

The “jails” are malicious operating systems that are designed to impose censorship of which applications the user can install. The image of the iPrison illustrates this issue.

These systems are platforms for censorship imposed by the company that owns the system. Selling products designed as platforms for a company to impose censorship ought to be forbidden by law, but it isn't.

This page lists a few jails, along with some of the methods they use to censor apps, and includes specific examples of apps that were blocked using this censorship power.

Guiding Principles in Community-Oriented GPL Enforcement

• Our primary goal in GPL enforcement is to bring about GPL compliance.
• Legal action is a last resort. Compliance actions are primarily education and assistance processes to aid those who are not following the license.
• Confidentiality can increase receptiveness and responsiveness.
• Community-oriented enforcement must never prioritize financial gain.
• Community-oriented compliance work does not request nor accept payment to overlook problems.
• Community-oriented compliance work starts with carefully verifying violations and finishes only after a comprehensive analysis.
• Community-oriented compliance processes should extend the benefit of GPLv3-like termination, even for GPLv2-only works.

Copyleft itself is not a moral philosophy; rather, copyleft is a strategy that software freedom activists constructed to advance a particular set of policy goals. Specifically, software copyleft was designed to ensure that all users received complete, corresponding source for all binaries, and that any modifications or improvements made anywhere in the chain of custody of the software were available in source form to downstream users. As orginially postulated, copyleft was a simple strategy to disarm proprietarization as an anti-software-freedom tactic.
The Corruption of Copyleft

Copyleft is a tool to achieve software freedom. Any tool can be fashioned into a weapon when wielded the wrong way. That's precisely what occurred with copyleft — and it happened early in copyleft's history, too. Before even the release of GPLv2, Aladdin Ghostscript used a copyleft via a proprietary relicensing model (which is sometimes confusingly called the “dual licensing” model). This business model initially presented as benign to software freedom activists; leaders declared the business model “barely legitimate”, when it rose to popularity through MySQL AB (later Sun, and later Oracle)'s proprietary relicensing of the MySQL codebase.

In theory, proprietary relicensors would only offer the proprietary license by popular demand to those who had some specific reason for wanting to proprietarize the codebase — a process that has been called “selling exceptions”. In practice, however, every company I'm aware of that sought to engage in “selling exceptions” eventually found a more aggressive and lucrative tack. //

Most proprietary relicensing businesses work as follows: a single codebase is produced by a for-profit company, which retains 100% control over all copyright in the software (either via an ©AA or a CLA). That codebase is offered as a gratis product to the marketplace, and the company invests substantial resources in marketing the software to users looking for FOSS solutions. The marketing department then engages in captious and unprincipled copyleft enforcement actions in an effort to “convert” those FOSS users into paying customers for proprietary licensing for the same codebase. (Occasionally, the company also offers additional proprietary add-ons, improvements, or security updates that are not available under the FOSS license — when used this way, the model is often specifically called “Open Core”.)

Why We Must End The Proprietary Relicensing Exploitation of Copyleft

This business model has a toxic effect on copyleft at every level. Users don't enjoy their software freedom under an assurance that a large community of contributors and users have all been bound to each other under the same, strong, and freedom-ensuring license. Instead, they dread the vendor finding a minor copyleft violation and blowing it out of proportion. The vendor offers no remedy (such as repairing the violation and promise of ongoing compliance) other than purchase of a proprietary license. Industry-wide. I have observed to my chagrin that the copyleft license that I helped create and once loved, the Affero GPL, was seen for a decade as inherently toxic because its most common use was by companies who engaged in these seedy practices. You've probably seen me and other software freedom activists speak out on this issue, in our ongoing efforts to clarify that the intent of the Affero GPL was not to create these sorts of corporate code silos that vendors constructed as copyleft-fueled traps for the unwary. Meanwhile, proprietary relicensing discourages contributions from a broad community, since any contributor must sign a CLA giving special powers to the vendor to continue the business model. Neither users nor co-developers benefit from copyleft protection. //

Given the near ubiquity of proprietary relicensing and the promulgation of stricter copylefts by companies who seek to engage (or help their clients engage) in such business models, I've come to a stark policy conclusion: the community should reject any new copyleft license without a clause that deflates the power of proprietary relicensing. Not only can we incorporate such a clause into new licenses (such as copyleft-next), but Conservancy's Executive Director, Karen Sandler, came up with a basic approach to incorporating similar copyleft equality clauses into written exceptions for existing copyleft licenses, such as the Affero GPL. I have received authorization to spend some of my Conservancy time and the time of our lawyers on this endeavor, and we hope to publish more about it in the coming months.

We've finished the experiment. After thirty years of proprietary relicensing, beginning with Aladdin and culminating with MongoDB and their SS Public License, we now know that proprietary relicensing does not serve or extend software freedom, and in most cases has the opposite effect. We must now categorically reject it, and outright reject any new licenses that can be used for it.

Heat pump heating technology is starting to pop up more and more lately, as the technology becomes cheaper and public awareness and acceptance improves. Touted as a greener residential heating system, they are rapidly gaining popularity, at least in part due to various government green policies and tax breaks.

[Gonzho] has been busy the last few years working on his own Arduino Powered Open Source heat pump controller, and the project logs show some nice details of what it takes to start experimenting with heat pumps in general, if that’s your game. Or you could use this to give an old system a new lease of life with an Arduino brain transplant.

Spec revision № 1.0

Time Card is the heart of the Open Time Server Project.
This spec can be accessed using http://www.timingcard.com

Time Master is a critical part of a PTP enabled network. It provides accurate time via GNSS while maintains the accuracy in case of GNSS failure via a high stability (and holdover) oscillator such as an atomic clock. Exisiting products in the market are often closed sourced an far from sufficient features. The Time Card project presents an open source solution via a PCIe card.
Form Factor

• Standard PCIe Stand-up Card
• Single Slot - Passive Cooling Solution

....

Repository content

• Bill of Materials (parts from Digikey)
• Schematic and PCB of the time card
• Driver (Kernel Module) CentOS 8
• CAD files for the custom PCIe bracket

Where can I get one?

You have all necessary source code, BOM, Gerber files and binaries to build it youself. However, we are currently working with several suppliers and will have their contact info soon available to allow you to puchase an out-of-the-box ready Time Card.

• Facebook engineers have built and open-sourced an Open Compute Time Appliance, an important component of the modern timing infrastructure.
• To make this possible, we came up with the Time Card — a PCI Express (PCIe) card that can turn almost any commodity server into a time appliance.
• With the help of the OCP community, we established the Open Compute Time Appliance Project and open-sourced every aspect of the Open Time Server.

In March 2020, we announced that we were in the process of switching over the servers in our data centers (together with our consumer products) to a new timekeeping service based on the Network Time Protocol (NTP). The new service, built in-house and later open-sourced, was more scalable and improved the accuracy of timekeeping in the Facebook infrastructure from 10 milliseconds to 100 microseconds. More accurate time keeping enables more advanced infrastructure management across our data centers, as well as faster performance of distributed databases.

The new NTP-based time architecture uses a Stratum 1 — an important component that is directly linked to an authoritative source of time, such as a global navigation satellite system (GNSS) or a cesium clock.

http://ocptap.com/

http://opentimeserver.com/

https://github.com/opencomputeproject/Time-Appliance-Project

bout the Atomic Reference Time Card (ART Card)

The Atomic Reference Time Card (ART Card) developed by Orolia is intended to work in pair with OCP’s PTP-OCP driver, which offers a PTP Hardware clock (PHC) interface to use for time synchronization.

The architecture of the ART Card as well as the software architecture that will manage the card are intended to be embedded in any Open Compute server to build a PTP Grand Master.

This new timing card has been developed in the framework of the Time Appliances Project (TAP), a sub-project initiated by the Open Compute Project (OCP).

PowerDNS, founded in the late 1990s, is a premier supplier of open source DNS software, services and support. Deployed throughout the world with some of the most demanding users of DNS, we pride ourselves on providing quality software and the very best support available. Since 2015 we are part of Open-Xchange.

Our Authoritative Server, Recursor and dnsdist products are 100% open source. For the service provider market, OX also sells OX Protect which builds on our Open Source products to deliver an integrated DNS solution with 24/7 support and includes features as parental control, malware filtering, automated attack mitigation, and long-term query logging & searching.

ArchiveBox is a powerful, self-hosted internet archiving solution to collect, save, and view sites you want to preserve offline.

You can set it up as a command-line tool, web app, and desktop app (alpha), on Linux, macOS, and Windows.

You can feed it URLs one at a time, or schedule regular imports from browser bookmarks or history, feeds like RSS, bookmark services like Pocket/Pinboard, and more. See input formats for a full list.

It saves snapshots of the URLs you feed it in several formats: HTML, PDF, PNG screenshots, WARC, and more out-of-the-box, with a wide variety of content extracted and preserved automatically (article text, audio/video, git repos, etc.). See output formats for a full list.

The goal is to sleep soundly knowing the part of the internet you care about will be automatically preserved in durable, easily accessible formats for decades after it goes down.

OpenSCAD is software for creating solid 3D CAD objects.
It is free software and available for Linux/UNIX, MS Windows and Mac OS X.

The brouhaha started just a few months ago when Audacity was bought by the Muse Group, the company behind equally popular music software like MuseScore, which is also open source, and Ultimate Guitar. So far, Audacity remains open source (and can’t really be changed into proprietary software in its current form), but that doesn’t mean that Muse Group can’t do some pretty damaging changes. Those changes come in the form of the new privacy policy that was just updated a few days ago, a policy that now allows it to collect user data.

As a desktop application with no core online functionality, Audacity never had any need to “phone home” in the first place. Now the privacy policy says that the new company does collect data and does so in a way that’s both over-arching and vague, most likely by design. For example, it says that it collects data necessary for law enforcement but doesn’t specify what kind of data is collected.

There are also questions regarding the storage of data, which is located in servers in the USA, Russia, and the European Economic Area. IP addresses, for example, are stored in an identifiable way for a day before being hashed and then stored in servers for a year. The new policy also disallows people under the age of 13 from using the software, which, as FOSS Post points out, is a violation of the GPL license that Audacity uses.

Google offers many desirable, easy-to-use, effective features. Going open source is trickier. //

Finding a solution to organizing and safely storing these precious memories is more important than ever, and it's becoming an increasingly large problem to solve. Photos depict a special moment in time, a memory or event that can't be recreated. They are irreplaceable and largely only exist digitally. Because of this, there are few categories of data that suit a free and open self-hosted solution better.

In May 2020, Microsoft surprised everyone (including me) by releasing the source code to GW-BASIC. Rich Turner (Microsoft) wrote in the announcement on the Microsoft Developer Blog:
Since re-open-sourcing MS-DOS 1.25 & 2.0 on GitHub last year, we’ve received numerous requests to also open-source Microsoft BASIC. Well, here we are! As clearly stated in the repo's readme, these sources are the 8088 assembly language sources from 10th Feb 1983 and are being open-sourced for historical reference and educational purposes. This means we will not be accepting PRs (Pull Requests) that modify the source in any way.

You can find the GW-BASIC source code release at the GW-BASIC GitHub. And yes, Microsoft used the MIT License, which makes this open source software.

https://devblogs.microsoft.com/commandline/microsoft-open-sources-gw-basic/

https://github.com/microsoft/GW-BASIC