Skip to content

Commit 0d3ab7d

Browse files
danielpeintnerdanielpeintner
authored
Merge pull request #83 from eclipse-thingweb/egekorkan-patch-2
Adding Administrative Files
2 parents 9a91bea + 70b238b commit 0d3ab7d

File tree

4 files changed

+152
-0
lines changed

4 files changed

+152
-0
lines changed

‎CODE_OF_CONDUCT.md

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

‎LICENSE.md

+12
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
Copyright (c) 2022 Contributors to the Eclipse Foundation
2+
3+
See the NOTICE file(s) distributed with this work for additional
4+
information regarding copyright ownership.
5+
6+
This program and the accompanying materials are made available under the
7+
terms of the Eclipse Public License v. 2.0 which is available at
8+
http://www.eclipse.org/legal/epl-2.0, or the W3C Software Notice and
9+
Document License (2015-05-13) which is available at
10+
https://www.w3.org/Consortium/Legal/2015/copyright-software-and-document.
11+
12+
SPDX-License-Identifier: EPL-2.0 OR W3C-20150513

‎NOTICE.md

+43
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,43 @@
1+
# Notices for Eclipse Thingweb
2+
3+
This content is produced and maintained by the Eclipse Thingweb project.
4+
5+
- Project home: https://projects.eclipse.org/projects/iot.thingweb
6+
7+
## Trademarks
8+
9+
Eclipse Thingweb is a trademark of the Eclipse Foundation.
10+
11+
## Copyright
12+
13+
All content is the property of the respective authors or their employers. For
14+
more information regarding authorship of content, please consult the listed
15+
source code repository logs.
16+
17+
Note: The {year} in the copyright statements is the year in which the content
18+
was created (e.g. “2004”). A range of years is not used.
19+
20+
## Declared Project Licenses
21+
22+
This program and the accompanying materials are made available under the terms
23+
of the Eclipse Public License v. 2.0 which is available at
24+
http://www.eclipse.org/legal/epl-2.0, or the W3C Software Notice and Document
25+
License (2015-05-13) which is available at
26+
https://www.w3.org/Consortium/Legal/2015/copyright-software-and-document.
27+
28+
SPDX-License-Identifier: EPL-2.0 OR W3C-20150513
29+
30+
## Source Code
31+
32+
The project maintains the following source code repositories:
33+
34+
## Third-party Content
35+
36+
## Cryptography
37+
38+
Content may contain encryption software. The country in which you are currently
39+
may have restrictions on the import, possession, and use, and/or re-export to
40+
another country, of encryption software. BEFORE using any encryption software,
41+
please check the country's laws, regulations and policies concerning the import,
42+
possession, or use, and re-export of encryption software, to see if this is
43+
permitted.

‎SECURITY.md

+50
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,50 @@
1+
<!--- https://www.eclipse.org/security/ --->
2+
3+
_ISO 27005 defines vulnerability as:
4+
"A weakness of an asset or group of assets that can be exploited by one or more threats."_
5+
6+
## The Eclipse Security Team
7+
8+
The Eclipse Security Team provides help and advice to Eclipse projects
9+
on vulnerability issues and is the first point of contact
10+
for handling security vulnerabilities.
11+
Members of the Security Team are committers on Eclipse Projects
12+
and members of the Eclipse Architecture Council.
13+
14+
Contact the [Eclipse Security Team](mailto:security@eclipse.org).
15+
16+
**Note that, as a matter of policy, the security team does not open attachments.**
17+
18+
## Reporting a Security Vulnerability
19+
20+
Vulnerabilities can be reported either via email to the Eclipse Security Team
21+
or directly with a project via the Eclipse Foundation's Bugzilla instance.
22+
23+
The general security mailing list address is security@eclipse.org.
24+
Members of the Eclipse Security Team will receive messages sent to this address.
25+
This address should be used only for reporting undisclosed vulnerabilities;
26+
regular issue reports and questions unrelated to vulnerabilities in Eclipse software
27+
will be ignored.
28+
Note that this email address is not encrypted.
29+
30+
The community is also encouraged to report vulnerabilities using the
31+
[Eclipse Foundation's Bugzilla instance](https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Community&component=Vulnerability%20Reports&keywords=security&groups=Security_Advisories).
32+
Note that you will require an Eclipse Foundation account to create an issue report,
33+
but by doing so you will be able to participate directly in the resolution of the issue.
34+
35+
Issue reports related to vulnerabilities must be marked as "committers-only",
36+
either automatically by clicking the provided link, by the reporter,
37+
or by a committer during the triage process.
38+
Note that issues marked "committers-only" are visible to all Eclipse committers.
39+
By default, a "committers-only" issue is also accessible to the reporter
40+
and individuals explicitly indicated in the "cc" list.
41+
42+
## Disclosure
43+
44+
Disclosure is initially limited to the reporter and all Eclipse Committers,
45+
but is expanded to include other individuals, and the general public.
46+
The timing and manner of disclosure is governed by the
47+
[Eclipse Security Policy](https://www.eclipse.org/security/policy.php).
48+
49+
Publicly disclosed issues are listed on the
50+
[Disclosed Vulnerabilities Page](https://www.eclipse.org/security/known.php).

0 commit comments

Comments
 (0)