Skip to content

Latest commit

 

History

History
34 lines (23 loc) · 3.01 KB

CONTRIBUTING.md

File metadata and controls

34 lines (23 loc) · 3.01 KB
Raw

We happily welcome contributions to Unity Catalog. We use GitHub Issues to track community reported issues and GitHub Pull Requests for accepting changes.

Governance

Unity Catalog is an independent open-source project and is also a project of the LF AI and Data Foundation. The project under the Linux Foundation follows open governance, which means that there is no one company or individual in control of a project.

Unity Catalog is built on OpenAPI spec and an open source server implementation under Apache 2.0 license. It is also compatible with Apache Hive's metastore API and Apache Iceberg's REST catalog API. This is a community effort and is supported by Amazon Web Services (AWS), Microsoft Azure, Google Cloud, Nvidia, Salesforce, DuckDB, LangChain, dbt Labs, Fivetran, Confluent, Unstructured, Onehouse, Immuta, Informatica and many more.

We are excited to work with the open source communities in the many years to come to realize this vision. You can join the Unity Catalog open source community at unitycatalog.io and the Unity Catalog Community Slack.

Communication

  • Before starting work on a major feature, please reach out to us via GitHub, Slack, etc. We will make sure no one else is already working on it and ask you to open a GitHub issue.
  • A "major feature" is defined as any change that is > 100 LOC altered (not including tests), or changes any user-facing behavior.
  • We will use the GitHub issue to discuss the feature and come to agreement.
  • This is to prevent your time being wasted, as well as ours.
  • The GitHub review process for major features is also important so that organizations with commit access can come to agreement on design.
  • If it is appropriate to write a design document, the document must be hosted either in the GitHub tracking issue, or linked to from the issue and hosted in a world-readable location.
  • Specifically, if the goal is to add a new extension, please read the extension policy.
  • Small patches and bug fixes don't need prior communication. If you have identified a bug and have ways to solve it, please create an issue or create a pull request.

Coding style

We generally follow the Apache Spark Scala Style Guide.

Sign your work

The sign-off is a simple line at the end of the explanation for the patch. Your signature certifies that you wrote the patch or otherwise have the right to pass it on as an open-source patch.

Signed-off-by: Jane Smith <jane.smith@email.com>
Use your real name (sorry, no pseudonyms or anonymous contributions.)