Contribute to Apache Ignite

Before you start working on Apache Ignite, you should sign up to the dev mailing list and say "Hello" to everyone in the community. We have a very friendly group and intend to make joining the project as easy as possible.

Note, you need to subscribe to the dev list, before sending emails to it. To subscribe, send an empty email to dev-subscribe@ignite.apache.org and follow simple instructions in the reply.

You should also sign up to Ignite Jira and browse through open tickets.

Before you start contributing, it helps to familiarize yourself with Ignite Development Process.

• Choose any of the tickets below or if your interest.
• Send an email to the dev list letting us know that you want to work on it (make sure to subscribe first).
• Share your JIRA ID in the email so that one of the committers can add you to the contributor list and you are able to assign the ticket to yourself.
• Visit our How to Contribute page for details about the project workflow and JIRA process.

Pick a Ticket

• Easy tickets to get started with Apache Ignite: easy tickets
• All other issues: Ignite Jira

• Apache Apex Connectors, IGNITE-3131
• DynaCache Provider, IGNITE-5047

Parent Jira ticket for the Kubernetes related work: IGNITE-4159.

• Discovery for Nodes to Connect to Kubernetes From Outside, IGNITE-4161

Parent Jira ticket for the streaming work: IGNITE-108.

• Streaming from Akka, IGNITE-532
• Streaming from ZeroMQ, IGNITE-533
• Streaming from Amazon Kinesis, IGNITE-536

Parent Jira ticket for the data structures work: IGNITE-641.

• Distributed reentrant read-write lock, IGNITE-637
• Distributed multi-map, IGNITE-640
• Queue persistence, IGNITE-2389

• Python API for Ignite RDD for Spark, IGNITE-949

Getting Started guide on wiki: Ignite.NET Development.

• Easy tickets to get started: starter tickets
• ADO.NET Data Provider, IGNITE-4206
• NHibernate Second Level Cache, IGNITE-2658
• LINQ plan caching, IGNITE-2764
• Distributed LINQ parallel extensions, IGNITE-4101

Start Developing

Apache Ignite uses GIT for its VCS system. The "master" branch contains the last released version. The "sprint-N" branch contains the latest code for the Nth sprint.

                # Master branch.
                $ git clone https://git-wip-us.apache.org/repos/asf/ignite

                # Release branch.
                $ git clone https://git-wip-us.apache.org/repos/asf/ignite -b ignite-1.3.0
            

                # Build project.
                $ mvn clean package -DskipTests

                # Run Apache RAT
                $ mvn clean validate -Pcheck-licenses
            

See more detailed build instructions in the DEVNOTES.txt file.

• Pick a ticket from Ignite Jira
• Follow GitHub pull-request's based contribution way that is described here in details.

Nightly Builds

• Last successful build

Nightly builds are not official Apache Ignite releases, have not been tested, and come with no guarantees.

Become a Committer

We love contributions and gladly promote active contributors to committers and PMC members!

The most important point of becoming a committer for Apache projects is active participation within the community. Being an active community member means participating on mailing list discussions, helping to answer questions, being respectful towards others, and following the meritocratic principles of community management.

Of course, code contributions are also important. Once you make a few code contributions, you will become eligible to join Ignite committers, and possibly Ignite PMC. Candidates for new committers or PMC members are suggested by the current committers, mentors, or PMC members, and then must be approved by the PMC voting process.