Context Navigation

Submitted patches

Page 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 ...
Show: all, applied, pending, rejected

Patch Description	Branch	Submit Time	Status	Test Status
[PATCH] ticket:1639 - Petascope hibernate shouldn't update a coverage's crs to database implicitly when it's crs is replaced from $ to configuration in petascope.properties	master	2017-11-21 19:02:32	PENDING	SUCCESS
[PATCH] ticket:1640 - WCS client uses imported sample coverages from petascope_insertdemo.sh for WCPS queries example	master	2017-11-21 17:38:19	PENDING	SUCCESS
[PATCH] ticket:1631 - Petascope should not replace '-' with '_' for importing coverage id	master	2017-11-21 17:37:52	PENDING	SUCCESS
[PATCH] ticket:1636 - Build petascope_insertdemo.sh and petascope_insertdemo_data needs to be installed with cmake/autotools	master	2017-11-21 09:48:04	PENDING	SUCCESS
[PATCH] ticket:1638 - Petascope migration returns a success message when petascopedb doesn't exist	master	2017-11-20 18:28:58	PENDING	SUCCESS
[PATCH] ticket:1268 - remove the warning of wrong parent elemnt from maven build for petascope	master	2017-11-13 14:12:46	PENDING	SUCCESS
[PATCH] ticket:1629 - SECORE cannot resolve parametertized CRSs inside a parameterized CRS definition	master	2017-11-13 10:30:54	PENDING	SUCCESS
[PATCH] ticket:1630 - remove residual files in test_select & update Makefile.am in qlparser and raslib	master	2017-11-08 13:44:22	PENDING	SUCCESS
[PATCH] ticket:1627 - Embedded SECORE needs user's configuration for secoredb path	master	2017-11-07 17:06:15	PENDING	SUCCESS
[PATCH] ticket:1626 - SECORE should run without update scripts folder	master	2017-11-06 13:20:09	PENDING	SUCCESS

Submit a new patch

Select your locally generated patch file below for upload. Note that the patch can only be accepted if you agree to the Rasdaman Contribution Agreement by ticking the checkbox.

See How to submit patches for a step-by-step guide, in particular regarding the patch subject format. In order to ensure quick processing and to avoid rejection, you may want to make sure your patch adheres to the rasdaman code guide.

Rasdaman Contributor Agreement v1.0

These terms apply to your contribution of materials to a product or project owned or managed by us ('project'), and set out the intellectual property rights you grant to us (rasdaman GmbH, Germany, see www.rasdaman.com) in the contributed materials. If this contribution is on behalf of a company, the term 'you' will also mean the company you identify below. If you agree to be bound by these terms, fill in the information requested below and provide your signature. Alternatively, when provided together with a submission of your contribution by email, you agree to be bound by the agreement as it can be downloaded from www.rasdaman.org and that no other terms potentially supplied with your submission in addition apply.

Read this agreement carefully before signing and/or submitting.

  1. The term 'contribution' means any source code, object code, patch, tool, sample, graphic, specification, manual, documentation, or any other material posted or submitted by you to a project.

  2. With respect to any worldwide copyrights, or copyright applications and registrations, in your contribution:

    2.1. you hereby assign to us joint ownership, and to the extent that such assignment is or becomes invalid, ineffective or unenforceable, you hereby grant to us a perpetual, irrevocable, non-exclusive, worldwide, no-charge, royalty-free, unrestricted license to exercise all rights under those copyrights. This includes, at our option, the right to sublicense these same rights to third parties through multiple levels of sublicensees or other licensing arrangements;

    2.2. you agree that each of us can do all things in relation to your contribution as if each of us were the sole owners, and if one of us makes a derivative work of your contribution, the one who makes the derivative work (or has it made) will be the sole owner of that derivative work;

    2.3. you agree that you will not assert any moral rights in your contribution against us, our licensees or transferees;

    2.4. you agree that we may register a copyright in your contribution and exercise all ownership rights associated with it; and

    2.5. you agree that neither of us has any duty to consult with, obtain the consent of, pay or render an accounting to the other for any use or distribution of your contribution.

  3. With respect to any patents you own, or that you can license without payment to any third party, you hereby grant to us a perpetual, irrevocable, non-exclusive, worldwide, no-charge, royalty-free license to:

    3.1. make, have made, use, sell, offer to sell, import, and otherwise transfer your contribution in whole or in part, alone or in combination with or included in any product, work or materials arising out of the project to which your contribution was submitted, and

    3.2. at our option, to sublicense these same rights to third parties through multiple levels of sublicensees or other licensing arrangements.

  4. Except as set out above, you keep all right, title, and interest in your contribution. The rights that you grant to us under these terms are effective on the date you first submitted a contribution to us, even if your submission took place before the date you sign these terms. Any contribution we make available under any license will also be made available under a suitable FSF (Free Software Foundation) or OSI (Open Source Initiative) approved license which we choose at our discretion.

  5. With respect to your contribution, you represent that:

    5.1. it is an original work and that you can legally grant the rights set out in these terms;

    5.2. it does not to the best of your knowledge violate any third party's copyrights, trademarks, patents, or other intellectual property rights; and

    5.3. you are authorized to sign this contract on behalf of your company (if identified below).

  6. These terms will be governed by the laws of Germany. Any choice of law rules will not apply.

Select the code branch below to which you want to commit (help); if you are not sure what this means just leave the default (master).

I agree to the Rasdaman Contribution Agreement.