From 05a1910968b88a791085074a5375a6024242a33e Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Wed, 29 Nov 2000 07:48:14 +0000 Subject: I'd love to see test cases with submitted patches... --- docs/CONTRIBUTE | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-) diff --git a/docs/CONTRIBUTE b/docs/CONTRIBUTE index 3c53ed36a..bf4a33e85 100644 --- a/docs/CONTRIBUTE +++ b/docs/CONTRIBUTE @@ -20,7 +20,10 @@ The License Issue GNU Public License. We can never re-use sources from a GPL program in curl. If you add a larger piece of code, you can opt to make that file or set of files to use a different license as long as they don't enfore any changes to - the rest of the package. Such "separate parts" can not be GPL either. + the rest of the package and they make sense. Such "separate parts" can not be + GPL either (although they should use "GPL compatible" licenses). + + Curl and libcurl will soon become dual licensed, MozPL/MITX! Naming @@ -82,3 +85,12 @@ Write Access to CVS Repository course get write access to the CVS repository and then you'll be able to check-in all your changes straight into the CVS tree instead of sending all changes by mail as patches. Just ask if this is what you'd want. + +Test Cases + + Since the introduction of the test suite, we will get the possibility to + quickly verify that the main features are working as supposed to. To maintain + this situation and improve it, all new features and functions that are added + need tro be tested. Every feature that is added should get at least one valid + test case that verifies that it works as documented. If every submitter also + post a few test cases, it won't end up as a heavy burden on a single person! -- cgit v1.2.3