Accept governance alpha version

ANTITRUST.md

@@ -3,5 +3,4 @@
 Participants acknowledge that they may compete with other participants in various lines of business and that it is therefore imperative that they and their respective representatives act in a manner that does not violate any applicable antitrust laws, competition laws, or associated regulations. This Policy does not restrict any participant from engaging in other similar projects. Each participant may design, develop, manufacture, acquire or market competitive deliverables, products, and services, and conduct its business, in whatever way it chooses. No participant is obligated to announce or market any products or services. Without limiting the generality of the foregoing, participants agree not to have any discussion relating to any product pricing, methods or channels of product distribution, contracts with third-parties, division or allocation of markets, geographic territories, or customers, or any other topic that relates in any way to limiting or lessening fair competition.
 
 ---
-Part of MVG-0.1-beta.
-Made with love by GitHub. Licensed under the [CC-BY 4.0 License](https://creativecommons.org/licenses/by-sa/4.0/).
+Adapted from [GitHub's MVG-0.1-beta](https://github.com/github/MVG). Licensed under the [CC-BY 4.0](https://creativecommons.org/licenses/by-sa/4.0/) License.

BRANDING.md

@@ -0,0 +1,20 @@
+# Branding and promotion
+
+## Promotion
+PL and members of TSC and PAB should make their priority to promote the SciCat project and all its subproject, their adoption and sustainability.
+
+## Branding
+All the project members should follow the branding posted in the related repository
+
+### Logo
+Anytime a project member is presenting about the SciCat project, they should use the official logo available in the branding repo.
+
+### Tagline
+If a member is promoting the SciCat project should mention the official tag line, available in the file [TAGLINE.md]():
+
+__Advance your scientific data__
+
+### Project Mission
+If a member is required to explain the SciCat project as a whole, she/he is encouraged to become familiar with and use the official project mission available in the file [PROJECT-MISSION.md]():
+
+Advance your scientific data to accelerate your research and generate new insights. SciCat provides the right platform to lead your organization to an innovative data culture, where data sharing and collaboration is part of everybody's mindset. SciCat provides a central hub for metadata, making data easily findable, accessible for the entire community . We are committed to being the open source scientific metadata catalogue that can be easily integrated into any workplace infrastructure.

CODE-OF-CONDUCT.md

@@ -82,3 +82,6 @@ Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcem
 
 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.
+
+---
+Adapted from [GitHub's MVG-0.1-beta](https://github.com/github/MVG). Licensed under the [CC-BY 4.0](https://creativecommons.org/licenses/by-sa/4.0/) License.

CONTRIBUTING.md

@@ -0,0 +1,32 @@
+# Contributing to SciCat Projects
+
+Each SciCat repository should have designated Maintainers (listed in the repository's MAINTAINERS.md file). They determine the repository's process for accepting contributions, articulated in the repository's CONTRIBUTING.md file.
+
+Broadly, repositories should use one of the following workflows:
+
+## Latest Stable
+* Every change should go through a Pull Request.
+* The person submitting a Pull Request should not merge their own Pull Request.
+* Proposed changes with a large impact---including changes that introduce
+  new concepts, technologies or depenencies; alter the project's scope; or make significant backward-incompatible changes---should be left open for at least one week to allow time for comment, and review should be solicited from a broad range of Maintainers or Contributors who may have useful input on the impact of the change. It is up to a repositiory's Maintainers to judge how much review is needed for a given Pull Request.
+* This code should be in the `main` or `master` branch
+* utilize automated CI pipelines to test prior PR merging
+
+## Releases
+* have releases with a clear naming convention. We suggest using semantic naming. 
+* produce releases in a predictable manner and according to a schedule, if possbile.
+* have a dedicated release branch
+* utilize automated CI pipelines to test and versioning
+
+## Experimental
+SciCat projects are typically public from the very first commit. In this
+early stage, the Maintainers have complete discretion about what
+if any review is needed. Changes may be pushed directly to the `main`
+branch; pull request may be self-merged.
+
+## Non-code repositories
+Non-code repositories should select a workflow repository-by-repository basis that matches the intended usage.
+
+
+---
+Licensed under the [CC-BY 4.0](https://creativecommons.org/licenses/by-sa/4.0/) License.