Get Involved

From code, design and translation to spreading the world and donation, here are a number of ways to contribute to FreedomBox.

1. Quick Links

Progress calls
TODO page
Donation page

2. Welcome to newcomers

As a new contributor, you are more than welcome to introduce yourself to others on the FreedomBox discussion forum, mailing list or on the #freedombox IRC channel. In addition to make useful contacts, you can start reporting bugs and translate (see below) the wiki website and the FreedomBox web interface.

3. Development priorities

Upcoming priorities are discussed on an regular basis. You find the progress of the FreedomBox Service (Plinth) with its priorities here: issues board and milestones.

Please check next progress calls to keep yourself on track and meet members of the release team. A TODO page aggregates the complete list of the items to work on for FreedomBox.

4. Contributions needed

4.1. Add an Application

If you are a developer and wish to see an application available in FreedomBox, you can contribute by adding the application to FreedomBox. See the FreedomBox Developer Manual.

4.2. Bugs

List of bugs, feature requests and improvements are tracked on the FreedomBox issue tracker. In addition to that, see list of bugs to help out the Debian package we depend on. Also see the FreedomBox packaging team's dashboard for status of various packages that we use.

4.3. Code

If you are a developer, you can contribute code to one of the sub-projects of FreedomBox. Step-by-step process of contributing code to FreedomBox is available.

• FreedomBox Service (Plinth): a web interface to administer the functions of FreedomBox.

• Freedom Maker: a script to build FreedomBox disk images for use on various hardware devices or virtual machines.

You can pickup a task from one of the TODO lists. The individual page project pages contain information availabily of the code, how to build and TODO lists.

4.4. Design

4.4.1. User Experience Design

If you are a user experience designer, you can help FreedomBox with the following items:

• UI experience for the FreedomBox Service (Plinth) web interface

• Web design for freedombox.org, freedomboxfoundation.org and the wiki pages

• Logo and branding (we currently have an identity manual and logos)

• Possible designs for custom FreedomBox cases on single board computers

• User experience design

4.4.2. Technical Design

FreedomBox needs your technical expertise to devise implementation plans for upcoming features. You can contribute to the discussion on various technical design and implementation aspects of FreedomBox. See FreedomBox discussion forum's development category.

4.5. Donate

The FreedomBox Foundation is a 501(c)(3) federal nonprofit corporation with recognition from the IRS. FreedomBox project is run by volunteers. You can help the project financially by donating via PayPal, Bitcoin or by mailing a check. Please see the donation page for details on how to donate.

4.6. Document: User Manual, Website and Wiki

FreedomBox needs better documentation for users and contributors. FreedomBox manual is prepared by aggregating various pages on the wiki and exporting to various formats. The manual is then used in FreedomBox Service (Plinth) and elsewhere.

If you wish to contribute to the FreedomBox wiki (and consequently the FreedomBox manual), you can create a wiki account and start editing.

For contributing to the website please start a discussion on the FreedomBox discussion forum's development category.

4.7. Quality Assurance

• FreedomBox already runs on many platforms and it is not possible for developers to test all possible platforms. If you have one of the supported hardware you can help with testing FreedomBox on the platform.

• When an application is made available on FreedomBox, not all of its functionality is tested in the real world by developer doing the work. Deploying the application and testing it will help ensure high quality applications in FreedomBox.

See the quality assurance page for a basic list of test cases to check for and information on reporting bugs.

4.8. Localization

All text visible to users of FreedomBox needs to be localized to various languages. This translation work includes:

• Web Interface for FreedomBox

• FreedomBox documentation

• FreedomBox wiki, website and foundation website.

• Django web framework that FreedomBox uses.

• Individual applications that FreedomBox exposes to users.

You can contribute to the localization effort using the web-based tool at Weblate or directly to the source tree via Salsa.

If you wish to see FreedomBox available for one of your languages, please start a discussion on the FreedomBox discussion forum's development category to work with others translating for that language.

For more information, please visit the FreedomBox translators page.

4.9. Spread the Word

Speak to your family, friends, local community or at global conferences about the importance of FreedomBox. To be a successful project we need many more participants, be it users or contributors. Write about your efforts at the talks page and on the wiki.

CategoryFreedomBox