From 7f74686df1a75f7ebf08f5907a063be52d05917f Mon Sep 17 00:00:00 2001
From: Andriy Iun <andriy.yun@gmail.com>
Date: Thu, 28 Nov 2019 09:11:45 +0100
Subject: [PATCH 1/5] Initial commit

---
 README.md | 83 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 83 insertions(+)
 create mode 100644 README.md

diff --git a/README.md b/README.md
new file mode 100644
index 0000000..80425a6
--- /dev/null
+++ b/README.md
@@ -0,0 +1,83 @@
+# OS2Forms
+
+## Table of contents
+
+* [Description](#description)
+* [License](#license)
+* [Testing and CI](#testing-and-ci)
+* [Git guideline](#git-guideline)
+* [Code review](#code-review)
+* [Code of Conduct](#coc)
+* [Links](#links)
+
+<a name="description"></a>
+## Description
+
+__OS2Forms__ is a drupal based solution for creating advanced webform functionality for Danish Municipalities.
+
+<a name="license"></a>
+## License
+All OS2Forms projects are using [EUPL v1.2 License](https://opensource.org/licenses/EUPL-1.2).
+
+<a name="testing-and-ci"></a>
+## Testing and CI
+This project has continuous integration builds that are performing by [Travis CI](https://travis-ci.org).
+To improve code quality and integration possibilities there are using set of following tools:
+ * [PHP_CodeSniffer]() with [Drupal coding standards](https://www.drupal.org/docs/develop/standards/coding-standards) and best practices defined in [Coder module](https://www.drupal.org/project/coder).
+ * [ESLint](https://eslint.org/) with [Drupal ESLint rules set](https://www.drupal.org/node/1955232).
+ * [Stylelint](https://stylelint.io/) with rules set defined for Drupal core.
+ * [Twigcs](https://github.com/friendsoftwig/twigcs) with standard set of rules
+  for twig templates.
+ * [Drupl-check](https://github.com/mglaman/drupal-check) to check project
+ readiness to Drupal 9 via checking of deprecated code usage.
+ * @TODO [PHPUnit](https://phpunit.de/) test to check key contrib modules tests.
+
+For more details about travis-ci continuous integration builds
+see `.travis-ci.yml` file.
+
+NOTE: Project doesn't have its own PHPUnit test. This is a part of future
+development scope.
+
+<a name="git-guideline"></a>
+## Git guideline
+Since OS2Forms is Drupal module project, there is used drupal-friendly
+git branch/tag names.
+
+### Bracnhes
+* `8.x` - genral development branch.
+* `8.x-2.x` - development branch for version 2.x.
+
+There is no specific rules for feature branch names. However we recommend
+use [OS2Forms JIRA](https://os2web.atlassian.net/browse/OS2FORMS) or
+[github issue](https://github.com/OS2Forms/os2forms/issues) ticket number
+as prefix for your branch name.
+
+### Tags
+Release tags should be created from related branches. 
+Examples for tags created from `8.x-2.x`:
+* `8.x-2.0-alpha`, `8.x-2.0-alpha1`, `8.x-2.0-beta` - test release tags.
+* `8.x-2.0-rc1`, `8.x-2.0-rc2` - release candidate tags.
+* `8.x-2.0`, `8.x-2.1` - stable release tags.
+
+<a name="code-review"></a>
+## Code review
+New changes or bugfixes in existing codebase have to be added to repository
+through general [code review process](https://github.com/features/code-review/).
+To request a code review, use the following process:
+1. Add Github pull request from the feature/bugfix branch to 8.x or other related dev branch.
+2. Request code review from one of project contributor.
+3. Reviewer approves, requests changes or rejects pull request.
+4. Discuss/Add requested changes or merge approved pull request.
+
+NOTE: There are preconditions that have to be met before accepting a pull request:
+- All requested changes have to be done
+- All discussion have to be resolved
+- Pull request should have green Travis CI build status.
+
+<a name="coc"></a>
+## Code of Conduct
+See [Drupal community code of Conduct](https://www.drupal.org/dcoc)
+
+<a name="links"></a>
+## Links
+* [Drupal code standards](https://www.drupal.org/docs/develop/standards)

From 3c4093cc9a2493ca999bf4098d0e3d0c51de2fdb Mon Sep 17 00:00:00 2001
From: Andriy Iun <andriy.yun@gmail.com>
Date: Thu, 28 Nov 2019 10:47:54 +0100
Subject: [PATCH 2/5] Adjusted docs repo to OS2Web

---
 README.md | 13 +++++--------
 1 file changed, 5 insertions(+), 8 deletions(-)

diff --git a/README.md b/README.md
index 80425a6..9a5d775 100644
--- a/README.md
+++ b/README.md
@@ -1,4 +1,4 @@
-# OS2Forms
+# OS2Web
 
 ## Table of contents
 
@@ -13,11 +13,11 @@
 <a name="description"></a>
 ## Description
 
-__OS2Forms__ is a drupal based solution for creating advanced webform functionality for Danish Municipalities.
+__OS2Web__ is a drupal based solution for creating Drupal projects for Danish Municipalities.
 
 <a name="license"></a>
 ## License
-All OS2Forms projects are using [EUPL v1.2 License](https://opensource.org/licenses/EUPL-1.2).
+All OS2Web projects are using [EUPL v1.2 License](https://opensource.org/licenses/EUPL-1.2).
 
 <a name="testing-and-ci"></a>
 ## Testing and CI
@@ -30,7 +30,6 @@ To improve code quality and integration possibilities there are using set of fol
   for twig templates.
  * [Drupl-check](https://github.com/mglaman/drupal-check) to check project
  readiness to Drupal 9 via checking of deprecated code usage.
- * @TODO [PHPUnit](https://phpunit.de/) test to check key contrib modules tests.
 
 For more details about travis-ci continuous integration builds
 see `.travis-ci.yml` file.
@@ -40,7 +39,7 @@ development scope.
 
 <a name="git-guideline"></a>
 ## Git guideline
-Since OS2Forms is Drupal module project, there is used drupal-friendly
+Since OS2Web is Drupal module project, there is used drupal-friendly
 git branch/tag names.
 
 ### Bracnhes
@@ -48,9 +47,7 @@ git branch/tag names.
 * `8.x-2.x` - development branch for version 2.x.
 
 There is no specific rules for feature branch names. However we recommend
-use [OS2Forms JIRA](https://os2web.atlassian.net/browse/OS2FORMS) or
-[github issue](https://github.com/OS2Forms/os2forms/issues) ticket number
-as prefix for your branch name.
+use github issue ticket number as prefix for your branch name.
 
 ### Tags
 Release tags should be created from related branches. 

From 5077a208cbe87c671d0080737b752dcb82e7bc18 Mon Sep 17 00:00:00 2001
From: Andriy Iun <andriy.yun@gmail.com>
Date: Mon, 20 Apr 2020 09:57:13 +0200
Subject: [PATCH 3/5] Updated git guidelines

---
 README.md | 28 +++++++++++++++++++---------
 1 file changed, 19 insertions(+), 9 deletions(-)

diff --git a/README.md b/README.md
index 9a5d775..09509d3 100644
--- a/README.md
+++ b/README.md
@@ -39,22 +39,32 @@ development scope.
 
 <a name="git-guideline"></a>
 ## Git guideline
-Since OS2Web is Drupal module project, there is used drupal-friendly
-git branch/tag names.
+Project use default approach for branch naming.
 
 ### Bracnhes
-* `8.x` - genral development branch.
-* `8.x-2.x` - development branch for version 2.x.
+* `develop` - general development branch (Default).
+* `develop-2.x` - development branch for version 2.x. (if requires)
+* `master` - stable version of code.
 
 There is no specific rules for feature branch names. However we recommend
 use github issue ticket number as prefix for your branch name.
 
 ### Tags
-Release tags should be created from related branches. 
-Examples for tags created from `8.x-2.x`:
-* `8.x-2.0-alpha`, `8.x-2.0-alpha1`, `8.x-2.0-beta` - test release tags.
-* `8.x-2.0-rc1`, `8.x-2.0-rc2` - release candidate tags.
-* `8.x-2.0`, `8.x-2.1` - stable release tags.
+Release tags should be created from related branches. Tag name space should
+ follow [Semantic Versioning](https://semver.org/) rules. 
+Given a version number MAJOR.MINOR.PATCH, increment the:
+
+* MAJOR version when you make incompatible API changes,
+* MINOR version when you add functionality in a backwards compatible manner, and
+* PATCH version when you make backwards compatible bug fixes.
+
+#### Outdated approach
+Since OS2Forms projects are Drupal friendly, there was used drupal-friendly
+git branch/tag names like 8.x, 8.x-2.x. Please keep use it or ask about changes
+in case this names are not compatible with changes you have.
+
+For new repositories it was decided to switch back to github,
+composer way to for branch names.
 
 <a name="code-review"></a>
 ## Code review

From 9f1f1ba38d12ee286d11d1dfc2bef1e2ab803f47 Mon Sep 17 00:00:00 2001
From: Andriy Iun <andriy.yun@gmail.com>
Date: Mon, 4 May 2020 15:41:14 +0200
Subject: [PATCH 4/5] Fixed typo

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 09509d3..76bdf52 100644
--- a/README.md
+++ b/README.md
@@ -28,7 +28,7 @@ To improve code quality and integration possibilities there are using set of fol
  * [Stylelint](https://stylelint.io/) with rules set defined for Drupal core.
  * [Twigcs](https://github.com/friendsoftwig/twigcs) with standard set of rules
   for twig templates.
- * [Drupl-check](https://github.com/mglaman/drupal-check) to check project
+ * [Drupal-check](https://github.com/mglaman/drupal-check) to check project
  readiness to Drupal 9 via checking of deprecated code usage.
 
 For more details about travis-ci continuous integration builds

From 295baa2f444f6700d74ab49062b31038cd00a875 Mon Sep 17 00:00:00 2001
From: Andriyun <andriy.yun@gmail.com>
Date: Wed, 10 Nov 2021 13:26:02 +0100
Subject: [PATCH 5/5] Update README.md

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 76bdf52..bdc031a 100644
--- a/README.md
+++ b/README.md
@@ -79,7 +79,7 @@ To request a code review, use the following process:
 NOTE: There are preconditions that have to be met before accepting a pull request:
 - All requested changes have to be done
 - All discussion have to be resolved
-- Pull request should have green Travis CI build status.
+- Pull request should have green Github actions/Travis CI build status.
 
 <a name="coc"></a>
 ## Code of Conduct
