# HG changeset patch
# User František Kučera <franta-hg@frantovo.cz>
# Date 1543787312 -3600
# Node ID a64671d5f997d7630118e9f0f8786d220bf33165
# Parent  46042297e0d6008a2912ccc8f2ecef56d581d846
faq: help

diff -r 46042297e0d6 -r a64671d5f997 relpipe-data/faq.xml
--- a/relpipe-data/faq.xml	Sun Dec 02 20:47:38 2018 +0100
+++ b/relpipe-data/faq.xml	Sun Dec 02 22:48:32 2018 +0100
@@ -22,7 +22,20 @@
 		<p>
 			<strong>How can I help you?</strong>		
 			<br/>
-			...
+			<ul>
+				<li>Suggest more examples how <m:name/> can be used; especially how YOU would like to use it.</li>
+				<li>We are looking for illustrations that would supplement our documentation and website.</li>
+				<li>
+					As an author of a program that generates or consumes some data, you could add relational input and output to your program. 
+					But please mention that we do not have v1.0 yet, so these features should be marked as experimental. 
+					The API might/will change. 
+					Other (and maybe better for now) option is to add input/output of values separated by null byte (<code>\0</code>).
+					This "API" will be supported for sure and data are simply the attribute values. There are no record separators (we know the number of attributes, so they are not needed).
+					Disadvantage of this approach is that the stream can contain only a single relation; and that the metadata are not embedded in the stream and must be passed separately.
+				</li>
+				<li>Review our source code and suggest improvements and fixes. Constructive criticism is always welcome. This is one of reasons why we publish our programs as free software.</li>
+				<li>Native speakers could suggest improvements and corrections of our English texts.</li>
+			</ul>
 		</p>
 		
 		<p>