Creating the best software in multiple fields.

Releases

Tagged commits can be downloaded as .tar.gz files by accessing https://dec05eba.com/snapshot/<project-name>.git.<version>.tar.gz, for example version 5.5.1 of GPU Screen Recorder can be downloaded at https://dec05eba.com/snapshot/gpu-screen-recorder.git.5.5.1.tar.gz. This is the recommended way to download projects if you only want to install them (for example for distro packaging).

Reporting issues

Send an email to dec05eba@protonmail.com to report issues and include the terminal output of running the program and steps to reproduce the issue.

If you are reporting an issue with GPU Screen Recorder or related software then please also mention which distro you use, if you use x11 or wayland and your desktop environment/window manager, which gpu and cpu you use and where you installed GPU Screen Recorder from (flatpak, aur, etc) and the command you ran or the options you used (or take a screenshot of them).

If it's an issue related to the video output then please also include the output of drm_info (run sudo drm_info > log.txt and include that log.txt file in the email). Some distros have drm_info available in its package manager repositories.

If the program crashed then please send a call stack from gdb or valgrind output to the email address, if you know how to do that.

Suggesting features

I do not currently accept feature requests. If you want a feature you will have to implement it yourself and send a patch.

Questions

Email your questions to dec05eba@protonmail.com.

Contributing

Send an email to dec05eba@protonmail.com to contribute a bug fix/feature. To contribute a patch, first commit your change and then use the git format-patch command, like so:

git format-patch -1 HEAD

That creates a .patch file in the same directory. Send that patch file to my email dec05eba@protonmail.com. Remember that the patch includes your git name and email. If you dont want to include that information for privacy reasons then commit your change and use the git diff command instead, like so:

git diff HEAD^ > file.patch

and then send that patch file to my email dec05eba@protonmail.com.

Don't be afraid to contribute changes. Unlike many others, I'm not picky about code when it comes to bug fixes or new features. As long as there aren't bugs in the code or performance issues, then it's good enough.

The only exception is large architectural changes to existing code (refactoring). I might have a plan to do such changes myself, in which case your work could go to waste. It would be better if you contact me before you make such changes, if your intention is to contribute back those changes.

I also dont accept purely cosmetic patches.

Business inquiries

If you as a corporation have questions or need help implementing software that is in any way related to software on this website then you will need to hire me as a consultant. Send an email to dec05eba@protonmail.com with your inquiry.

Donation links:

Bitcoin: bc1qqvuqnwrdyppf707ge27fqz2n9y9gu7lf5ypyuf
Monero: 4An9kp2qW1C9Gah7ewv4JzcNFQ5TAX7ineGCqXWK6vQnhsGGcRpNgcn8r9EC3tMcgY7vqCKs3nSRXhejMHBaGvFdN2egYet

PGP

My PGP public key: