This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
opensoftware:contract [2020/01/18 07:03] jrmu created |
opensoftware:contract [2020/01/18 07:46] (current) jrmu |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ===== Commitment to Open Info ===== | ||
| + | |||
| Here is our commitment to you, the people: | Here is our commitment to you, the people: | ||
| - | All works on our website ircnow.org, as well as all apps and server software will follow these guidelines: | + | All works on our website ircnow.org, as well as all apps and server software will guarantee these freedoms: |
| + | |||
| + | - The freedom to use the work | ||
| + | - The freedom to study the work | ||
| + | - The freedom to modify the work | ||
| + | - The freedom to share the work | ||
| + | - The freedom to reproduce the work | ||
| + | |||
| + | …for any purpose, without fee, without requiring permission. | ||
| + | |||
| + | We are committed to the following: | ||
| - | - The user will be free to use the software for any purpose | + | Our project will be functional using only open protocols and standards. These include protocols such as XMPP, IRC, and SIP. There will be no requirements to use proprietary protocols. We allow interoperability with proprietary protocols, but we will not require customers to use proprietary protocols. |
| - | Our project must be functional using only open source protocols. Our goals are to use XMPP, IRC, SIP, and WebRTC. There must be no requirements to use proprietary or 3rd party protocols. Use is allowed, but must not be required from customers. | + | |
| - | Specifically, we must not require the use of Telegram, Signal, Facebook, Discord, WhatsApp, LINE, Facebook Messenger, Dropbox, Google Drive, Google Docs, Gmail, Microsoft Azure, Amazon AWS, Google App Engine, Google FireBase. The app must work without using any of these apps or protocols. Use of these services are allowed, but must not be required from customers. | + | |
| - | Our project must be functional using only open source software. There must be no requirement to use proprietary software. Specifically, customers must be able to run a functional app using only open-source software on BSD and Linux. Use of proprietary software is allowed, but must not be required from customers. | + | |
| - | Specifically, we must not require customers install Zoom, Microsoft Windows, Apple Mac, Apple iPhone, Google Android, Google Play, Apple App Store. Use of these services is allowed, but must not be required from customers. | + | |
| - | Our project's goal is to eventually release all software and content into the public domain. There must be no copyrighted content in the project that forbids redistribution, modification, or usage. Use outside of the project is allowed, but not inside the project. | + | |
| - | Our project must allow anyone to easily self-host. There must be no requirements to use proprietary services or 3rd party infrastructure. Specifically, we must guarantee that our servers work on Linux and BSD using only open-source software. Providing support for proprietary software like Windows is allowed, but must not be required from customers. | + | |
| - | Software Quality | + | Specifically, our project will not require the use of Telegram, Signal, Facebook, Discord, WhatsApp, LINE, Facebook Messenger, Dropbox, Google Drive, Google Docs, Gmail, Microsoft Azure, Amazon AWS, Google App Engine, or Google FireBase. The app must be functional without any of these apps or protocols. |
| - | The goals for Software Quality are not promises. They are flexible rules. If we agree, we may break the following rules at times. | + | Customers must be able to run a functional app using only open-source software on BSD and Linux. Project software can depend on proprietary software (such as Windows or iOS) but must **never** be required from customers. |
| - | Where possible, we will follow open standards | + | |
| - | Where possible, we will prefer using software that has fewer CVEs. We will code with security as a priority. | + | |
| - | Where possible, we will prefer using software that has a long history of being reliable and stable | + | |
| - | Where possible, we will prefer using software that has a permissive license rather than the GPL. The ideal software is public domain | + | |
| - | Where possible, we will prefer using software that has been better tested | + | |
| - | Where possible, we will prefer using software that has better documentation. We must produce good documentation. | + | |
| - | Where possible, we will prefer using software that is simpler for the programmer to understand. We must write software that is easy to understand. | + | |
| - | Where possible, we will avoid 3rd party dependencies | + | |
| - | The following are not as important: features, cost, popularity, appearance | + | |
| - | Software Privacy | + | This project's software must respect users' freedoms. There must be no copyrighted content in the project that forbids reproduction, modification, or usage. |
| + | |||
| + | Specifically, it **must** be possible to reproduce and self-host this software on outside infrastructure. We must guarantee that our servers work on open source Linux and BSD operating systems. | ||
| - | The goals for Software Privacy are not promises. They are flexible rules. If we agree, we may break the following rules at times. | + | ===== Software Quality ===== |
| - | We will collect as little personal information as possible about students. | + | |
| - | We will avoid logging except when necessary for critical features. Specifically, we should allow the user the option to never log any chats, audio, or video. | + | |
| - | We will try to allow anonymous login unless we have too much criminal activity using our software. Specifically, we will avoid asking for phone numbers, emails, or legal names. | + | |
| - | We will not sell or share data to 3rd parties except as required by law. | + | |
| - | We should try to offer the best encryption that is legally allowed. | + | |
| + | The rules below are flexible goals which cannot always be fulfilled, but which we strive for: | ||
| + | - Security and correctness are top priorities, not performance, cost, popularity, or appearance | ||
| + | - We prefer software with a long history of reliability and portability, not features | ||
| + | - We prefer software with a permissive license rather than the GPL. The ideal is the public domain. | ||
| + | - We strive for accurate, complete, and fully open documentation. | ||
| + | - We prefer software that is simpler for the programmer to understand | ||
| + | - We strive to avoid 3rd party dependencies | ||
| + | We strive to follow the UNIX philosophy: | ||
| + | - Software should do one thing and do it well | ||
| + | - Programs are designed to work together | ||
| + | - Text streams are the common interface between programs | ||