Hot Chocolate

1.   General Information

Project Name:
Hot Chocolate

License:
MIT

Contributor (Company, Organization or individual name(s)):
ChilliCream, Michael Staib, Rafael Staib, Pascal Senn, Tobias Tengler

Existing OSS Project? (Yes/No):
Yes

Source Code URL:
https://github.com/ChilliCream/hotchocolate

Project Homepage URL (if different):
https://chillicream.com

Project Transfer Signatories:

Name: Michael Staib
Email: michael@chillicream.com
GitHub Profile URL: https://github.com/michaelstaib

Name: Rafael Staib
Email: rafael@chillicream.com
GitHub Profile URL: https://github.com/rstaib

Name: Pascal Senn
Email: pascal@chillicream.com
GitHub Profile URL: https://github.com/PascalSenn

2.   Description

The ChilliCream GraphQL Platform provides a new way to create powerful GraphQL backends and reactive frontends. HotChocolate, our .NET GraphQL server, connects any service or data source and creates a cohesive service to offer your consumers a unified API. Strawberry Shake, our .NET state management client, allows users to focus on their problem domain while creating complex reactive frontends with ease.

3.   Project Governance

Project Lead:

Name: Michael Staib
Email: michael@chillicream.com
GitHub Profile URL: https://github.com/michaelstaib

Maintainers:

Name: Rafael Staib
Email: rafael@chillicream.com
GitHub Profile URL: https://github.com/rstaib

Name: Pascal Senn
Email: pascal@chillicream.com
GitHub Profile URL: https://github.com/PascalSenn

Name: Tobias Tengler
Email: tobias@chillicream.com
GitHub Profile URL: https://github.com/tobias-tengler

Committers:

Name: Ben McCallum
Email: ben@chillicream.com
GitHub https://github.com/benmccallum

Name: Arif Hanif
Email: arif@chillicream.com
GitHub https://github.com/arif-hanif

Other Committers:

https://github.com/Alxandr
https://github.com/damikun
https://github.com/gmiserez
https://github.com/huysentruitw
https://github.com/jmercha
https://github.com/John0x
https://github.com/joslat
https://github.com/martetassyns
https://github.com/nigel-sampson
https://github.com/OneCyrus
https://github.com/promontis
https://github.com/pkellner
https://github.com/steveoh
https://github.com/tunurgitr
https://github.com/wonbyte
https://github.com/zaneclaes

Governance Model:

New code, bug fixes, or documentation changes have to be provided in a PR. If the change is more complex, we demand an issue as well. Changes need to be reviewed by a maintainer or by the project lead. If a maintainer does a change, it has to be reviewed by another maintainer.

We have a philosophy where we enable people quickly to grant write access on the repo itself. If we see that someone starts committing regularly, we grant write access. However, these people cannot merge PRs into the main or develop branches.

The project lead and the maintainers (core contributors) can merge pull requests. We, from the start, created an open culture where we encourage people to become core contributors. We, at this stage, have four core contributors (incl. project lead), which we are listing here as maintainers. We have two more contributors that we consider to become part of this circle soon.

We have a very open community where we discuss and steer changes to the platform through our slack channel. The community is engaged very early with regular previews and polls regarding changes. People are encouraged to take part and start contributing.

The group of core contributors decides if a contributor shall become part of the group of core contributors by simple majority. The core contributors meet weekly. One single-core contributor can decide to grant simple write access to the repository.

We welcome people from all backgrounds, genders, and any color to become part of the project.

CLA

We do not yet have a CLA check.

CLA Notification Alias
contact@chillicream.com

Contribution Model

4.   Repository Layout

5. Eligibility Criteria

Please complete the following for your project

• The project is built on the .NET platform and/or creates value within the .NET ecosystem.

• Yes
• No

• The project produces source code for distribution to the public at no charge.

• Yes
• No

• The project's code is easily discoverable and publicly accessible (preferably on GitHub).

• Yes
• No

• The project contains a build script that can produce deployable artifacts that are identical to the official deployable artifacts, with the exception of code signing (Exception may be granted for strong name keys, though strongly encouraged to be committed. Exception relies on OSS signing being in the build script for public builds).

• Yes
• No

• When applicable, project must use reproducible build settings in its toolchain.

• Yes
• No

• The project uses Source Link.

• Yes
• No

• The project uses either embedded PDBs or publish symbol packages to NuGet (if applicable).

• Yes
• No

• The project code signs their artifacts as appropriate.

• Yes
• No

• The project organization has 2FA enabled. Requiring 2FA must be done as part of onboarding if not already enabled.

• Yes
• No

• Libraries that are mandatory dependencies of the project are offered under a standard, permissive open source license which has been approved by the .NET Foundation (exceptions include a dependency that is required by the target platform where no alternative open source dependency is available such as the .NET Framework or a hardware specific library).

• Yes
• No

• Committers are bound by a Contributor License Agreement (CLA) and/or are willing to embrace the .NET Foundation's CLA when the project becomes a Member.

• Yes
• No

• The copyright ownership of everything that the project produces is clearly defined and documented.

• Yes
• No

• The project has a public issue tracker where the status of any defect can be easily obtained.

• Yes
• No

• The project has a published Security Policy.

• Yes
• No

• The project has a home page which provides high level information about its status and purpose.

• Yes
• No

• The project has a public communication channel where community members can engage with maintainers.

• Yes (http://slack.chillicream.com)
• No

• The project has a publicly available location where members can review and contribute to documentation.

• Yes (website and docs are part of the main repository)
• No

6.   PR Plan

Please summarize the public relations plan for the announcement when joining the foundation (and releasing as open source if appropriate). What is the main story we wish to promote, through what channels, what issues should we be aware of?  For significant news events then please also work with your .NET Foundation contact to ensure a full PR plan is developed.

7.   Infrastructure Requirements

Please describe any infrastructure requirements for the project. For example, how will build servers be operated? Any web hosting or service hosting requirements? Do we need to set up SSL certificates or provide Authenticode Code Signing arrangement for releases?

The project is run using Azure DevOps. We have an open DevOps project that takes advantage of the offer by Microsoft for OSS projects. The group of core contributors has access to these systems.

The website is hosted through GitHub.

Also we are using the sonar cloud under the offer by sonar for OSS projects.

8.   Additional Notes