Skip to content

Commit 1a84b2d

Browse files
brownleejbrownleej
committed
Add missing license information.
Standardize formatting of licensing comments.
1 parent 0fe8fd4 commit 1a84b2d

18 files changed

+679
-85
lines changed

‎ACKNOWLEDGEMENTS

+87
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,87 @@
1+
Acknowledgements
2+
Portions of this FoundationDB Kubernetes Operator Software may utilize the
3+
following copyrighted material, the use of which is hereby acknowledged.
4+
5+
_____________________
6+
7+
The Kubernetes Authors (Kubernetes)
8+
Licensed under the Apache License, Version 2.0 (the "License");
9+
you may not use this file except in compliance with the License.
10+
You may obtain a copy of the License at
11+
12+
http://www.apache.org/licenses/LICENSE-2.0
13+
14+
Unless required by applicable law or agreed to in writing, software
15+
distributed under the License is distributed on an "AS IS" BASIS,
16+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
17+
See the License for the specific language governing permissions and
18+
limitations under the License.
19+
20+
The Go Authors (Go Tools)
21+
Copyright (c) 2009 The Go Authors. All rights reserved.
22+
23+
Redistribution and use in source and binary forms, with or without
24+
modification, are permitted provided that the following conditions are
25+
met:
26+
27+
* Redistributions of source code must retain the above copyright
28+
notice, this list of conditions and the following disclaimer.
29+
* Redistributions in binary form must reproduce the above
30+
copyright notice, this list of conditions and the following disclaimer
31+
in the documentation and/or other materials provided with the
32+
distribution.
33+
* Neither the name of Google Inc. nor the names of its
34+
contributors may be used to endorse or promote products derived from
35+
this software without specific prior written permission.
36+
37+
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
38+
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
39+
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
40+
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
41+
OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
42+
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
43+
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
44+
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
45+
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
46+
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
47+
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
48+
49+
Ernest Micklei (go-restful)
50+
Permission is hereby granted, free of charge, to any person obtaining
51+
a copy of this software and associated documentation files (the
52+
"Software"), to deal in the Software without restriction, including
53+
without limitation the rights to use, copy, modify, merge, publish,
54+
distribute, sublicense, and/or sell copies of the Software, and to
55+
permit persons to whom the Software is furnished to do so, subject to
56+
the following conditions:
57+
58+
The above copyright notice and this permission notice shall be
59+
included in all copies or substantial portions of the Software.
60+
61+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
62+
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
63+
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
64+
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
65+
LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
66+
OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
67+
WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
68+
69+
Onsi Fakhouri (ginkgo, gomega)
70+
Permission is hereby granted, free of charge, to any person obtaining
71+
a copy of this software and associated documentation files (the
72+
"Software"), to deal in the Software without restriction, including
73+
without limitation the rights to use, copy, modify, merge, publish,
74+
distribute, sublicense, and/or sell copies of the Software, and to
75+
permit persons to whom the Software is furnished to do so, subject to
76+
the following conditions:
77+
78+
The above copyright notice and this permission notice shall be
79+
included in all copies or substantial portions of the Software.
80+
81+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
82+
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
83+
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
84+
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
85+
LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
86+
OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
87+
WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

‎CODE_OF_CONDUCT.md

+71
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,71 @@
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+
education, socio-economic status, nationality, personal appearance, race,
10+
religion, or sexual identity and 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 [email protected]. 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](https://www.contributor-covenant.org/), version 1.4,
71+
available at [https://www.contributor-covenant.org/version/1/4/code-of-conduct.html](https://www.contributor-covenant.org/version/1/4/code-of-conduct.html)

‎CONTRIBUTING.md

+68
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,68 @@
1+
# Contributing to FoundationDB
2+
3+
Welcome to the FoundationDB community, and thank you for contributing! The following guide outlines the basics of how to get involved.
4+
5+
If you have questions, we encourage you to engage in discussion on the [community forums](https://forums.foundationdb.org). Pull requests to update and expand this guide are also welcome.
6+
7+
#### Table of Contents
8+
9+
* [Before you get started](#before-you-get-started)
10+
* [Community Guidelines](#community-guidelines)
11+
* [Project Licensing](#project-licensing)
12+
* [Governance and Decision Making](#governance-and-decision-making)
13+
* [Contributing](#contributing)
14+
* [Opening a Pull Request](#opening-a-pull-request)
15+
* [Reporting Issues](#reporting-issues)
16+
* [Project Communication](#project-communication)
17+
* [Community Forums](#community-forums)
18+
* [Using GitHub Issues and Community Forums](#using-github-issues-and-community-forums)
19+
* [Project and Development Updates](#project-and-development-updates)
20+
21+
## Before you get started
22+
### Community Guidelines
23+
We want the FoundationDB community to be as welcoming and inclusive as possible, and have adopted a [Code of Conduct](CODE_OF_CONDUCT.md) that we ask all community members to read and observe.
24+
25+
### Project Licensing
26+
By submitting a pull request, you represent that you have the right to license your contribution to Apple and the community, and agree by submitting the patch that your contributions are licensed under the Apache 2.0 license.
27+
28+
### Governance and Decision Making
29+
At project launch, FoundationDB has a light governance structure. The intention is for the community to evolve quickly and adopt additional processes as participation grows. Stay tuned, and stay engaged! Your feedback is welcome.
30+
31+
We draw inspiration from the Apache Software Foundation's informal motto: ["community over code"](https://blogs.apache.org/foundation/entry/asf_15_community_over_code), and their emphasis on meritocratic rules. You'll also observe that some initial community structure is [inspired by the Swift community](https://swift.org/community/#community-structure).
32+
33+
The project technical lead is Evan Tschannen ([email protected]).
34+
35+
Members of the Apple FoundationDB team are part of the initial core committers helping review individual contributions; you'll see them commenting on your pull requests. Future committers to the open source project, and the process for adding individuals in this role will be formalized in the future.
36+
37+
## Contributing
38+
### Opening a Pull Request
39+
We love pull requests! For minor changes, feel free to open up a PR directly. For larger feature development and any changes that may require community discussion, we ask that you discuss your ideas on the [community forums](https://forums.foundationdb.org) prior to opening a PR, and then reference that thread within your PR comment.
40+
41+
CI will be run automatically for core committers, and for community PRs it will be initiated by the request of a core committer. Tests can also be run locally via `make test`, and core committers can run additional validation on pull requests prior to merging them.
42+
43+
### Reporting issues
44+
Please refer to the section below on [using GitHub issues and the community forums](#using-github-issues-and-community-forums) for more info.
45+
46+
#### Security issues
47+
To report a security issue, please **DO NOT** start by filing a public issue or posting to the forums; instead send a private email to [[email protected]](mailto:[email protected]).
48+
49+
## Project Communication
50+
### Community Forums
51+
We encourage your participation asking questions and helping improve the FoundationDB project. Check out the [FoundationDB community forums](https://forums.foundationdb.org), which serve a similar function as mailing lists in many open source projects. The forums are organized into three sections:
52+
53+
* [Development](https://forums.foundationdb.org/c/development): For discussing the internals and development of the FoundationDB core, as well as layers.
54+
* [Using FoundationDB](https://forums.foundationdb.org/c/using-foundationdb): For discussing user-facing topics. Getting started and have a question? This is the place for you.
55+
* [Site Feedback](https://forums.foundationdb.org/c/site-feedback): A category for discussing the forums and the OSS project, its organization, how it works, and how we can improve it.
56+
57+
### Using GitHub Issues and Community Forums
58+
GitHub issues and the community forums both offer features to facilitate discussion. To clarify how and when to use each tool, here's a quick summary of how we think about them:
59+
60+
GitHub Issues should be used for tracking tasks. If you know the specific code that needs to be changed, then it should go to GitHub Issues. Everything else should go to the Forums. For example:
61+
62+
* I am experiencing some weird behavior, which I think is a bug, but I don't know where exactly (mysteries and unexpected behaviors): *Forums*
63+
* I see a bug in this piece of code: *GitHub Issues*
64+
* Feature requests and design documents: *Forums*
65+
* Implementing an agreed upon feature: *GitHub Issues*
66+
67+
### Project and Development Updates
68+
Stay connected to the project and the community! For project and community updates, follow the [FoundationDB project blog](https://www.foundationdb.org/blog/). Development announcements will be made via the community forums' [dev-announce](https://forums.foundationdb.org/c/development/dev-announce) section.

‎Dockerfile

+19
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,22 @@
1+
# Dockerfile
2+
#
3+
# This source file is part of the FoundationDB open source project
4+
#
5+
# Copyright 2018-2019 Apple Inc. and the FoundationDB project authors
6+
#
7+
# Licensed under the Apache License, Version 2.0 (the "License");
8+
# you may not use this file except in compliance with the License.
9+
# You may obtain a copy of the License at
10+
#
11+
# http://www.apache.org/licenses/LICENSE-2.0
12+
#
13+
# Unless required by applicable law or agreed to in writing, software
14+
# distributed under the License is distributed on an "AS IS" BASIS,
15+
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
16+
# See the License for the specific language governing permissions and
17+
# limitations under the License.
18+
#
19+
120
# Build the manager binary
221
FROM golang:1.12.5 as builder
322

0 commit comments

Comments
 (0)