THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Page History
...
Apache Way, Apache Con (Slides)
Introduction
Please start from sending out an introduction email to the project's dev mailing list (at first: subscribe) with a request for contributors permissions.
| Info | ||
|---|---|---|
| ||
Subject: I want to contribute to Apache ignite Hello, Everyone! My name is [ Name ]. I want to contribute to Ignite. I would like to start from [ identification of particular ticket or module, if you have one in mind ]. Please, help me to start contributing. My ASF JIRA username is [ username ]*. Regards, [ Name ] *learn more about ASF JIRA below |
JIRA Process
| Info | ||
|---|---|---|
| ||
If you do not have ASF JIRA account, use https://selfserve.apache.org/jira-account.html to request a new one before going to the next step. Once you have an ASF JIRA account, send out an introduction email to the project's dev mailing list (at first: subscribe) with a request for contributors permissions. PMCs should handle this request and grant contributor access to a new community member. |
...
- Anyone in the community may start working on any Unassigned ticket.
- (OPTIONAL) It is recommended to clarify the relevance and correctness of the ticket with the community before doing actual implementation. To do this, you can write an email to the dev mailing list and wait for an answer (please do not forget to subscribe to the list first).
- Before beginning working to work on a ticket, you should assign the ticket to yourself.
- Move the ticket to
IN PROGRESSstate. - If necessary, add comments describing the design decisions or approach approaches you plan to take.
Documenting a ticket
...
- Attach Pull Request URL to ticket (see instructions at Workflow)
- Add a comment describing what has been implemented.
- Run tests using Run All... TeamCity suite. Validate that all tests have passed using TeamCity bot. It allows checking that no new non-flaky tests have failed, and posting the confirmation ("TC green visa") to the ticket.
- Move ticket to
PATCH AVAILABLEstate. - If you know a contributor who should review this ticket, you should mention them directly:
...
| Component | Maintainers | |
|---|---|---|
| Ignite Core (the rest of internals not covered below) | ||
| PME | ||
| Rebalance | ||
| Affinity | ||
| PDS | ||
| Encryption | ||
| MVCC (obsolete) | ||
| Transactions | ||
| Snapshots | ||
| Marshalling (Binary, Optimized, JDK) | ||
| Discovery & Communication SPIs | ||
| Ignite Compute API | ||
| Ignite Services API | ||
| Ignite SQL & Text Queries & JDBC | ||
| Ignite Continuous Queries | ||
| Machine Learning/Deep Learning (ml, TensorFlow, sub-modules in ml) | ||
| Build System / Releases | ||
| TeamCity Bot | ||
| Spark Integration | ||
| .NET API | ||
| C++ API | ||
| Other thin clients (Python, Node.js, PHP, etc) | ||
| ODBC | ||
| JDBC | ||
| Streamers (JMS, Flume, Kafka, etc.) | ||
| Docker, Mesos, YARN integration | ||
| AWS, Google Compute Engine, JClouds integration | ||
| Visor Console | ||
| WebSession & WebSession Filter | ||
...
Overview
Content Tools
Apps