# Contributors documentation
This document summarizes information for DDF committers and contributors. It includes information about the development processes, policies and development guide.
* Report bug
* Pull requests
* Request a new feature
* Best practices
| First | Last | Affiliation | Commiter? | Areas |
| ------------- | ------------- |
| Andy | Twigg | C9 | √ | Backend Algorithm |
| Binh | Han | Adatao | √ | TBD |
| Brian | Kursar | Toyota | TBD | TBD |
| Carlos | Fuertes | Fiksu | TBD | TBD |
| Chris | Larsen | Qlik | TBD | TBD |
| Christopher | Nguyen | Adatao | √| Architecture, Steering |
| David | Gonzalez | Ziff | TBD | TBD |
| Dustin| Keefer | Concilio Labs | TBD | TBD |
| Evan| Chan | Socrata | TBD | TBD |
| Grecia| Lapizco | LivingSocial | TBD | TBD |
| Greg | Bowyer| | TBD | TBD |
| Holden | Karau | | √| pandas-inspired API|
| Huan | Dao | Adatao | √|TBD|
| James | Paul| MIT Sloan| TBD |TBD|
| Kai | Lu | Applovin | TBD | TBD |
| Kevin | Mader | 4Quant | TBD | TBD|
| Khang | Pham | Adatao |√ | Project Management, Roadmap|
| Michael| Fairchild | | TBD | TBD |
| Michal | Malohlava | 0xdata | TBD| TBD|
| Navot | Akiva | Vocativ | TBD | TBD |
| Nhan | Vu | Adatao |√ | TBD |
| Oleg | White | Whitechno | TBD | TBD |
| Rajeev | Vij | Cisco | TBD | TBD |
| Ravi | Mody | | TBD | TBD |
| Sid | Chaudhary | | TBD | TBD |
| Vi | Ngo Van | | TBD | TBD |
| Victor | Hong | Novartis | TBD | TBD |
| Vivian | Zhang | | TBD | TBD |
Welcome to DDF project! If you're reading this document then you are probably interested in contributing to DDF. DDF is under active development and needs contributions not only in the form of code but also in documentation, feedback, ideas, bug reports etc. We would like you to consider yourself part of this endeavor.
This section explains the different ways in which to contribute to DDF
## Report a bug
To report a bug you need to create an issue on github. To help us solve issues efficiently, you can provide us with following information:
1. Include error messages and log, we recommend to use [gist](http://gist.github.com) to paste log.
2. Short description how to reproduce the bug.
## Contributing code
### Open a new issue
Issue can cover anything, a bug, a new feature, an enhancement, in code or documentation. In addition to that, provide a problem statement or feature description and proposed solution. The issue number should be present in each commit aimed at resolving that issue, which allows to see all the related commit together. Even if you develop in a feature branch (more on this later) the information is lost if a fast forward merge is performed, so it's better to comment with issue number. If the development is substantial wait for somebody to comment on the issue. No point in getting axed later. Normally for bug fix you don't need this, unless the fix is complex.
### Open branch
Open a new branch for a new feature, named after the feature, or for any more substantial or risky development (that you may have to give up), otherwise you can develop in master (fixes) or dev (new features). Feature branches will be delated after they are merged or abandoned.
### Develop test
Development of a new feature starts with one or more tests. Ideally, they define what the feature. If fixing bug, we hopefully have a test case for it. Or we may be just adding a test for an existing feature
### Develop feature or fix bug or docs
### Create a Pull Request
You should create a pull request on the DDF project repository. Please follow the instructions on github. Please mention the issue number in your puill request. Submitting a pull request is no guarantee of acceptance, albeit we the committers want to work with you to merge your contribution. Hopefully a healthy discussion when the issue was created will prevent bad surprises later on.
### Approval process
All Pull Requests will be reviewed by a committer, even those created by a committer. We want to have two intelligent beings involved in each change. He or she will review, test it and respond in a timely manner. In general all pull requests need to satisfy the following criteria:
1. Pass all unit tests.
2. Conform to formatting standard (we will strive to provide an automated solution for this)
## Request a new feature
We welcome all ideas and comments. Before you request feature, please take a look at our current roadmap and current open issues.
To request a new feature you should open an issue in our issue tracker and summarize the desired functionality.
You can also send a message to DDF google group.
We use maven to run unit test. You can also use sbt test.
We use Eclipse and IntelliJ IDE to write code. It's required to import our java-formatter into your IDE. Recommendations for other languages will be added here in due course.
1. Google group
2. Meetings: If you would to have DDF project members to present in some meeting, feel free let us know in Google Groups.
If you have any questions after reading this document, then please reach out to us via the DDF's google group