first commit

.editorconfig

@@ -0,0 +1,18 @@
+# https://editorconfig.org
+
+# top-most EditorConfig file
+root = true
+
+[*]
+charset = utf-8
+indent_style = space
+indent_size = 4
+end_of_line = lf
+trim_trailing_whitespace = true
+insert_final_newline = true
+
+[*.md]
+indent_size = 2
+
+[*.yml]
+indent_size = 2

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,38 @@
+---
+name: Bug report
+about: Create a report to help us improve OpenSourceWebsite
+title: ''
+labels: bug
+assignees: ''
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Desktop (please complete the following information):**
+ - OS: [e.g. iOS]
+ - Browser [e.g. chrome, safari]
+ - Version [e.g. 22]
+
+**Smartphone (please complete the following information):**
+ - Device: [e.g. iPhone 6]
+ - OS: [e.g. iOS 8.1]
+ - Browser [e.g. stock browser, safari]
+ - Version [e.g. 22]
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,20 @@
+---
+name: Feature request
+about: Suggest an idea for OpenSourceWebsite
+title: ''
+labels: enhancement
+assignees: ''
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

.github/ISSUE_TEMPLATE/question---help.md

@@ -0,0 +1,11 @@
+---
+name: Question / Help
+about: Need help using OpenSourceWebsite?
+title: ''
+labels: help wanted
+assignees: ''
+
+---
+
+**Question**
+Describe in details what you are trying to achieve and where do you need guidance.

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,46 @@
+<!--
+
+* Filling out the template is required. Any pull request that does not include enough information to be reviewed in a timely manner may be closed at the maintainers' discretion.
+* Pull requests that do not solve an existing issue are essentially un-prioritized – don't expect these to be addressed quickly.
+* Try not to pollute your pull request with unintended changes–keep them simple and small.
+* All new code requires tests to ensure against regressions (if applicable).
+
+-->
+
+### Description of the Change
+
+<!--
+
+We must be able to understand the design of your change from this description. If we can't get a good idea of what the code will be doing from the description here, the pull request may be closed at the maintainers' discretion. Keep in mind that the maintainer reviewing this PR may not be familiar with or have worked with the code here recently, so please walk us through the concepts.
+
+-->
+
+### Alternate Designs
+
+<!-- Explain what other alternates were considered and why the proposed version was selected -->
+
+### Benefits
+
+<!-- What benefits will be realized by the code change? -->
+
+### Possible Drawbacks
+
+<!-- What are the possible side-effects or negative impacts of the code change? -->
+
+### Verification Process
+
+<!--
+
+What process did you follow to verify that your change has the desired effects?
+
+Describe the actions you performed (e.g., buttons you clicked, text you typed, commands you ran, etc.), and describe the results you observed.
+
+Try to share which browsers your code has been tested in before submitting a pull request.
+
+Include screenshots and animated GIFs in your pull request whenever possible.
+
+-->
+
+### Applicable Issues
+
+<!-- Enter any applicable Issues here -->

.github/workflows/build-jekyll.yml

@@ -0,0 +1,35 @@
+name: Build and Deploy to Github Pages
+
+# Controls when the workflow will run
+on:
+  # Triggers the workflow on push or pull request events but only for the main branch
+  push:
+    branches: [ main ]
+  pull_request:
+    branches: [ main ]
+
+  # Allows you to run this workflow manually from the Actions tab
+  workflow_dispatch:
+
+jobs:
+  build_and_deploy:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v3
+
+      # Use GitHub Actions' cache to cache dependencies on servers
+      - uses: actions/cache@v3
+        with:
+          path: vendor/bundle
+          key: ${{ runner.os }}-gems-${{ hashFiles('**/Gemfile.lock') }}
+          restore-keys: |
+            ${{ runner.os }}-gems-
+
+      # Use GitHub Deploy Action to build and deploy to Github
+      - uses: jeffreytse/jekyll-deploy-action@v0.5.1
+        with:
+          provider: 'github'
+          token: ${{ secrets.GITHUB_TOKEN }} # It's your Personal Access Token(PAT)
+          repository: ''             # Default is current repository
+          branch: 'gh-pages'         # Default is gh-pages for github provider
+          cname: 'opensourcewebsite.org'     # Default is to not use a cname

CODE_OF_CONDUCT.md

@@ -0,0 +1,83 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at [hello@opensourcewebsite.org](mailto:hello@opensourcewebsite.org). All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.1, available at [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at [https://www.contributor-covenant.org/faq][FAQ]. Translations are available at [https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

CONTRIBUTING.md

@@ -0,0 +1,49 @@
+# Contributing Guidelines
+
+[Русская версия](CONTRIBUTING.ru.md)
+
+First off, thanks for taking the time to contribute!
+
+Your contributions increase your Rating in our community.
+
+Please read through our [Installation Instructions](INSTALL.md).
+
+## Getting Started
+
+When contributing to this repository, please first discuss the change you wish to make via issue, email, or any other method with the core team before making a change.
+
+- Make sure you have a [GitHub account](https://github.com/login).
+- Submit a GitHub issue for your issue if one does not already exist.
+  - A issue is not necessary for trivial changes.
+- [Fork](https://help.github.com/en/articles/working-with-forks) the repository on GitHub.
+    - [Configuring a remote for a fork](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork)
+    - [Syncing a fork](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/syncing-a-fork)
+      - `git fetch upstream`
+      - `git checkout main`
+      - `git merge upstream/main`
+    - [Merging an upstream repository into your fork](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork)
+      - `git checkout main`
+      - `git pull upstream main`
+      - Commit the merge
+      - `git push origin main`
+- When working on an issue, create a new branch from `main` named for issue number or custom name. Name the branch `issue/<issue-number>` or `issue/<custom-name>`. For example `issue/22` for fixing issue #22.
+- Make your changes.
+  - Follow the [Style Guides](#style-guides).
+  - [Avoid platform-dependent code](https://flight-manual.atom.io/hacking-atom/sections/cross-platform-compatibility/).
+  - Add tests if your changes contains new, testable behavior.
+  - Make the tests pass.
+- Create a [pull request](https://help.github.com/en/articles/creating-a-pull-request-from-a-fork) to the repository.
+
+### Tips and tricks for using the Git
+
+- [GitHub Cheat Sheet](https://github.com/tiimgreen/github-cheat-sheet)
+- [git-tips](https://github.com/git-tips/tips)
+
+### Key branches
+
+- `main` is the latest, deployed version
+
+## Additional information
+
+- [Adding content to your GitHub Pages site using Jekyll](https://help.github.com/en/articles/adding-content-to-your-github-pages-site-using-jekyll)
+- [Jekyll - Static Site Generator / Tutorial](https://www.youtube.com/playlist?list=PLLAZ4kZ9dFpOPV5C5Ay0pHaa0RJFhcmcB)

CONTRIBUTING.ru.md

@@ -0,0 +1,49 @@
+# Руководство контрибьютора
+
+[English version](CONTRIBUTING.md)
+
+Прежде всего, спасибо, что нашли время внести вклад!
+
+Ваш вклад увеличивает ваш Рейтинг в нашем сообществе.
+
+Пожалуйста, прочитайте нашу [Инструкцию по установке](INSTALL.ru.md).
+
+## Начнём
+
+При внесении вклада в этот репозиторий, прежде чем вносить изменения, сначала обсудите изменения, которые вы хотите внести, при помощи issue, электронной почты или любым другим способом, с основной командой.
+
+- Удостоверьтесь, что у вас есть [аккаунт GitHub](https://github.com/login).
+- Отправьте GitHub issue для вашей проблемы если таковой еще нет.
+  - Issue не нужно для незначительных изменений.
+- Сделайте [fork](https://help.github.com/en/articles/working-with-forks) репозитория на GitHub.
+    - [Настройка удалённого репозитория для fork](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork)
+    - [Синхронизация fork](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/syncing-a-fork)
+      - `git fetch upstream`
+      - `git checkout master`
+      - `git merge upstream/master`
+    - [Слияние (merge) upstream-репозитория в ваш fork](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork)
+      - `git checkout master`
+      - `git pull upstream master`
+      - Сделать commit слияния (merge)
+      - `git push origin master`
+- При работе над issue, создайте новую ветку (branch) от `master` названную номером issue или другим именем. Назовите ветку `issue/<issue-number>` или `issue/<custom-name>`. Например, `issue/22` при работе над issue #22.
+- Внесите изменения.
+  - Следуйте [Руководству по стилю](#style-guides).
+  - [Избегайте платформозависимого кода](https://flight-manual.atom.io/hacking-atom/sections/cross-platform-compatibility/).
+  -   Добавьте тесты если ваши изменения содержат новые, тестируемые поведения.
+  - Сделайте тесты проходимыми (успешными).
+- Создайте [pull request](https://help.github.com/en/articles/creating-a-pull-request-from-a-fork) к репозиторию.
+
+### Советы и рекомендации по использованию Git
+
+- [GitHub Cheat Sheet](https://github.com/tiimgreen/github-cheat-sheet)
+- [git-tips](https://github.com/git-tips/tips)
+
+### Ключевые ветки
+
+- `main` - последняя, развёртываемая версия.
+
+## Дополнительная информация
+
+- [Adding content to your GitHub Pages site using Jekyll](https://help.github.com/en/articles/adding-content-to-your-github-pages-site-using-jekyll)
+- [Jekyll - Static Site Generator / Tutorial](https://www.youtube.com/playlist?list=PLLAZ4kZ9dFpOPV5C5Ay0pHaa0RJFhcmcB)

DONATE.md

@@ -0,0 +1,9 @@
+# Donation Details
+
+[Русская версия](DONATE.ru.md)
+
+First off, thanks for taking the opportunity to donate!
+
+Your donations increase your Rating in our community.
+
+Please send all donation offers to [hello@opensourcewebsite.org](mailto:hello@opensourcewebsite.org).

DONATE.ru.md

@@ -0,0 +1,9 @@
+# Пожертвования
+
+[English version](DONATE.md)
+
+Прежде всего, спасибо, что нашли возможность сделать пожертвование!
+
+Ваши пожертвования повышают ваш Рейтинг в нашем сообществе.
+
+Пожалуйста, пришлите любые предложения с пожертвованиями на [hello@opensourcewebsite.org](mailto:hello@opensourcewebsite.org).