Difference between revisions of "Contributing"

From BoofCV
Jump to navigationJump to search
m
 
(7 intermediate revisions by the same user not shown)
Line 1: Line 1:
= Ways to Contribute =
BoofCV is an open source project and in order for it to grow its users need contribute to the project!  Even if you don't know computer vision or how to program there are many ways you can contribute.


# Report bugs!
== Report Bugs! ==
# Submit fixes on Github for code and javadoc errors
 
# Write code for using BoofCV in [http://www.processing.org/ Processing]
Seriously, if you find a bug please report it!  Make sure you read the documentation first though. Sometimes its useful to report a but even if there isn't really one. That can be an indication that the documentation in that area needs improvement.
# Clean up its Maven build
 
# Continuous integration using [https://www.atlassian.com/software/bamboo Bamboo]
== Source Code ==
# [[Validation:Algorithms |Validate the correctness of algorithms]]
 
# Image segmentation algorithms
Got something you think might be useful in BoofCV?  Well let us know!  You should post it online to make it easy to inspect and provide one or more examples.  It's ok if the code is not perfect.
# Clean up the Wiki
 
# Wavelets
To actually make it into BoofCV the code will need rigorous unit tests and be programmed in a certain way to make it more efficient.  The good news is that those can be done afterwards.  We will do our best to your code conform and might even modify it ourselves, depending on time and need.  All code which is contributed into BoofCV will need to be transferred to the standard BoofCV license, but your contribution will be acknowledged!
## Arbitrary length Coiflet coefficients
 
## Arbitrary length Daub coefficients
If for some reason your code doesn't make it in we will still advertise it if it looks like a useful feature, but is out of scope or just not ready yet.
## Verify that Biorthogonal Daub is buggy and fix
 
## Don't add any addition jar file requires for wavelet tasks
== Social Media ==
# Suggesting ways to improve the API.
 
# Runtime regression tests
We are actively trying to grow the BoofCV community and need help spreading the word.  YouTube videos, blog posts, articles, or papers are good ways to do this.  Also participating on the message boards and answering questions is a good idea too.

Latest revision as of 05:25, 21 September 2015

Report Bugs!

Seriously, if you find a bug please report it! Make sure you read the documentation first though. Sometimes its useful to report a but even if there isn't really one. That can be an indication that the documentation in that area needs improvement.

Source Code

Got something you think might be useful in BoofCV? Well let us know! You should post it online to make it easy to inspect and provide one or more examples. It's ok if the code is not perfect.

To actually make it into BoofCV the code will need rigorous unit tests and be programmed in a certain way to make it more efficient. The good news is that those can be done afterwards. We will do our best to your code conform and might even modify it ourselves, depending on time and need. All code which is contributed into BoofCV will need to be transferred to the standard BoofCV license, but your contribution will be acknowledged!

If for some reason your code doesn't make it in we will still advertise it if it looks like a useful feature, but is out of scope or just not ready yet.

Social Media

We are actively trying to grow the BoofCV community and need help spreading the word. YouTube videos, blog posts, articles, or papers are good ways to do this. Also participating on the message boards and answering questions is a good idea too.

Retrieved from "http://boofcv.org/index.php?title=Contributing&oldid=1642"