Migration to gitlab

README.md

@@ -12,32 +12,31 @@ let the user fix them in an easy way, and generate the final CMakeLists files.
 
 This is what Autovala does. This process is done in three steps:
 
-  * First, Autovala checks all the folders and files, and writes a project
+    * First, Autovala checks all the folders and files, and writes a project
     file with the type of each file
-  * It also peeks the source files to determine which Vala packages they need,
+    * It also peeks the source files to determine which Vala packages they need,
     and generate automagically that list
-  * After that (and after allowing the user to check, if (s)he wishes, the
+    * After that (and after allowing the user to check, if (s)he wishes, the
     project file), it uses that project file to generate the needed CMakeLists
     files
 
 Autovala greatly simplifies the process of working with Vala because:
 
-  * Automatically determines the vala packages and libraries needed to compile
+    * Automatically determines the vala packages and libraries needed to compile
     and run the project, by inspecting the source code
-  * Automatically generates the .vapi and pkg-config files for libraries
-  * Automatically determinates the final destination for an icon, by checking
+    * Automatically generates the .vapi and pkg-config files for libraries
+    * Automatically determinates the final destination for an icon, by checking
     its type (svg or png) and, in the later case, its size.
-  * Automatically generates manpages from text files in several possible input
+    * Automatically generates manpages from text files in several possible input
     format (markdown, html, latex...).
-  * Greatly simplifies creating libraries in Vala, or a project with a binary
+    * Greatly simplifies creating libraries in Vala, or a project with a binary
     that uses a library defined in the same project.
-  * Automatically generates the metadata files to create .DEB and .RPM packages.
-  * Easily integrates unitary tests for each binary in the project.
-  * Can generate automatically DBUS bindings by using the DBUS introspection
+    * Automatically generates the metadata files to create .DEB and .RPM packages.
+    * Easily integrates unitary tests for each binary in the project.
+    * Can generate automatically DBUS bindings by using the DBUS introspection
     capabilities.
-  * Automatically generates the list of source files for GETTEXT.
-  * Simplifies mixing C and Vala source files.
-
+    * Automatically generates the list of source files for GETTEXT.
+    * Simplifies mixing C and Vala source files.
 
 ## COMPILING AUTOVALA ##
 
@@ -47,9 +46,15 @@ You also can compile the plugins for Gedit and Scratch Text Editor, which are
 in the folders *gedit_plugin* and *scratch_plugin*. You can find inside the
 instructions.
 
-
 ## USING AUTOVALA ##
 
 The DOC folder contains the Wiki dumped in HTML format. Just open the
 **index.html** file with your browser, or go to the **Wiki section** in GitHub,
 and enjoy.
+
+## CONTACTING THE AUTHOR ##
+
+Sergio Costas Rodriguez  
+rastersoft@gmail.com  
+http://www.rastersoft.com  
+https://gitlab.com/rastersoft/autovala