commit: 8dc30be4e82370073139246b349687e2ceaa8330
parent d0a815f2ba86b2808183a5dce35402653d1e4f8c
Author: Haelwenn (lanodan) Monnier <contact@hacktivis.me>
Date: Sun, 5 Jan 2020 04:25:04 +0100
projects/badwolf: 2020-01 update
Diffstat:
1 file changed, 18 insertions(+), 14 deletions(-)
diff --git a/projects/badwolf.shtml b/projects/badwolf.shtml
@@ -9,34 +9,38 @@
<main>
<h1>BadWolf</h1>
<a href="/images/badwolf_2019-05-11.png"><img class="thumb_inline right" src="/images/badwolf_2019-05-11.png" alt="Screenshot of badwolf on this page"/></a>
- <p>BadWolf is a privacy-oriented WebKitGTK browser that doesn’t do compromises for first-usage usability. Privacy is the first goal, and it should be usable (the security=usability<sup>-1</sup> is false in my opinion). It should also stay fairly minimalist, stuff done in our dependencies that would need modification should be done upstream instead of us doing work we aren’t supposed to do in the first place.</p>
- <p>It has also been my daily driver for quite a while now (specially since I added tabs) so you can expect it to be quite usable but still have few missing areas.</p>
+ <p>BadWolf is a privacy-oriented WebKitGTK browser that doesn’t do compromises for first-usage intuitiveness. Privacy is the first goal, and it should be nicely usable/accessible (the security=usability<sup>-1</sup> is false in my opinion). It should also stay fairly minimalist, stuff done in our dependencies that would need modification should be done upstream instead of us doing work we aren’t supposed to do in the first place.</p>
<p>For now it is de-facto is a personnal project but I welcome contributions and could add maintainers and move to a more community-oriented way of doing the development.</p>
<p>Features that are not wanted to be present by default will either be done as an option or as a separate branch, this is to avoid having a pile of browsers doing the same thing. Also extensions will try to be independant of the browser.</p>
<h2>Releases</h2>
- <p>The releases are stable but I would consider the current stage of development to be in beta as not everything is present yet. Badwolf is using <a href="https://semver.org/spec/v2.0.0.html">Semantic Versioning</a>.</p>
- <p>You can get the releases tarballs and changelogs at <a href="https://hacktivis.me/releases/">https://hacktivis.me/releases/</a> and <a href="https://gitlab.com/lanodan/badWolf/-/tags">https://gitlab.com/lanodan/badWolf/-/tags</a> (which also provides an <a href="https://gitlab.com/lanodan/badWolf/-/tags?format=atom">Atom feed</a>), there is only source releases for now but if I can be sure that I can have portable binairies without having to bundle the dependencies I’ll do them too.</p>
+ <p>Badwolf is using <a href="https://semver.org/spec/v2.0.0.html">Semantic Versioning</a> with considering the User-Interface as an API. Once 1.0.0 release is out, a release branch (ie. 1.0.x) is supported for 6 months for any bug fixes and 2 years for security fixes.</p>
+ <p>You can get the releases tarballs and changelogs at <a href="https://hacktivis.me/releases/">https://hacktivis.me/releases/</a> and <a href="https://gitlab.com/lanodan/badWolf/-/tags">https://gitlab.com/lanodan/badWolf/-/tags</a>, the latter also provides an <a href="https://gitlab.com/lanodan/badWolf/-/tags?format=atom">Atom feed</a>. Only source release are supported outside of ones supported by software distribution, static-linking and Flatpaks should work but their distribution of them will have to be done by some other party.</p>
<h3>Packages / Recipes</h3>
<ul>
<!-- Alphabetically sorted -->
+ <li>Alpine: Added in edge testing in 2019-12-30 as <code><a href="https://pkgs.alpinelinux.org/packages?name=badwolf">badwolf</a></code></li>
<li>ArchLinux: Present in the AUR as <code><a href="https://aur.archlinux.org/packages/badwolf/">badwolf</a></code></li>
<li>Gentoo: Present in the <a href="https://wiki.gentoo.org/wiki/Project:GURU">GURU overlay</a> as <code><a href="http://gpo.zugaina.org/www-client/badwolf">www-client/badwolf</a></code></li>
</ul>
- <p>And maybe other platforms not added to this list yet but can be found via <a href="https://repology.org/project/badwolf/versions">https://repology.org/project/badwolf/versions</a></a>
- <h2>Supported platforms</h2>
- <p>In a sort-of descending priority list, X11 and Wayland are supported.</p>
+ <p>And maybe other platforms not added to this list yet but can probably be found via <a href="https://repology.org/project/badwolf/versions">https://repology.org/project/badwolf/versions</a></a>
+ <h2>Tested and supported platforms</h2>
<ul>
- <li>Gentoo Linux (what I use)</li>
- <li>Other regularly up-to-date linux distros like: Alpine Linux, Archlinux, …</li>
- <li>Other systems like: NetBSD</li>
- <li>Outdated by design linux distros: Debian, RedHat, …</li>
+ <li>OS: */Linux, NetBSD, OpenBSD, FreeBSD</li>
+ <li>CPU Architectures: x86_64/amd64, armv7hf</li>
+ <li>Display: Wayland, X11</li>
+ <li>WebKitGTK: 2.26.x+, compiling it yourself is recommended</li>
</ul>
- <p>Note: proprietary systems like Microsoft Windows and Apple OS are unsupported. If you have systems where WebKitGTK runs but isn’t a *BSD or a linux distro, I’ll be interested in knowing about them.</p>
+ <p>Badwolf should also work well on other similar systems, feel free to report tests on them and volunteer for testing releases before they are published.<br/>If you have a libre system where WebKitGTK runs but isn't Linux or *BSD, I'll be interested in knowing about them. Proprietary systems are unsupported.</p>
<h2>Bug reports / Contributions</h2>
- <p>The git repositories are using <a href="https://nvie.com/posts/a-successful-git-branching-model/">GitFlow</a> with commits that are clean with descriptive messages. Expect your patchs to be rewrote or rejected if not, with proper explaination at it should always be.</p>
+ <p>Please try to reach me before modifying code, I wish to avoid rejecting patches because their design didn't fit while the idea could be more than welcome.</p>
+ <h3>Translation</h3>
+ <p>Badwolf is using gettext po files for translations, help in getting it translated in more languages is welcome (but please do not submit machine translation, I can do this myself).</p>
+ <h3>Code</h3>
+ <p>The git repositories are using <a href="https://nvie.com/posts/a-successful-git-branching-model/">GitFlow</a> with commits that are clean with descriptive messages. I'll probably ask you to rewrite your commits or rewrite them if they aren't.</p>
<ul>
- <li>You can use <a href="/git/badwolf">/git/badwolf.git</a> and send me an email (<code>git send-email</code> is accepted, <a href="https://git-send-email.io/">here is a tutorial</a>) at <code>contact+badwolf@</code></li>
+ <li>You can use <a href="/git/badwolf">/git/badwolf.git</a> and send me an email (<code>git send-email</code> is accepted, <a href="https://git-send-email.io/">here is a tutorial</a>) at <code>contact+badwolf@hacktivis.me</code></li>
<li>You can use <a href="https://gitlab.com/lanodan/badwolf">the gitlab repository</a> (note: will get cleanly migrated to something else at some point)</li>
+ <li>You can also use other means, like an actual pull request(sending a link to a repo and a branch)</li>
</ul>
<h2>See also</h2>
<h3>Similar browsers</h3>
