Donating to BoofCV - Revision history

Peter at 22:21, 30 December 2016

2016-12-30T22:21:24Z

← Older revision		Revision as of 22:21, 30 December 2016
Line 6:		Line 6:
	* Everyone who contributes is mentioned in the project's change log and when applicable their code		* Everyone who contributes is mentioned in the project's change log and when applicable their code

			When submitting a pull request do the following:

			* Pull latest BoofCV code from GitHub
			* Merge in latest code from SNAPSHOT
			* Fix merge conflicts
			* Make sure the code compiles
			* Run the unit tests to make sure nothing is broken
			* Follow GitHub [https://help.github.com/articles/about-pull-requests/ instructions] for a pull request

	= Copyright Assignment =		= Copyright Assignment =

Peter at 21:58, 30 December 2016

2016-12-30T21:58:55Z

← Older revision		Revision as of 21:58, 30 December 2016
Line 4:		Line 4:
	* For bug fixes and other small changes a simple pull request on GitHub is all that's needed		* For bug fixes and other small changes a simple pull request on GitHub is all that's needed
	* Larger changes will require a review and a formal transfer of copyright		* Larger changes will require a review and a formal transfer of copyright
			* Everyone who contributes is mentioned in the project's change log and when applicable their code


Line 10:		Line 11:
	Copyright of code submitted to BoofCV needs to be transferred to Peter Abeles. For small bits of code this transfer will be implicit. Entirely new features or large changes to the code will require a formal license transfer. This can be done over e-mail.		Copyright of code submitted to BoofCV needs to be transferred to Peter Abeles. For small bits of code this transfer will be implicit. Entirely new features or large changes to the code will require a formal license transfer. This can be done over e-mail.

	We wish to keep the code ownership under one individual instead of everyone who submits so that the license can be changed in the future. This has already happened with one of my past projects where it went from LGPL to Apache 2.0. Getting numerous committers to agree or evening respond is a difficult time consuming task that might result in code being removed or rewritten. The most likely change is that if in the future BoofCV falls under the governance of a non-profit organization the copyright will be transferred to it.		We wish to keep the code ownership under one individual or group instead of everyone who submits so that the license can be changed in the future. This has already happened with one of my past projects where it went from LGPL to Apache 2.0. Getting numerous committers to agree or evening respond is a difficult time consuming task that might result in code being removed and rewritten. The most likely change for BoofCV is that if in the future BoofCV falls under the governance of a non-profit organization the copyright will be transferred to it.

	Because the code is being released under an open source license you will never lose access to it. Even if the maintainers become evil and make all future released proprietary your access cannot be revoked because you already have an perpetual open source license to the current code.		Because the code is being released under an open source license you will never lose access to it. Even if the maintainers become evil and make all future released proprietary your access cannot be revoked because you already have an perpetual open source license to the current code.

Peter: Created page with "= Donating Code = * All donated code must be owned by the person who submitted it * For bug fixes and other small changes a simple pull request on GitHub is all that's needed..."

2016-12-30T21:57:00Z

Created page with "= Donating Code = * All donated code must be owned by the person who submitted it * For bug fixes and other small changes a simple pull request on GitHub is all that's needed..."

New page

= Donating Code =

* All donated code must be owned by the person who submitted it
* For bug fixes and other small changes a simple pull request on GitHub is all that's needed
* Larger changes will require a review and a formal transfer of copyright

= Copyright Assignment =

Copyright of code submitted to BoofCV needs to be transferred to Peter Abeles. For small bits of code this transfer will be implicit. Entirely new features or large changes to the code will require a formal license transfer. This can be done over e-mail.

We wish to keep the code ownership under one individual instead of everyone who submits so that the license can be changed in the future. This has already happened with one of my past projects where it went from LGPL to Apache 2.0. Getting numerous committers to agree or evening respond is a difficult time consuming task that might result in code being removed or rewritten. The most likely change is that if in the future BoofCV falls under the governance of a non-profit organization the copyright will be transferred to it.

Because the code is being released under an open source license you will never lose access to it. Even if the maintainers become evil and make all future released proprietary your access cannot be revoked because you already have an perpetual open source license to the current code.