background and about

README.md

@@ -20,11 +20,25 @@ There are lots of software licenses out there (e.g. see [ScanCode LicenseDB](htt
 
 ## License name proliferation
 
-When you're working with compliance you are used to liceses called differently in source code or by tools (e.g. `GPLv2`, `GPL (v2)` and `GNU General Public License Version 2`) when all you really want too see is the [SPDX identifier](https://spdx.org/licenses/) `GPL-2.0-only`. A seasoned compliance engineer or lawyer knows this already, but we need this information machine readable.This projet aims at keeping a list of "all" different names for a license in a database, a Python API and a command line tool to easily convert a license name to an SPDX identifiers.
+When you're working with compliance you are used to liceses called differently in source code or by tools (e.g. `GPLv2`, `GPL (v2)` and `GNU General Public License Version 2`) when all you really want too see is the [SPDX identifier](https://spdx.org/licenses/) `GPL-2.0-only`. A seasoned compliance engineer or lawyer knows this already, but we need this information machine readable.
 
 ## License proliferation
 
-Another problem you face when working with compliance is the need to check whether the licenses in a combined work are compatible. One example is the [`X11-Style (Keith Packard)`](https://scancode-licensedb.aboutcode.org/x11-keith-packard.html) license, which really is the same license as the [Historical Permission Notice and Disclaimer - sell variant](https://spdx.org/licenses/HPND-sell-variant.html). `X11-Style (Keith Packard)` is not supported in for example the OSADL matrix, but `HPND-sell-variant` is. Again, a seasoned license engineer or lawyer knows which licenses are compatible and not, but we need to make it possible for a machine to assist us. This projet provides a database with mappings from one license to another license which is supported by the OSADL matrix, a Python API and a command line tool to assist you in checking compatibility.
+Another problem you face when working with compliance is the need to check whether the licenses in a combined work are compatible. One example is the [`X11-Style (Keith Packard)`](https://scancode-licensedb.aboutcode.org/x11-keith-packard.html) license, which really is the same license as the [Historical Permission Notice and Disclaimer - sell variant](https://spdx.org/licenses/HPND-sell-variant.html). `X11-Style (Keith Packard)` is not supported in for example the OSADL matrix, but `HPND-sell-variant` is. Again, a seasoned license engineer or lawyer knows which licenses are compatible and not, but we need to make it possible for a machine to assist us. 
+
+# About
+
+This projet aims at providing a database with:
+
+* "all" different names for a license in a database
+
+* mappings from one license to another license which is supported by the OSADL matrix
+
+and, to make the database easier to use:
+
+* a Python API
+
+* command line tool
 
 # Database
 
@@ -34,7 +48,11 @@ The data can be found in the [var directory](https://github.com/hesa/foss-licens
 
 * [flame](https://github.com/hesa/foss-licenses/blob/main/FLAME.md) - command line program
 
-* [Python API](https://github.com/hesa/foss-licenses/blob/main/PYTHON_API.md) - well, a Python API
+* [Python API](https://github.com/hesa/foss-licenses/blob/main/PYTHON_API.md)
+
+# Contributions
+
+More info soon.
 
 # Related tools and projects