Home.md

@@ -157,7 +157,7 @@ For each project, there may be reasons to lean towards a permissive, weakly reci
           - [LICENCE](https://www.ohwr.org/project/pts/tree/master/)
           - [pts main
             program](https://www.ohwr.org/project/pts/tree/master/)
-      - Please consider using "GPL version 3 or later" if looking for a good strongly-reciprocal licence for your software.
+      - Please consider using "GPL version 3 or later" if looking for a good strongly-reciprocal licence for your software. The SPDC identifiers for the "or later" versions of the GNU licences are special. They do not use the "+" suffix but prefer the more explicit "-or-later". Therefore, "GPL-3.0-or-later" is the correct SPDX identifier in this case.
 
 
 <!-- end list -->
@@ -167,6 +167,7 @@ For each project, there may be reasons to lean towards a permissive, weakly reci
       - Used in projects where a strong copyleft license will result in
         reduced adoption, such as the [masterFIP
         library](https://gitlab.cern.ch/cohtdrivers/masterfip/tree/master/lib).
+      - For new projects in which a weakly reciprocal sharing regime makes sense, we recommend licensing under "LGPL-3.0-or-later". Version 2.1 of LGPL is also OK. We have several projects licensed under "LGPL-2.1-or-later" and the benefits brought about by 3.0 do not offset the hassle/risk to change licence, so we are leaving them as 2.1. 
       - Another good weakly reciprocal option is the [Mozilla Public License v2](https://www.mozilla.org/en-US/MPL/).
 
    - Permissive: a modern option for this licensing regime, including a patent licensing clause, is the [Apache v2](https://www.apache.org/licenses/) licence.