Tech Project FAQs

Here are answers to some of the most frequently asked questions.

Where can I find the most urgent projects that need help?

Click the Projects tab and browse the list of projects. Find one that interests you.

How do I check out code?

We use Git as our code management system. Each project has its own Subversion repository. Before you can check out any code, however, you must have a Church Account username (see Join a project (volunteers) for information about how to get a Church Account username). Visit the project page for details on where to find the Subversion repository for the project.

How do I check in code?

This depends on the project. For some projects, you can request to have commit rights to Subversion. Other projects require that you submit code patches to be reviewed before they are applied. See the project's wiki page for specifics. If you have any questions, please contact us.

Is there a testing environment for the various projects?

Most projects have a test environment that you can use. Most projects will automatically look for Subversion commits and generate builds to the test environment. See the individual project pages for more information about their test environments.

Are there any coding or other community standards that must be followed?

Each project may have its own standards but overall, you can read the currently defined best practices.

I'm not a programmer. How can I contribute?

We always have need for UI designers, QA engineers and testers, technical writers, translators, security experts, project managers, etc. Contact the project manager for a project and ask how you can contribute.

What do I do if I have a great idea for a new application?

We love to hear your ideas or even see projects you have created. Please contact us with your idea or project.

Who do I contact for more information?

You can submit any questions with the ask a question form.