Data Streaming application built for continuous data delivery
Data Integration made simple and powerful
We appreciate any contribution, from adding new modules or fixing modules for better performance. Please read this section if you are contributing your work.
Please pickup any task defined in Issues
Your contribution will be tested by our automated testing on Travis CI to save time and energy. After you have submitted your pull request, you should see the Travis tests start to run at the bottom of your submission page. If those tests fail, then click on the details button try to read through the Travis output to understand the failure. If you do not understand, please leave a comment on your submission page and a community member will try to help.
New files that you contribute should use the standard copyright header:
# Copyright 2020 The Nadi Data Authors. All rights reserved.# Use of this source code is governed by a BSD-style# license that can be found in the LICENSE file.
You’ve written and tested your code, but before sending code out for review, run all the tests for the whole tree to make sure the changes don’t break other packages or programs
The first line of the change description is conventionally a short one-line summary of the change, prefixed by the primary affected package.
A rule of thumb is that it should be written so to complete the sentence “This change modifies _.” That means it does not start with a capital letter, is not a complete sentence, and actually summarizes the result of the change.
Follow the first line by a blank line.
The rest of the description elaborates and should provide context for the change and explain what it does. Write in complete sentences with correct punctuation, just like for your comments in Go. Don’t use HTML, Markdown, or any other markup language.