From 67698e2a14b82a2f58215338877cc51a85755988 Mon Sep 17 00:00:00 2001 From: Muhammet Kara Date: Sat, 20 Dec 2025 01:32:59 +0300 Subject: [PATCH 1/7] Add Apache License 2.0 to the project --- LICENSE | 201 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 201 insertions(+) create mode 100644 LICENSE diff --git a/LICENSE b/LICENSE new file mode 100644 index 0000000..261eeb9 --- /dev/null +++ b/LICENSE @@ -0,0 +1,201 @@ + Apache License + Version 2.0, January 2004 + http://www.apache.org/licenses/ + + TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION + + 1. Definitions. + + "License" shall mean the terms and conditions for use, reproduction, + and distribution as defined by Sections 1 through 9 of this document. + + "Licensor" shall mean the copyright owner or entity authorized by + the copyright owner that is granting the License. + + "Legal Entity" shall mean the union of the acting entity and all + other entities that control, are controlled by, or are under common + control with that entity. For the purposes of this definition, + "control" means (i) the power, direct or indirect, to cause the + direction or management of such entity, whether by contract or + otherwise, or (ii) ownership of fifty percent (50%) or more of the + outstanding shares, or (iii) beneficial ownership of such entity. + + "You" (or "Your") shall mean an individual or Legal Entity + exercising permissions granted by this License. + + "Source" form shall mean the preferred form for making modifications, + including but not limited to software source code, documentation + source, and configuration files. + + "Object" form shall mean any form resulting from mechanical + transformation or translation of a Source form, including but + not limited to compiled object code, generated documentation, + and conversions to other media types. + + "Work" shall mean the work of authorship, whether in Source or + Object form, made available under the License, as indicated by a + copyright notice that is included in or attached to the work + (an example is provided in the Appendix below). + + "Derivative Works" shall mean any work, whether in Source or Object + form, that is based on (or derived from) the Work and for which the + editorial revisions, annotations, elaborations, or other modifications + represent, as a whole, an original work of authorship. For the purposes + of this License, Derivative Works shall not include works that remain + separable from, or merely link (or bind by name) to the interfaces of, + the Work and Derivative Works thereof. + + "Contribution" shall mean any work of authorship, including + the original version of the Work and any modifications or additions + to that Work or Derivative Works thereof, that is intentionally + submitted to Licensor for inclusion in the Work by the copyright owner + or by an individual or Legal Entity authorized to submit on behalf of + the copyright owner. For the purposes of this definition, "submitted" + means any form of electronic, verbal, or written communication sent + to the Licensor or its representatives, including but not limited to + communication on electronic mailing lists, source code control systems, + and issue tracking systems that are managed by, or on behalf of, the + Licensor for the purpose of discussing and improving the Work, but + excluding communication that is conspicuously marked or otherwise + designated in writing by the copyright owner as "Not a Contribution." + + "Contributor" shall mean Licensor and any individual or Legal Entity + on behalf of whom a Contribution has been received by Licensor and + subsequently incorporated within the Work. + + 2. Grant of Copyright License. Subject to the terms and conditions of + this License, each Contributor hereby grants to You a perpetual, + worldwide, non-exclusive, no-charge, royalty-free, irrevocable + copyright license to reproduce, prepare Derivative Works of, + publicly display, publicly perform, sublicense, and distribute the + Work and such Derivative Works in Source or Object form. + + 3. Grant of Patent License. Subject to the terms and conditions of + this License, each Contributor hereby grants to You a perpetual, + worldwide, non-exclusive, no-charge, royalty-free, irrevocable + (except as stated in this section) patent license to make, have made, + use, offer to sell, sell, import, and otherwise transfer the Work, + where such license applies only to those patent claims licensable + by such Contributor that are necessarily infringed by their + Contribution(s) alone or by combination of their Contribution(s) + with the Work to which such Contribution(s) was submitted. If You + institute patent litigation against any entity (including a + cross-claim or counterclaim in a lawsuit) alleging that the Work + or a Contribution incorporated within the Work constitutes direct + or contributory patent infringement, then any patent licenses + granted to You under this License for that Work shall terminate + as of the date such litigation is filed. + + 4. Redistribution. You may reproduce and distribute copies of the + Work or Derivative Works thereof in any medium, with or without + modifications, and in Source or Object form, provided that You + meet the following conditions: + + (a) You must give any other recipients of the Work or + Derivative Works a copy of this License; and + + (b) You must cause any modified files to carry prominent notices + stating that You changed the files; and + + (c) You must retain, in the Source form of any Derivative Works + that You distribute, all copyright, patent, trademark, and + attribution notices from the Source form of the Work, + excluding those notices that do not pertain to any part of + the Derivative Works; and + + (d) If the Work includes a "NOTICE" text file as part of its + distribution, then any Derivative Works that You distribute must + include a readable copy of the attribution notices contained + within such NOTICE file, excluding those notices that do not + pertain to any part of the Derivative Works, in at least one + of the following places: within a NOTICE text file distributed + as part of the Derivative Works; within the Source form or + documentation, if provided along with the Derivative Works; or, + within a display generated by the Derivative Works, if and + wherever such third-party notices normally appear. The contents + of the NOTICE file are for informational purposes only and + do not modify the License. You may add Your own attribution + notices within Derivative Works that You distribute, alongside + or as an addendum to the NOTICE text from the Work, provided + that such additional attribution notices cannot be construed + as modifying the License. + + You may add Your own copyright statement to Your modifications and + may provide additional or different license terms and conditions + for use, reproduction, or distribution of Your modifications, or + for any such Derivative Works as a whole, provided Your use, + reproduction, and distribution of the Work otherwise complies with + the conditions stated in this License. + + 5. Submission of Contributions. Unless You explicitly state otherwise, + any Contribution intentionally submitted for inclusion in the Work + by You to the Licensor shall be under the terms and conditions of + this License, without any additional terms or conditions. + Notwithstanding the above, nothing herein shall supersede or modify + the terms of any separate license agreement you may have executed + with Licensor regarding such Contributions. + + 6. Trademarks. This License does not grant permission to use the trade + names, trademarks, service marks, or product names of the Licensor, + except as required for reasonable and customary use in describing the + origin of the Work and reproducing the content of the NOTICE file. + + 7. Disclaimer of Warranty. Unless required by applicable law or + agreed to in writing, Licensor provides the Work (and each + Contributor provides its Contributions) on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or + implied, including, without limitation, any warranties or conditions + of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A + PARTICULAR PURPOSE. You are solely responsible for determining the + appropriateness of using or redistributing the Work and assume any + risks associated with Your exercise of permissions under this License. + + 8. Limitation of Liability. In no event and under no legal theory, + whether in tort (including negligence), contract, or otherwise, + unless required by applicable law (such as deliberate and grossly + negligent acts) or agreed to in writing, shall any Contributor be + liable to You for damages, including any direct, indirect, special, + incidental, or consequential damages of any character arising as a + result of this License or out of the use or inability to use the + Work (including but not limited to damages for loss of goodwill, + work stoppage, computer failure or malfunction, or any and all + other commercial damages or losses), even if such Contributor + has been advised of the possibility of such damages. + + 9. Accepting Warranty or Additional Liability. While redistributing + the Work or Derivative Works thereof, You may choose to offer, + and charge a fee for, acceptance of support, warranty, indemnity, + or other liability obligations and/or rights consistent with this + License. However, in accepting such obligations, You may act only + on Your own behalf and on Your sole responsibility, not on behalf + of any other Contributor, and only if You agree to indemnify, + defend, and hold each Contributor harmless for any liability + incurred by, or claims asserted against, such Contributor by reason + of your accepting any such warranty or additional liability. + + END OF TERMS AND CONDITIONS + + APPENDIX: How to apply the Apache License to your work. + + To apply the Apache License to your work, attach the following + boilerplate notice, with the fields enclosed by brackets "[]" + replaced with your own identifying information. (Don't include + the brackets!) The text should be enclosed in the appropriate + comment syntax for the file format. We also recommend that a + file or class name and description of purpose be included on the + same "printed page" as the copyright notice for easier + identification within third-party archives. + + Copyright [yyyy] [name of copyright owner] + + Licensed under the Apache License, Version 2.0 (the "License"); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. From 5ebbc000a870e305702b985503334fc281ca225d Mon Sep 17 00:00:00 2001 From: Muhammet Kara Date: Sat, 20 Dec 2025 01:34:21 +0300 Subject: [PATCH 2/7] Add Contributor Covenant Code of Conduct This document outlines the standards of behavior expected from community members and the enforcement guidelines for violations. --- CODE_OF_CONDUCT.md | 128 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 128 insertions(+) create mode 100644 CODE_OF_CONDUCT.md diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md new file mode 100644 index 0000000..f1d2db2 --- /dev/null +++ b/CODE_OF_CONDUCT.md @@ -0,0 +1,128 @@ +# Contributor Covenant Code of Conduct + +## Our Pledge + +We as members, contributors, and leaders pledge to make participation in our +community a harassment-free experience for everyone, regardless of age, body +size, visible or invisible 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. + +We pledge to act and interact in ways that contribute to an open, welcoming, +diverse, inclusive, and healthy community. + +## Our Standards + +Examples of behavior that contributes to a positive environment for our +community include: + +* Demonstrating empathy and kindness toward other people +* Being respectful of differing opinions, viewpoints, and experiences +* Giving and gracefully accepting constructive feedback +* Accepting responsibility and apologizing to those affected by our mistakes, + and learning from the experience +* Focusing on what is best not just for us as individuals, but for the + overall community + +Examples of unacceptable behavior include: + +* The use of sexualized language or imagery, and sexual attention or + advances of any kind +* Trolling, insulting or derogatory comments, and personal or political attacks +* Public or private harassment +* Publishing others' private information, such as a physical or email + address, without their explicit permission +* Other conduct which could reasonably be considered inappropriate in a + professional setting + +## Enforcement Responsibilities + +Community leaders are responsible for clarifying and enforcing our standards of +acceptable behavior and will take appropriate and fair corrective action in +response to any behavior that they deem inappropriate, threatening, offensive, +or harmful. + +Community 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, and will communicate reasons for moderation +decisions when appropriate. + +## Scope + +This Code of Conduct applies within all community spaces, and also applies when +an individual is officially representing the community in public spaces. +Examples of representing our community include using an official e-mail address, +posting via an official social media account, or acting as an appointed +representative at an online or offline event. + +## Enforcement + +Instances of abusive, harassing, or otherwise unacceptable behavior may be +reported to the community leaders responsible for enforcement at +community@make.services. +All complaints will be reviewed and investigated promptly and fairly. + +All community leaders are obligated to respect the privacy and security of the +reporter of any incident. + +## Enforcement Guidelines + +Community leaders will follow these Community Impact Guidelines in determining +the consequences for any action they deem in violation of this Code of Conduct: + +### 1. Correction + +**Community Impact**: Use of inappropriate language or other behavior deemed +unprofessional or unwelcome in the community. + +**Consequence**: A private, written warning from community leaders, providing +clarity around the nature of the violation and an explanation of why the +behavior was inappropriate. A public apology may be requested. + +### 2. Warning + +**Community Impact**: A violation through a single incident or series +of actions. + +**Consequence**: A warning with consequences for continued behavior. No +interaction with the people involved, including unsolicited interaction with +those enforcing the Code of Conduct, for a specified period of time. This +includes avoiding interactions in community spaces as well as external channels +like social media. Violating these terms may lead to a temporary or +permanent ban. + +### 3. Temporary Ban + +**Community Impact**: A serious violation of community standards, including +sustained inappropriate behavior. + +**Consequence**: A temporary ban from any sort of interaction or public +communication with the community for a specified period of time. No public or +private interaction with the people involved, including unsolicited interaction +with those enforcing the Code of Conduct, is allowed during this period. +Violating these terms may lead to a permanent ban. + +### 4. Permanent Ban + +**Community Impact**: Demonstrating a pattern of violation of community +standards, including sustained inappropriate behavior, harassment of an +individual, or aggression toward or disparagement of classes of individuals. + +**Consequence**: A permanent ban from any sort of public interaction within +the community. + +## Attribution + +This Code of Conduct is adapted from the [Contributor Covenant][homepage], +version 2.0, available at +https://www.contributor-covenant.org/version/2/0/code_of_conduct.html. + +Community Impact Guidelines were inspired by [Mozilla's code of conduct +enforcement ladder](https://github.com/mozilla/diversity). + +[homepage]: https://www.contributor-covenant.org + +For answers to common questions about this code of conduct, see the FAQ at +https://www.contributor-covenant.org/faq. Translations are available at +https://www.contributor-covenant.org/translations. From cbab6b375f8971cddcdeb561ee9fdeb3de331639 Mon Sep 17 00:00:00 2001 From: Muhammet Kara Date: Sat, 20 Dec 2025 01:43:56 +0300 Subject: [PATCH 3/7] Create CONTRIBUTING.md with contribution guidelines Added guidelines for contributing, issue submission, and signing commits. --- CONTRIBUTING.md | 43 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 43 insertions(+) create mode 100644 CONTRIBUTING.md diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md new file mode 100644 index 0000000..dcb58b7 --- /dev/null +++ b/CONTRIBUTING.md @@ -0,0 +1,43 @@ +# Contributing to Make Traffic Integration JS Library + +The following is a set of rules and guidelines for contributing to this repo. Please feel free to propose changes to this document in a pull request. + +## Submitting issues + +If you have questions about integrating Make Traffic Integration JS Library into your app, or need help, please contact us via community@make.services + +### Guidelines +* Please search the existing issues first, it's likely that your issue was already reported or even fixed. + - Go to the main page of the repository, click "issues" and type any word in the top search/command bar. + - You can also filter by appending e. g. "state:open" to the search string. + - More info on [search syntax within GitHub](https://help.github.com/articles/searching-issues) + +## Contributing to Make Traffic Integration JS Library + +All contributions to this repository are considered to be licensed under Apache License 2.0. + +Workflow for bug fixes: +* Check open issues and unmerged pull requests to make sure the topic is not already covered elsewhere +* Fork the repository +* Do your changes on your fork +* Make sure to add or update relevant test cases +* Create a pull request, with a suitable title and description, referring to the related issue + +### Sign your work + +We use the Developer Certificate of Origin (DCO) as a additional safeguard +for the Make Traffic Integration JS Library project. This is a well established and widely used +mechanism to assure contributors have confirmed their right to license +their contribution under the project's license. +Please read [developer-certificate-of-origin](https://github.com/make-software/make-traffic-integration-lib/blob/master/.github/developer-certificate-of-origin). +If you can certify it, then just add a line to every git commit message: + +```` + Signed-off-by: Random J Developer +```` + +Use your real name (sorry, no pseudonyms or anonymous contributions). +If you set your `user.name` and `user.email` git configs, you can sign your +commit automatically with `git commit -s`. You can also use git [aliases](https://git-scm.com/book/tr/v2/Git-Basics-Git-Aliases) +like `git config --global alias.ci 'commit -s'`. Now you can commit with +`git ci` and the commit will be signed. From c9d19fa1c00e185d7a93cce9efff87f82ae7df01 Mon Sep 17 00:00:00 2001 From: Muhammet Kara Date: Sat, 20 Dec 2025 01:46:44 +0300 Subject: [PATCH 4/7] Revise SECURITY.md for clarity and updates Removed supported versions section and updated vulnerability reporting instructions. --- SECURITY.md | 5 +++++ 1 file changed, 5 insertions(+) create mode 100644 SECURITY.md diff --git a/SECURITY.md b/SECURITY.md new file mode 100644 index 0000000..fd9c9a3 --- /dev/null +++ b/SECURITY.md @@ -0,0 +1,5 @@ +# Security Policy + +## Reporting a Vulnerability + +If you find a security vulnerability in Make Traffic Integration JS Library, please send an email to *security@make.software*. From 0731254f8f56270465465f90bf11da876bf56236 Mon Sep 17 00:00:00 2001 From: Muhammet Kara Date: Sat, 20 Dec 2025 02:16:20 +0300 Subject: [PATCH 5/7] Update issue templates --- .github/ISSUE_TEMPLATE/bug_report.md | 84 +++++++++++++++++++++++ .github/ISSUE_TEMPLATE/feature_request.md | 57 +++++++++++++++ 2 files changed, 141 insertions(+) create mode 100644 .github/ISSUE_TEMPLATE/bug_report.md create mode 100644 .github/ISSUE_TEMPLATE/feature_request.md diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md new file mode 100644 index 0000000..c89ddda --- /dev/null +++ b/.github/ISSUE_TEMPLATE/bug_report.md @@ -0,0 +1,84 @@ +--- +name: Bug report +about: Create a report to help us improve +title: "[BUG] " +labels: '' +assignees: koltsov-iv + +--- + +**Describe the bug** +A clear and concise description of what the bug is. Include whether the issue occurs in the core library, a specific framework wrapper (e.g., React), or the example application. + +**Library and Version** +- Core library version: [e.g., 1.0.0] +- Wrapper library (if applicable): [e.g., make-traffic-integration-react-wrapper] +- Wrapper version: [e.g., 1.0.0] +- Node.js version: [e.g., 18.0.0] + +**To Reproduce** +Steps to reproduce the behavior: +1. Initialize TaskManagerApp with [describe your configuration] +2. Call [method name, e.g., `getTasks()`, `claimProcess()`] +3. [Any additional steps] +4. See error + +**Expected behavior** +A clear and concise description of what you expected to happen. + +**Actual behavior** +What actually happened instead. Include any error messages or unexpected output. + +**Code Example** +If applicable, provide a minimal code example that reproduces the issue: + +```typescript +// Your code here +import { TaskManagerApp } from "make-traffic-integration-core"; + +const appConfig = { + apiUrl: 'https://...', + appKey: 'your-app-key', +}; + +const taskManager = new TaskManagerApp(appConfig); +// Steps to reproduce the bug +``` + +**Error Messages and Logs** +If applicable, include: +- Full error stack trace +- Console logs +- Network request/response details (from browser DevTools) +- Event subscription callback errors + +**Environment** +- **Operating System**: [e.g., macOS, Windows, Linux] +- **Browser** (if applicable): [e.g., Chrome, Firefox, Safari] +- **Browser Version** (if applicable): [e.g., 120.0] +- **Package Manager**: [e.g., npm, yarn, pnpm] +- **TypeScript Version** (if using TypeScript): [e.g., 5.0] + +**Affected Components** +- [ ] Core library (`make-traffic-integration-core`) +- [ ] React wrapper (`make-traffic-integration-react-wrapper`) +- [ ] Example application (`examples/react-app`) +- [ ] Other: [please specify] + +**API Integration Details** (if relevant) +- API URL being used: [e.g., https://make-traffic-integration.dot.com] +- User ID format: [e.g., string, UUID] +- Task type/category: [if applicable] + +**Screenshots or Network Traces** +If applicable, add screenshots or network traces to help explain your problem. Include: +- Browser DevTools Network tab showing API requests/responses +- Console error messages +- UI state when the bug occurs + +**Additional context** +Add any other context about the problem here, such as: +- Whether this is a regression (worked in a previous version) +- Frequency of occurrence (always, intermittent, etc.) +- Any workarounds you've found +- Related issues or discussions diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.md new file mode 100644 index 0000000..8f14f34 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/feature_request.md @@ -0,0 +1,57 @@ +--- +name: Feature request +about: Suggest an idea for this project +title: "[FEATURE] " +labels: '' +assignees: koltsov-iv + +--- + +**Is your feature request related to a problem? Please describe.** +A clear and concise description of what the problem is or what limitation you're experiencing. For example: "I'm always frustrated when [the task manager doesn't support batch operations]" or "Currently, there's no way to [filter tasks by category]." + +**Describe the solution you'd like** +A clear and concise description of what you want to happen. Include details such as: +- Which component(s) would be affected: core library, React wrapper, or both? +- What new method(s) or functionality would be needed? +- How would this integrate with existing APIs like `TaskManagerApp`, `getTasks()`, `claimProcess()`, etc.? +- Would this require new event types? + +**Use Case and Impact** +Explain the use case for this feature: +- How would this improve the developer experience? +- What problems does it solve? +- How many users/projects would benefit from this feature? +- Is this a critical feature or a nice-to-have enhancement? + +**Describe alternatives you've considered** +A clear and concise description of any alternative solutions or features you've considered. For example: +- Workarounds you're currently using +- Other libraries or approaches that provide similar functionality +- Why those alternatives are not sufficient + +**Implementation Suggestions** (optional) +If you have ideas about how this could be implemented, share them: +- Proposed API design or method signatures +- Changes to existing interfaces or types +- New event types that might be needed +- Impact on the React wrapper or other framework-specific implementations + +**Affected Components** +- [ ] Core library (`make-traffic-integration-core`) +- [ ] React wrapper (`make-traffic-integration-react-wrapper`) +- [ ] Example application (`examples/react-app`) +- [ ] Documentation +- [ ] Other: [please specify] + +**Priority and Scope** +- **Priority**: [Low / Medium / High] +- **Scope**: [Small enhancement / Medium feature / Large feature] +- **Breaking Changes**: Would this require breaking changes to existing APIs? [Yes / No] + +**Additional context** +Add any other context, screenshots, or mockups about the feature request here. Include: +- Links to related issues or discussions +- Examples of how similar features are implemented in other libraries +- Any relevant code snippets or configuration examples +- User feedback or community requests From a62563ef6d665480c11478612fdcedb544496769 Mon Sep 17 00:00:00 2001 From: Muhammet Kara Date: Sat, 20 Dec 2025 02:24:16 +0300 Subject: [PATCH 6/7] Create pull_request_template.md for PR submissions Added a pull request template to standardize submissions. --- .github/pull_request_template.md | 36 ++++++++++++++++++++++++++++++++ 1 file changed, 36 insertions(+) create mode 100644 .github/pull_request_template.md diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md new file mode 100644 index 0000000..6258dfd --- /dev/null +++ b/.github/pull_request_template.md @@ -0,0 +1,36 @@ +## Resolves +Closes # + +## Summary +Brief description of changes and why they're needed. + +## Type of Change +- [ ] Bug fix +- [ ] New feature +- [ ] Breaking change +- [ ] Documentation update + +## Affected Components +- [ ] Core library +- [ ] React wrapper +- [ ] Example application +- [ ] Other: [specify] + +## Changes +- What was changed? +- What new methods/types were added (if any)? + +## Testing +- [ ] Tests added/updated +- [ ] Manual testing performed +- [ ] No tests needed + +## API Changes (if applicable) +Describe any changes to `TaskManagerApp`, method signatures, or `Events`. + +## Checklist +- [ ] Code is properly formatted +- [ ] All commits are signed +- [ ] Tests included/updated or not needed +- [ ] Documentation updated or not required +- [ ] No breaking changes (or documented if present) From 571b9f6fbd44f919421173f221cc4fd1da89f873 Mon Sep 17 00:00:00 2001 From: Muhammet Kara Date: Sat, 20 Dec 2025 02:33:14 +0300 Subject: [PATCH 7/7] Add developer certificate of origin --- .github/developer-certificate-of-origin | 35 +++++++++++++++++++++++++ 1 file changed, 35 insertions(+) create mode 100644 .github/developer-certificate-of-origin diff --git a/.github/developer-certificate-of-origin b/.github/developer-certificate-of-origin new file mode 100644 index 0000000..a6bbb98 --- /dev/null +++ b/.github/developer-certificate-of-origin @@ -0,0 +1,35 @@ +Developer Certificate of Origin +Version 1.1 + +Copyright (C) 2004, 2006 The Linux Foundation and its contributors. +660 York Street, Suite 102, +San Francisco, CA 94110 USA + +Everyone is permitted to copy and distribute verbatim copies of this +license document, but changing it is not allowed. + +Developer's Certificate of Origin 1.1 + +By making a contribution to this project, I certify that: + +(a) The contribution was created in whole or in part by me and I + have the right to submit it under the open source license + indicated in the file; or + +(b) The contribution is based upon previous work that, to the best + of my knowledge, is covered under an appropriate open source + license and I have the right under that license to submit that + work with modifications, whether created in whole or in part + by me, under the same open source license (unless I am + permitted to submit under a different license), as indicated + in the file; or + +(c) The contribution was provided directly to me by some other + person who certified (a), (b) or (c) and I have not modified + it. + +(d) I understand and agree that this project and the contribution + are public and that a record of the contribution (including all + personal information I submit with it, including my sign-off) is + maintained indefinitely and may be redistributed consistent with + this project or the open source license(s) involved.