How to contribute on metabase with adding a feature

sandronikos · November 9, 2018, 8:09am

We have made a small useful addition of a feature and we want to push this change on metabase. We want to tell me how to do that (e.g. by creating a branch with specific name or something else ). The change is into file apply_tooltips.js on path : frontend\src\metabase\visualizations\lib. The feature gives the ability for an end-user to click a node on a graph and get the coordinates and some data like the graph that has been clicked or the value of the node. The reason is to perform data-mining with the data from the click on a graph. We use postmessage so as not to have cross-domain problems. I thnk it would be useful to other people. If you find it useful you can add it to a next release.

jornh · November 10, 2018, 5:19am

In general code contributions are done by GitHub pull requests. There’s some overall guidance to the contribution process on this page:

github.com

metabase/metabase/blob/master/docs/contributing.md

## Thank you

First off, thanks for your interest in Metabase and for wanting to contribute!

In this guide, we'll discuss how Metabase is built. This should give you a good sense of our process and where you might want to fit in.

## What we're trying to build

Metabase is all about letting non-technical users get access to the their organization's data. We're trying to maximize the amount of power that can be comfortably used by someone who understands their business, is quantitatively bent, but probably only comfortable with Excel.

It's important to keep in mind these goals of the Metabase project. Many times
proposals will be marked "Out of Scope" or otherwise deprioritized. This doesn't mean the proposal isn't useful, or that we wouldn't be interested in seeing it done as a side project or as an experimental branch. However, it does mean that we won't point the core team or contributors to it in the near term. Issues that are slightly out of scope will be kept open in case there is community support (and ideally contributions).

To get a sense for the end goals, make sure to read the [Zen of Metabase](../zen.md)

## Our product process:

The core team runs a pretty well defined product process. It is actively being tweaked, but the below is a pretty faithful description of it at the time of writing. You should have a clear idea of how we work before jumping in with a PR.

### A) Identify product needs from the community

This file has been truncated. show original