Page Comparison

...

To make this even more interesting I'm proposing to develop new In-Portal functionality (when possible) in a way of pluggable 3rd party library. Such libraries then can be reused even without In-Portal itself.

Separating In-Portal into Components

Right now there is a lot of code in In-Portal and it's modules. Codebase is separated into 2 groups:

...

In-Portal releases also take a lot time to happen (1-2 months and up) because of way how decision is made whatever to create release or not. Right now we delay release until by our subjective opinion (as a release managers) we think, that all possible bugs were fixed. If a new bug is found then release is delayed to make this bug fix fit into release for greater benefit. This concept on a large codebase results in long release cycle which is bad in either case.

What I'm proposing:

Step 1

1. create account on GitHub (git repository hosting, that is free for OpenSource projects) for Intechnic company
2. put all In-Portal code (in-portal, open-source modules, themes) there (on GitHub), where each module/theme would be a separated GitHub repository
3. existing aliases would be empty Git repositories with a composer.phar and composer.json file in them, that would tell what versions of which modules are required
4. project checkout is easy:
   1. clone a git repository
   2. run "php composer.phar install" command

...

• all In-Portal code accessible and searchable on GitHub, which is already good
• anyone having composer in their In-Portal installation could install a new module with 3 steps:
  1. put module name into his composer.json file
  2. run "php composer.phar update" to get new module
  3. install module from In-Portal's Admin Console

Step 2

1. move out loosely coupled reusable code into it's own GitHub repository (repository per-piece), e.g. ImageHelper goes to one repository and CurlHelper goes to other
2. each moved out piece will have it's own release cycle (can get released even before In-Portal does)
3. all component bug fixes are automatically applied to all projects using it (through usage of Composer "1.*" dependency)
4. as any code, hosted on GitHub we'll also be granted with usage of TravisCI (https://travis-ci.org/), which is Continuous Integration server, that would automatically run our tests (or whatever we need to run) on every commit.

...