Do you want to help us improve Friendica? Here we have compiled some hints on how to get started and some tasks to help you choose. A project like Friendica is the sum of many different contributions. Very different skills are required to make good software. Some of them involve coding, others do not. We are looking for helpers in all areas, whether you write text or code, whether you spread the word to convince people or design new icons. Whether you feel like an expert or like a newbie - join us with your ideas!
The discussion of Friendica development takes place in the following Friendica forums:
Remember the questions you had when you first tried Friendica? A good place to start can be to help new people find their way around Friendica in the general support forum. Welcome them, answer their questions, point them to documentation or ping other helpers directly if you can't help but think you know who can.
The documentation contains help on how to translate Friendica at Transifex where the UI is translated. If you don't want to translate the UI, or it is already done to your satisfaction, you might want to work on the translation of the /help files?
Are you good at designing things? If you have seen Friendica you probably have ideas to improve it, haven't you?
For the sake of consistency between contribution and general code readability, Friendica follows the widespread PSR-2 coding standards to the exception of a few rules.
Here's a few primers if you are new to Friendica or to the PSR-2 coding standards:
* Indentation is tabs, period (not PSR-2).
* By default, strings are enclosed in single quotes, but feel free to use double quotes if it makes more sense (SQL queries, adding tabs and line feeds).
* Operators are wrapped by spaces, e.g.
$var === true,
$var = 1 + 2 and
'string' . $concat . 'enation'
* Braces are mandatory in conditions
* No closing PHP tag
* No trailing spaces
Don't worry, you don't have to know by heart the PSR-2 coding standards to start contributing to Friendica. There are a few tools you can use to check or fix your files before you commit.
This tool checks your files against a variety of coding standards, including PSR-2, and ouputs a report of all the standard violations.
You can simply install it through PEAR:
pear install PHP_CodeSniffer
Once it is installed and available in your PATH, here's the command to run before committing your work:
$> phpcs --standard=PSR2 <file or directory>
The output is a list of all the coding standards violations that you should fix before committing your work.
phpcs integrates with a few IDEs (Eclipse, Netbeans, PHPStorm...) so that you don't have to fiddle with the command line.
If you're getting a massive list of standards violations when running
phpcs, it can be annoying to fix all the violations by hand.
Thankfully, PHP Code Sniffer is shipped with an automatic code fixer that can take care of the tedious task for you.
Here's the command to automatically fix the files you created/modified:
$> phpcbf --standard=PSR2 <file or directory>
If the command-line tools
patch are unavailabe for you,
phpcbf can use slightly slower PHP equivalents by using the
If you are interested in having the documentation of the Friendica code outside of the code files, you can use Doxygen to generate it.
The configuration file for Doxygen is located in the
util directory of the project sources.
$> doxygen util/Doxyfile
to generate the files which will be located in the
doc/html subdirectory in the Friendica directory.
You can browse these files with any browser.
If you find missing documentation, don't hesitate to contact us and write it down to enhance the code documentation.
Have a look at our issue tracker on github!
The thing many people want most is a better interface, preferably a responsive Friendica theme. This is a piece of work! If you want to get involved here:
As Friendica is using a Twitter/GNU Social compatible API any of the clients for those platforms should work with Friendica as well. Furthermore there are several client projects, especially for use with Friendica. If you are interested in improving those clients, please contact the developers of the clients directly.