adding start of new structure

we will want to add the automated builds and deploy to GitHub packages next.
Since this first round is just very base images (e.g., ubuntu, and maybe others
are wanted) there will another kind of automated update that can handle building
a matrix of containers based on build args from a config file. This will be
developed next, see the README for more notes.

Signed-off-by: vsoch <[email protected]>

COPYRIGHT

@@ -0,0 +1,16 @@
+Intellectual Property Notice
+----------------------------
+
+RADIUSS Docker is licensed under the MIT license (LICENSE).
+
+Copyrights and patents in the RADIUSS Docker project are retained by
+contributors. No copyright assignment is required to contribute to RADIUSS
+Docker.
+
+
+SPDX usage
+------------
+
+Individual files contain SPDX tags instead of the full license text.
+This enables machine processing of license information based on the SPDX
+License Identifiers that are available here: https://spdx.org/licenses/

LICENSE

@@ -1,27 +1,22 @@
-Copyright (c) 2017-2020, Lawrence Livermore National Security, LLC.
-All rights reserved.
+MIT License
 
-Redistribution and use in source and binary forms, with or without
-modification, are permitted provided that the following conditions are met:
+Copyright (c) 2021, Lawrence Livermore National Security, LLC
 
-* Redistributions of source code must retain the above copyright notice, this
-  list of conditions and the following disclaimer.
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
 
-* Redistributions in binary form must reproduce the above copyright notice,
-  this list of conditions and the following disclaimer in the documentation
-  and/or other materials provided with the distribution.
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
 
-* Neither the name of the copyright holder nor the names of its
-  contributors may be used to endorse or promote products derived from
-  this software without specific prior written permission.
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
 
-THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
-AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
-IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
-DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
-FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
-DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
-SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
-CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
-OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
-OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

NOTICE

@@ -1,21 +1,22 @@
-Additional BSD Notice
+This work was produced under the auspices of the U.S. Department of
+Energy by Lawrence Livermore National Laboratory under Contract
+DE-AC52-07NA27344.
 
-1. This notice is required to be provided under our contract with the U.S. 
-Department of Energy (DOE). This work was produced at Lawrence Livermore 
-National Laboratory under Contract No. DE-AC52-07NA27344 with the DOE.
+This work was prepared as an account of work sponsored by an agency of
+the United States Government. Neither the United States Government nor
+Lawrence Livermore National Security, LLC, nor any of their employees
+makes any warranty, expressed or implied, or assumes any legal liability
+or responsibility for the accuracy, completeness, or usefulness of any
+information, apparatus, product, or process disclosed, or represents that
+its use would not infringe privately owned rights.
 
-2. Neither the United States Government nor Lawrence Livermore National 
-Security, LLC nor any of their employees, makes any warranty, express or 
-implied, or assumes any liability or responsibility for the accuracy, 
-completeness, or usefulness of any information, apparatus, product, or 
-process disclosed, or represents that its use would not infringe 
-privately-owned rights.
+Reference herein to any specific commercial product, process, or service
+by trade name, trademark, manufacturer, or otherwise does not necessarily
+constitute or imply its endorsement, recommendation, or favoring by the
+United States Government or Lawrence Livermore National Security, LLC.
+
+The views and opinions of authors expressed herein do not necessarily
+state or reflect those of the United States Government or Lawrence
+Livermore National Security, LLC, and shall not be used for advertising
+or product endorsement purposes.
 
-3. Also, reference herein to any specific commercial products, process, 
-or services by trade name, trademark, manufacturer or otherwise does not 
-necessarily constitute or imply its endorsement, recommendation, or favoring 
-by the United States Government or Lawrence Livermore National Security, LLC. 
-The views and opinions of authors expressed herein do not necessarily state 
-or reflect those of the United States Government or Lawrence Livermore 
-National Security, LLC, and shall not be used for advertising or product 
-endorsement purposes.

README.md

@@ -1,23 +1,52 @@
-# <img src="/share/axom/logo/axom_logo.png?raw=true" width="250" valign="middle" alt="Axom"/>
+# Radiuss Docker
 
-[![License](https://img.shields.io/badge/License-BSD%203--Clause-blue.svg)](https://github.com/LLNL/axom/blob/develop/LICENSE)
+![img/rse-radiuss.png](img/rse-radiuss.png)
 
-This repository contains Dockerfiles for CI builds for the
-[Axom](https://github.com/LLNL/Axom) project.
+[![License](https://img.shields.io/badge/License-MIT%203--Clause-blue.svg)](https://github.com/rse-radiuss/radius-docker/blob/main/LICENSE)
 
-Axom provides robust, flexible software infrastructure for the development of
-multi-physics applications and computational tools.
+This project is part of [RADIUSS](https://computing.llnl.gov/projects/radiuss), which
+has a focus on helping open source scientific projects use best practices for
+automation and development.
+
+This repository contains Dockerfiles for CI builds for use by the various
+[RADIUSS](https://software.llnl.gov/radiuss/) projects, and anyone else that
+might be interested. The image builds are automated and self-updating, and process
+described more below in detail.
+
+## Base Images
+
+A core base image is considered the lowest level - an operating system with
+only a handful of additional dependencies that won't vary with the operating system.
+For comparison with the [previous axom repository](https://github.com/LLNL/axom-docker), 
+these are currently only considered the "base" image (e.g., the "base" subfolders present 
+in nested folders there). A strategy to build other
+bases on top of that (e.g., with gcc, clang, etc.) is still in the works.
+To maintain these images, we will use the [uptodate](https://github.com/vsoch/uptodate)
+GitHub action.
+
+## Matrix Images
+
+A matrix image uses a base image, as described above, to add a matrix of different
+installs. This is a different approach than a core base image because we likely
+want to use a common template with different build arguments, as opposed to
+very different `Dockerfile` (as would be expected with base). We will
+also be using a GitHub action for this approach (not developed yet, and the
+`Dockerfile` and other logic is not added yet to the repository here.
+
+**under development**
 
 License
 -------
 
-Copyright (c) 2017-2020, Lawrence Livermore National Security, LLC. 
+Copyright (c) 2017-2021, Lawrence Livermore National Security, LLC. 
 Produced at the Lawrence Livermore National Laboratory.
 
-Copyrights and patents in the Axom project are retained by contributors.
-No copyright assignment is required to contribute to Axom.
+RADIUSS Docker is licensed under the MIT license [LICENSE](./LICENSE).
 
-See [LICENSE](./LICENSE) for details.
+Copyrights and patents in the RADIUSS Docker project are retained by
+contributors. No copyright assignment is required to contribute to RADIUSS
+Docker.
 
-Unlimited Open Source - BSD 3-clause Distribution
-`LLNL-CODE-741217` `OCEC-17-187`
+This work was produced under the auspices of the U.S. Department of
+Energy by Lawrence Livermore National Laboratory under Contract
+DE-AC52-07NA27344.