Contributing Overview

Please do! Thank you for your help in improving Meshery! 🎈

Find the complete set of contributor guides at https://docs.meshery.io/project/contributing

All contributors are welcome. Not sure where to start? Please see the newcomers welcome guide for how, where, and why to contribute. This project is community-built and welcomes collaboration. Contributors are expected to adhere to our Code of Conduct.

All set to contribute? Grab an open issue with the help-wanted label and jump in. Join our Slack channel and engage in conversation. Create a new issue if needed. All pull requests should ideally reference an open issue. Include keywords in your pull request descriptions, as well as commit messages, to automatically close related issues in GitHub.

Sections

General Contribution Flow
- Developer Certificate of Origin
Meshery Contribution Flow
- Meshery Documentation
- Meshery Backend
  - Writing a Meshery Adapter
- Meshery UI Relevant coding style guidelines are the Go Code Review Comments and the Formatting and style section of Peter Bourgon's Go: Best Practices for Production Environments.
- Mesheryctl Documentation
  - Command Reference and Tracker

General Contribution Flow

To contribute to Meshery, please follow the fork-and-pull request workflow described here.

Issues & Pull Requests

Creating an Issue

Before creating an Issue i.e for features/bugs/improvements please follow these steps:

Search existing Issues before creating a new Issue (look to see if the Issue has already been created).
If it doesn't exist create a new Issue giving as much context as possible (please take note and select the correct Issue type, for example bug, documentation or feature.
If you wish to work on the Issue once it has been triaged, please include this in your Issue description.

Working on an Issue

Before working on an existing Issue please follow these steps:

Comment asking for the Issue to be assigned to you.
To best position yourself for Issues assignment, we recommend that you:
1. Confirm that you have read the CONTRIBUTING.md.
2. Have a functional development environment (have built and are able to run the project).
3. Convey your intended approach to solving the issue.
4. Put each of these items in writing in one or more comments.
After the Issue is assigned to you, you can start working on it.
In general, only start working on this Issue (and open a Pull Request) when it has been assigned to you. Doing so will prevent confusion, duplicate work (some of which may go unaccepted given its duplicity), incidental stepping on toes, and the headache involved for maintainers and contributors alike as Issue assignments collide and heads bump together.
Reference the Issue in your Pull Request (for example This PR fixes #123). so that the corresponding Issue is automatically closed upon merge of your Pull Request.

Notes:

Check the Assignees box at the top of the page to see if the Issue has been assigned to someone else before requesting this be assigned to you. If the issue has a current Assignee, but appears to be inactive, politely inquire with the current Assignee as to whether they are still working on a solution and/or if you might collaborate with them.

Only request to be assigned an Issue if you know how to work on it.

If an Issue is unclear, ask questions to get more clarity before asking to have the Issue assigned to you; avoid asking "what do I do next? how do I fix this?" (see the item above this line)

An Issue can be assigned to multiple people, if you all agree to collaborate on the Issue (the Pull Request can contain commits from different collaborators)

Any Issues that has no activity after 2 weeks will be unassigned and re-assigned to someone else.

Reviewing Pull Requests

We welcome everyone to review Pull Requests. It is a great way to learn, network, and support each other.

DOs

Use inline comments to explain your suggestions
Use inline suggestions to propose changes
Exercise patience and empathy while offering critiques of the works of others.

DON'Ts

Do not repeat feedback, this creates more noise than value (check the existing conversation), use GitHub reactions if you agree/disagree with a comment
Do not blindly approve Pull Requests to improve your GitHub contributors graph

Signing-off on Commits (Developer Certificate of Origin)

To contribute to this project, you must agree to the Developer Certificate of Origin (DCO) for each commit you make. The DCO is a simple statement that you, as a contributor, have the legal right to make the contribution.

See the DCO file for the full text of what you must agree to and how it works here. To signify that you agree to the DCO for contributions, you simply add a line to each of your git commit messages:

Signed-off-by: Jane Smith <jane.smith@example.com>

In most cases, you can add this signoff to your commit automatically with the -s or --signoff flag to git commit. You must use your real name and a reachable email address (sorry, no pseudonyms or anonymous contributions). An example of signing off on a commit:

$ commit -s -m “my commit message w/signoff”

To ensure all your commits are signed, you may choose to add this alias to your global .gitconfig:

~/.gitconfig

[alias]
  amend = commit -s --amend
  cm = commit -s -m
  commit = commit -s

Or you may configure your IDE, for example, Visual Studio Code to automatically sign-off commits for you:

Documentation Contribution Flow

Please contribute! Meshery documentation uses GitHub Pages to host the docs site. Learn more about Meshery's documentation framework. The process of contributing follows this flow:

Create a fork, if you have not already, by following the steps described here
In the local copy of your fork, navigate to the docs folder. cd docs
Create and checkout a new branch to make changes within git checkout -b <my-changes>
Edit/add documentation. vi <specific page>.md
Add redirect link on the old page (only when a new page is created that replaces the old page)
Run site locally to preview changes. make docs

Note: From the Makefile, this command is actually running $ bundle exec jekyll serve --drafts --livereload --config _config_dev.yml. If this command causes errors try running the server without Livereload with this command: $ bundle exec jekyll serve --drafts --config _config_dev.yml. Just keep in mind you will have to manually restart the server to reflect any changes made without Livereload. There are two Jekyll configuration, jekyll serve for developing locally and jekyll build when you need to generate the site artifacts for production.

Commit, sign-off, and push changes to your remote branch. git push origin <my-changes>
Open a pull request (in your web browser) against our main repo: https://github.com/meshery/meshery.

_Alternatively, LiveReload is available as an option during development: with jekyll serve --livereload no more manual page refresh.

bundle exec jekyll serve --drafts --livereload --incremental --config _config_dev.yml

Meshery Contribution Flow

Meshery is written in Go (Golang) and leverages Go Modules. UI is built on React and Next.js. To make building and packaging easier a Makefile is included in the main repository folder.

Relevant coding style guidelines are the Go Code Review Comments and the Formatting and style section of Peter Bourgon's Go: Best Practices for Production Environments.

Please note: All make commands should be run in a terminal from within the Meshery's main folder.

Prerequisites for building Meshery in your development environment:

Go version 1.21.1 must be installed if you want to build and/or make changes to the existing code. The binary go1.21.1 should be available in your path. If you don't want to disturb your existing version of Go, then follow these instructions to keep multiple versions of Go in your system.
GOPATH environment variable should be configured appropriately
npm and node should be installed on your machine, preferably the latest versions.
Fork this repository (git clone https://github.com/meshery/meshery.git), and clone your forked version of Meshery to your development environment, preferably outside GOPATH.
golangci-lint should be installed if you want to test Go code, for MacOS and linux users.

Build and Run Meshery Server

Before you can access the Meshery UI, you need to install the UI dependencies,

make ui-setup

and then build and export the UI

make ui-build

To build & run Meshery Server, run the following command:

make server

Any time changes are made to the Go code, you will have to stop the server and run the above command again. Once the Meshery server is up and running, you should be able to access Meshery on your localhost on port 9081 at http://localhost:9081.

Please note: If you see "Meshery Development Incompatible" while trying to sign into Meshery Server, then follow these steps:

Potential Solution:

Go to your meshery folder in your local-system where you’ve cloned it. Execute:
git remote add upstream https://github.com/meshery/meshery
git fetch upstream
Restart the meshery server
Additionally, before restarting the server, if you like to pull the latest changes, you can do: git pull upstream master

UI Development Server

If you want to work on the UI, it will be a good idea to use the included UI development server. You can run the UI development server by running the following command:

make ui

Once you have the server configured, and running successfully on the default port http://localhost:9081, you may proceed to access the Meshery UI at http://localhost:3000. Any UI changes made now will automatically be recompiled and served in the browser.

To access the Meshery UI Development Server on port 3000, you will need to select your Cloud Provider by navigating to localhost:9081 after running the Meshery server.

Please note: When running make server on the macOS platform, some may face errors with the crypto module in Go. This is caused due to invalid C headers in Clang installed with XCode platform tools. Replacing Clang with gcc by adding export CC=gcc to .bashrc / .zshrc should fix the issue. More information on the issue can be found here

Please Note : Little minor things where you can face some issues in the windows platform -

Meshery requires gcc at the make server step, x64 windows architecture can face issues while finding the best GCC compiler, You can install tdm64-GCC which worked smoothly but many compilers other than that can cause issues, you also have to set an environment variable for this step.
Installing make in windows requires you to install choco first, which makes it easier to install make then, It requires security access which can only be done in admin mode.

Tests

Users can now test their code changes on their local machine against the CI checks implemented through golang-ci lint.

To test code changes on your local machine, run the following command:

make golangci-run

Building Docker image

To build a Docker image of Meshery, please ensure you have Docker installed to be able to build the image. Now, run the following command to build the Docker image:

make docker

Writing a Meshery Adapter

Meshery uses adapters to provision and interact with different service meshes. Follow these instructions to create a new adapter or modify an existing adapter.

Get the proto buf spec file from Meshery repo: wget https://raw.githubusercontent.com/meshery/meshery/master/server/meshes/meshops.proto
Generate code
1. Using Go as an example, do the following:
  - install the protocol buffer compiler: https://grpc.io/docs/protoc-installation/
  - add GOPATH to PATH: export PATH=$PATH:$(go env GOPATH)/bin
  - install the protocol compiler plugins for go: go install google.golang.org/protobuf/cmd/protoc-gen-go@latest go install google.golang.org/grpc/cmd/protoc-gen-go-grpc@latest
  - create a directory meshes
  - Generate Go code: protoc --proto_path=. --go_out=meshes --go_opt=paths=source_relative --go-grpc_out=meshes --go-grpc_opt=paths=source_relative meshops.proto
2. For other languages, please refer to gRPC.io for language-specific guides.
Implement the service methods and expose the gRPC server on a port of your choice (e.g. 10000).

Tip: The Meshery adapter for Istio is a good reference adapter to use as an example of a Meshery adapter written in Go.

Running Meshery Adapter (Meshery-Istio)

Meshery-Istio is a pre-written example of Meshery Adapter written in Go. Follow these instructions to run meshery-istio to avoid errors related to Meshery Adapters

Fork Meshery-Istio
Clone your fork locally
Run this command from the root directory of meshery-istio
```
make run
```
Try connecting to port 10000 as Meshery Adapter URL

UI Contribution Flow

Meshery is written in Go (Golang) and leverages Go Modules. UI is built on React, Billboard.js and Next.js. To make building and packaging easier a Makefile is included in the main repository folder.

Install UI dependencies

To install/update the UI dependencies:

make ui-setup

Build and export UI

To build and export the UI code:

make ui-build

Build and run Meshery Server

To build & run Meshery Server:

make server

Now that the UI code is built, Meshery UI will be available at http://localhost:9081. Any time changes are made to the UI code, the above code will have to run to rebuild the UI.

UI Development Server

If you want to work on the UI, it will be a good idea to use the included UI development server. You can run the UI development server by running the following command:

make ui

Once you have the server configured, and running successfully on the default port http://localhost:9081, you may proceed to access the Meshery UI at http://localhost:3000. Any UI changes made now will automatically be recompiled and served in the browser.

Running Meshery from IDE

If you want to run Meshery from IDE like Goland, VSCode. set below environment variable

PROVIDER_BASE_URLS="https://meshery.layer5.io"
PORT=9081
DEBUG=true
ADAPTER_URLS=localhost:10000 localhost:10001 localhost:10002 localhost:10003 localhost:10004 localhost:10005 localhost:10006 localhost:10007 localhost:10008 localhost:10009

go tool argument

-tags draft

UI Lint Rules

We are using ES-Lint to maintain code quality & consistency in our UI Code. To make sure your PR passes all the UI & ES-Lint Tests, please see below :

Remember to run make ui-lint & make ui-provider-lint if you are making changes in Meshery-UI & Provider-UI respectively.
The above commands will only fix some basic indenting rules. You will have to manually check your code to ensure there are no duplications, un-used variables or un-declared constants.
We will soon be adding Pre-Commit Hooks to make sure you get to know your errors before you commit the code.
In case you are unable to fix your lint errors, ping us on our Slack.

Using Sistent in Meshery UI

Overview

Meshery UI utilizes three component libraries:

Material-UI (MUI) v4
Material-UI (MUI) v5
Sistent

While MUI v4 and v5 are being phased out, Sistent is now the preferred component library. Sistent internally uses MUI v5, and Meshery UI globally still relies on MUI v4. This can lead to conflicts between themes when Sistent components are used directly.

The `UseSistent` Wrapper

To resolve theme conflicts and ensure proper functionality, a custom wrapper called UseSistent has been created. This wrapper provides the Sistent theme to its child components.

Usage Guidelines

Wrap any custom component that exclusively uses Sistent components with UseSistent.
Individual Sistent components can also be wrapped with UseSistent.
Avoid using MUI v4 components within a component wrapped with UseSistent.

Examples

Example 1: Wrapping a custom component

import { UseSistent } from './UseSistent';
import { Button, TextField } from 'sistent';

const MyCustomForm = () => (
  <UseSistent>
    <form>
      <TextField label="Name" />
      <Button>Submit</Button>
    </form>
  </UseSistent>
);

Example 2: Wrapping an individual Sistent component

import { UseSistent } from './UseSistent';
import { DataGrid } from 'sistent';

const MyDataGridComponent = ({ data }) => (
  <UseSistent>
    <DataGrid rows={data} columns={columns} />
  </UseSistent>
);

Example 3: Incorrect usage (avoid this)

import { UseSistent } from './UseSistent';
import { Button } from 'sistent';
import { TextField } from '@material-ui/core'; // MUI v4

// Don't do this!
const IncorrectUsage = () => (
  <UseSistent>
    <Button>Sistent Button</Button>
    <TextField label="MUI v4 TextField" /> {/* This will cause conflicts */}
  </UseSistent>
);

Best Practices

Gradually migrate components to use Sistent instead of MUI v4 or v5.
Always wrap Sistent components or custom components using Sistent with UseSistent.
Keep MUI v4 components separate from Sistent components to avoid theme conflicts.

Mesheryctl Documentation

mesheryctl

mesheryctl is the CLI client for Meshery.

Contributing

Please refer to the Meshery Contributing Guidelines for setting up your development environment and the mesheryctl Command Reference and Tracker for current status of mesheryctl.

For a quick introduction to mesheryctl, checkout Beginner's guide to contributing to Meshery and mesheryctl.

Building and running `mesheryctl`

The /mesheryctl folder contains the complete code for mesheryctl.

mesheryctl is written in Golang or the Go Programming Language. For development use Go version 1.15+.

After making changes, run make in the mesheryctl folder to build the binary. You can then use the binary by, say, ./mesheryctl system start.

`mesheryctl` command reference

See user-facing, documentation of the mesheryctl commands is available in the Meshery Docs.
See contributor-facing design spec for Meshery CLI Commands and Documentation for a complete reference of mesheryctl.

General guidelines and resources

mesheryctl might be the interface that the users first have with Meshery. As such, mesheryctl needs to provide a great UX.

The following principles should be taken in mind while designing mesheryctl commands-

Provide user experiences that are familiar.
Make the commands and their behavior intuitive.
Avoid long commands with chained series of flags.
Design with automated testing in mind, e.g. provide possibility to specify output format as json (-o json) for easy inspection of command response.

Part of delivering a great user experience is providing intuitive interfaces. In the case of mesheryctl, we should take inspiration from and deliver similar user experiences as popular CLIs do in this ecosystem, like kubectl and docker. Here is relevant kubectl information to reference - Kubectl SIG CLI Community Meeting Minutes, contributing to kubectl, code.

mesheryctl uses the Cobra framework. A good first-step towards contributing to mesheryctl would be to familiarise yourself with the Cobra concepts.

For manipulating config files, mesheryctl uses Viper.

A central struct is maintained in the mesheryctl/internal/cli/root/config/config.go file. These are updated and should be used for getting the Meshery configuration.

For logs, mesheryctl uses Logrus. Going through the docs and understanding the different log-levels will help a lot.

mesheryctl uses golangci-lint. Refer to it for lint checks.

All contributors are invited to review pull requests on mesheryctl as on other Meshery components.

Reviews

All contributors are invited to review pull requests. See this short video on how to review a pull request.

New to Git?

Resources: https://lab.github.com and https://try.github.com/

License

This repository and site are available as open-source under the terms of the Apache 2.0 License.

Files

CONTRIBUTING.md

Latest commit

History

CONTRIBUTING.md

File metadata and controls

Find the complete set of contributor guides at https://docs.meshery.io/project/contributing

Issues & Pull Requests

Creating an Issue

Working on an Issue

Reviewing Pull Requests

DOs

DON'Ts

Prerequisites for building Meshery in your development environment:

Build and Run Meshery Server

UI Development Server

Tests

Building Docker image

Install UI dependencies

Build and export UI

Build and run Meshery Server

UI Development Server

Running Meshery from IDE

UI Lint Rules

Using Sistent in Meshery UI

Overview

The UseSistent Wrapper

Usage Guidelines

Examples

Example 1: Wrapping a custom component

Example 2: Wrapping an individual Sistent component

Example 3: Incorrect usage (avoid this)

Best Practices

mesheryctl

Contributing

Building and running mesheryctl

mesheryctl command reference

General guidelines and resources

New to Git?

License

The `UseSistent` Wrapper

Building and running `mesheryctl`

`mesheryctl` command reference