edit | blame | history | raw

Contributing to Projectfork Translations

Please take a moment to review this document in order to make the contribution
process easy and effective for everyone involved.

Using the issue tracker

The issue tracker is the preferred channel for bug reports and submitting pull requests

Bug reports

A bug is a demonstrable problem that is caused by the code in the repository.
Good bug reports are extremely helpful - thank you!

Guidelines for bug reports:

  1. Check if an update is available — Purge Cache in Joomla => Extension
    Manager => Update => Purge Cache
    . After that, click Find Updates

  2. Use the GitHub issue search — check if the issue has already been
    reported and/or fixed. Search now for issues

  3. Isolate the problem — ideally create a live example. (Issues related to the Language Pack Installer only)

A good bug report shouldn't leave others needing to chase you up for more
information. Please try to be as detailed as possible in your report. What is
your environment? What steps will reproduce the issue? What browser(s), Projectfork,
Joomla and PHP version experience the problem? What would you expect to be the outcome?
All these details will help people to fix any potential bugs.

Example Language Files:

Title
Short and descriptive example bug report title (such as Missing or unupdated language string)

Comment:
Joomla Version: 3.2.1
Projectfork Version: 4.2.0
Language Pack Version: 4.2.0.3

  1. This is the first step (eg Go to the backend, click on repository and you will see at the top the untranslated string)
  2. This is the second step (_This string is also located in the frontend. Click here... there... etc....)
  3. Further steps, etc.

You can also share a screenshot with ease.
Just do a screenshot, drag & drop the file/screenshot in the github comment textarea
Or if you're screenshot is in the clipboard, just paste it in the comment textarea

Any other information you want to share that is relevant to the issue being
reported. This might include the lines of code that you have identified as
causing the bug, and potential solutions (and your opinions on their merits).

Example Language pack Installer:

Short and descriptive example bug report title

A summary of the issue and the browser/Joomla version/Projectfork version/PHP version in which it occurs. If
suitable, include the steps required to reproduce the bug.

  1. This is the first step
  2. This is the second step
  3. Further steps, etc.

Any other information you want to share that is relevant to the issue being
reported. This might include the lines of code that you have identified as
causing the bug, and potential solutions (and your opinions on their merits).

Feature requests

Feature requests are welcome. But take a moment to find out whether your idea fits with the scope and aims of Projectfork.

Language requests

Please note that all translations are created and maintained by community members.
That you request a new or an update of existing language does not mean it is automatically included in a future versions.
You can help to translate Projectfork

Pull requests

Please ask first before embarking on any significant pull request (e.g.
implementing new language, refactoring code), otherwise you risk spending a lot
of time working on something that the project's developers might not want to
merge into the project.

If you want to be a part of the Projectfork Translation Team, please have a look at
the wiki => Getting Involved.

IMPORTANT: By submitting a patch, you agree to allow the project owner to
license your work under the same license as that used by the project.