Marquez uses a multi-project structure and contains the modules api, web, clients, and chart. Below, we describe the process for proposing, documenting, and implementing changes to Marquez.

1. Open a new issue briefly describing your proposal

2. Work with Marquez committers to get your proposal reviewed

   Note: Your proposal can have one of two outcomes: accepted or decline; if the proposal is declined, the process is done.

3. If the proposal is accepted, it will be added to our Backlog; the proposal author must write a design doc using our template for new proposals

   Note: Your proposal must be added under proposals/ using the naming convention: [#ISSUE]-[SHORT-NAME].md, where [#ISSUE] is the GitHub issue in Step 1, and [SHORT-NAME] is a shortened name of your proposal (each word seperated by dashes (-)).

4. Open a pull request with your proposal for final discussion; once Marquez committers reach a general consensus on your proposal, it will be added to a Milestone

Once your proposal has been accepted, and has been associated with a milestone, you can begin implementation work by following our contributing guide for Marquez.

If you need help with the proposal process, please reach out to us on our slack channel.