Explore the idea of creating an OPM (O2 Package Manager) to replace the O2.Platform.Scripts folder

[DinisCruz]

This should make the scripts much easier to consume, customise and deploy

[DinisCruz]

This is really they way to go, where each main area of the 'O2.Platform.Scripts' is converted into separate repos (which are cloned during setup, or on demand)

[DinisCruz]

moving on with this idea, I just created the organisation O2PM (for O2 Platform Package Manager) : https://github.com/o2pm

The idea is to move the tools that are currently at https://bintray.com/o2-platform/O2-Tools into here

Key concepts:

• code to be moved from https://github.com/o2platform/O2.Platform.Scripts
• each tool has its own repo with
  ** tests for that tool
  ** trigger of CI (appveyor) with tests execution and push into bintray
  ** documentation on how to use it
  ** issue tracking for probs with tool
• update OWASP pages to point to the tools that are mature
• need to create o2pm package which will load the other packages (this needs a command line and UI tool)
• this provides a cleaner separation between the FluentSharp modules and the rest of O2