The old build script is probably no longer working, check it and fix it.

Implement support for multiple repositories. Script needs to support array of repositories to pull.

Create a tool to build JS files. Functionality required is:

1. config file
   a. Source files per output
   b. Output
   c. minimization settings
   d. concatenate settings
2. minimize (use existing tools)
3. concatenate (without repeating the dynamic initialization)

Create a language file manager which:

• Checks all *.en.lang.php files and creates the language file in the same directory for a different language
• Creates a single language file which can be edited and then exported into the original language files. This makes it easier to translate large amounts of text. Maybe use a csv file format

Reflections shouldn't be used by modules. Be careful modules also MUST NOT use the TestUtils.

The file MultiMap got adjusted and doesn't have an empty line at the end of the file. This hould have cause an error during the commit but went through without problems.

Following problems could be the reason for this:

1. Bad config
2. CodeSniffer is not running during commit
3. CodeSniffer runs but the error gets dumped and not evaluated
4. CodeSniffer returns error but the checking script for the error is invalid

How to solve?

Run the inspection manually and see if it returns an error. If yes the config is correct and only reason 2-4 have to be evaluated.

https://github.com/Orange-Management/phpOMS/blob/develop/Stdlib/Map/MultiMap.php

Make readme repository specific and improve the content similarly to the Orange-Management readme.

Framework & Resources

1. commit/pull request
2. minimize images [and push minimized version]
3. run linters [js, php, json, sh]
4. do unit test [framework + default resources + all OMS modules]
5. do static test
6. do code style test
7. create code coverage report [html + files]
8. create test report [html + pdf + other files]
9. create change log
10. create private update package including test reports and change log [pdf + other files]
11. test install of private update package
12. run unit tests on private update package [important to ensure the update process works]
13. make update package public
14. do a re-setup of the public test environment
15. release on website [pdf test report, code style, unit test, code coverage]
16. create a twitter post about the update
17. create a website post / small note

Module

1. commit/pull request
2. minimize images [and push minimized version]
3. run linters [js, php, json, sh]
4. do unit test [framework + default resources + default modules + this module/dependencies/providing]
5. do static test
6. do code style test
7. create code coverage report [html + files]
8. create test report
9. create change log
10. create private update package including test reports and change log [pdf + other files]
11. test install of private update package
12. run unit tests on private update package [important to ensure the update process works]

The next step requires a manual approval:
13. make update package public
14. do a re-setup of the public test environment
15. release on website / module site [pdf test report, code style, unit test, code coverage]
16. add/update module to the website shop and/or module section
17. create a twitter post about the update
18. create a website post / small note

Docs & Developer-Guide & Documentation

1. commit/pull request
2. minimize images [and push minimized version]
3. run linters [js, php, json, sh]

For software audits the unit tests should create an automated test report as pdf which can be used by audits for internal and external purposes.

All javascript inline calls should be prohibited e.g.

onload=alert(0)

1. $_GET etc... are only allowed in the request classes
2. file_get_contents and fopen mustn't load sensitive data thorugh potential user input
3. include etc mustn't load sensitive data thorugh potential user input