Skip to content

Commit d3add20

Browse files
ololxololx
committedApr 2, 2020
init(init first release)
·
1.0.0
1 parent 4163e87 commit d3add20

16 files changed

+1329
-1
lines changed
 

‎.gitattributes

+2
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,2 @@
1+
*.workflow linguist-vendored=true
2+
*.workflow linguist-language=Automator

‎.gitignore

+6
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
# all hidden files
2+
.*
3+
4+
#exclude
5+
!.gitignore
6+
!.gitattributes

‎BADGES_GUIDE.md

+40
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,40 @@
1+
# Badges Guide
2+
3+
This section presents a some badges reference guide from the [readme](README.md) file, which are project activity info and are not widely distributed or are attached special for this project.
4+
5+
## Status
6+
7+
Status is an informational badge which shows the project development activity. This information can be represented by the following statuses:
8+
9+
- `active` - this means that the project is under active development.
10+
- `frozen` - this means that the project is still under development, but all work on it was temporarily suspended to clarify and formalize new ideas.
11+
- `completed` - this means that the project implements the intended functionality and the development is completed. Development can be resumed if new ideas for an improvements or features appear.
12+
13+
If you want to help in development, you have any feature suggestions for the project or if you faced a problem or bug, please visit the [contributing](CONTRIBUTING.md) section.
14+
15+
## Version
16+
17+
This information represents the actual version of the project. For the versioning is used [SemVer](http://semver.org/).
18+
19+
## OSS Lifecycle
20+
21+
OSS Lifecycle is an initiative started by Netflix to classify open-source projects into lifecycles and clearly identify which projects are active and which ones are retired. To enable this badge, simply create an `OSSMETADATA` tagging file at the root of your GitHub repository containing a single line similar to the following: `osslifecycle=active`. Other suggested values are `osslifecycle=maintenance` and `osslifecycle=archived`. A working example can be viewed on the [OSS Tracker repository](https://github.com/Netflix/osstracker).
22+
23+
## Maintenance
24+
25+
This is an informational badge which shows the maintenance process state of the project. The following statuses are applied:
26+
27+
- `yes` - this means that the project is under maintenance.
28+
- `no (of {expiration date})` - this means that the project is no longer maintained.
29+
30+
In both cases, the project can still be used.
31+
32+
Please visit the [contributing](CONTRIBUTING.md) page if you faced with some issues with the project.
33+
34+
## Release Date
35+
36+
This is an information about the project release date which would be stable and could be used. In this case, it is possible to indicate the date of the first release, last release, release of a specific version.
37+
38+
## Commit Date
39+
40+
This is an information about the project commit date, which would show the last commit date in the project repository.

‎CHANGELOG.md

+13
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
# Changelog
2+
3+
All notable changes to this project will be documented in this file.
4+
5+
The format is based on [Keep a Changelog](http://keepachangelog.com/) and this project adheres to [Semantic Versioning](http://semver.org/).
6+
7+
## [1.0.0] - 2020-03-01]
8+
9+
### Added
10+
- The mac Automator workflow which allows to:
11+
- automate the symbolic links creation;
12+
- create symbolic links for the selected files or folders;
13+
- save symbolic links to the selected directory.

‎CODE_OF_CONDUCT.md

+128
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,128 @@
1+
# Contributor Covenant Code of Conduct
2+
3+
## Our Pledge
4+
5+
We as members, contributors, and leaders pledge to make participation in our
6+
community a harassment-free experience for everyone, regardless of age, body
7+
size, visible or invisible disability, ethnicity, sex characteristics, gender
8+
identity and expression, level of experience, education, socio-economic status,
9+
nationality, personal appearance, race, religion, or sexual identity
10+
and orientation.
11+
12+
We pledge to act and interact in ways that contribute to an open, welcoming,
13+
diverse, inclusive, and healthy community.
14+
15+
## Our Standards
16+
17+
Examples of behavior that contributes to a positive environment for our
18+
community include:
19+
20+
* Demonstrating empathy and kindness toward other people
21+
* Being respectful of differing opinions, viewpoints, and experiences
22+
* Giving and gracefully accepting constructive feedback
23+
* Accepting responsibility and apologizing to those affected by our mistakes,
24+
and learning from the experience
25+
* Focusing on what is best not just for us as individuals, but for the
26+
overall community
27+
28+
Examples of unacceptable behavior include:
29+
30+
* The use of sexualized language or imagery, and sexual attention or
31+
advances of any kind
32+
* Trolling, insulting or derogatory comments, and personal or political attacks
33+
* Public or private harassment
34+
* Publishing others' private information, such as a physical or email
35+
address, without their explicit permission
36+
* Other conduct which could reasonably be considered inappropriate in a
37+
professional setting
38+
39+
## Enforcement Responsibilities
40+
41+
Community leaders are responsible for clarifying and enforcing our standards of
42+
acceptable behavior and will take appropriate and fair corrective action in
43+
response to any behavior that they deem inappropriate, threatening, offensive,
44+
or harmful.
45+
46+
Community leaders have the right and responsibility to remove, edit, or reject
47+
comments, commits, code, wiki edits, issues, and other contributions that are
48+
not aligned to this Code of Conduct, and will communicate reasons for moderation
49+
decisions when appropriate.
50+
51+
## Scope
52+
53+
This Code of Conduct applies within all community spaces, and also applies when
54+
an individual is officially representing the community in public spaces.
55+
Examples of representing our community include using an official e-mail address,
56+
posting via an official social media account, or acting as an appointed
57+
representative at an online or offline event.
58+
59+
## Enforcement
60+
61+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
62+
reported to the community leaders responsible for enforcement at
63+
ololx@icloud.com.
64+
All complaints will be reviewed and investigated promptly and fairly.
65+
66+
All community leaders are obligated to respect the privacy and security of the
67+
reporter of any incident.
68+
69+
## Enforcement Guidelines
70+
71+
Community leaders will follow these Community Impact Guidelines in determining
72+
the consequences for any action they deem in violation of this Code of Conduct:
73+
74+
### 1. Correction
75+
76+
**Community Impact**: Use of inappropriate language or other behavior deemed
77+
unprofessional or unwelcome in the community.
78+
79+
**Consequence**: A private, written warning from community leaders, providing
80+
clarity around the nature of the violation and an explanation of why the
81+
behavior was inappropriate. A public apology may be requested.
82+
83+
### 2. Warning
84+
85+
**Community Impact**: A violation through a single incident or series
86+
of actions.
87+
88+
**Consequence**: A warning with consequences for continued behavior. No
89+
interaction with the people involved, including unsolicited interaction with
90+
those enforcing the Code of Conduct, for a specified period of time. This
91+
includes avoiding interactions in community spaces as well as external channels
92+
like social media. Violating these terms may lead to a temporary or
93+
permanent ban.
94+
95+
### 3. Temporary Ban
96+
97+
**Community Impact**: A serious violation of community standards, including
98+
sustained inappropriate behavior.
99+
100+
**Consequence**: A temporary ban from any sort of interaction or public
101+
communication with the community for a specified period of time. No public or
102+
private interaction with the people involved, including unsolicited interaction
103+
with those enforcing the Code of Conduct, is allowed during this period.
104+
Violating these terms may lead to a permanent ban.
105+
106+
### 4. Permanent Ban
107+
108+
**Community Impact**: Demonstrating a pattern of violation of community
109+
standards, including sustained inappropriate behavior, harassment of an
110+
individual, or aggression toward or disparagement of classes of individuals.
111+
112+
**Consequence**: A permanent ban from any sort of public interaction within
113+
the community.
114+
115+
## Attribution
116+
117+
This Code of Conduct is adapted from the [Contributor Covenant][homepage],
118+
version 2.0, available at
119+
https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
120+
121+
Community Impact Guidelines were inspired by [Mozilla's code of conduct
122+
enforcement ladder](https://github.com/mozilla/diversity).
123+
124+
[homepage]: https://www.contributor-covenant.org
125+
126+
For answers to common questions about this code of conduct, see the FAQ at
127+
https://www.contributor-covenant.org/faq. Translations are available at
128+
https://www.contributor-covenant.org/translations

‎CONTRIBUTING.md

+116
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,116 @@
1+
# Contributing
2+
3+
🎉 If you want to contribute this project thanks for taking the time on it and wish you to have fun.
4+
5+
When contributing to this repository, please first discuss the change you wish to make via issue,
6+
email, or any other method with the owners of this repository before making a change.
7+
8+
Please note this repository have a [code of conduct](CODE_OF_CONDUCT.md), please follow it in all your interactions with the project.
9+
10+
## Contributing Factors
11+
12+
### 🐞 Did you find a bug?
13+
14+
- Ensure the bug was not already reported by searching on GitHub under **Issues**.
15+
- If you're unable to find an open issue addressing the problem, open a **new one**. Be sure to include a title and clear description, as much relevant information as possible, and a code sample or an executable test case demonstrating the expected behavior that is not occurring.
16+
- Provide test images, which can be used for reproducing.
17+
18+
#### Bug Report Template
19+
20+
For the creating **Issues**, please see this template.
21+
22+
----
23+
24+
| name | about | title | labels | assignees |
25+
| :--------: | :--------------------------------: | :---: | :----: | --------: |
26+
| Bug report | Create a report to help us improve | | | |
27+
28+
**Describe the bug** A clear and concise description of what the bug is.
29+
30+
**To Reproduce** Steps to reproduce the behavior:
31+
32+
1. Go to '...'
33+
2. Click on '....'
34+
3. Scroll down to '....'
35+
4. See error
36+
37+
**Expected behavior** A clear and concise description of what you expected to happen.
38+
39+
**Screenshots** If applicable, add screenshots to help explain your problem.
40+
41+
**Desktop (please complete the following information):**
42+
43+
- OS: [e.g. iOS]
44+
- Browser [e.g. chrome, safari]
45+
- Version [e.g. 22]
46+
47+
**Smartphone (please complete the following information):**
48+
49+
- Device: [e.g. iPhone6]
50+
- OS: [e.g. iOS8.1]
51+
- Browser [e.g. stock browser, safari]
52+
- Version [e.g. 22]
53+
54+
**Additional context** Add any other context about the problem here.
55+
56+
----
57+
58+
### 🩹 Did you write a patch that fixes a bug?
59+
60+
- Open a new GitHub **pull request** with the patch.
61+
62+
- Ensure the **pull request** description clearly describes the problem and solution. Include the relevant issue number if applicable.
63+
64+
### 🎈 Did you fix whitespace, format code, or make a purely cosmetic patch?
65+
66+
- Changes that are cosmetic in nature and do not add anything substantial to the stability,
67+
functionality, or testability of this project - you are welcome.
68+
69+
### ⚙️ Do you intend to add a new feature or change an existing one?
70+
71+
- Suggest your change in the **feature request** and wait for approval to avoid writing code, which won't be added.
72+
- Do not open a **pull request** on GitHub until you have collected positive feedback about the change.
73+
74+
#### Feature Request Template
75+
76+
For the creating **feature request**, please see this template.
77+
78+
----
79+
80+
| name | about | title | labels | assignees |
81+
| :-------------: | :------------------------------: | :---: | :----: | --------: |
82+
| Feature request | Suggest an idea for this project | | | |
83+
84+
**Is your feature request related to a problem? Please describe.**
85+
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
86+
87+
**Describe the solution you'd like**
88+
A clear and concise description of what you want to happen.
89+
90+
**Describe alternatives you've considered**
91+
A clear and concise description of any alternative solutions or features you've considered.
92+
93+
**Additional context**
94+
Add any other context or screenshots about the feature request here.
95+
96+
----
97+
98+
## Pull Request Process
99+
100+
1. Update the [readme](README.md) file and [changelog](#CHANGELOG.md) file with details of changes to the interface, this includes new environment variables, exposed ports, useful file locations and container parameters.
101+
2. Increase the version numbers in any examples files, the [readme](README.md) file, the [changelog](#CHANGELOG.md) file, and also badges (if it is needed) to the new version that this **pull request** would represent. For the versioning is used [Semantic Versioning](http://semver.org/).
102+
3. You may merge the **pull request** in once you have the sign-off of one or more other developers, or if you do not have permission to do that, you may request the second reviewer to merge it for you.
103+
104+
### Pull Request Checklist
105+
106+
For any pull request, please refer to this checklist.
107+
108+
----
109+
110+
- [ ] Ensure any install or build dependencies are removed before the end of the layer when doing a build.
111+
- [ ] Make sure you are requesting to **pull a topic/feature/bugfix branch** (right side). Don't request your master!
112+
- [ ] Make sure you are making a pull request against the **master branch** (left side).
113+
- [ ] Check the commit's or even all commits' message styles matches our requested structure.
114+
- [ ] Check your code additions will fail neither code linting checks nor unit test.
115+
116+
----

‎LICENSE

+1-1
Original file line numberDiff line numberDiff line change
@@ -18,4 +18,4 @@ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
1818
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
1919
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
2020
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21-
SOFTWARE.
21+
SOFTWARE.

‎OSSMETADATA

+1
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
osslifecycle=maintenance

0 commit comments

Comments
 (0)
Please sign in to comment.