Localizations - New way to contribute

[lubos]

@sharpdrivetek

while it is okay to enable tabs so that some localization features can be added, it is not okay to leave the tabs enabled after adding the features. a new user will be provided with a lot of tabs and features irrelevent to their business.

This is not a problem. Keep those tabs enabled. Manager will cherry-pick from localizations only relevant data. For example, feel free to create test transactions and other test data to demonstrate how custom fields are used or that report transformations and extensions are working.

@sharpdrivetek

i personally preferred the old method to contribute where users had the opportunity to discuss and review the changes being proposed.

I found out it won’t work. Too high barrier of entry. A lot of users are keen to work on this but understanding Git workflow and JSON diffs is too much to ask. Also, it’s important we all work in real-time. If you work on report transformation and something is not right, I can have look into the same database you are working with. Much easier to reproduce issues as we should see the same thing.

@Patch

I do suspect it would be difficult to make a localisation for the USA as Manager’s tax code architecture does not sensibly accommodate the many tax authorities in USA tax system.

Eventually, I will branch United States per state. So it will be possible to create United States (California), United States (Oregon) etc.

@sharpdrivetek

anyway the point was to have the developer involved in implementing the localizations where he had the authority to decide whether a proposed change should be implemented and suggest changes. the old method had this and I am not sure about this new method.

This new method has it too. There is approval model baked in. I will review daily all the changes and either accept or decline.

@Patch

User A helps user B. In turn user B repays by helping a different user in the future.

It’s this but also helping themselves. Fixing / improving report transformation in localization will benefit all users who have the given country set under Business Details. For example, if there is an improvement to Single Touch Payroll Worksheet in Australia, the improvement will be rolled out to everyone with Australia set as their country in their business.