Skip to content

Commit 18a9800

Browse files
grandmotivatorgrandmotivator
committed
first commit
1 parent 18c46c7 commit 18a9800

38 files changed

+1361
-1
lines changed

‎.editorconfig

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
# https://editorconfig.org
2+
3+
# top-most EditorConfig file
4+
root = true
5+
6+
[*]
7+
charset = utf-8
8+
indent_style = space
9+
indent_size = 4
10+
end_of_line = lf
11+
trim_trailing_whitespace = true
12+
insert_final_newline = true
13+
14+
[*.md]
15+
indent_size = 2
16+
17+
[*.yml]
18+
indent_size = 2

‎.github/ISSUE_TEMPLATE/bug_report.md

Lines changed: 38 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,38 @@
1+
---
2+
name: Bug report
3+
about: Create a report to help us improve OpenSourceWebsite
4+
title: ''
5+
labels: bug
6+
assignees: ''
7+
8+
---
9+
10+
**Describe the bug**
11+
A clear and concise description of what the bug is.
12+
13+
**To Reproduce**
14+
Steps to reproduce the behavior:
15+
1. Go to '...'
16+
2. Click on '....'
17+
3. Scroll down to '....'
18+
4. See error
19+
20+
**Expected behavior**
21+
A clear and concise description of what you expected to happen.
22+
23+
**Screenshots**
24+
If applicable, add screenshots to help explain your problem.
25+
26+
**Desktop (please complete the following information):**
27+
- OS: [e.g. iOS]
28+
- Browser [e.g. chrome, safari]
29+
- Version [e.g. 22]
30+
31+
**Smartphone (please complete the following information):**
32+
- Device: [e.g. iPhone 6]
33+
- OS: [e.g. iOS 8.1]
34+
- Browser [e.g. stock browser, safari]
35+
- Version [e.g. 22]
36+
37+
**Additional context**
38+
Add any other context about the problem here.

‎.github/ISSUE_TEMPLATE/feature_request.md

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
---
2+
name: Feature request
3+
about: Suggest an idea for OpenSourceWebsite
4+
title: ''
5+
labels: enhancement
6+
assignees: ''
7+
8+
---
9+
10+
**Is your feature request related to a problem? Please describe.**
11+
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
12+
13+
**Describe the solution you'd like**
14+
A clear and concise description of what you want to happen.
15+
16+
**Describe alternatives you've considered**
17+
A clear and concise description of any alternative solutions or features you've considered.
18+
19+
**Additional context**
20+
Add any other context or screenshots about the feature request here.

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

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
---
2+
name: Question / Help
3+
about: Need help using OpenSourceWebsite?
4+
title: ''
5+
labels: help wanted
6+
assignees: ''
7+
8+
---
9+
10+
**Question**
11+
Describe in details what you are trying to achieve and where do you need guidance.

‎.github/PULL_REQUEST_TEMPLATE.md

Lines changed: 46 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,46 @@
1+
<!--
2+
3+
* 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.
4+
* Pull requests that do not solve an existing issue are essentially un-prioritized – don't expect these to be addressed quickly.
5+
* Try not to pollute your pull request with unintended changes–keep them simple and small.
6+
* All new code requires tests to ensure against regressions (if applicable).
7+
8+
-->
9+
10+
### Description of the Change
11+
12+
<!--
13+
14+
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.
15+
16+
-->
17+
18+
### Alternate Designs
19+
20+
<!-- Explain what other alternates were considered and why the proposed version was selected -->
21+
22+
### Benefits
23+
24+
<!-- What benefits will be realized by the code change? -->
25+
26+
### Possible Drawbacks
27+
28+
<!-- What are the possible side-effects or negative impacts of the code change? -->
29+
30+
### Verification Process
31+
32+
<!--
33+
34+
What process did you follow to verify that your change has the desired effects?
35+
36+
Describe the actions you performed (e.g., buttons you clicked, text you typed, commands you ran, etc.), and describe the results you observed.
37+
38+
Try to share which browsers your code has been tested in before submitting a pull request.
39+
40+
Include screenshots and animated GIFs in your pull request whenever possible.
41+
42+
-->
43+
44+
### Applicable Issues
45+
46+
<!-- Enter any applicable Issues here -->

‎.github/workflows/build-jekyll.yml

Lines changed: 35 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,35 @@
1+
name: Build and Deploy to Github Pages
2+
3+
# Controls when the workflow will run
4+
on:
5+
# Triggers the workflow on push or pull request events but only for the main branch
6+
push:
7+
branches: [ main ]
8+
pull_request:
9+
branches: [ main ]
10+
11+
# Allows you to run this workflow manually from the Actions tab
12+
workflow_dispatch:
13+
14+
jobs:
15+
build_and_deploy:
16+
runs-on: ubuntu-latest
17+
steps:
18+
- uses: actions/checkout@v3
19+
20+
# Use GitHub Actions' cache to cache dependencies on servers
21+
- uses: actions/cache@v3
22+
with:
23+
path: vendor/bundle
24+
key: ${{ runner.os }}-gems-${{ hashFiles('**/Gemfile.lock') }}
25+
restore-keys: |
26+
${{ runner.os }}-gems-
27+
28+
# Use GitHub Deploy Action to build and deploy to Github
29+
- uses: jeffreytse/[email protected]
30+
with:
31+
provider: 'github'
32+
token: ${{ secrets.GITHUB_TOKEN }} # It's your Personal Access Token(PAT)
33+
repository: '' # Default is current repository
34+
branch: 'gh-pages' # Default is gh-pages for github provider
35+
cname: 'opensourcewebsite.org' # Default is to not use a cname

‎CODE_OF_CONDUCT.md

Lines changed: 83 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,83 @@
1+
# Contributor Covenant Code of Conduct
2+
3+
## Our Pledge
4+
5+
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.
6+
7+
We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
8+
9+
## Our Standards
10+
11+
Examples of behavior that contributes to a positive environment for our community include:
12+
13+
* Demonstrating empathy and kindness toward other people
14+
* Being respectful of differing opinions, viewpoints, and experiences
15+
* Giving and gracefully accepting constructive feedback
16+
* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
17+
* Focusing on what is best not just for us as individuals, but for the overall community
18+
19+
Examples of unacceptable behavior include:
20+
21+
* The use of sexualized language or imagery, and sexual attention or advances of any kind
22+
* Trolling, insulting or derogatory comments, and personal or political attacks
23+
* Public or private harassment
24+
* Publishing others' private information, such as a physical or email address, without their explicit permission
25+
* Other conduct which could reasonably be considered inappropriate in a professional setting
26+
27+
## Enforcement Responsibilities
28+
29+
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.
30+
31+
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.
32+
33+
## Scope
34+
35+
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.
36+
37+
## Enforcement
38+
39+
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at [[email protected]](mailto:[email protected]). All complaints will be reviewed and investigated promptly and fairly.
40+
41+
All community leaders are obligated to respect the privacy and security of the reporter of any incident.
42+
43+
## Enforcement Guidelines
44+
45+
Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
46+
47+
### 1. Correction
48+
49+
**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
50+
51+
**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.
52+
53+
### 2. Warning
54+
55+
**Community Impact**: A violation through a single incident or series of actions.
56+
57+
**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.
58+
59+
### 3. Temporary Ban
60+
61+
**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
62+
63+
**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.
64+
65+
### 4. Permanent Ban
66+
67+
**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.
68+
69+
**Consequence**: A permanent ban from any sort of public interaction within the community.
70+
71+
## Attribution
72+
73+
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].
74+
75+
Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder][Mozilla CoC].
76+
77+
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].
78+
79+
[homepage]: https://www.contributor-covenant.org
80+
[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
81+
[Mozilla CoC]: https://github.com/mozilla/diversity
82+
[FAQ]: https://www.contributor-covenant.org/faq
83+
[translations]: https://www.contributor-covenant.org/translations

‎CONTRIBUTING.md

Lines changed: 49 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,49 @@
1+
# Contributing Guidelines
2+
3+
[Русская версия](CONTRIBUTING.ru.md)
4+
5+
First off, thanks for taking the time to contribute!
6+
7+
Your contributions increase your Rating in our community.
8+
9+
Please read through our [Installation Instructions](INSTALL.md).
10+
11+
## Getting Started
12+
13+
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.
14+
15+
- Make sure you have a [GitHub account](https://github.com/login).
16+
- Submit a GitHub issue for your issue if one does not already exist.
17+
- A issue is not necessary for trivial changes.
18+
- [Fork](https://help.github.com/en/articles/working-with-forks) the repository on GitHub.
19+
- [Configuring a remote for a fork](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork)
20+
- [Syncing a fork](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/syncing-a-fork)
21+
- `git fetch upstream`
22+
- `git checkout main`
23+
- `git merge upstream/main`
24+
- [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)
25+
- `git checkout main`
26+
- `git pull upstream main`
27+
- Commit the merge
28+
- `git push origin main`
29+
- 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.
30+
- Make your changes.
31+
- Follow the [Style Guides](#style-guides).
32+
- [Avoid platform-dependent code](https://flight-manual.atom.io/hacking-atom/sections/cross-platform-compatibility/).
33+
- Add tests if your changes contains new, testable behavior.
34+
- Make the tests pass.
35+
- Create a [pull request](https://help.github.com/en/articles/creating-a-pull-request-from-a-fork) to the repository.
36+
37+
### Tips and tricks for using the Git
38+
39+
- [GitHub Cheat Sheet](https://github.com/tiimgreen/github-cheat-sheet)
40+
- [git-tips](https://github.com/git-tips/tips)
41+
42+
### Key branches
43+
44+
- `main` is the latest, deployed version
45+
46+
## Additional information
47+
48+
- [Adding content to your GitHub Pages site using Jekyll](https://help.github.com/en/articles/adding-content-to-your-github-pages-site-using-jekyll)
49+
- [Jekyll - Static Site Generator / Tutorial](https://www.youtube.com/playlist?list=PLLAZ4kZ9dFpOPV5C5Ay0pHaa0RJFhcmcB)

‎CONTRIBUTING.ru.md

Lines changed: 49 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,49 @@
1+
# Руководство контрибьютора
2+
3+
[English version](CONTRIBUTING.md)
4+
5+
Прежде всего, спасибо, что нашли время внести вклад!
6+
7+
Ваш вклад увеличивает ваш Рейтинг в нашем сообществе.
8+
9+
Пожалуйста, прочитайте нашу [Инструкцию по установке](INSTALL.ru.md).
10+
11+
## Начнём
12+
13+
При внесении вклада в этот репозиторий, прежде чем вносить изменения, сначала обсудите изменения, которые вы хотите внести, при помощи issue, электронной почты или любым другим способом, с основной командой.
14+
15+
- Удостоверьтесь, что у вас есть [аккаунт GitHub](https://github.com/login).
16+
- Отправьте GitHub issue для вашей проблемы если таковой еще нет.
17+
- Issue не нужно для незначительных изменений.
18+
- Сделайте [fork](https://help.github.com/en/articles/working-with-forks) репозитория на GitHub.
19+
- [Настройка удалённого репозитория для fork](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork)
20+
- [Синхронизация fork](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/syncing-a-fork)
21+
- `git fetch upstream`
22+
- `git checkout master`
23+
- `git merge upstream/master`
24+
- [Слияние (merge) upstream-репозитория в ваш fork](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork)
25+
- `git checkout master`
26+
- `git pull upstream master`
27+
- Сделать commit слияния (merge)
28+
- `git push origin master`
29+
- При работе над issue, создайте новую ветку (branch) от `master` названную номером issue или другим именем. Назовите ветку `issue/<issue-number>` или `issue/<custom-name>`. Например, `issue/22` при работе над issue #22.
30+
- Внесите изменения.
31+
- Следуйте [Руководству по стилю](#style-guides).
32+
- [Избегайте платформозависимого кода](https://flight-manual.atom.io/hacking-atom/sections/cross-platform-compatibility/).
33+
- Добавьте тесты если ваши изменения содержат новые, тестируемые поведения.
34+
- Сделайте тесты проходимыми (успешными).
35+
- Создайте [pull request](https://help.github.com/en/articles/creating-a-pull-request-from-a-fork) к репозиторию.
36+
37+
### Советы и рекомендации по использованию Git
38+
39+
- [GitHub Cheat Sheet](https://github.com/tiimgreen/github-cheat-sheet)
40+
- [git-tips](https://github.com/git-tips/tips)
41+
42+
### Ключевые ветки
43+
44+
- `main` - последняя, развёртываемая версия.
45+
46+
## Дополнительная информация
47+
48+
- [Adding content to your GitHub Pages site using Jekyll](https://help.github.com/en/articles/adding-content-to-your-github-pages-site-using-jekyll)
49+
- [Jekyll - Static Site Generator / Tutorial](https://www.youtube.com/playlist?list=PLLAZ4kZ9dFpOPV5C5Ay0pHaa0RJFhcmcB)

‎DONATE.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
# Donation Details
2+
3+
[Русская версия](DONATE.ru.md)
4+
5+
First off, thanks for taking the opportunity to donate!
6+
7+
Your donations increase your Rating in our community.
8+
9+
Please send all donation offers to [[email protected]](mailto:[email protected]).

‎DONATE.ru.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
# Пожертвования
2+
3+
[English version](DONATE.md)
4+
5+
Прежде всего, спасибо, что нашли возможность сделать пожертвование!
6+
7+
Ваши пожертвования повышают ваш Рейтинг в нашем сообществе.
8+
9+
Пожалуйста, пришлите любые предложения с пожертвованиями на [[email protected]](mailto:[email protected]).

0 commit comments

Comments
 (0)