<commit_before>Company | Address | Phone | Mail |
:------:| :------: | :-----: | :-----: |
[![Creasoup Logo](http://www.creasoup.com/wp-content/uploads/2012/10/logo.png)](http://creasoup.com/) | Bağdat Cad. No:147, Dilman Apt. Daire:3, Feneryolu İstanbul | +90(216)4784200 | [<EMAIL>](mailto:<EMAIL>) |

# creasoup  main work flow 


Version| Build Status| Parent ID |
:------:|:-----:| :------:|
v.0.1 b |[![Build Status](https://travis-ci.org/kardesyazilim/proper.svg?branch=master)](https://travis-ci.org/kardesyazilim/proper)| 0 |


> creasoup workflow prepare

``` 
The “PHP Specification Requests” are based on a similar idea—they should, in particular, ensure that software components made by different manufacturers and frameworks are compatible to one another and can be used in combination. In contrast to “JSR”, the “PSR” procedure is relative new. To date only three specifications have been agreed upon.
• PSR-0: Defines the coherency between PHP namespaces and the organisation of PHP files in a file system in order to make the autoloading of classes, which should also be component- and manufacturer-independent, as simple as possible.
• PSR-1 / PSR-1 basic: A new common coding standard.
• PSR-2: An extension of the PSR-1 Coding Standard.

[!Michael Romer - Web Development with ZF2](https://leanpub.com/zendframework2-en)

```


>> Moudle List

Module | Module Description | Stability | Priority | * |
:------ | :-------: |  :------: | :-------: |:-----:|
Root | Core Block | Unstable | 0 | high |

>> Changelog

Version  | Commit | Priority |
:-------- | :--------: | :--------: | 
v.0.01 | add zend framework library 2 | root | 
v.0.02 | application folder desing | root |
v.0.03 | add autoloader , add bootstrap | root |
<commit_msg>fix document<commit_after>Company | Address | Phone | Mail |
:------:| :------: | :-----: | :-----: |
[![Creasoup Logo](http://www.creasoup.com/wp-content/uploads/2012/10/logo.png)](http://creasoup.com/) | Bağdat Cad. No:147, Dilman Apt. Daire:3, Feneryolu İstanbul | +90(216)4784200 | [<EMAIL>](mailto:<EMAIL>) |

# creasoup  main work flow 


Version| Build Status| Parent ID |
:------:|:-----:| :------:|
v.0.1 b |[![Build Status](https://travis-ci.org/kardesyazilim/proper.svg?branch=master)](https://travis-ci.org/kardesyazilim/proper)| 0 |


> creasoup workflow prepare

``` 
The “PHP Specification Requests” are based on a similar idea—they should, in particular, ensure that
software components made by different manufacturers and frameworks are compatible to one another and
can be used in combination. In contrast to “JSR”, the “PSR” procedure is relative new. To date only
three specifications have been agreed upon.
• PSR-0: Defines the coherency between PHP namespaces and the organisation of PHP files in a file 
system in order to make the autoloading of classes, which should also be component- and manufacturer-
independent, as simple as possible.
• PSR-1 / PSR-1 basic: A new common coding standard.
• PSR-2: An extension of the PSR-1 Coding Standard.

[!Michael Romer - Web Development with ZF2](https://leanpub.com/zendframework2-en)

```


>> Moudle List

Module | Module Description | Stability | Priority | * |
:------ | :-------: |  :------: | :-------: |:-----:|
Root | Core Block | Unstable | 0 | high |

>> Changelog

Version  | Commit | Priority |
:-------- | :--------: | :--------: | 
v.0.01 | add zend framework library 2 | root | 
v.0.02 | application folder desing | root |
v.0.03 | add autoloader , add bootstrap | root |

{'fraction_non_alphanumeric': 0.17772714326402733, 'fraction_numerical': 0.024494446026773, 'mean_word_length': 3.171021377672209, 'pattern_counts': {'":': 0, '<': 7, '<?xml version=': 0, '>': 17, 'https://': 6, 'lorem ipsum': 0, 'www.': 2, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 3, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1808389', 'n_tokens_mistral': 1207, 'n_tokens_neox': 1117, 'n_words': 366}