diff options
| author | Namilskyy <alive6863@gmail.com> | 2025-11-25 19:54:46 +0300 |
|---|---|---|
| committer | Namilskyy <alive6863@gmail.com> | 2025-11-25 19:55:11 +0300 |
| commit | 8efb28c1f675071b5571192cd6581bfb3eb7cca5 (patch) | |
| tree | 626ed7395851ed0f01efb5e4f8de0c0f81695cee | |
| parent | b9d6c9ab98890136027c2b17cf9cb7ec42f66881 (diff) | |
Added 'our policy' and 'support us' items to README.md
| -rw-r--r-- | README.md | 17 |
1 files changed, 16 insertions, 1 deletions
@@ -35,4 +35,19 @@ You can set the package compilation parameters in the global /etc/mesk.toml. (Re The `.mesk` package can be generated automatically, given that the software is open source and based on standard build systems: `make`, `CMake`, `meson`, `cargo`. If the package does not require compilation, you must specify how and where to install it. -We only support open source software. Binary builds of proprietary applications will not appear in the official repositories, but, for example, there will be open clients for messengers with a closed backend.
\ No newline at end of file +We only support open source software. Binary builds of proprietary applications will not appear in the official repositories, but, for example, there will be open clients for messengers with a closed backend. + +# Our policy +1. Documentation is a sore point for i2p client implementations (even for the official i2p-rs, for example), after tinkering with a ton of non-working and undocumented libraries for i2p, our conscience will not allow us not to work on documentation. + +_By the way, I will mention that the official examples of i2p-rs have a completely different structure of imports and library operation than crates.io versions. Over time, we plan to switch to our own implementations of client libraries for i2p._ + +2. The style of the code. So far, we have not reached a functioning prototype, the code works on a procedural programming paradigm, but eventually we will switch to a functional one. The code may hurt the eye, but it must contain documentation comments and its logic must be clear. + +3. Minimalism and reliability. Our programs will not contain unnecessary functions that may lead to misunderstandings of the program interface (the CLI is also an interface), as well as functions that benefit but are controversial in their reliability. + +A free network should be available to everyone. + +# Support us +This project cannot be implemented without some support. The most valuable thing you can do for us is to create a Pull Request or spread information about us in any circle. We are a team of enthusiasts who do not have all the means to do this initially. All big projects absolutely always start small. + |
