Contributing

When contributing to this repository, please discuss the change you wish to make via issue or email list dev@marvin.apache.org with the members/administrators of this repository before.

Components

Toolbox: Set of CLI's, utilities, classes, specific libraries to each language, which supports the entire process of exploration, development, testing and delivery of an Engine.

Engine-executor: Implementation of architectural abstraction around the Engine, such as parallelism, distribution, version control, APIs, availability.

Public-engines: Engine examples.

Get started

Clone the repository, install and run “marvin” to confirm the installation.

Choose the issues that are labeled as “Good First Issue”.

Unit test

The unit test is very important and of course it's required for this project, you can use “marvin test” command to run your tests.

New issue and pull request

The community discusses and tracks known bugs and potential features in the [Github Issue Tracker][tbissue]. If you have a new idea or have identified a bug then you should raise it there to start public discussion

This repository contains Issue Templates and Pull Request Templates, just follow the instructions described in templates.

Where to ask for help

  1. Apache Jira Issue Tracker: for discussions about new features or established bugs
  2. dev@marvin.apache.org: for general development discussions

Separate Code Repositories

Marvin-AI maintains all your code and documentation in multiple repositories on the Github. This includes the primary repository and several others repositories for different components.

Standard procedure for contribution

  1. Fork the repository from Here.
  2. Create a new branch in the forked repository for new changes.
  3. Create pull request from your branch to the main repository using a name that start with issue ID.

Code of Conduct

Our Code of Conduct is available at Here