Skip to content

Commit 6e4c83f

Browse files
dsyerdsyer
committed
Add metadata files
1 parent 76930da commit 6e4c83f

File tree

3 files changed

+361
-0
lines changed

3 files changed

+361
-0
lines changed

Diff for: ‎CODE_OF_CONDUCT.adoc

+44
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,44 @@
1+
= Contributor Code of Conduct
2+
3+
As contributors and maintainers of this project, and in the interest of fostering an open
4+
and welcoming community, we pledge to respect all people who contribute through reporting
5+
issues, posting feature requests, updating documentation, submitting pull requests or
6+
patches, and other activities.
7+
8+
We are committed to making participation in this project a harassment-free experience for
9+
everyone, regardless of level of experience, gender, gender identity and expression,
10+
sexual orientation, disability, personal appearance, body size, race, ethnicity, age,
11+
religion, or nationality.
12+
13+
Examples of unacceptable behavior by participants include:
14+
15+
* The use of sexualized language or imagery
16+
* Personal attacks
17+
* Trolling or insulting/derogatory comments
18+
* Public or private harassment
19+
* Publishing other's private information, such as physical or electronic addresses,
20+
without explicit permission
21+
* Other unethical or unprofessional conduct
22+
23+
Project maintainers have the right and responsibility to remove, edit, or reject comments,
24+
commits, code, wiki edits, issues, and other contributions that are not aligned to this
25+
Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors
26+
that they deem inappropriate, threatening, offensive, or harmful.
27+
28+
By adopting this Code of Conduct, project maintainers commit themselves to fairly and
29+
consistently applying these principles to every aspect of managing this project. Project
30+
maintainers who do not follow or enforce the Code of Conduct may be permanently removed
31+
from the project team.
32+
33+
This Code of Conduct applies both within project spaces and in public spaces when an
34+
individual is representing the project or its community.
35+
36+
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by
37+
contacting a project maintainer at [email protected] . All complaints will
38+
be reviewed and investigated and will result in a response that is deemed necessary and
39+
appropriate to the circumstances. Maintainers are obligated to maintain confidentiality
40+
with regard to the reporter of an incident.
41+
42+
This Code of Conduct is adapted from the
43+
https://contributor-covenant.org[Contributor Covenant], version 1.3.0, available at
44+
https://contributor-covenant.org/version/1/3/0/[contributor-covenant.org/version/1/3/0/]

Diff for: ‎CONTRIBUTING.md

+115
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,115 @@
1+
# Contributing to the Spring Boot Thin Launcher
2+
3+
First off, thank you for taking the time to contribute! :+1: :tada:
4+
5+
### Table of Contents
6+
7+
* [Code of Conduct](#code-of-conduct)
8+
* [How to Contribute](#how-to-contribute)
9+
* [Discuss](#discuss)
10+
* [Create an Issue](#create-an-issue)
11+
* [Issue Lifecycle](#issue-lifecycle)
12+
* [Submit a Pull Request](#submit-a-pull-request)
13+
* [Build from Source](#build-from-source)
14+
* [Source Code Style](#source-code-style)
15+
* [Reference Docs](#reference-docs)
16+
17+
### Code of Conduct
18+
19+
This project is governed by the [Spring Code of Conduct](CODE_OF_CONDUCT.adoc).
20+
By participating you are expected to uphold this code.
21+
Please report unacceptable behavior to [email protected].
22+
23+
### How to Contribute
24+
25+
#### Discuss
26+
27+
If you have a question, check Stack Overflow using
28+
[this list of tags](https://stackoverflow.com/questions/tagged/spring?tab=Newest).
29+
Find an existing discussion, or start a new one if necessary.
30+
31+
If you believe there is an issue, search through
32+
[existing issues](https://github.com/spring-projects-experimental/spring-boot-thin-launcher/issues) trying a
33+
few different ways to find discussions, past or current, that are related to the issue.
34+
Reading those discussions helps you to learn about the issue, and helps us to make a
35+
decision.
36+
37+
38+
#### Create an Issue
39+
40+
Reporting an issue or making a feature request is a great way to contribute. Your feedback
41+
and the conversations that result from it provide a continuous flow of ideas. However,
42+
before creating a ticket, please take the time to [discuss and research](#discuss) first.
43+
44+
If creating an issue after a discussion on Stack Overflow, please provide a description
45+
in the issue instead of simply referring to Stack Overflow. The issue tracker is an
46+
important place of record for design discussions and should be self-sufficient.
47+
48+
Once you're ready, create an issue on
49+
[GitHub](https://github.com/spring-projects-experimental/spring-boot-thin-launcher/issues).
50+
51+
#### Issue Lifecycle
52+
53+
When an issue is first created, it is flagged `waiting-for-triage` waiting for a team
54+
member to triage it. Once the issue has been reviewed, the team may ask for further
55+
information if needed, and based on the findings, the issue is either assigned a target
56+
milestone or is closed with a specific status.
57+
58+
When a fix is ready, the issue is closed and may still be re-opened until the fix is
59+
released. After that the issue will typically no longer be reopened. In rare cases if the
60+
issue was not at all fixed, the issue may be re-opened. In most cases however any
61+
follow-up reports will need to be created as new issues with a fresh description.
62+
63+
#### Submit a Pull Request
64+
65+
1. If you have not previously done so, please sign the
66+
[Contributor License Agreement](https://cla.pivotal.io/sign/spring). You will be reminded
67+
automatically when you submit the PR.
68+
69+
1. Should you create an issue first? No, just create the pull request and use the
70+
description to provide context and motivation, as you would for an issue. If you want
71+
to start a discussion first or have already created an issue, once a pull request is
72+
created, we will close the issue as superseded by the pull request, and the discussion
73+
about the issue will continue under the pull request.
74+
75+
1. Always check out the `master` branch and submit pull requests against it
76+
(for target version see [settings.gradle](settings.gradle)).
77+
Backports to prior versions will be considered on a case-by-case basis and reflected as
78+
the fix version in the issue tracker.
79+
80+
1. Choose the granularity of your commits consciously and squash commits that represent
81+
multiple edits or corrections of the same logical change. See
82+
[Rewriting History section of Pro Git](https://git-scm.com/book/en/Git-Tools-Rewriting-History)
83+
for an overview of streamlining the commit history.
84+
85+
1. Format commit messages using 55 characters for the subject line, 72 characters per line
86+
for the description, followed by the issue fixed, e.g. `Closes gh-22276`. See the
87+
[Commit Guidelines section of Pro Git](https://git-scm.com/book/en/Distributed-Git-Contributing-to-a-Project#Commit-Guidelines)
88+
for best practices around commit messages, and use `git log` to see some examples.
89+
90+
1. If there is a prior issue, reference the GitHub issue number in the description of the
91+
pull request.
92+
93+
If accepted, your contribution may be heavily modified as needed prior to merging.
94+
You will likely retain author attribution for your Git commits granted that the bulk of
95+
your changes remain intact. You may also be asked to rework the submission.
96+
97+
If asked to make corrections, simply push the changes against the same branch, and your
98+
pull request will be updated. In other words, you do not need to create a new pull request
99+
when asked to make changes.
100+
101+
#### Participate in Reviews
102+
103+
Helping to review pull requests is another great way to contribute. Your feedback
104+
can help to shape the implementation of new features. When reviewing pull requests,
105+
however, please refrain from approving or rejecting a PR unless you are a core
106+
committer for the Spring Framework.
107+
108+
### Build from Source
109+
110+
As covered in the [README](README.md) you can build the project with Maven and import it into the IDE of your choice.
111+
112+
### Reference Docs
113+
114+
The reference documentation is in the [README](README.md). For trivial changes, you may be able to browse,
115+
edit source files, and submit directly from GitHub.

Diff for: ‎LICENSE.txt

+202
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,202 @@
1+
2+
Apache License
3+
Version 2.0, January 2004
4+
https://www.apache.org/licenses/
5+
6+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
7+
8+
1. Definitions.
9+
10+
"License" shall mean the terms and conditions for use, reproduction,
11+
and distribution as defined by Sections 1 through 9 of this document.
12+
13+
"Licensor" shall mean the copyright owner or entity authorized by
14+
the copyright owner that is granting the License.
15+
16+
"Legal Entity" shall mean the union of the acting entity and all
17+
other entities that control, are controlled by, or are under common
18+
control with that entity. For the purposes of this definition,
19+
"control" means (i) the power, direct or indirect, to cause the
20+
direction or management of such entity, whether by contract or
21+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
22+
outstanding shares, or (iii) beneficial ownership of such entity.
23+
24+
"You" (or "Your") shall mean an individual or Legal Entity
25+
exercising permissions granted by this License.
26+
27+
"Source" form shall mean the preferred form for making modifications,
28+
including but not limited to software source code, documentation
29+
source, and configuration files.
30+
31+
"Object" form shall mean any form resulting from mechanical
32+
transformation or translation of a Source form, including but
33+
not limited to compiled object code, generated documentation,
34+
and conversions to other media types.
35+
36+
"Work" shall mean the work of authorship, whether in Source or
37+
Object form, made available under the License, as indicated by a
38+
copyright notice that is included in or attached to the work
39+
(an example is provided in the Appendix below).
40+
41+
"Derivative Works" shall mean any work, whether in Source or Object
42+
form, that is based on (or derived from) the Work and for which the
43+
editorial revisions, annotations, elaborations, or other modifications
44+
represent, as a whole, an original work of authorship. For the purposes
45+
of this License, Derivative Works shall not include works that remain
46+
separable from, or merely link (or bind by name) to the interfaces of,
47+
the Work and Derivative Works thereof.
48+
49+
"Contribution" shall mean any work of authorship, including
50+
the original version of the Work and any modifications or additions
51+
to that Work or Derivative Works thereof, that is intentionally
52+
submitted to Licensor for inclusion in the Work by the copyright owner
53+
or by an individual or Legal Entity authorized to submit on behalf of
54+
the copyright owner. For the purposes of this definition, "submitted"
55+
means any form of electronic, verbal, or written communication sent
56+
to the Licensor or its representatives, including but not limited to
57+
communication on electronic mailing lists, source code control systems,
58+
and issue tracking systems that are managed by, or on behalf of, the
59+
Licensor for the purpose of discussing and improving the Work, but
60+
excluding communication that is conspicuously marked or otherwise
61+
designated in writing by the copyright owner as "Not a Contribution."
62+
63+
"Contributor" shall mean Licensor and any individual or Legal Entity
64+
on behalf of whom a Contribution has been received by Licensor and
65+
subsequently incorporated within the Work.
66+
67+
2. Grant of Copyright License. Subject to the terms and conditions of
68+
this License, each Contributor hereby grants to You a perpetual,
69+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
70+
copyright license to reproduce, prepare Derivative Works of,
71+
publicly display, publicly perform, sublicense, and distribute the
72+
Work and such Derivative Works in Source or Object form.
73+
74+
3. Grant of Patent License. Subject to the terms and conditions of
75+
this License, each Contributor hereby grants to You a perpetual,
76+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
77+
(except as stated in this section) patent license to make, have made,
78+
use, offer to sell, sell, import, and otherwise transfer the Work,
79+
where such license applies only to those patent claims licensable
80+
by such Contributor that are necessarily infringed by their
81+
Contribution(s) alone or by combination of their Contribution(s)
82+
with the Work to which such Contribution(s) was submitted. If You
83+
institute patent litigation against any entity (including a
84+
cross-claim or counterclaim in a lawsuit) alleging that the Work
85+
or a Contribution incorporated within the Work constitutes direct
86+
or contributory patent infringement, then any patent licenses
87+
granted to You under this License for that Work shall terminate
88+
as of the date such litigation is filed.
89+
90+
4. Redistribution. You may reproduce and distribute copies of the
91+
Work or Derivative Works thereof in any medium, with or without
92+
modifications, and in Source or Object form, provided that You
93+
meet the following conditions:
94+
95+
(a) You must give any other recipients of the Work or
96+
Derivative Works a copy of this License; and
97+
98+
(b) You must cause any modified files to carry prominent notices
99+
stating that You changed the files; and
100+
101+
(c) You must retain, in the Source form of any Derivative Works
102+
that You distribute, all copyright, patent, trademark, and
103+
attribution notices from the Source form of the Work,
104+
excluding those notices that do not pertain to any part of
105+
the Derivative Works; and
106+
107+
(d) If the Work includes a "NOTICE" text file as part of its
108+
distribution, then any Derivative Works that You distribute must
109+
include a readable copy of the attribution notices contained
110+
within such NOTICE file, excluding those notices that do not
111+
pertain to any part of the Derivative Works, in at least one
112+
of the following places: within a NOTICE text file distributed
113+
as part of the Derivative Works; within the Source form or
114+
documentation, if provided along with the Derivative Works; or,
115+
within a display generated by the Derivative Works, if and
116+
wherever such third-party notices normally appear. The contents
117+
of the NOTICE file are for informational purposes only and
118+
do not modify the License. You may add Your own attribution
119+
notices within Derivative Works that You distribute, alongside
120+
or as an addendum to the NOTICE text from the Work, provided
121+
that such additional attribution notices cannot be construed
122+
as modifying the License.
123+
124+
You may add Your own copyright statement to Your modifications and
125+
may provide additional or different license terms and conditions
126+
for use, reproduction, or distribution of Your modifications, or
127+
for any such Derivative Works as a whole, provided Your use,
128+
reproduction, and distribution of the Work otherwise complies with
129+
the conditions stated in this License.
130+
131+
5. Submission of Contributions. Unless You explicitly state otherwise,
132+
any Contribution intentionally submitted for inclusion in the Work
133+
by You to the Licensor shall be under the terms and conditions of
134+
this License, without any additional terms or conditions.
135+
Notwithstanding the above, nothing herein shall supersede or modify
136+
the terms of any separate license agreement you may have executed
137+
with Licensor regarding such Contributions.
138+
139+
6. Trademarks. This License does not grant permission to use the trade
140+
names, trademarks, service marks, or product names of the Licensor,
141+
except as required for reasonable and customary use in describing the
142+
origin of the Work and reproducing the content of the NOTICE file.
143+
144+
7. Disclaimer of Warranty. Unless required by applicable law or
145+
agreed to in writing, Licensor provides the Work (and each
146+
Contributor provides its Contributions) on an "AS IS" BASIS,
147+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
148+
implied, including, without limitation, any warranties or conditions
149+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
150+
PARTICULAR PURPOSE. You are solely responsible for determining the
151+
appropriateness of using or redistributing the Work and assume any
152+
risks associated with Your exercise of permissions under this License.
153+
154+
8. Limitation of Liability. In no event and under no legal theory,
155+
whether in tort (including negligence), contract, or otherwise,
156+
unless required by applicable law (such as deliberate and grossly
157+
negligent acts) or agreed to in writing, shall any Contributor be
158+
liable to You for damages, including any direct, indirect, special,
159+
incidental, or consequential damages of any character arising as a
160+
result of this License or out of the use or inability to use the
161+
Work (including but not limited to damages for loss of goodwill,
162+
work stoppage, computer failure or malfunction, or any and all
163+
other commercial damages or losses), even if such Contributor
164+
has been advised of the possibility of such damages.
165+
166+
9. Accepting Warranty or Additional Liability. While redistributing
167+
the Work or Derivative Works thereof, You may choose to offer,
168+
and charge a fee for, acceptance of support, warranty, indemnity,
169+
or other liability obligations and/or rights consistent with this
170+
License. However, in accepting such obligations, You may act only
171+
on Your own behalf and on Your sole responsibility, not on behalf
172+
of any other Contributor, and only if You agree to indemnify,
173+
defend, and hold each Contributor harmless for any liability
174+
incurred by, or claims asserted against, such Contributor by reason
175+
of your accepting any such warranty or additional liability.
176+
177+
END OF TERMS AND CONDITIONS
178+
179+
APPENDIX: How to apply the Apache License to your work.
180+
181+
To apply the Apache License to your work, attach the following
182+
boilerplate notice, with the fields enclosed by brackets "{}"
183+
replaced with your own identifying information. (Don't include
184+
the brackets!) The text should be enclosed in the appropriate
185+
comment syntax for the file format. We also recommend that a
186+
file or class name and description of purpose be included on the
187+
same "printed page" as the copyright notice for easier
188+
identification within third-party archives.
189+
190+
Copyright {yyyy} {name of copyright owner}
191+
192+
Licensed under the Apache License, Version 2.0 (the "License");
193+
you may not use this file except in compliance with the License.
194+
You may obtain a copy of the License at
195+
196+
https://www.apache.org/licenses/LICENSE-2.0
197+
198+
Unless required by applicable law or agreed to in writing, software
199+
distributed under the License is distributed on an "AS IS" BASIS,
200+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
201+
See the License for the specific language governing permissions and
202+
limitations under the License.

0 commit comments

Comments
 (0)