It’s common knowledge that any open source project wouldn’t mind having more contributors and Tox is not an exception. This blog post is for those who want to contribute but don’t know where to start.
Starting contributing to Tox is as easy as joining #toktok channel on Freenode IRC, which is where majority of the development discussion takes place, and asking what part of Tox would benefit the most given your skill set and interests, unless you already have an idea which part of Tox you would like to help with. Just note that it might take some time for you to get a reply as not everyone is always in the chat, so please be patient. Many Tox developers and community members are connected to the chat 24/7 but get on it only in their free time. Mailing list might sound more appropriate for such possibly asynchronous discussions, and we do have a mailing list, but it doesn’t seem to catch on among developers much, so you will get better response on IRC.
Here is a non-exhaustive list of things you could help with, just to give an idea.
You don’t have to know programming in order to help. You can help by testing nightly builds of clients and translating clients to different languages.
You can help by testing nightly builds of Tox clients, the in-development, yet to be released, versions of clients, and reporting any problems you encounter to the developers. Testing nightly builds can help to find bugs and get them fixed before a release is made. Some clients don’t have nightly builds available for testing, or they do but they are not well maintained and might be broken. If this is the case for a client you want to test, simply asking developers for nightlies should resolve this issue. Also, even if the client you test is non-nightly, your testing is still useful. Just make sure that you are testing the latest release version of the client, as any issues you encounter might have been fixed in a newer version. You can get a client to test from the Download page of our website. You can provide feedback to the client developers by opening an issue in the client’s issue tracker, which is generally located on the client’s repository page. When reporting feedback, especially bugs, is a good idea to provide as much information to the developers as possible: operating system you are running and the version of it, the version of the Tox client you are running, exact steps on to how to reproduce the issue you are having and what you have expected to happen instead when you took those steps.
Some of the clients support multiple languages in their user interface, you can help translate the user interface to any language you know and correct existing translations if you find them unsatisfactory.
Here are links for some of clients:
Anyone with programming background is welcome, as we have quite diverse codebases. We could use help of people familiar with any of C, C++, Go, Haskell, Java, Python, Rust, Scala, Swift and other. Familiarity with networking, peer-to-peer software design, distributed hash table, cryptography and writing secure code is preferred, but not required for all of the codebases we have. You can help with an existing software project or start a new project of your own that would be useful to Tox. Also, you don’t have to write code to contribute. Reviewing the code that is considered for merging into the codebase is also a great way to help.
We are in need of package maintainers (to the point that we don’t have packages for Ubuntu 17.10 (Artful) at all), anyone familiar with shell scripting, building software, debugging and fixing failed builds and creating packages is welcome. We maintain Debian and Ubuntu package repositories, with packages being created using pbuilder, so familiarity with pbuilder helps.
Join #toktok and become a contributor today!
I’m thinking to create two app using golang
1: http proxy for tox, making it able to host “internal services”: more or less like I2P, but based on the tox protocol, with internal services as destinations and a proxy to enter the network with a browser.
2: file sync for tox. Something similar to syncthing , but based on tox protocol.
I will join the IRC chat ASAP, even if, I think, it could be better to have something like discord, or a forum, or any other offline/capable discussion system.
Sounds interesting, will see you on IRC!
Basically I think the http proxy will be an exercise. I mean, what I plan to do is to record the http request and send it as it was a file. Then, record the http answer and send it back as it was a file. Does not look hard, but I need to get familiar with tox protocol in golang.
The file sync seems harder, because of deltas , partial and synchronization. But, I am not sure: if the http proxy will be able to address webdav/ownCloud, maybe to add socks support to the proxy (in order to support IMAP/SMTP and others) may be better. Still don’t know.
From there, you can forward data sent from the web browser to the server to a tox instance running on the server. Furthermore, you can forward data from the tox instance to the websocket to the web browser.
ANOTHER thing you could do, is compile a tox client to webassembly but you still need to do some work on the server side to get websockets converted to tox communication.
I want to do something LIKE this, but I think it’s a lot of work.
And I’m NOT a Robot! I’m a Free Man!!
I’m interested in contributing as a developer if I can get the time.
My tox ID is
I want to expand the guts of the system. I stumble on the problem of NAT traversal, and I’m EXTREMELY curious how this bypasses it as a P2P system. Once you get beyond that problem, you have a lot more power than you realize. This system can be GREATLY expanded beyond just voice and IM chat.
I also have a very simple, easy to use, program to detect memory leaks:
I don’t have memory leaks in any of my code, because of that. Of course, it’s Linux only. I’m not much of a Windows coder.
Decentralized communication is a good idea and I would like to work on it if I can find the time. I guess you have my email, I’ll try to keep a tox instance running…
Comments are closed.