Skip to content

Commit 2049f97

Browse files
ArangoGutierrezArangoGutierrez
authored
Merge pull request #8 from ArangoGutierrez/master
cut release v1.0.0-alpha
2 parents 5007d45 + c5327aa commit 2049f97

File tree

1,662 files changed

+871
-589892
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

1,662 files changed

+871
-589892
lines changed

‎.circleci/config.yaml

Lines changed: 104 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,104 @@
1+
version: 2.1
2+
3+
defaults: &defaults
4+
working_directory: /src
5+
docker:
6+
- image: golang:1.12
7+
8+
jobs:
9+
get_source:
10+
<<: *defaults
11+
steps:
12+
- checkout
13+
- restore_cache:
14+
keys:
15+
- go-mod-{{ checksum "go.sum" }}
16+
- run:
17+
name: Populate Go Mod Cache
18+
command: |
19+
if [ ! -d /go/pkg/mod ]; then
20+
go mod download
21+
fi
22+
- save_cache:
23+
key: go-mod-{{ checksum "go.sum" }}
24+
paths:
25+
- /go/pkg/mod
26+
- run:
27+
name: Go Mod Verify
28+
command: go mod verify
29+
- persist_to_workspace:
30+
root: /
31+
paths:
32+
- go/pkg/mod
33+
- src
34+
35+
build_source:
36+
<<: *defaults
37+
steps:
38+
- attach_workspace:
39+
at: /
40+
- run:
41+
name: Build Source
42+
command: make build
43+
44+
check_formatting:
45+
<<: *defaults
46+
steps:
47+
- attach_workspace:
48+
at: /
49+
- run:
50+
name: Check Formatting
51+
command: test -z $(go fmt ./...)
52+
53+
vet_source:
54+
<<: *defaults
55+
steps:
56+
- attach_workspace:
57+
at: /
58+
- run:
59+
name: Vet Source
60+
command: make vet
61+
62+
lint_source:
63+
<<: *defaults
64+
steps:
65+
- attach_workspace:
66+
at: /
67+
- run:
68+
name: Install golangci-lint
69+
command: curl -sfL https://install.goreleaser.com/github.com/golangci/golangci-lint.sh | sh -s -- -b $(go env GOPATH)/bin v1.15.0
70+
- run:
71+
name: Check for Lint
72+
command: golangci-lint run ./...
73+
74+
lint_markdown:
75+
docker:
76+
- image: circleci/ruby:2.4.1-node
77+
steps:
78+
- attach_workspace:
79+
at: .
80+
- run:
81+
name: Install markdownlint
82+
command: sudo npm install -g markdownlint-cli
83+
- run:
84+
name: Check for Lint
85+
command: markdownlint --config src/.markdownlint.json src/
86+
87+
build_and_test:
88+
jobs:
89+
- get_source
90+
- build_source:
91+
requires:
92+
- get_source
93+
- check_formatting:
94+
requires:
95+
- get_source
96+
- vet_source:
97+
requires:
98+
- get_source
99+
- lint_source:
100+
requires:
101+
- get_source
102+
- lint_markdown:
103+
requires:
104+
- get_source

‎CONTRIBUTING.md

Lines changed: 122 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,122 @@
1+
# Contributor's Agreement
2+
3+
You are under no obligation whatsoever to provide any bug fixes, patches,
4+
or upgrades to the features, functionality or performance of the source
5+
code ("Enhancements") to anyone; however, if you choose to make your
6+
Enhancements available either publicly, or directly to the project,
7+
without imposing a separate written license agreement for such
8+
Enhancements, then you hereby grant the following license: a non-exclusive,
9+
royalty-free perpetual license to install, use, modify, prepare derivative
10+
works, incorporate into other computer software, distribute, and sublicense
11+
such enhancements or derivative works thereof, in binary and source code
12+
form.
13+
14+
15+
# Contributing
16+
17+
When contributing to [sylabs/nomad-driver-singularity](https://github.com/sylabs/nomad-driver-singularity/), it
18+
is important to properly communicate the gist of the contribution. If it is a simple code or
19+
editorial fix, simply explaining this within the GitHub Pull Request (PR) will suffice. But
20+
if this is a larger fix or Enhancement, you are advised to first discuss the change
21+
with the project leader or developers.
22+
23+
Please note we have a code of conduct, described below. Please follow it in
24+
all your interactions with the project members and users.
25+
26+
## Pull Requests (PRs)
27+
28+
### Process
29+
1. Essential bug fix PRs should be sent to both master and release branches.
30+
2. Small bug fix and feature enhancement PRs should be sent to master only.
31+
3. Follow the existing code style precedent, especially for C. For Golang, you
32+
will mostly conform to the style and form enforced by the "goimports" and
33+
"golint" tools for proper formatting.
34+
4. Ensure any install or build dependencies are removed before doing a build
35+
to test your PR locally.
36+
5. For any new functionality, please write appropriate go tests that will run
37+
as part of the Continuous Integration (Circle CI) system.
38+
6. The project's default copyright and header have been included in any new
39+
source files.
40+
7. Make sure you have run a local `make lint && make test` and all tests succeed
41+
before submitting the PR.
42+
8. Is the code human understandable? This can be accomplished via a clear code
43+
style as well as documentation and/or comments.
44+
9. The pull request will be reviewed by others, and finally merged when all
45+
requirements are met.
46+
10. Documentation must be provided if necessary (next section)
47+
48+
# Code of Conduct
49+
50+
## Our Pledge
51+
52+
In the interest of fostering an open and welcoming environment, we as
53+
contributors and maintainers pledge to making participation in our project and
54+
our community a harassment-free experience for everyone, regardless of age, body
55+
size, disability, ethnicity, gender identity and expression, level of experience,
56+
nationality, personal appearance, race, religion, or sexual identity and
57+
orientation.
58+
59+
## Our Standards
60+
61+
Examples of behavior that contributes to creating a positive environment
62+
include:
63+
64+
* Using welcoming and inclusive language
65+
* Being respectful of differing viewpoints and experiences
66+
* Gracefully accepting constructive criticism
67+
* Focusing on what is best for the community
68+
* Showing empathy towards other community members
69+
70+
Examples of unacceptable behavior by participants include:
71+
72+
* The use of sexualized language or imagery and unwelcome sexual attention or
73+
advances
74+
* Trolling, insulting/derogatory comments, and personal or political attacks
75+
* Public or private harassment
76+
* Publishing others' private information, such as a physical or electronic
77+
address, without explicit permission
78+
* Other conduct which could reasonably be considered inappropriate in a
79+
professional setting
80+
81+
### Our Responsibilities
82+
83+
Project maintainers are responsible for clarifying the standards of acceptable
84+
behavior and are expected to take appropriate and fair corrective action in
85+
response to any instances of unacceptable behavior.
86+
87+
Project maintainers have the right and responsibility to remove, edit, or
88+
reject comments, commits, code, wiki edits, issues, and other contributions
89+
that are not aligned to this Code of Conduct, or to ban temporarily or
90+
permanently any contributor for other behaviors that they deem inappropriate,
91+
threatening, offensive, or harmful.
92+
93+
## Scope
94+
95+
This Code of Conduct applies both within project spaces and in public spaces
96+
when an individual is representing the project or its community. Examples of
97+
representing a project or community include using an official project e-mail
98+
address, posting via an official social media account, or acting as an appointed
99+
representative at an online or offline event. Representation of a project may be
100+
further defined and clarified by project maintainers.
101+
102+
## Enforcement
103+
104+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
105+
reported by contacting the project leaders ([email protected]). All
106+
complaints will be reviewed and investigated and will result in a response
107+
that is deemed necessary and appropriate to the circumstances. The project
108+
team is obligated to maintain confidentiality with regard to the reporter of
109+
an incident. Further details of specific enforcement policies may be posted
110+
separately.
111+
112+
Project maintainers, contributors and users who do not follow or enforce the
113+
Code of Conduct in good faith may face temporary or permanent repercussions
114+
with their involvement in the project as determined by the project's leader(s).
115+
116+
## Attribution
117+
118+
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
119+
available at [http://contributor-covenant.org/version/1/4][version]
120+
121+
[homepage]: http://contributor-covenant.org
122+
[version]: http://contributor-covenant.org/version/1/4/

‎CONTRIBUTORS.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
# Maintainers:
2+
3+
- Eduardo Arango <[email protected]>
4+
5+
# Contributors:

0 commit comments

Comments
 (0)