Contribute

Customizer always depends on your help and support.

Contents

1. Support and helping users
2. Provide useful feedbacks
3. Update resources and documentation
4. Translation and localization (L10n)
5. Reporting bugs and push fixes
6. Join the development team
7. Anything else

1. Support and helping users

If you have been using Customizer or remastering Ubuntu-based ISO images, that's great! The easiest way for you to help is, to explain other users how you did that.

This project lacking place for active discussion. We used to have a forum, twice, but went hiatus forever. Any suggestion?

Should there be any discussion on Customizer elsewhere, we'd be happy to quote a link in the archive.

2. Provide useful feedbacks

For users whom already using Customizer to do remastering, your feedback is important to let others know what worked and didn't work.

To submit your feedback, use the feedback form. Users can also view the feedback result from the link.

3. Update resources and documentation

This project heavily relies on GitHub Wiki as main resource. While the Wiki may be relevant for now, eventually some resources will get outdated.

That is when this project needs someone to update the resources and documentation. The following are good places to start:

• Tutorials page: Write a short tutorial, explaining how to use Customizer, or create a screencast to demonstrate using Customizer

• Manuals page: Prepare a user guide for Customizer

4. Translation and localization (L10n)

Customizer has been made available in these languages:

• English (default)
• Bulgarian
• Korean

For users fluent with English and other languages, you can translate Customizer into your native language. You can submit your translation by either way:

• Include the link to translation files and submit as new issue
• Create fork of the repository
• Send the translation files itself to [email protected]

5. Reporting bugs and push fixes

At times, you may enocunter bugs while using Customizer. If you do, then follow the issue submission guideline before creating an issue to report.

6. Join the development team

The development has moved on to 4.1 release, favoring Python over Gambas. Coding has not much changed since then, other than bug fixes.

The developer notes page is a good place to get started.

7. Anything else

Send your enquiry by creating new issue. Else, contact the development team members in the list.