├── COMMITTERS.csv ├── tests └── README.md ├── THIRD_PARTY.md ├── tsc ├── meetings │ └── README.md ├── README.md └── CHARTER.md ├── CODE_OF_CONDUCT.md ├── CHANGELOG.md ├── .github ├── workflows │ ├── send_agenda.yml │ ├── create_agenda.yml │ └── repolinter.yml ├── ISSUE_TEMPLATE │ ├── feature_request.md │ ├── bug_report.md │ └── meeting.md └── PULL_REQUEST_TEMPLATE │ └── pull_request_template.md ├── .gitignore ├── SECURITY.md ├── INSTRUCTIONS.md ├── SUPPORT.md ├── README.md ├── CONTRIBUTING.md ├── GOVERNANCE.md └── LICENSE /COMMITTERS.csv: -------------------------------------------------------------------------------- 1 | Name, Email, Github ID 2 | -------------------------------------------------------------------------------- /tests/README.md: -------------------------------------------------------------------------------- 1 | Any test for this project go in this folder. If there are no tests, please keep this folder to avoid repolinter errors and notate in this field why. 2 | -------------------------------------------------------------------------------- /THIRD_PARTY.md: -------------------------------------------------------------------------------- 1 | _Use this file to list out any third-party dependencies used by this project. You may choose to point to a Gemfile or other language specific packaging file for details._ 2 | -------------------------------------------------------------------------------- /tsc/meetings/README.md: -------------------------------------------------------------------------------- 1 | # TSC Meeting notes 2 | 3 | All TSC meeting notes are stored here in YYYY-MM-DD.md format. Recordings and other assets from conference calls systems can also be stored in YYYY-MM-DD.XXX format. 4 | -------------------------------------------------------------------------------- /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | This is a project hosted under the LF AI Foundation. As such, we would like to urge you to please be mindful of and adhere to the Linux Foundation’s Code of Conduct when contributing to the OpenBytes. 2 | 3 | If you have any questions or concerns, please email conduct@lfai.foundation. 4 | 5 | Thank you. 6 | -------------------------------------------------------------------------------- /CHANGELOG.md: -------------------------------------------------------------------------------- 1 | # Changelog 2 | 3 | All notable changes to this project will be documented in this file. 4 | 5 | The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), 6 | and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). 7 | 8 | ## [Unreleased] 9 | 10 | ### Added 11 | 12 | ### Changed 13 | 14 | ### Removed 15 | -------------------------------------------------------------------------------- /.github/workflows/send_agenda.yml: -------------------------------------------------------------------------------- 1 | name: Send TSC meeting agenda to email list 2 | on: 3 | issues: 4 | types: [opened] 5 | jobs: 6 | build: 7 | runs-on: ubuntu-latest 8 | steps: 9 | - uses: timheuer/issue-notifier@v1 10 | env: 11 | SENDGRID_API_KEY: ${{ secrets.SENDGRID_API_KEY }} 12 | with: 13 | fromMailAddress: 'tac@openmainframeproject.org' 14 | toMailAddress: '[MAILING LIST EMAIL]' 15 | subject: 'TSC meeting agenda' 16 | labelsToMonitor: 'meeting' 17 | -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | # General 2 | .DS_Store 3 | .AppleDouble 4 | .LSOverride 5 | 6 | # Icon must end with two \r 7 | Icon 8 | 9 | # Thumbnails 10 | ._* 11 | 12 | # Files that might appear in the root of a volume 13 | .DocumentRevisions-V100 14 | .fseventsd 15 | .Spotlight-V100 16 | .TemporaryItems 17 | .Trashes 18 | .VolumeIcon.icns 19 | .com.apple.timemachine.donotpresent 20 | 21 | # Directories potentially created on remote AFP share 22 | .AppleDB 23 | .AppleDesktop 24 | Network Trash Folder 25 | Temporary Items 26 | .apdisk 27 | 28 | -------------------------------------------------------------------------------- /.github/workflows/create_agenda.yml: -------------------------------------------------------------------------------- 1 | # TODO: 'schedules' will need to be updated to coincide with the meeting frequency 2 | 3 | name: Schedule TSC meetings 4 | on: 5 | workflow_dispatch: 6 | # schedule: 7 | # - cron: '0 0 * * *' 8 | jobs: 9 | build: 10 | runs-on: ubuntu-latest 11 | steps: 12 | - uses: pkgjs/meet 13 | with: 14 | token: ${{ secrets.GITHUB_TOKEN }} 15 | schedules: 2020-05-14T17:00:00.0Z/P4W 16 | createWithin: P1D 17 | issueTitle: "TSC Meeting <%= date.toFormat('yyyy-MM-dd') %>" 18 | agendaLabel: meeting-agenda 19 | -------------------------------------------------------------------------------- /.github/workflows/repolinter.yml: -------------------------------------------------------------------------------- 1 | name: Weekly Lint repository 2 | on: 3 | schedule: 4 | - cron: "0 0 * * 0" 5 | workflow_dispatch: 6 | 7 | jobs: 8 | repo-lint: 9 | name: "repolint" 10 | runs-on: ubuntu-latest 11 | steps: 12 | - name: "Checkout repo" 13 | uses: actions/checkout@v2.0.0 14 | with: 15 | fetch-depth: 0 16 | - name: "Install Node.js" 17 | uses: actions/setup-node@v1 18 | with: 19 | node-version: '12.x' 20 | - name: "Install repolinter" 21 | run: npm install -g repolinter 22 | - name: "Run repolinter" 23 | run: repolinter lint --dryRun -g $GITHUB_SERVER_URL/$GITHUB_REPOSITORY 24 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/feature_request.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Feature request 3 | about: Suggest an idea for this project 4 | title: '' 5 | labels: '' 6 | assignees: '' 7 | 8 | --- 9 | 10 | **Is your feature request related to a problem? Please describe.** 11 | A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] 12 | 13 | **Describe the solution you'd like** 14 | A clear and concise description of what you want to happen. 15 | 16 | **Describe alternatives you've considered** 17 | A clear and concise description of any alternative solutions or features you've considered. 18 | 19 | **Additional context** 20 | Add any other context or screenshots about the feature request here. 21 | -------------------------------------------------------------------------------- /SECURITY.md: -------------------------------------------------------------------------------- 1 | # Security Policy 2 | 3 | ## Supported Versions 4 | 5 | Use this section to tell people about which versions of your project are 6 | currently being supported with security updates. 7 | 8 | | Version | Supported | 9 | | ------- | ------------------ | 10 | | 5.1.x | :white_check_mark: | 11 | | 5.0.x | :x: | 12 | | 4.0.x | :white_check_mark: | 13 | | < 4.0 | :x: | 14 | 15 | ## Reporting a Vulnerability 16 | 17 | Use this section to tell people how to report a vulnerability. 18 | 19 | Tell them where to go, how often they can expect to get an update on a 20 | reported vulnerability, what to expect if the vulnerability is accepted or 21 | declined, etc. 22 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/bug_report.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Bug report 3 | about: Create a report to help us improve 4 | title: '' 5 | labels: '' 6 | assignees: '' 7 | 8 | --- 9 | 10 | **Describe the bug** 11 | A clear and concise description of what the bug is. 12 | 13 | **To Reproduce** 14 | Steps to reproduce the behavior: 15 | 1. Go to '...' 16 | 2. Click on '....' 17 | 3. Scroll down to '....' 18 | 4. See error 19 | 20 | **Expected behavior** 21 | A clear and concise description of what you expected to happen. 22 | 23 | **Screenshots** 24 | If applicable, add screenshots to help explain your problem. 25 | 26 | **Desktop (please complete the following information):** 27 | - OS: [e.g. iOS] 28 | - Browser [e.g. chrome, safari] 29 | - Version [e.g. 22] 30 | 31 | **Smartphone (please complete the following information):** 32 | - Device: [e.g. iPhone6] 33 | - OS: [e.g. iOS8.1] 34 | - Browser [e.g. stock browser, safari] 35 | - Version [e.g. 22] 36 | 37 | **Additional context** 38 | Add any other context about the problem here. 39 | -------------------------------------------------------------------------------- /INSTRUCTIONS.md: -------------------------------------------------------------------------------- 1 | # Instructions for using this template 2 | 3 | 1) Review and update (README.md) and (tsc/README.md) with the [PROJECT NAME] and [PROJECT LOGO], as well as the contents for the various sections. 4 | 2) To enable creating meeting agendas from GitHub issues, follow steps 3-5. 5 | 3) In the [meeting agenda template](.github/ISSUE_TEMPLATE/meeting.md), update `[PROJECT NAME]` and add the TSC members under the ['Attendance' section](.github/ISSUE_TEMPLATE/meeting.md#attendance). 6 | 4) Set the meeting date and time, along with the cadence in the [build agenda workflow](.github/workflows/build_agenda.yml) in the key `schedules:` that specifies a ISO-8601 interval. Examples for repeating: 7 | 8 | ``` 9 | # start 2020-04-22 at 16:00, repeat every 2 weeks 10 | schedules: 2020-04-22T16:00:00.0Z/P2W 11 | # start 2020-04-22 at 16:00, repeat every 7 days 12 | schedules: 2020-06-22T16:00:00.0Z/P7D 13 | ``` 14 | 5) In the [send agenda workflow](.github/workflows/send_agenda.yml), update `[PROJECT NAME]` and `[MAILING LIST EMAIL]`. 15 | 6) Any items with the label `meeting` will be added to the agenda automatically when it is built the day prior to the meeting. 16 | -------------------------------------------------------------------------------- /SUPPORT.md: -------------------------------------------------------------------------------- 1 | 2 | 3 | # Getting Help 4 | 5 | There are a few ways to connect with the PROJECT NAME project: 6 | 7 | * Drop an [email] (mailto:contact@openbytes.io) 8 | * Connect on [Slack](https://join.slack.com/t/openbytes/shared_invite/zt-xmlybz36-kc7SnQnmrIyz1m79oOu6pg) 9 | * submit an [issue](https://github.com/Project-OpenBytes/OpenBytes/issues) 10 | 11 | ## How to Ask for Help 12 | 13 | If you have trouble installing, building, or using OpenBytes, but there's not yet reason to suspect you've encountered a genuine bug, 14 | start by posting a question to the mailing list or Slack channel. This is the place for question such has "How do I...". 15 | 16 | ## How to report a bug or request an enhancement 17 | 18 | OpenBytes manages bug and enhancement using it's [issue tracker]. The issue template will guide you on making an effective report. 19 | 20 | ## How to report a security vulnerability 21 | 22 | If you think you've found a potential vulnerability in PROJECT NAME, please 23 | email contact@openbytes.io to responsibly disclose it. 24 | 25 | ## Contributing a fix 26 | 27 | Please refer to [CONTRIBUTING.md](CONTRIBUTING.md) to make a project contribution. 28 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | 2 | ![](https://us-tutu.s3.us-west-1.amazonaws.com/company-website/OpenBytes/Mobile/logo.png) 3 | 4 | # OpenBytes 5 | 6 | We are a non-profit open data project hosted under the Linux Foundation with neutral governance, aiming to bring transformational changes to AI by making open datasets more available and accessible. 7 | 8 | ## Discussion 9 | 10 | You can connect with the community in a variety of ways... 11 | 12 | 13 | - [OpenBytes Slack](https://openbytes.slack.com/join/shared_invite/zt-xmlybz36-kc7SnQnmrIyz1m79oOu6pg#/shared-invite/email) 14 | 15 | ## Contributing 16 | Anyone can contribute to the OpenBytes project - learn more at [CONTRIBUTING.md](CONTRIBUTING.md) 17 | 18 | ## Governance 19 | OpenBytes is a project hosted by the [LF AI and Data Foundation](https://lfaidata.foundation). This project has established it's own processes for managing day-to-day processes in the project, and the techincal charter is located in at [GOVERNANCE.md](GOVERNANCE.md). 20 | 21 | ## Reporting Issues 22 | To report a problem, you can open an [issue](https://github.com/Project-OpenBytes/OpenBytes/issues) in repository against a specific workflow. If the issue is senstive in nature or a security related issue, please do not report in the issue tracker but instead email contact@openbytes.io. 23 | -------------------------------------------------------------------------------- /.github/PULL_REQUEST_TEMPLATE/pull_request_template.md: -------------------------------------------------------------------------------- 1 | # Description 2 | 3 | Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change. 4 | 5 | Fixes # (issue) 6 | 7 | ## Type of change 8 | 9 | Please delete options that are not relevant. 10 | 11 | - [ ] Bug fix (non-breaking change which fixes an issue) 12 | - [ ] New feature (non-breaking change which adds functionality) 13 | - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) 14 | - [ ] This change requires a documentation update 15 | 16 | # How Has This Been Tested? 17 | 18 | Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration 19 | 20 | # Checklist: 21 | 22 | - [ ] My code follows the style guidelines of this project 23 | - [ ] I have performed a self-review of my own code 24 | - [ ] I have commented my code, particularly in hard-to-understand areas 25 | - [ ] I have made corresponding changes to the documentation 26 | - [ ] My changes generate no new warnings 27 | - [ ] I have added tests that prove my fix is effective or that my feature works 28 | - [ ] New and existing unit tests pass locally with my changes 29 | - [ ] Any dependent changes have been merged and published in downstream modules 30 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/meeting.md: -------------------------------------------------------------------------------- 1 | # [PROJECT NAME] TSC Meeting - <%= date.toFormat("MMMM d, yyyy") %> 2 | 3 | ## Date/Time 4 | 5 | | Timezone | Date/Time | 6 | |----------|-----------| 7 | <%= [ 8 | 'America/Los_Angeles', 9 | 'America/Denver', 10 | 'America/Chicago', 11 | 'America/New_York', 12 | 'Europe/London', 13 | 'Europe/Amsterdam', 14 | 'Asia/Shanghai', 15 | 'Asia/Tokyo', 16 | ].map((zone) => { 17 | return `| ${zone} | ${date.setZone(zone).toFormat('EEE dd-MMM-yyyy HH:mm (hh:mm a)')} |` 18 | }).join('\n') %> 19 | 20 | Or in your local time: 21 | * https://www.timeanddate.com/worldclock/?iso=<%= date.toFormat("yyyy-MM-dd'T'HH:mm:ss") %> 22 | 23 | All meetings are listed on the project calendar at https://lists.openmainframeproject.org/calendar, subject to the mailing lists you are subscribed to. 24 | 25 | ### Conference call details 26 | 27 | _fill in Zoom details_ 28 | 29 | ### Meeting recordings 30 | 31 | _fill in recording details_ 32 | 33 | ## Attendance 34 | 35 | ### Voting member rollcall: 36 | 37 | _fill in voting members as a checklist_ 38 | 39 | ### Other Attendees 40 | 41 | 42 | ## Agenda 43 | 44 | Extracted from **<%= agendaLabel %>** labelled issues and pull requests from **<%= owner %>/<%= repo %>** prior to the meeting. 45 | 46 | * Project updates ( list at https://github.com/openmainframeproject/tac#tac-projects ) 47 | <%= agendaIssues.map((i) => { 48 | return `* ${i.title} [#${i.number}](${i.html_url})` 49 | }).join('\n') %> 50 | 51 | ## Action Items 52 | 53 | 54 | ## Notes 55 | -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | 2 | # Contributing to PROJECT OpenBytes 3 | 4 | Thank you for your interest in contributing to OpenBytes! This document explains our contribution process and procedures: 5 | 6 | * [How to Contribute a Bug Fix or Change](#How-to-Contribute-a-Bug-Fix-or-Change) 7 | * [Development Workflow](#Development-Workflow) 8 | * [Coding Style](#Coding-Style) 9 | 10 | For a description of the roles and responsibilities of the various members of the Openbytes community and further details, see the [governance policies]. Briefly, Contributors are anyone who submits content to the project, Committers review and approve such submissions, and the Technical Steering Committee provides general project oversight. 11 | 12 | If you just need help or have a question, refer to [SUPPORT.md](SUPPORT.md). 13 | 14 | ## How to Contribute a Bug Fix or Change 15 | 16 | To contribute code to the project, first read over the [governance policies] page to understand the roles involved. 17 | 18 | Each contribution must meet the [coding style] and include.. 19 | 20 | * Tests and documentation to explain the functionality. 21 | * Any new files have [copyright and license headers] 22 | * A [Developer Certificate of Origin signoff]. 23 | * Submitted to the project as a pull request. 24 | 25 | OpenBytes is licensed under the [Creative Commons Attribution 4.0 International](LICENSE) license. Contributions should abide by that standard license. 26 | 27 | Project committers will review the contribution in a timely manner, and advise of any changes needed to merge the request. 28 | 29 | 30 | [governance policies]: GOVERNANCE.md 31 | [copyright and license headers]: https://github.com/lfai/tac/blob/main/process/contribution_guidelines.md#license 32 | [Developer Certificate of Origin signoff]: https://github.com/lfai/tac/blob/main/process/contribution_guidelines.md#contribution-sign-off 33 | 34 | -------------------------------------------------------------------------------- /tsc/README.md: -------------------------------------------------------------------------------- 1 | # TSC Materials for [PROJECT NAME] 2 | 3 | This directory contains the meeting notes, process documentations, and other materials related to this project. 4 | 5 | ## Project Intake checklist 6 | 7 | This is a checklist for TSC's to review as part of the intake process. The TSC should review this entire list during the kickoff meeting. For anything outstanding, create an [issue](../issues) to track and link to it in the list 8 | 9 | ### Prior to Project Contribution Proposal 10 | 11 | - [ ] Project license identified and exists in root directory of all repos ( named LICENSE ) 12 | - [ ] Any third-party components/dependencies included are listed along with thier licenses ( example template at [THIRD_PARTY.md](../THIRD_PARTY.md) ) 13 | - [ ] Code scan completed and any recommendations remedyed. 14 | - [ ] README.md file exists ( template started at [README.md](../README.md) ) 15 | - [ ] Governance defined, outlining community roles and how decisions are made ( starting point at [GOVERNANCE.md](../GOVERNANCE.md) if needed ). 16 | - [ ] Contribution Policy defined ( [CONTRIBUTING](../CONTRIBUTING.md) 17 | - [ ] Code of Conduct defined ( default is at [CODE_OF_CONDUCT.md](../CODE_OF_CONDUCT.md) - if using a different code of conduct please contact [LF AI and Data Staff](mailto:operations@lfaidata.foundation) ). 18 | - [ ] Release methodology defined ( [RELEASE.md](../RELEASE.md) ) 19 | - [ ] Release/Testing process defined ( [RELEASE.md](../RELEASE.md) ) 20 | - [ ] Committers/Maintainers defined in the project ( [COMMITTERS](COMMITTERS.csv) or MAINTAINERS file - recommended to be in a CSV format for machine parsing) 21 | - [ ] Project support policies defined ( [SUPPORT](../SUPPORT.md) ) 22 | 23 | ### Project Proposal 24 | 25 | - [ ] Project Charter completed and approved ( [CHARTER](CHARTER.md) ) 26 | - [ ] Trademarks/mark ownership rights ( complete [LF Projects - Form of Trademark and Account Assignment](lf_projects_trademark_assignment.md) ) 27 | - [ ] Submit a completed Project Contribution Proposal via a GitHub pull request to https://github.com/lfai/proposing-projects/tree/master/proposals. 28 | - [ ] Presentation scheduled on the TAC calendar. 29 | - [ ] Prepare a presentation on the project for the TAC meeting. 30 | 31 | ### Post Acceptance 32 | 33 | - Project assets 34 | - [ ] Domain name ( create [service desk request] to setup/transfer ) 35 | - [ ] Social media accounts ( create [service desk request] to setup/transfer ) 36 | - [ ] Logo(s) ( create [service desk request] to create]; will be added to [artwork repo] in SVG and PNG format and color/black/white ) 37 | - Infrastructure 38 | - [ ] Source Control (Github, GitLab, something else ) and LF AI and Data Staff is an administrator. 39 | - [ ] Developer Certificate of Origin past commit signoff done and DCO Probot enabled. 40 | - [ ] Issue/feature tracker (JIRA, GitHub issues) and LF AI and Data Staff is an administrator. 41 | - Collaboration tools 42 | - [ ] Mailing lists - one of: 43 | - [ ] Create new list(s) ( default is -discussion@ and -private@ - create [service desk request] to provision ) 44 | - [ ] Move to groups.io ( create [service desk request] to setup/transfer ) 45 | - [ ] Establish project calendar on groups.io ( refer to [tac guidelines]) 46 | - [ ] Slack or IRC ( create [service desk request] to setup Slack project channel ) 47 | - [ ] Website ( refer to [tac guidelines] ) 48 | - [ ] CI/build environment 49 | - [ ] Add project to [LFX Insights] ( create [service desk request] to trigger ) 50 | - TSC Formation 51 | - [ ] TSC members identified, added to [GOVERNANCE.md]. 52 | - [ ] First TSC meeting held ( [agenda](meetings) ) 53 | - [ ] TSC Chairperson identified and added to [GOVERNANCE.md] 54 | - [ ] TSC meeting cadence set and added to project calendar (https://lists.lfaidata.foundation/calendar) 55 | - [ ] TSC meeting minutes saved under (meetings). 56 | - Outreach 57 | - [ ] New project announcement done ( create [service desk request] to trigger ) 58 | - [ ] Project added to LF AI and Data website and LF AI and Data landscape 59 | 60 | ### Stage requirements 61 | 62 | #### Incubation Stage requirements 63 | 64 | - [ ] CII Badge achieved ( apply at https://bestpractices.coreinfrastructure.org/en ) 65 | - [ ] Have at least two organizations actively contributing to the project. 66 | - [ ] Have a defined Technical Steering Committee (TSC) with a chairperson identified, with open and transparent communication. 67 | - [ ] Have a sponsor who is an existing LF AI & Data member. Alternatively, a new organization would join LF AI & Data and sponsor the project’s incubation application. 68 | - [ ] Have at least 300 stars on GitHub; this is an existing requirement for a project to be listed on the LF AI & Data landscape. 69 | - [ ] Submit a request for Incubation stage review by the TAC. 70 | - [ ] Presentation scheduled on the TAC calendar. 71 | - [ ] Prepare a presentation on the project for the TAC meeting. 72 | - [ ] Affirmative vote of the TAC 73 | - [ ] Affirmative vote of the Governing Board. 74 | 75 | #### Graduation Stage Requirements 76 | 77 | - [ ] Have a healthy number of code contributions coming from at least five organizations. 78 | - [ ] Have reached a minimum of 1000 stars on GitHub. 79 | - [ ] Have achieved and maintained a Core Infrastructure Initiative Best Practices Gold Badge. 80 | - [ ] Have demonstrated a substantial ongoing flow of commits and merged contributions for the past 12 months. 81 | - [ ] Have completed at least one collaboration with another LF AI & Data hosted project 82 | - [ ] Have a technical lead appointed for representation of the project on the LF AI & Data Technical Advisory Council. 83 | - [ ] Submit a request for Incubation stage review by the TAC. 84 | - [ ] Presentation scheduled on the TAC calendar. 85 | - [ ] Prepare a presentation on the project for the TAC meeting. 86 | - [ ] Affirmative vote of two-thirds of the TAC. 87 | - [ ] Affirmative vote of the Governing Board. 88 | 89 | 90 | [artwork repo]: https://artwork.lfaidata.foundation 91 | [service desk request]: https://github.com/lfai/foundation/issues/new/choose 92 | [tac guidelines]: https://github.com/lfai/tac 93 | [GOVERNANCE.md]: ../GOVERNANCE.md 94 | [LFX Insights]: https://insights.lfx.linuxfoundation.org/projects/lfai-f 95 | -------------------------------------------------------------------------------- /tsc/CHARTER.md: -------------------------------------------------------------------------------- 1 | _Template - update with Adopted Date when TSC approves and send to operations@lfaidata.foundation to file_ 2 | 3 | # Technical Charter (the "Charter") for [PROJECT NAME] a Series of LF Projects, LLC 4 | 5 | **Adopted [DATE]** 6 | 7 | This charter (the "Charter") sets forth the responsibilities and procedures for technical contribution to, and oversight of, the [PROJECT NAME] project, which has been established as [PROJECT NAME] a Series of LF Projects, LLC (the "Project"). LF Projects, LLC ("LF Projects") is a Delaware series limited liability company. All Contributors to the Project must comply with the terms of this Charter. 8 | 9 | ## 1. Mission and Scope of the Project 10 | * **a.** The mission of the Project is [MISSION]. 11 | * **b.** The scope of the Project includes software development under an OSI-approved open source license supporting the mission, including documentation, testing, integration and the creation of other artifacts that aid the development, deployment, operation or adoption of the open source software project. 12 | 13 | ## 2. Technical Steering Committee 14 | * **a.** The Technical Steering Committee (the "TSC") will be responsible for all technical oversight of the open source Project. 15 | * **b.** The TSC voting members are initially the Project's Committers. At the inception of the project, the Committers of the Project will be as set forth within the "CONTRIBUTING" file within the Project's code repository. The TSC may choose an alternative approach for determining the voting members of the TSC, and any such alternative approach will be documented in the CONTRIBUTING file. Any meetings of the Technical Steering Committee are intended to be open to the public, and can be conducted electronically, via teleconference, or in person. 16 | * **c.** TSC projects generally will involve Contributors and Committers. The TSC may adopt or modify roles so long as the roles are documented in the CONTRIBUTING file. Unless otherwise documented: 17 | * **i.** Contributors include anyone in the technical community that contributes code, documentation, or other technical artifacts to the Project; 18 | * **ii.** Committers are Contributors who have earned the ability to modify ("commit") source code, documentation or other technical artifacts in a project's repository; and 19 | * **iii.** A Contributor may become a Committer by a majority approval of the existing Committers. A Committer may be removed by a majority approval of the other existing Committers. 20 | * **d.** Participation in the Project through becoming a Contributor and Committer is open to anyone so long as they abide by the terms of this Charter. 21 | * **e.** The TSC may (1) establish work flow procedures for the submission, approval, and closure/archiving of projects, (2) set requirements for the promotion of Contributors to Committer status, as applicable, and (3) amend, adjust, refine and/or eliminate the roles of Contributors, and Committers, and create new roles, and publicly document any TSC roles, as it sees fit. 22 | * **f.** The TSC may elect a TSC Chair, who will preside over meetings of the TSC and will serve until their resignation or replacement by the TSC. The TSC Chair, or any other TSC member so designated by the TSC, will serve as the primary communication contact between the Project and the Technical Advisory Council of the Academy Software Foundation of The Linux Foundation. 23 | * **g.** Responsibilities: The TSC will be responsible for all aspects of oversight relating to the Project, which may include: 24 | * **i.** coordinating the technical direction of the Project; 25 | * **ii.** approving project or system proposals (including, but not limited to, incubation, deprecation, and changes to a sub-project's scope); 26 | * **iii.** organizing sub-projects and removing projects; 27 | * **iv.** creating sub-committees or working groups to focus on cross-project technical issues and requirements; 28 | * **v.** appointing representatives to work with other open source or open standards communities; 29 | * **vi.** establishing community norms, workflows, issuing releases, and security issue reporting policies; 30 | * **vii.** approving and implementing policies and processes for contributing (to be published in the CONTRIBUTING file) and coordinating with the Series Manager to resolve matters or concerns that may arise as set forth in Section 7 of this Charter; 31 | * **viii.** discussions, seeking consensus, and where necessary, voting on technical matters relating to the code base that affect multiple projects; and 32 | * **ix.** coordinating any marketing, events, or communications regarding the Project with the LF Projects Manager or their designee. 33 | 34 | ## 3. TSC Voting 35 | * **a.** While the Project aims to operate as a consensus based community, if any TSC decision requires a vote to move the Project forward, the voting members of the TSC will vote on a one vote per voting member basis. 36 | * **b.** Quorum for TSC meetings requires at least two-thirds of all voting members of the TSC to be present. The TSC may continue to meet if quorum is not met, but will be prevented from making any decisions at the meeting. 37 | * **c.** Except as provided in Section 7.c. and 8.a, decisions by vote at a meeting require a majority vote of those in attendance, provided quorum is met. Decisions made by electronic vote without a meeting require a majority vote of all voting members of the TSC. 38 | * **d.** In the event a vote cannot be resolved by the TSC, any voting member of the TSC may refer the matter to the Series Manager for assistance in reaching a resolution. 39 | 40 | ## 4. Compliance with Policies 41 | * **a.** This Charter is subject to the Series Agreement for the Project and the Operating Agreement of LF Projects. Contributors will comply with the policies of LF Projects as may be adopted and amended by LF Projects, including, without limitation the policies listed at https://lfprojects.org/policies/. 42 | * **b.** The TSC may adopt a code of conduct ("CoC") for the Project, which is subject to approval by the Series Manager. Contributors to the Project will comply with the CoC or, in the event that a Project-specific CoC has not been approved, the LF Projects Code of Conduct listed at https://lfprojects.org/policies/. 43 | * **c.** When amending or adopting any policy applicable to the Project, LF Projects will publish such policy, as to be amended or adopted, on its web site at least 30 days prior to such policy taking effect; provided, however, that in the case of any amendment of the Trademark Policy or Terms of Use of LF Projects, any such amendment is effective upon publication on LF Projects web site. 44 | * **d.** All participants must allow open participation from any individual or organization meeting the requirements for contributing under this Charter and any policies adopted for all participants by the TSC, regardless of competitive interests. Put another way, the Project community must not seek to exclude any participant based on any criteria, requirement, or reason other than those that are reasonable and applied on a non-discriminatory basis to all participants in the Project community. 45 | * **e.** The Project will operate in a transparent, open, collaborative, and ethical manner at all times. The output of all Project discussions, proposals, timelines, decisions, and status should be made open and easily visible to all. Any potential violations of this requirement should be reported immediately to the LF Projects Manager. 46 | 47 | ## 5. Community Assets 48 | * **a.** LF Projects shall hold title to all trade or service marks used by the Project ("Project Trademarks"), whether based on common law or registered rights. Project Trademarks shall be transferred and assigned to LF Projects to hold on behalf of the Project. Any use of any Project Trademarks by participants in the Project shall be in accordance with the license from LF Projects and inure to the benefit of LF Projects. 49 | * **b.** The Project shall, as permitted and in accordance with such license from LF Projects, develop and own all Project GitHub and social media accounts, and domain name registrations created by the Project community. 50 | * **c.** Under no circumstances shall LF Projects be expected or required to undertake any action on behalf of the Project that is inconsistent with the tax-exempt status or purpose, as applicable, of LFP, Inc. or LF Projects, LLC. 51 | 52 | ## 6. General Rules and Operations. 53 | * **a.** The Project will: 54 | * **i.** engage in the work of the project in a professional manner consistent with maintaining a cohesive community, while also maintaining the goodwill and esteem of LF Projects, LFP, Inc. and other partner organizations in the open source software community; and 55 | * **ii.** respect the rights of all trademark owners, including any branding and trademark usage guidelines. 56 | 57 | ## 7. Intellectual Property Policy 58 | * **a.** Participants acknowledge that the copyright in all new contributions shall be retained by the copyright holder as independent works of authorship and that no contributor or copyright holder will be required to assign copyrights to the Project. 59 | * **b.** Except as described in Section 7.c., all code contributions to the Project are subject to the following: 60 | * **i.** All new inbound code contributions to the Project must be made using the **[Apache License, Version 2.0 (available here: https://www.apache.org/licenses/LICENSE-2.0)]** (the "Project License"). 61 | * **ii.** All new inbound code contributions must be accompanied by a Developer Certificate of Origin (http://developercertificate.org) sign-off in the source code system that is submitted through a TSC-approved contribution process which will bind the authorized contributor and, if not self-employed, their employer to the applicable license; 62 | * **iii.** All outbound code will be made available under the Project License. 63 | * **iv.** Documentation will be received and made available by the Project under the Creative Commons Attribution 4.0 International License (available at http://creativecommons.org/licenses/by/4.0/). 64 | * **v.** The Project may seek to integrate and contribute back to other open source projects ("Upstream Projects"). In such cases, the Project will conform to all license requirements of the Upstream Projects, including dependencies, leveraged by the Project. Upstream Project code contributions not stored within the Project's main code repository shall comply with the contribution process and license terms for the applicable Upstream Project. 65 | * **c.** If an alternative inbound or outbound license is required for compliance with the license for a leveraged open source project or is otherwise required to achieve the Project's mission, the Governing Board of the Academy Software Foundation of The Linux Foundation ("Governing Board") or the Governing Board's designated committee may approve the use of an alternative license for specific inbound or outbound contributions on an exception basis. Any exceptions must be approved by a vote of the Governing Board and must be limited in scope to what is required for such purpose. To request an exception, please describe the contribution, the alternative open source license(s), and the justification for using an alternative open source license for the Project. 66 | * **d.** Contributed files should contain license information, such as SPDX short form identifiers, indicating the open source license or licenses pertaining to the file. 67 | 68 | ## 8. Amendments 69 | * **a.** This charter may be amended by a two-thirds vote of the entire TSC and is subject to approval by LF Projects. 70 | -------------------------------------------------------------------------------- /GOVERNANCE.md: -------------------------------------------------------------------------------- 1 | # **Technical Charter (the "Charter") for OpenBytes a Series of LF Projects, LLC** 2 | 3 | 4 | 5 | **Adopted October 2, 2020** 6 | 7 | This Charter sets forth the responsibilities and procedures for 8 | technical contribution to, and oversight of, the OpenBytes open source 9 | project, which has been established as OpenBytes a Series of LF 10 | Projects, LLC (the "Project"). LF Projects, LLC ("LF Projects") is a 11 | Delaware series limited liability company. All contributors (including 12 | committers, maintainers, and other technical positions) and other 13 | participants in the Project (collectively, "Collaborators") must comply 14 | with the terms of this Charter. 15 | 16 | > **1. Mission and Scope of the Project** 17 | > 18 | > a\. The mission of the Project is to facilitate wider sharing of, and collaboration with, data in the AI community through the creation of data standards and formats and enabling contributions of data. 19 | > 20 | > b\. The scope of the Project includes the curation of open datasets, open data specifications and collaborative development under open licenses (OSI-approved in the case of open source software) supporting the mission, including documentation, testing, integration and the creation of other artifacts that aid the development, deployment, operation or adoption of the open source project. The Project intends to combine a data warehouse, data lake, and user-friendly front end, and it intends to incorporate both structured and unstructured data from public sources and contributing participants. 21 | > 22 | > **2. Technical Steering Committee** 23 | > 24 | > a\. The Technical Steering Committee (the "TSC") will be responsible for all technical oversight of the Project. 25 | > 26 | > b\. The TSC voting members are initially the Project's Committers. At the inception of the project, the Committers of the Project will be as set forth within the "CONTRIBUTING" file within the Project's code repository. The TSC may choose an alternative approach for determining the voting members of the TSC, and any such alternative approach will be documented in the CONTRIBUTING file. Any meetings of the Technical Steering Committee are intended to be open to the public, and can be conducted electronically, via teleconference, or in person. 27 | 28 | 29 | > c\. TSC projects generally will involve Contributors and Committers. The TSC may adopt or modify roles so long as the roles are documented in the CONTRIBUTING file. Unless otherwise documented: 30 | > 31 | > i\. Contributors include anyone in the technical community that contributes data, data specifications, software source code, documentation, or other technical artifacts to the Project; 32 | > 33 | > ii\. Committers are Contributors who have earned the ability to modify ("commit") data, data specifications, software source code, documentation or other technical artifacts in a project's repository; and 34 | 35 | > iii\. A Contributor may become a Committer by a majority approval of the existing Committers. A Committer may be removed by a majority approval of the other existing Committers. 36 | > 37 | > d\. Participation in the Project through becoming a Contributor and Committer is open to anyone so long as they abide by the terms of this Charter. 38 | > 39 | > e\. The TSC may (1) establish work flow procedures for the submission, approval, and closure/archiving of projects, (2) set requirements for the promotion of Contributors to Committer status, as applicable, and (3) amend, adjust, refine and/or eliminate the roles of Contributors, and Committers, and create new roles, and publicly document any TSC roles, as it sees fit. 40 | > 41 | > f\. The TSC may elect a TSC Chair, who will preside over meetings of the TSC and will serve until their resignation or replacement by the TSC. The TSC Chair, or any other TSC member so designated by the TSC, will serve as the primary communication contact between the Project and any directed fund of the Linux Foundation that supports the Project. 42 | > 43 | > g\. Responsibilities: The TSC will be responsible for all aspects of oversight relating to the Project, which may include: 44 | > 45 | > i\. coordinating the technical direction of the Project; 46 | > 47 | > ii\. approving, maintaining and updating a data architecture for the contribution, curation and organization of data; 48 | > 49 | > iii\. approving project or system proposals (including, but not limited to, incubation, deprecation, and changes to a sub-project's scope); 50 | > 51 | > iv\. organizing sub-projects and removing sub-projects; 52 | > 53 | > v\. creating sub-committees or working groups to focus on cross-project technical issues and requirements; 54 | 55 | > vi\. appointing representatives to work with other open data, open source software or standards communities; 56 | > 57 | > vii\. establishing data practices, data contribution policies, software source code contribution policies, community norms, workflows, data management systems, issuing releases, and security issue reporting policies (collectively, "Policies"). All Policies will be available on the Project's repository and linked to from within the CONTRIBUTING file. Following the inception of the Project, it is anticipated that the SC will develop and publish a data contribution policy. 58 | > 59 | > viii\. approving and implementing policies and processes for contributing (to be published in the CONTRIBUTING file) and coordinating with the series manager of the Project (as provided for in the Series Agreement, the "Series Manager") to resolve matters or concerns that may arise as set forth in Section 7 of this Charter; 60 | > 61 | > ix\. discussions, seeking consensus, and where necessary, voting on technical matters relating to the code base that affect multiple projects; and 62 | > 63 | > x\. coordinating any marketing, events, or communications regarding the Project. 64 | > 65 | > **3. TSC Voting** 66 | > 67 | > a\. While the Project aims to operate as a consensus-based community, if any TSC decision requires a vote to move the Project forward, the voting members of the TSC will vote on a one vote per voting member basis. 68 | > 69 | > b\. Quorum for TSC meetings requires at least fifty percent of all voting members of the TSC to be present. The TSC may continue to meet if quorum is not met but will be prevented from making any decisions at the meeting. 70 | > 71 | > c\. Except as provided in Section 7.c. and 8.a, decisions by vote at a meeting require a majority vote of those in attendance, provided quorum is met. Decisions made by electronic vote without a meeting require a majority vote of all voting members of the TSC. 72 | > 73 | > d\. In the event a vote cannot be resolved by the TSC, any voting member of the TSC may refer the matter to the Series Manager for assistance in reaching a resolution. 74 | > 75 | > **4. Compliance with Policies** 76 | > 77 | > a\. This Charter is subject to the Series Agreement for the Project and the Operating Agreement of LF Projects. Contributors will comply with the policies of LF Projects as may be adopted and amended by LF Projects, including, without limitation the policies listed at 78 | https://lfprojects.org/policies/. 79 | 80 | 3 81 | 82 | > b\. The TSC may adopt a code of conduct ("CoC") for the Project, which is subject to approval by the Series Manager. In the event that a Project-specific CoC has not been approved, the LF Projects Code of Conduct listed at https://lfprojects.org/policies/code-of-conduct/ will apply for all Collaborators in the Project. 83 | 84 | > c\. When amending or adopting any policy applicable to the Project, LF Projects will publish such policy, as to be amended or adopted, on its web site at least 30 days prior to such policy taking effect; provided, however, that in the case of any amendment of the Trademark Policy or Terms of Use of LF Projects, any such amendment is effective upon publication on LF Project's web site. 85 | > 86 | > d\. All Collaborators must allow open participation from any individual or organization meeting the requirements for contributing under this Charter and any policies adopted for all Collaborators by the TSC, regardless of competitive interests. Put another way, the Project community must not seek to exclude any participant based on any criteria, requirement, or reason other than those that are reasonable and applied on a non-discriminatory basis to all Collaborators in the Project community. 87 | > 88 | > e\. The Project will operate in a transparent, open, collaborative, and ethical manner at all times. The output of all Project discussions, proposals, timelines, decisions, and status should be made open and easily visible to all. Any potential violations of this requirement should be reported immediately to the Series Manager. 89 | > 90 | > **5. Community Assets** 91 | > 92 | > a\. LF Projects will hold title to all trade or service marks used by the Project ("Project Trademarks"), whether based on common law or registered rights. Project Trademarks will be transferred and assigned to LF Projects to hold on behalf of the Project. Any use of any Project Trademarks by Collaborators in the Project will be in accordance with the license from LF Projects and inure to the benefit of LF Projects. 93 | > 94 | > b\. The Project will, as permitted and in accordance with such license from LF Projects, develop and own all Project GitHub and social media accounts, and domain name registrations created by the Project community. 95 | > 96 | > c\. Under no circumstances will LF Projects be expected or required to undertake any action on behalf of the Project that is inconsistent with the tax-exempt status or purpose, as applicable, of the Joint Development Foundation or LF Projects, LLC. 97 | > 98 | > **6. General Rules and Operations.** 99 | > 100 | > a\. The Project will: 101 | > 102 | > i\. engage in the work of the Project in a professional manner consistent with maintaining a cohesive community, while also maintaining the goodwill and esteem of LF Projects, Joint Development Foundation and other partner organizations in the open source community; and 103 | 104 | > ii\. respect the rights of all trademark owners, including any branding and trademark usage guidelines. 105 | > 106 | > **7. Intellectual Property Policy** 107 | > 108 | > a\. Collaborators acknowledge that the copyright in all new contributions will be retained by the copyright holder as independent works of authorship and that no contributor or copyright holder will be required to assign copyrights to the Project. 109 | > 110 | > b\. Except as described in Section 7.c., all contributions to the Project are subject to the following: 111 | > 112 | > i\. To the extent a contribution includes or consists of data, any rights in such data shall be made available under the CDLA-Permissive 2.0 License, available at https://cdla.io/permissive-2-0/. 113 | > 114 | > ii\. All new inbound software source code contributions to the Project must be made using the Apache License, Version 2.0, available at https://www.apache.org/licenses/LICENSE-2.0 (the "Source Code License"). 115 | > 116 | > iii\. All new inbound software source code contributions must also be accompanied by a Developer Certificate of Origin (http://developercertificate.org) sign-off in the source code system that is submitted through a TSC-approved contribution process which will bind the authorized contributor and, if not self-employed, their employer to the applicable license; 117 | 118 | > iv\. All outbound code will be made available under the Source Code License. 119 | 120 | > v\. Data models, formats and labels as well as other specifications to be developed by the Project will use the Community Specification License Agreement 1.0 (available at https://github.com/CommunitySpecification/1.0). 121 | > 122 | > vi\. Documentation will be received and made available by the Project under the Creative Commons Attribution 4.0 International License (available at http://creativecommons.org/licenses/by/4.0/). 123 | > 124 | > vii\. The Project may seek to integrate and contribute back to other open data, open specification and open source projects ("Upstream Projects"). In such cases, the Project will conform to all license requirements of the Upstream Projects, including dependencies, leveraged by the Project. Upstream Project code contributions not stored within the Project's main code repository will comply with the contribution process and license terms for the applicable Upstream Project. 125 | > 126 | > c\. The TSC may approve the use of an alternative license or licenses for inbound or outbound contributions on an exception basis. To request an exception, please describe the contribution, the alternative open source license(s), and the justification for using an alternative open source license for the Project. License exceptions must be approved by a two-thirds vote of the entire TSC. 127 | > 128 | > d\. Contributed files should contain license information, such as SPDX short form identifiers, indicating the open source license or licenses pertaining to the file. 129 | > 130 | > **8. Amendments** 131 | > 132 | > a\. This charter may be amended by a two-thirds vote of the entire TSC and is subject to approval by LF Projects. 133 | 134 | 135 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | Creative Commons Attribution 4.0 International 2 | 3 | Creative Commons Corporation ("Creative Commons") is not a law firm and does not provide legal services or legal advice. Distribution of Creative Commons public licenses does not create a lawyer-client or other relationship. Creative Commons makes its licenses and related information available on an "as-is" basis. Creative Commons gives no warranties regarding its licenses, any material licensed under their terms and conditions, or any related information. Creative Commons disclaims all liability for damages resulting from their use to the fullest extent possible. 4 | 5 | Using Creative Commons Public Licenses 6 | 7 | Creative Commons public licenses provide a standard set of terms and conditions that creators and other rights holders may use to share original works of authorship and other material subject to copyright and certain other rights specified in the public license below. The following considerations are for informational purposes only, are not exhaustive, and do not form part of our licenses. 8 | 9 | Considerations for licensors: Our public licenses are intended for use by those authorized to give the public permission to use material in ways otherwise restricted by copyright and certain other rights. Our licenses are irrevocable. Licensors should read and understand the terms and conditions of the license they choose before applying it. Licensors should also secure all rights necessary before applying our licenses so that the public can reuse the material as expected. Licensors should clearly mark any material not subject to the license. This includes other CC-licensed material, or material used under an exception or limitation to copyright. More considerations for licensors : wiki.creativecommons.org/Considerations_for_licensors 10 | 11 | Considerations for the public: By using one of our public licenses, a licensor grants the public permission to use the licensed material under specified terms and conditions. If the licensor's permission is not necessary for any reason–for example, because of any applicable exception or limitation to copyright–then that use is not regulated by the license. Our licenses grant only permissions under copyright and certain other rights that a licensor has authority to grant. Use of the licensed material may still be restricted for other reasons, including because others have copyright or other rights in the material. A licensor may make special requests, such as asking that all changes be marked or described. Although not required by our licenses, you are encouraged to respect those requests where reasonable. More considerations for the public : wiki.creativecommons.org/Considerations_for_licensees 12 | 13 | Creative Commons Attribution 4.0 International Public License 14 | 15 | By exercising the Licensed Rights (defined below), You accept and agree to be bound by the terms and conditions of this Creative Commons Attribution 4.0 International Public License ("Public License"). To the extent this Public License may be interpreted as a contract, You are granted the Licensed Rights in consideration of Your acceptance of these terms and conditions, and the Licensor grants You such rights in consideration of benefits the Licensor receives from making the Licensed Material available under these terms and conditions. 16 | 17 | Section 1 – Definitions. 18 | 19 | a. Adapted Material means material subject to Copyright and Similar Rights that is derived from or based upon the Licensed Material and in which the Licensed Material is translated, altered, arranged, transformed, or otherwise modified in a manner requiring permission under the Copyright and Similar Rights held by the Licensor. For purposes of this Public License, where the Licensed Material is a musical work, performance, or sound recording, Adapted Material is always produced where the Licensed Material is synched in timed relation with a moving image. 20 | b. Adapter's License means the license You apply to Your Copyright and Similar Rights in Your contributions to Adapted Material in accordance with the terms and conditions of this Public License. 21 | c. Copyright and Similar Rights means copyright and/or similar rights closely related to copyright including, without limitation, performance, broadcast, sound recording, and Sui Generis Database Rights, without regard to how the rights are labeled or categorized. For purposes of this Public License, the rights specified in Section 2(b)(1)-(2) are not Copyright and Similar Rights. 22 | d. Effective Technological Measures means those measures that, in the absence of proper authority, may not be circumvented under laws fulfilling obligations under Article 11 of the WIPO Copyright Treaty adopted on December 20, 1996, and/or similar international agreements. 23 | e. Exceptions and Limitations means fair use, fair dealing, and/or any other exception or limitation to Copyright and Similar Rights that applies to Your use of the Licensed Material. 24 | f. Licensed Material means the artistic or literary work, database, or other material to which the Licensor applied this Public License. 25 | g. Licensed Rights means the rights granted to You subject to the terms and conditions of this Public License, which are limited to all Copyright and Similar Rights that apply to Your use of the Licensed Material and that the Licensor has authority to license. 26 | h. Licensor means the individual(s) or entity(ies) granting rights under this Public License. 27 | i. Share means to provide material to the public by any means or process that requires permission under the Licensed Rights, such as reproduction, public display, public performance, distribution, dissemination, communication, or importation, and to make material available to the public including in ways that members of the public may access the material from a place and at a time individually chosen by them. 28 | j. Sui Generis Database Rights means rights other than copyright resulting from Directive 96/9/EC of the European Parliament and of the Council of 11 March 1996 on the legal protection of databases, as amended and/or succeeded, as well as other essentially equivalent rights anywhere in the world. 29 | k. You means the individual or entity exercising the Licensed Rights under this Public License. Your has a corresponding meaning. 30 | Section 2 – Scope. 31 | 32 | a. License grant. 33 | 1. Subject to the terms and conditions of this Public License, the Licensor hereby grants You a worldwide, royalty-free, non-sublicensable, non-exclusive, irrevocable license to exercise the Licensed Rights in the Licensed Material to: 34 | A. reproduce and Share the Licensed Material, in whole or in part; and 35 | B. produce, reproduce, and Share Adapted Material. 36 | 2. Exceptions and Limitations. For the avoidance of doubt, where Exceptions and Limitations apply to Your use, this Public License does not apply, and You do not need to comply with its terms and conditions. 37 | 3. Term. The term of this Public License is specified in Section 6(a). 38 | 4. Media and formats; technical modifications allowed. The Licensor authorizes You to exercise the Licensed Rights in all media and formats whether now known or hereafter created, and to make technical modifications necessary to do so. The Licensor waives and/or agrees not to assert any right or authority to forbid You from making technical modifications necessary to exercise the Licensed Rights, including technical modifications necessary to circumvent Effective Technological Measures. For purposes of this Public License, simply making modifications authorized by this Section 2(a)(4) never produces Adapted Material. 39 | 5. Downstream recipients. 40 | A. Offer from the Licensor – Licensed Material. Every recipient of the Licensed Material automatically receives an offer from the Licensor to exercise the Licensed Rights under the terms and conditions of this Public License. 41 | B. No downstream restrictions. You may not offer or impose any additional or different terms or conditions on, or apply any Effective Technological Measures to, the Licensed Material if doing so restricts exercise of the Licensed Rights by any recipient of the Licensed Material. 42 | 6. No endorsement. Nothing in this Public License constitutes or may be construed as permission to assert or imply that You are, or that Your use of the Licensed Material is, connected with, or sponsored, endorsed, or granted official status by, the Licensor or others designated to receive attribution as provided in Section 3(a)(1)(A)(i). 43 | b. Other rights. 44 | 1. Moral rights, such as the right of integrity, are not licensed under this Public License, nor are publicity, privacy, and/or other similar personality rights; however, to the extent possible, the Licensor waives and/or agrees not to assert any such rights held by the Licensor to the limited extent necessary to allow You to exercise the Licensed Rights, but not otherwise. 45 | 2. Patent and trademark rights are not licensed under this Public License. 46 | 3. To the extent possible, the Licensor waives any right to collect royalties from You for the exercise of the Licensed Rights, whether directly or through a collecting society under any voluntary or waivable statutory or compulsory licensing scheme. In all other cases the Licensor expressly reserves any right to collect such royalties. 47 | Section 3 – License Conditions. 48 | 49 | Your exercise of the Licensed Rights is expressly made subject to the following conditions. 50 | 51 | a. Attribution. 52 | 1. If You Share the Licensed Material (including in modified form), You must: 53 | A. retain the following if it is supplied by the Licensor with the Licensed Material: 54 | i. identification of the creator(s) of the Licensed Material and any others designated to receive attribution, in any reasonable manner requested by the Licensor (including by pseudonym if designated); 55 | ii. a copyright notice; 56 | iii. a notice that refers to this Public License; 57 | iv. a notice that refers to the disclaimer of warranties; 58 | v. a URI or hyperlink to the Licensed Material to the extent reasonably practicable; 59 | B. indicate if You modified the Licensed Material and retain an indication of any previous modifications; and 60 | C. indicate the Licensed Material is licensed under this Public License, and include the text of, or the URI or hyperlink to, this Public License. 61 | 2. You may satisfy the conditions in Section 3(a)(1) in any reasonable manner based on the medium, means, and context in which You Share the Licensed Material. For example, it may be reasonable to satisfy the conditions by providing a URI or hyperlink to a resource that includes the required information. 62 | 3. If requested by the Licensor, You must remove any of the information required by Section 3(a)(1)(A) to the extent reasonably practicable. 63 | 4. If You Share Adapted Material You produce, the Adapter's License You apply must not prevent recipients of the Adapted Material from complying with this Public License. 64 | Section 4 – Sui Generis Database Rights. 65 | 66 | Where the Licensed Rights include Sui Generis Database Rights that apply to Your use of the Licensed Material: 67 | 68 | a. for the avoidance of doubt, Section 2(a)(1) grants You the right to extract, reuse, reproduce, and Share all or a substantial portion of the contents of the database; 69 | b. if You include all or a substantial portion of the database contents in a database in which You have Sui Generis Database Rights, then the database in which You have Sui Generis Database Rights (but not its individual contents) is Adapted Material; and 70 | c. You must comply with the conditions in Section 3(a) if You Share all or a substantial portion of the contents of the database. 71 | For the avoidance of doubt, this Section 4 supplements and does not replace Your obligations under this Public License where the Licensed Rights include other Copyright and Similar Rights. 72 | 73 | Section 5 – Disclaimer of Warranties and Limitation of Liability. 74 | 75 | a. Unless otherwise separately undertaken by the Licensor, to the extent possible, the Licensor offers the Licensed Material as-is and as-available, and makes no representations or warranties of any kind concerning the Licensed Material, whether express, implied, statutory, or other. This includes, without limitation, warranties of title, merchantability, fitness for a particular purpose, non-infringement, absence of latent or other defects, accuracy, or the presence or absence of errors, whether or not known or discoverable. Where disclaimers of warranties are not allowed in full or in part, this disclaimer may not apply to You. 76 | b. To the extent possible, in no event will the Licensor be liable to You on any legal theory (including, without limitation, negligence) or otherwise for any direct, special, indirect, incidental, consequential, punitive, exemplary, or other losses, costs, expenses, or damages arising out of this Public License or use of the Licensed Material, even if the Licensor has been advised of the possibility of such losses, costs, expenses, or damages. Where a limitation of liability is not allowed in full or in part, this limitation may not apply to You. 77 | c. The disclaimer of warranties and limitation of liability provided above shall be interpreted in a manner that, to the extent possible, most closely approximates an absolute disclaimer and waiver of all liability. 78 | Section 6 – Term and Termination. 79 | 80 | a. This Public License applies for the term of the Copyright and Similar Rights licensed here. However, if You fail to comply with this Public License, then Your rights under this Public License terminate automatically. 81 | b. Where Your right to use the Licensed Material has terminated under Section 6(a), it reinstates: 82 | 1. automatically as of the date the violation is cured, provided it is cured within 30 days of Your discovery of the violation; or 83 | 2. upon express reinstatement by the Licensor. 84 | c. For the avoidance of doubt, this Section 6(b) does not affect any right the Licensor may have to seek remedies for Your violations of this Public License. 85 | d. For the avoidance of doubt, the Licensor may also offer the Licensed Material under separate terms or conditions or stop distributing the Licensed Material at any time; however, doing so will not terminate this Public License. 86 | e. Sections 1, 5, 6, 7, and 8 survive termination of this Public License. 87 | Section 7 – Other Terms and Conditions. 88 | 89 | a. The Licensor shall not be bound by any additional or different terms or conditions communicated by You unless expressly agreed. 90 | b. Any arrangements, understandings, or agreements regarding the Licensed Material not stated herein are separate from and independent of the terms and conditions of this Public License. 91 | Section 8 – Interpretation. 92 | 93 | a. For the avoidance of doubt, this Public License does not, and shall not be interpreted to, reduce, limit, restrict, or impose conditions on any use of the Licensed Material that could lawfully be made without permission under this Public License. 94 | b. To the extent possible, if any provision of this Public License is deemed unenforceable, it shall be automatically reformed to the minimum extent necessary to make it enforceable. If the provision cannot be reformed, it shall be severed from this Public License without affecting the enforceability of the remaining terms and conditions. 95 | c. No term or condition of this Public License will be waived and no failure to comply consented to unless expressly agreed to by the Licensor. 96 | d. Nothing in this Public License constitutes or may be interpreted as a limitation upon, or waiver of, any privileges and immunities that apply to the Licensor or You, including from the legal processes of any jurisdiction or authority. 97 | Creative Commons is not a party to its public licenses. Notwithstanding, Creative Commons may elect to apply one of its public licenses to material it publishes and in those instances will be considered the "Licensor." The text of the Creative Commons public licenses is dedicated to the public domain under the CC0 Public Domain Dedication. Except for the limited purpose of indicating that material is shared under a Creative Commons public license or as otherwise permitted by the Creative Commons policies published at creativecommons.org/policies, Creative Commons does not authorize the use of the trademark "Creative Commons" or any other trademark or logo of Creative Commons without its prior written consent including, without limitation, in connection with any unauthorized modifications to any of its public licenses or any other arrangements, understandings, or agreements concerning use of licensed material. For the avoidance of doubt, this paragraph does not form part of the public licenses. 98 | 99 | Creative Commons may be contacted at creativecommons.org. 100 | --------------------------------------------------------------------------------