Skip to content
This repository was archived by the owner on Apr 8, 2023. It is now read-only.

Commit 94a46fb

Browse files
authored
Merge pull request #97 from mrmlnc/OPENSOURCE-8_dev_friendly
OPENSOURCE-8: Add community profile
2 parents 9a53e6d + ed9aea2 commit 94a46fb

File tree

4 files changed

+159
-0
lines changed

4 files changed

+159
-0
lines changed

.github/ISSUE_TEMPLATE.md

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
### Environment
2+
3+
* VSCode Version: ...
4+
* OS Version: ...
5+
6+
### Actual behavior
7+
8+
...
9+
10+
### Expected behavior
11+
12+
...
13+
14+
### Steps to reproduce
15+
16+
...
17+
18+
### Config
19+
20+
```js
21+
// Paste your configuration here.
22+
```

.github/PULL_REQUEST_TEMPLATE.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
### What is the purpose of this pull request?
2+
3+
...
4+
5+
### What changes did you make? (Give an overview)
6+
7+
...

CODE-OF-CONDUCT.md

Lines changed: 73 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,73 @@
1+
# Contributor Covenant Code of Conduct
2+
3+
## Our Pledge
4+
5+
In the interest of fostering an open and welcoming environment, we as
6+
contributors and maintainers pledge to making participation in our project and
7+
our community a harassment-free experience for everyone, regardless of age, body
8+
size, disability, ethnicity, gender identity and expression, level of experience,
9+
nationality, personal appearance, race, religion, or sexual identity and
10+
orientation.
11+
12+
## Our Standards
13+
14+
Examples of behavior that contributes to creating a positive environment
15+
include:
16+
17+
* Using welcoming and inclusive language
18+
* Being respectful of differing viewpoints and experiences
19+
* Gracefully accepting constructive criticism
20+
* Focusing on what is best for the community
21+
* Showing empathy towards other community members
22+
23+
Examples of unacceptable behavior by participants include:
24+
25+
* The use of sexualized language or imagery and unwelcome sexual attention or
26+
advances
27+
* Trolling, insulting/derogatory comments, and personal or political attacks
28+
* Public or private harassment
29+
* Publishing others' private information, such as a physical or electronic
30+
address, without explicit permission
31+
* Other conduct which could reasonably be considered inappropriate in a
32+
professional setting
33+
34+
## Our Responsibilities
35+
36+
Project maintainers are responsible for clarifying the standards of acceptable
37+
behavior and are expected to take appropriate and fair corrective action in
38+
response to any instances of unacceptable behavior.
39+
40+
Project maintainers have the right and responsibility to remove, edit, or
41+
reject comments, commits, code, wiki edits, issues, and other contributions
42+
that are not aligned to this Code of Conduct, or to ban temporarily or
43+
permanently any contributor for other behaviors that they deem inappropriate,
44+
threatening, offensive, or harmful.
45+
46+
## Scope
47+
48+
This Code of Conduct applies both within project spaces and in public spaces
49+
when an individual is representing the project or its community. Examples of
50+
representing a project or community include using an official project e-mail
51+
address, posting via an official social media account, or acting as an appointed
52+
representative at an online or offline event. Representation of a project may be
53+
further defined and clarified by project maintainers.
54+
55+
## Enforcement
56+
57+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
58+
reported by contacting the project team at dmalinochkin@rambler.ru. All
59+
complaints will be reviewed and investigated and will result in a response that
60+
is deemed necessary and appropriate to the circumstances. The project team is
61+
obligated to maintain confidentiality with regard to the reporter of an incident.
62+
Further details of specific enforcement policies may be posted separately.
63+
64+
Project maintainers who do not follow or enforce the Code of Conduct in good
65+
faith may face temporary or permanent repercussions as determined by other
66+
members of the project's leadership.
67+
68+
## Attribution
69+
70+
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
71+
available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
72+
73+
[homepage]: https://www.contributor-covenant.org

CONTRIBUTING.md

Lines changed: 57 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,57 @@
1+
# Contributing to my package
2+
3+
Welcome, and thank you for your interest in contributing to **vscode-csscomb**!
4+
5+
Please note that this project is released with a [Contributor Code of Conduct](CODE-OF-CONDUCT.md). By participating in this project you agree to abide by its terms.
6+
7+
## Contribution Guidelines
8+
9+
There are a couple of ways you can contribute to this repo:
10+
11+
* **Ideas, feature requests and bugs**: We are open to all ideas and we want to get rid of bugs! Use the [Issues section](https://github.com/mrmlnc/vscode-csscomb/issues) to either report a new issue, provide your ideas or contribute to existing threads.
12+
* **Documentation**: Found a typo or strangely worded sentences? Submit a PR!
13+
* **Code**: Contribute bug fixes, features or design changes.
14+
15+
### Creating an Issue
16+
17+
Before you create a new Issue:
18+
19+
* Check the [Issues](https://github.com/mrmlnc/vscode-csscomb/issues) on Github to ensure one doesn't already exist.
20+
* Clearly describe the issue, including the steps to reproduce the issue.
21+
22+
### Making Changes
23+
24+
#### Getting Started
25+
26+
* Install [Node.js](https://nodejs.org/en/).
27+
* Fork the project and clone the fork repo. ([how to create fork?](https://help.github.com/articles/fork-a-repo/#fork-an-example-repository)).
28+
* Create a topic branch from the master branch.
29+
* Run `yarn` or `npm install` to install the application dependencies.
30+
31+
#### Setup
32+
33+
1. Start watching:
34+
35+
```
36+
$ npm run watch
37+
```
38+
39+
2. Make changes:
40+
41+
```
42+
$ code .
43+
```
44+
45+
3. Run tests:
46+
47+
```
48+
$ npm t
49+
```
50+
51+
4. Test your version of the extension:
52+
53+
Press <kbd>F5</kbd> in the editor and then test extension commands and functions.
54+
55+
#### Commit
56+
57+
Keep git commit messages clear and appropriate. You can use [Angular guide](https://github.com/angular/angular.js/blob/master/DEVELOPERS.md#-git-commit-guidelines).

0 commit comments

Comments
 (0)