Today I thought it would be a fun idea to contribute to projects associated with tracking and disseminating information on the current state of COVID-19. However, in this repository it seems only a small subset of the opened PRs are being merged. Adding some contribution guidelines in CONTRIBUTING.md file will allow the broader community to know where they can contribute effectively.

Is your feature request related to a problem? Please describe.
I find it difficult when typing in the entire link to get to

Need to create a small design doc to get the big picture of CMake based build.

note: this follow google/or-tools#1116 (comment)

Roadmap

• Add design doc on CMake based build (like ortools/dotnet/README.md)
• Diagram on dependencies management
• Diagram on C++ build
• Diagram on Python build
• [

I am currently unable to override the resources and tolerations field for an operator deployment. According to the subscriptions.operators.coreos.com CRD, there is a field named subscription.spec.config to do so.

I have deployed a subscription CR using the following manifest:

apiVersion: operators.coreos.com/v1alpha1
kind: Subscription
metadata:
  name: tracing-operator-s

In every pull request I make, I end up getting told by @awesomekling to swap a piece of code with an existing one from the AK library. Wouldn't it be cool to have a Doxygen like documentation in which someone can search for something to see if it already exists in AK? I know I can grep the project to see if something exists but a documentation is always useful I think, especially if it documents a

It would be nice to be able to restore a sequential probe sequence in UBL, like when using bilinear bed leveling. Right now it jumps from point to point in a manner that involves a lot of travel. It simply doesn't look very good. I would be curious to know why UBL orders the probe points in such a peculiar way.