The Tox website doesn’t use anything fancy, we try to keep it as simple as possible: it’s a static page website which uses Jinja2 template engine and Python for page generation. The person currently maintaining the website is more of a C++ developer than a web developer, so while they keep the information on the website up-to-date, doing more involved changes, like changing the page layout, is something that is hard for them. We are in need of a website developer/designer or anyone familiar with HTML, CSS, Bootstrap, Jinja 2 templates and Python.
#Download qtox code
Reviewing the code that is considered for merging into the codebase is also a great way to help. Also, you don’t have to write code to contribute.
#Download qtox software
You can help with an existing software project or start a new project of your own that would be useful to Tox. 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. We could use help of people familiar with any of C, C++, Go, Haskell, Java, Python, Rust, Scala, Swift and other. 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.Īnyone with programming background is welcome, as we have quite diverse codebases.
#Download qtox how to
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. 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.
#Download qtox download
You can get a client to test from the Download page of our website. 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. Also, even if the client you test is non-nightly, your testing is still useful. If this is the case for a client you want to test, simply asking developers for nightlies should resolve this issue. Some clients don’t have nightly builds available for testing, or they do but they are not well maintained and might be broken. Testing nightly builds can help to find bugs and get them fixed before a release is made. 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. You can help by testing nightly builds of clients and translating clients to different languages. You don’t have to know programming in order to help. Here is a non-exhaustive list of things you could help with, just to give an idea. 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. Many Tox developers and community members are connected to the chat 24/7 but get on it only in their free time. 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. 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. This blog post is for those who want to contribute but don’t know where to start.
It’s common knowledge that any open source project wouldn’t mind having more contributors and Tox is not an exception.
0 kommentar(er)
