doc: add information for open source community

.gitlab/issue_templates/Bug.md

+## Summary
+
+(Summarize the bug encountered concisely)
+
+## Steps to reproduce
+
+(How one can reproduce the issue - this is very important)
+
+## Example Project
+
+(If possible, please create an example project here on GitLab.com that exhibits the problematic
+behavior, and link to it here in the bug report.
+If you are using an older version of GitLab, this will also determine whether the bug has been fixed
+in a more recent version)
+
+## What is the current bugged behavior?
+
+(What actually happens)
+
+## What is the expected correct behavior?
+
+(What should happen instead)
+
+## Relevant logs and/or screenshots
+
+(Paste any relevant logs - please use code blocks (```) to format console output, logs, and code, as
+it's very hard to read otherwise.)
+
+## Possible fixes
+
+(If you can, link to the line of code that might be responsible for the problem)
+
+/title [BUG] a new bug
+/promote_to_incident
+/label ~bug ~new

.gitlab/issue_templates/Feature.md

+## Summary
+
+(Summarize the new feature concisely)
+
+## Use Case 
+
+(Describe the details of the use case - main & secondary scenario)
+
+## Actors
+
+(Targeted users)
+
+/title [FEATURE] a new feature
+/promote_to_incident
+/label ~feature ~new

.gitlab/issue_templates/Question.md

+## Summary
+
+(Summarize the information your request)
+
+## Details
+
+(Give details or describe the context of your request)
+
+/title [INFO] a new question
+/label ~info ~new

.gitlab/issue_templates/Security.md

+## Summary
+
+(Summarize the bug encountered concisely)
+
+## Steps to reproduce
+
+(How one can reproduce the issue - this is very important)
+
+## Example Project
+
+(If possible, please create an example project here on GitLab.com that exhibits the problematic
+behavior, and link to it here in the bug report.
+If you are using an older version of GitLab, this will also determine whether the bug has been fixed
+in a more recent version)
+
+## What is the current bugged behavior?
+
+(What actually happens)
+
+## What is the expected correct behavior?
+
+(What should happen instead)
+
+## Relevant logs and/or screenshots
+
+(Paste any relevant logs - please use code blocks (```) to format console output, logs, and code, as
+it's very hard to read otherwise.)
+
+## Possible fixes
+
+(If you can, link to the line of code that might be responsible for the problem)
+
+/title [SECURITY] a new security vulnerability
+/promote_to_incident
+/label ~security ~new:wq
+/confidential

CODE_OF_CONDUCT.adoc

+= DLCM Code of Conduct
+
+== Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+== Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others’ private information, such as a physical or email address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+== Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
+
+== Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+== Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at mailto:eresearch-opensource@unige.ch[,Code of Conduct].
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+== Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+=== Guideline #1 - Correction
+
+*Community Impact*: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+
+*Consequence*: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate.
+A public apology may be requested.
+
+=== Guideline #2 - Warning
+
+*Community Impact*: A violation through a single incident or series of actions.
+
+*Consequence*: A warning with consequences for continued behavior.
+No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time.
+This includes avoiding interactions in community spaces as well as external channels like social media.
+Violating these terms may lead to a temporary or permanent ban.
+
+=== Guideline #3 - Temporary Ban
+
+*Community Impact*: A serious violation of community standards, including sustained inappropriate behavior.
+
+*Consequence*: A temporary ban from any sort of interaction or public communication with the community for a specified period of time.
+No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+=== Guideline #4 - Permanent Ban
+
+*Community Impact*: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+*Consequence*: A permanent ban from any sort of public interaction within the community.
+
+== Attribution
+
+This Code of Conduct is adapted from the https://www.contributor-covenant.org[Contributor Covenant], version 2.1, available at https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by https://github.com/mozilla/diversity[Mozilla’s code of conduct enforcement ladder].
+
+For answers to common questions about this code of conduct, see the FAQ at https://www.contributor-covenant.org/faq.
+Translations are available at https://www.contributor-covenant.org/translations.

CONTRIBUTING.adoc

+= Contributing to the DLCM technology
+
+The DLCM technology is released under the https://spdx.org/licenses/GPL-2.0-or-later.html[GNU General Public License v2.0 or later] license.
+
+If you would like to contribute to it, or hack the code, this document will help you get started.
+
+== Code of Conduct
+
+This project adheres to the Contributor Covenant link:CODE_OF_CONDUCT.adoc[code of conduct]. By participating, you are expected to uphold this code. +
+Please report unacceptable behavior to mailto:eresearch-opensource@unige.ch[,Code of Conduct].
+
+
+== Using GitLab Issues
+
+We use https://gitlab.unige.ch/dlcm/ui/dlcm-portal/-/issues[GitLab] issues to track bugs and enhancements:
+
+* for https://gitlab.unige.ch/dlcm/ui/dlcm-portal/-/issues/new?issuable_template=Bug[bugs]
+* for https://gitlab.unige.ch/dlcm/ui/dlcm-portal/-/issues/new?issuable_template=Feature[new features]
+* for https://gitlab.unige.ch/dlcm/ui/dlcm-portal/-/issues/new?issuable_template=Improvement[enhancements]
+* for https://gitlab.unige.ch/dlcm/ui/dlcm-portal/-/issues/new?issuable_template=Question[others requests]
+
+If you are reporting a bug, please help to speed up problem diagnosis by providing as much information as possible.
+Ideally, that would include a small sample project that reproduces the problem.
+
+== Reporting Security Vulnerabilities
+
+If you think you have found a security vulnerability in DLCM technology please *DO NOT* disclose it publicly until we've had a chance to fix it.
+
+You must create https://gitlab.unige.ch/dlcm/ui/dlcm-portal/-/issues/new?issuable_template=Security-Vulnerability[security issue] to inform the communauty and detail the vulnerability.
+
+== Code Conventions and Housekeeping
+
+None of these are essential for a merge request, but they will all help. They can also be added after the original merge request, but before a merge.
+
+* Respect the code style of link:https://gitlab.unige.ch/solidify/solidify-frontend[Solidify framework]
+* A few unit tests would help a lot as well -- someone has to do it.
+* If no one else is using your branch, please rebase it against the current main branch (or another target branch in the project).
+* When writing a commit message please follow https://ec.europa.eu/component-library/v1.14.2/ec/docs/conventions/git/[these conventions].
+** Commit message format:
++
+----
+<type>(<scope>): <subject>
+----
+
+
+.Commit message quick reference
+****
+
+[cols="1a,1,1a"]
+|===
+|*`<type>`*
+|*`<scope>`*
+|*`<subject>`*
+
+| _Mandatory_
+| _Optional_
+| _Mandatory_
+
+|
+* `feat:` A new feature
+* `fix:` A bug fix
+* `docs:` Documentation changes
+* `style:` Changes that do not affect the meaning of the code (white space, formatting, missing semicolons, etc)
+* `refactor:` A code change that neither fixes a bug nor adds a feature
+* `perf:` A code change that improves performance
+* `test:` Adding missing tests
+* `build:` Changes that affect the build system, CI configuration or external dependencies
+* `chore:` Changes to the build process or auxiliary tools and libraries such as documentation generation
+
+|The scope could be anything specifying the place of the commit change.
+|
+The subject contains succinct a description of the change:
+
+* use the imperative, present tense: “change” not “changed” nor “changes”
+* don’t capitalize the first letter
+* no dot (.) at the end
+|=== 
+
+****
+

LICENSE.txt

+		    GNU GENERAL PUBLIC LICENSE
+		       Version 2, June 1991
+
+ Copyright (C) 1989, 1991 Free Software Foundation, Inc.,
+ 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+			    Preamble
+
+  The licenses for most software are designed to take away your
+freedom to share and change it.  By contrast, the GNU General Public
+License is intended to guarantee your freedom to share and change free
+software--to make sure the software is free for all its users.  This
+General Public License applies to most of the Free Software
+Foundation's software and to any other program whose authors commit to
+using it.  (Some other Free Software Foundation software is covered by
+the GNU Lesser General Public License instead.)  You can apply it to
+your programs, too.
+
+  When we speak of free software, we are referring to freedom, not
+price.  Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+this service if you wish), that you receive source code or can get it
+if you want it, that you can change the software or use pieces of it
+in new free programs; and that you know you can do these things.
+
+  To protect your rights, we need to make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if you
+distribute copies of the software, or if you modify it.
+
+  For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must give the recipients all the rights that
+you have.  You must make sure that they, too, receive or can get the
+source code.  And you must show them these terms so they know their
+rights.
+
+  We protect your rights with two steps: (1) copyright the software, and
+(2) offer you this license which gives you legal permission to copy,
+distribute and/or modify the software.
+
+  Also, for each author's protection and ours, we want to make certain
+that everyone understands that there is no warranty for this free
+software.  If the software is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original, so
+that any problems introduced by others will not reflect on the original
+authors' reputations.
+
+  Finally, any free program is threatened constantly by software
+patents.  We wish to avoid the danger that redistributors of a free
+program will individually obtain patent licenses, in effect making the
+program proprietary.  To prevent this, we have made it clear that any
+patent must be licensed for everyone's free use or not licensed at all.
+
+  The precise terms and conditions for copying, distribution and
+modification follow.
+
+		    GNU GENERAL PUBLIC LICENSE
+   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+  0. This License applies to any program or other work which contains
+a notice placed by the copyright holder saying it may be distributed
+under the terms of this General Public License.  The "Program", below,
+refers to any such program or work, and a "work based on the Program"
+means either the Program or any derivative work under copyright law:
+that is to say, a work containing the Program or a portion of it,
+either verbatim or with modifications and/or translated into another
+language.  (Hereinafter, translation is included without limitation in
+the term "modification".)  Each licensee is addressed as "you".
+
+Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope.  The act of
+running the Program is not restricted, and the output from the Program
+is covered only if its contents constitute a work based on the
+Program (independent of having been made by running the Program).
+Whether that is true depends on what the Program does.
+
+  1. You may copy and distribute verbatim copies of the Program's
+source code as you receive it, in any medium, provided that you
+conspicuously and appropriately publish on each copy an appropriate
+copyright notice and disclaimer of warranty; keep intact all the
+notices that refer to this License and to the absence of any warranty;
+and give any other recipients of the Program a copy of this License
+along with the Program.
+
+You may charge a fee for the physical act of transferring a copy, and
+you may at your option offer warranty protection in exchange for a fee.
+
+  2. You may modify your copy or copies of the Program or any portion
+of it, thus forming a work based on the Program, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+    a) You must cause the modified files to carry prominent notices
+    stating that you changed the files and the date of any change.
+
+    b) You must cause any work that you distribute or publish, that in
+    whole or in part contains or is derived from the Program or any
+    part thereof, to be licensed as a whole at no charge to all third
+    parties under the terms of this License.
+
+    c) If the modified program normally reads commands interactively
+    when run, you must cause it, when started running for such
+    interactive use in the most ordinary way, to print or display an
+    announcement including an appropriate copyright notice and a
+    notice that there is no warranty (or else, saying that you provide
+    a warranty) and that users may redistribute the program under
+    these conditions, and telling the user how to view a copy of this
+    License.  (Exception: if the Program itself is interactive but
+    does not normally print such an announcement, your work based on
+    the Program is not required to print an announcement.)
+
+These requirements apply to the modified work as a whole.  If
+identifiable sections of that work are not derived from the Program,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works.  But when you
+distribute the same sections as part of a whole which is a work based
+on the Program, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Program.
+
+In addition, mere aggregation of another work not based on the Program
+with the Program (or with a work based on the Program) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+  3. You may copy and distribute the Program (or a work based on it,
+under Section 2) in object code or executable form under the terms of
+Sections 1 and 2 above provided that you also do one of the following:
+
+    a) Accompany it with the complete corresponding machine-readable
+    source code, which must be distributed under the terms of Sections
+    1 and 2 above on a medium customarily used for software interchange; or,
+
+    b) Accompany it with a written offer, valid for at least three
+    years, to give any third party, for a charge no more than your
+    cost of physically performing source distribution, a complete
+    machine-readable copy of the corresponding source code, to be
+    distributed under the terms of Sections 1 and 2 above on a medium
+    customarily used for software interchange; or,
+
+    c) Accompany it with the information you received as to the offer
+    to distribute corresponding source code.  (This alternative is
+    allowed only for noncommercial distribution and only if you
+    received the program in object code or executable form with such
+    an offer, in accord with Subsection b above.)
+
+The source code for a work means the preferred form of the work for
+making modifications to it.  For an executable work, complete source
+code means all the source code for all modules it contains, plus any
+associated interface definition files, plus the scripts used to
+control compilation and installation of the executable.  However, as a
+special exception, the source code distributed need not include
+anything that is normally distributed (in either source or binary
+form) with the major components (compiler, kernel, and so on) of the
+operating system on which the executable runs, unless that component
+itself accompanies the executable.
+
+If distribution of executable or object code is made by offering
+access to copy from a designated place, then offering equivalent
+access to copy the source code from the same place counts as
+distribution of the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+  4. You may not copy, modify, sublicense, or distribute the Program
+except as expressly provided under this License.  Any attempt
+otherwise to copy, modify, sublicense or distribute the Program is
+void, and will automatically terminate your rights under this License.
+However, parties who have received copies, or rights, from you under
+this License will not have their licenses terminated so long as such
+parties remain in full compliance.
+
+  5. You are not required to accept this License, since you have not
+signed it.  However, nothing else grants you permission to modify or
+distribute the Program or its derivative works.  These actions are
+prohibited by law if you do not accept this License.  Therefore, by
+modifying or distributing the Program (or any work based on the
+Program), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Program or works based on it.
+
+  6. Each time you redistribute the Program (or any work based on the
+Program), the recipient automatically receives a license from the
+original licensor to copy, distribute or modify the Program subject to
+these terms and conditions.  You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties to
+this License.
+
+  7. If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License.  If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Program at all.  For example, if a patent
+license would not permit royalty-free redistribution of the Program by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Program.
+
+If any portion of this section is held invalid or unenforceable under
+any particular circumstance, the balance of the section is intended to
+apply and the section as a whole is intended to apply in other
+circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system, which is
+implemented by public license practices.  Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+
+  8. If the distribution and/or use of the Program is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Program under this License
+may add an explicit geographical distribution limitation excluding
+those countries, so that distribution is permitted only in or among
+countries not thus excluded.  In such case, this License incorporates
+the limitation as if written in the body of this License.
+
+  9. The Free Software Foundation may publish revised and/or new versions
+of the General Public License from time to time.  Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+Each version is given a distinguishing version number.  If the Program
+specifies a version number of this License which applies to it and "any
+later version", you have the option of following the terms and conditions
+either of that version or of any later version published by the Free
+Software Foundation.  If the Program does not specify a version number of
+this License, you may choose any version ever published by the Free Software
+Foundation.
+
+  10. If you wish to incorporate parts of the Program into other free
+programs whose distribution conditions are different, write to the author
+to ask for permission.  For software which is copyrighted by the Free
+Software Foundation, write to the Free Software Foundation; we sometimes
+make exceptions for this.  Our decision will be guided by the two goals
+of preserving the free status of all derivatives of our free software and
+of promoting the sharing and reuse of software generally.
+
+			    NO WARRANTY
+
+  11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
+FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN
+OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
+PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
+OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS
+TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE
+PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
+REPAIR OR CORRECTION.
+
+  12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
+REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
+INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
+OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
+TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
+YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
+PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+
+		     END OF TERMS AND CONDITIONS
+
+	    How to Apply These Terms to Your New Programs
+
+  If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+  To do so, attach the following notices to the program.  It is safest
+to attach them to the start of each source file to most effectively
+convey the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+    <one line to give the program's name and a brief idea of what it does.>
+    Copyright (C) <year>  <name of author>
+
+    This program is free software; you can redistribute it and/or modify
+    it under the terms of the GNU General Public License as published by
+    the Free Software Foundation; either version 2 of the License, or
+    (at your option) any later version.
+
+    This program is distributed in the hope that it will be useful,
+    but WITHOUT ANY WARRANTY; without even the implied warranty of
+    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+    GNU General Public License for more details.
+
+    You should have received a copy of the GNU General Public License along
+    with this program; if not, write to the Free Software Foundation, Inc.,
+    51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
+
+Also add information on how to contact you by electronic and paper mail.
+
+If the program is interactive, make it output a short notice like this
+when it starts in an interactive mode:
+
+    Gnomovision version 69, Copyright (C) year name of author
+    Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+    This is free software, and you are welcome to redistribute it
+    under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License.  Of course, the commands you use may
+be called something other than `show w' and `show c'; they could even be
+mouse-clicks or menu items--whatever suits your program.
+
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a "copyright disclaimer" for the program, if
+necessary.  Here is a sample; alter the names:
+
+  Yoyodyne, Inc., hereby disclaims all copyright interest in the program
+  `Gnomovision' (which makes passes at compilers) written by James Hacker.
+
+  <signature of Ty Coon>, 1 April 1989
+  Ty Coon, President of Vice
+
+This General Public License does not permit incorporating your program into
+proprietary programs.  If your program is a subroutine library, you may
+consider it more useful to permit linking proprietary applications with the
+library.  If this is what you want to do, use the GNU Lesser General
+Public License instead of this License.

README.adoc

+= DLCM Portal
+
+image::DLCM-logo.png[DLCM Technology,100]
+
+This angular project was generated with https://github.com/angular/angular-cli[Angular CLI] version 7.3.8.
+
+== Prerequisites
+
+* Name the folder who host current sources `dlcm-portal`
+* Install https://nodejs.org/en/[NodeJS LTS] : Use ALWAYS the "LTS" version and not upper.
+Currently, node version supported is 16.
+* Install https://angular.io/cli[Angular CLI] : version 13.2.1
+* For user of Jetbrains IDE (IntelliJ, WebStorm), go to `File > Settings > Appaearance & Behavior > System Settings` and disable the option `Use "safe write" (save changes to a temporary file first)`.
+* Download is secured by Cookie.
+To allow downloading file in dev env, add the following config on dlcm backend `dlcm.security.downloadToken.cookie.secure=false` to prevent generation of cookie with flag secure.
+Indeed, this flag avoid to use cookie in localhost.
+
+== Install
+
+For run the project on a dev server or build the project, you need to install all dependencies with the command
+
+----
+npm install
+----
+
+== Development server
+
+Before running the project, you need to setup both things :
+
+* in link:src/environments/environment.local.ts[environment.local.ts], set the url of the backend admin module if different from the default value (http://localhost:16105/dlcm/admin) :
+
+----
+admin: "http://localhost:16115/dlcm/admin",
+----
+
+* in the link:proxy.conf.local.js[proxy.conf.local.js] update the settings if you want :
+
+----
+// --- START SETTINGS ---
+const authorizationModulePort = 16100;
+const userFirstName = "Marty";
+const userLastName = "McFly";
+const userEmail = "999999@unige.ch";
+// ---- END SETTINGS ----
+----
+
+For running the project on a dev server, run the following command
+
+----
+npm run start
+----
+
+Once the server is started, you can access it on the url http://localhost:4200[http://localhost:4200].
+
+The app will automatically reload if you change any of the source files.
+
+This command run a proxy to contact backend services.
+
+== Build
+
+To build the project, run the command :
+
+----
+npm run build
+----
+
+The build artifacts will be stored in the `dist/` directory.
+
+== Dev with solidify-frontend
+
+_DLCM Portal_ is a _UNIGE_ project based on the _UNIGE_ angular library _Solidify-Frontend_.
+
+=== Prerequisites
+
+If you want to dev in the library Solidify-Frontend you need to pull https://gitlab.unige.ch/solidify/solidify-frontend[Solidify-Frontend] project in a folder called `solidify-frontend`.
+
+The folder `solidify_frontend` should be sibling of the current folder `dlcm-portal`
+
+=== Re-build _Solidify-Frontend_
+
+If you edit _Solidify_Frontend_ sources and you want to test it before commit it, you can build _Solidify_Frontend_ and inject binary automatically into _DLCM Portal_ node_modules.
+For that, you can run command
+
+----
+npm run build-solidify
+----
+
+The disadvantage of this method is that you have to restart the dev server every time to take into account the new version of solidify_frontend, which is slow.
+
+The solution is to use the live edit method described below
+
+=== Live edit
+
+To dev in live edit mode (_Solidify-Frontend_ sources included directly like internal sources) you can run the dev server with the command :
+
+----
+npm run start:solidify
+----
+
+instead the traditional command `npm run start`
+
+NB: Work only for typescript *.ts files.
+If you edit html or css files in _Solidify_Frontend_ sources, you need to run the build command `npm run build-solidify` described previously.
+
+== Generate client api
+
+If you want to update the model and enums of the app, we use https://github.com/OpenAPITools/openapi-generator[Open Api Generator].
+
+* Pull the master branch of the project _DLCM-Backend_
+* On the project DLCM-Backend run `mvn clean package`
+* Copy the content of the file `target/DLCM-Solution-2.1.0-SNAPSHOT/WEB-INF/classes/static/docs/openapi/dlcm-api.json`
+* Paste it in this project into the file link:src/assets/openapi/DLCM-APIs.json[DLCM-APIs.json]
+* On this project run the following command to generate the model from the file freshly updated
+
+----
+npm run generate-models
+----
+
+NB : `nmp install`, `npm run start` and `npm run build` call systematically `npm run generate-models``
+
+== Extract string to translate
+
+Run the command
+
+----
+npm run extract-translations
+----
+
+to extract automatically string to translate into assets/i18n/*.json
+
+== Debug NGXS state
+
+This project is compatible with http://extension.remotedev.io/[Redux Devtools extension].
+
+== Running unit tests
+
+Run the command
+
+----
+npm run test
+----
+
+to execute the unit tests via https://karma-runner.github.io[Karma].
+
+== Running end-to-end tests with Cypress
+
+E2e test can be executed ba running the script :
+
+----
+npm run cypress
+----
+
+who run simultaneously the portal and cypress console
+
+or by running the script :
+
+----
+npm run cypress-open
+----
+
+who just run the cypress console (you need to have a dev server currently executed).
+
+== Further help
+
+To get more help on the Angular CLI use `ng help` or go check out the https://github.com/angular/angular-cli/blob/master/README.md[Angular CLI README].
+
+== CSS Style
+
+The project use https://sass-lang.com/guide[SCSS Preprocessor].
+
+=== Graphical lib
+
+The project use https://material.angular.io/[Material design] as graphical lib.
+
+=== Grid
+
+There is no grid library used in the project but pure CSS.
+
+We mainly use https://css-tricks.com/snippets/css/complete-guide-grid/[CSS Grid] combined with homemade SASS mixins.
+
+For example, if you want to manage specific CSS behavior depends of screen size, you should use the following mixins :
+
+----
+@include respond-to-breakpoint-and-bigger('md') {
+  // css apply only for size >= md (= md, lg)
+}
+
+@include respond-to-smaller-than-breakpoint('md') {
+  // css apply only for size < md (= xs and sm)
+}
+----
+
+=== Icons
+
+The project use two libs for font icons :
+
+* https://material.io/resources/icons/[Material icon]
+* https://fontawesome.com/v5.15/icons?d=gallery&m=free[Font awesome (free)]
+
+== Lexical
+
+=== Types of components :
+
+==== Concept
+
+With solidify, we introduce a new convention of component :
+
+* Routables : Component routable.
+Can communicate with the store (dispatch actions and retrieve datas from store)
+* Containers : Component non routable.
+Can communicate with the store (dispatch actions and retrieve datas from store)
+* Presentationals : Dumb component (just input / output, no connection with store)
+* Dialogs : Component embedded in a material modal.
+Can communicate with the store (dispatch actions and retrieve datas from store)
+
+==== Generation
+
+You can use solidify schematics project to generate this types of component.
+
+Please refer to the `README.adoc` of the project `Solidify-Frontend`.
+As reminder, the shortcut to generate this new type of components are :
+
+----
+ng g solidify-frontend:routable my-routable
+ng g solidify-frontend:routable
+ng g solidify-frontend:container my-container
+ng g solidify-frontend:container
+ng g solidify-frontend:presentational my-presentational
+ng g solidify-frontend:presentational
+ng g solidify-frontend:dialog my-dialog
+ng g solidify-frontend:dialog
+ng g solidify-frontend:store-resource my-store-resource
+ng g solidify-frontend:store-resource
+ng g solidify-frontend:store-relation-2-tiers my-store-relation-2-tiers
+ng g solidify-frontend:store-relation-2-tiers
+ng g solidify-frontend:store-composition my-store-composition
+ng g solidify-frontend:store-composition
+----
+
+We are also compatible with default angular schematics with the command
+
+----
+ng generate component component-name
+----
+
+to generate a new component.
+
+You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module`.
+
+More info https://angular.io/cli/generate[here].
+
+== Contributing to project
+
+Please read our link:CONTRIBUTING.adoc[contributing guidelines] before contributing to the project.

README.md

-# dlcm-portal
-
-This project was generated with [Angular CLI](https://github.com/angular/angular-cli) version 7.3.8.
-
-## Prerequisites
-
-- Install [NodeJS LTS](https://nodejs.org/en/) : Use ALWAYS the "LTS" version.
-- Install [Angular CLI](https://angular.io/cli) : version 10.0.4
-- For user of Jetbrains IDE (IntelliJ, WebStorm), go to `File > Settings > Appaearance & Behavior > System Settings` and disable the
-  option `Use "safe write" (save changes to a temporary file first)`.
-- To test download token in local, add the following config on dlcm backend `dlcm.security.downloadToken.cookie.secure=false`
-
-## Install
-
-`npm install`
-
-## Development server
-
-For a dev server, run command `npm start`. Navigate to `http://localhost:4200/`.
-
-If you use config server in docker you need to change the ports used :
-
-- in your environment.local.ts defined the property : `admin: "http://localhost:16105/dlcm/admin",`
-- in the proxy.conf.local.js add the following lines :  
-  `
-  ...proxyConfVariable.oauth(16110), ...proxyConfVariable.shiblogin(16110),
-  `
-
-The app will automatically reload if you change any of the source files. This command run a proxy to contact backend services.
-
-## Build
-
-Run `npm run build` to build the project. The build artifacts will be stored in the `dist/` directory. Use the `--prod` flag for a production build.
-
-## Generate client api
-
-If you want to update the DLCM Api :
-
-- Pull the master branch of the project DLCM-Backend in a folder named `DLCM-Backend` at the same level of the frontend folder
-- On the project DLCM-Backend run `mvn clean package`
-- On this project run `npm run generate-models`
-
-## Generate element
-
-Run `ng generate component component-name` to generate a new component.
-
-You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module`.
-
-More info [here](https://angular.io/cli/generate).
-
-## Extract string to translate
-
-Run `npm run extract-translations` to extract string to translate into assets/i18n/*.json
-
-## Debug NGXS state
-
-This project is compatible with [Redux Devtools extension](http://extension.remotedev.io/).
-
-## Running unit tests
-
-Run `npm test` to execute the unit tests via [Karma](https://karma-runner.github.io).
-
-## Running end-to-end tests
-
-Run `npm e2e` to execute the end-to-end tests via [Protractor](http://www.protractortest.org/).
-
-## Further help
-
-To get more help on the Angular CLI use `ng help` or go check out the [Angular CLI README](https://github.com/angular/angular-cli/blob/master/README.md).
-
-## Grid
-
-There is no grid used in the project. We use pure [flex box](https://css-tricks.com/snippets/css/a-guide-to-flexbox/) css rule instead.
-
-If you want to manage specific css behavior depending of screen size, you should use the following mixins :
-
-    @include respond-to-breakpoint-and-bigger('md') {
-      // css apply only for size >= md (= md, lg)
-    }
-    
-    @include respond-to-smaller-than-breakpoint('md') {
-      // css apply only for size < md (= xs and sm)
-    }
-
-## Lexical
-
-### Types of components :
-
-#### Concept
-
-With solidify, we introduce a new convention of component :
-
-- Routables : Component routable. Can communicate with the store (dispatch actions and retrieve datas from store)
-- Containers : Component non routable. Can communicate with the store (dispatch actions and retrieve datas from store)
-- Presentationals : Dumb component (just input / output, no connection with store)
-- Dialogs : Component embedded in a material modal. Can communicate with the store (dispatch actions and retrieve datas from store)
-
-#### Generation
-
-You can use solidify schematics project to generate this types of component.
-
-Please refer to the `README.md` of the project `Solidify-Frontend`. As reminder, the shortcut to generate this new type of components are :
-
-    ng g solidify-frontend:routable my-routable
-    ng g solidify-frontend:routable
-    ng g solidify-frontend:container my-container
-    ng g solidify-frontend:container
-    ng g solidify-frontend:presentational my-presentational
-    ng g solidify-frontend:presentational
-    ng g solidify-frontend:dialog my-dialog
-    ng g solidify-frontend:dialog
-    ng g solidify-frontend:store-resource my-store-resource
-    ng g solidify-frontend:store-resource
-    ng g solidify-frontend:store-relation-2-tiers my-store-relation-2-tiers
-    ng g solidify-frontend:store-relation-2-tiers
-    ng g solidify-frontend:store-composition my-store-composition
-    ng g solidify-frontend:store-composition
-
-#### Cypress E2E Tests
-
-For now e2e test can be executed ba running the script :
-
-    npm run cypress
-
-or by running the script :
-
-    npm run cypress-open
-
-the first command will run simultaneously the portal and cypress console, the second command will just run the cypress console.
-

package.json

 {
   "name": "dlcm-portal",
   "version": "2.1.0-SNAPSHOT",
+  "license": "GPL-2.0-or-later",
+  "author": "UNIGE (University of Geneva)",
+  "repository": {
+    "type": "git",
+    "url": "https://gitlab.unige.ch/dlcm/ui/dlcm-portal"
+  },
   "engines": {
     "node": "^16.0.0"
   },
@@ -45,7 +51,7 @@
     "build-solidify": "rm -rf ./node_modules/solidify-frontend && cd ../solidify-frontend && npm run build && cp -fr dist/solidify-frontend ../dlcm-portal/node_modules && cd ../dlcm-portal && npm run solidify-generate-timestamped-version",
     "solidify-generate-timestamped-version": "ts-node --project tsconfig-ts-node.json scripts/solidify-generate-timestamped-version.script.ts",
     "update-project-version": "ts-node --project tsconfig-ts-node.json scripts/dlcm-update-version.script.ts",
-    "extract-licenses": "npm-license-crawler --production --dependencies --csv ./dist/DLCM-Frontend/third-party-licenses.csv"
+    "extract-licenses": "npm-license-crawler --production --csv ./dist/dlcm-portal/third-party-licenses.csv"
   },
   "dependencies": {
     "@angular/animations": "13.2.1",
@@ -136,6 +142,7 @@
     "karma-jasmine-html-reporter": "1.7.0",
     "karma-junit-reporter": "2.0.1",
     "local-web-server": "5.1.1",
+    "npm-license-crawler": "0.2.1",
     "ngx-translate-extract-csv": "1.1.1",
     "protractor": "7.0.0",
     "ts-loader": "9.2.6",

pom.xml

 <?xml version="1.0" encoding="UTF-8"?>
-<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
+<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+         xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
     <modelVersion>4.0.0</modelVersion>
 
     <groupId>ch.dlcm</groupId>
@@ -7,6 +8,14 @@
     <packaging>pom</packaging>
     <version>2.1.0-SNAPSHOT</version>
 
+    <licenses>
+        <license>
+            <name>GNU General Public License v2.0 or later</name>
+            <url>https://spdx.org/licenses/GPL-2.0-or-later.html</url>
+            <comments>SPDX-License-Identifier: GPL-2.0-or-later</comments>
+        </license>
+    </licenses>
+
     <properties>
         <!-- Base web context used for the Angular application -->
         <web.context.root>undefined</web.context.root>

src/assets/files-to-copy/proxy.conf.local.js-to-copy.txt

-const proxyConfVariable = require("./proxy.conf.variable.js")
+const proxyConfVariable = require("./proxy.conf.variable.js");
+
+// --- START SETTINGS ---
+const authorizationModulePort = 16100;
+const userFirstName = "Marty";
+const userLastName = "McFly";
+const userEmail = "999999@unige.ch";
+// ---- END SETTINGS ----
 
 exports.obj = {
-    ...proxyConfVariable.oauth(16100),
-    ...proxyConfVariable.shiblogin(16100, "Marty", "McFly", "999999@unige.ch"),
+    ...proxyConfVariable.oauth(authorizationModulePort),
+    ...proxyConfVariable.shiblogin(authorizationModulePort, userFirstName, userLastName, userEmail),
 }