From fea815112be57c47d8c1b811489bbcee6921e937 Mon Sep 17 00:00:00 2001 From: kbp-di Date: Thu, 9 Nov 2023 13:04:08 +0100 Subject: [PATCH] Remove files that should be in main repo --- AUTHORS.md | 18 ------------------ CHANGELOG.md | 8 -------- CODE_OF_CONDUCT.md | 7 ------- CONTRIBUTING.md | 29 ----------------------------- GOVERNANCE.md | 18 ------------------ LICENSE | 21 --------------------- README.md | 25 ------------------------- 7 files changed, 126 deletions(-) delete mode 100644 AUTHORS.md delete mode 100644 CHANGELOG.md delete mode 100644 CODE_OF_CONDUCT.md delete mode 100644 CONTRIBUTING.md delete mode 100644 GOVERNANCE.md delete mode 100644 LICENSE delete mode 100644 README.md diff --git a/AUTHORS.md b/AUTHORS.md deleted file mode 100644 index 9fe55d2..0000000 --- a/AUTHORS.md +++ /dev/null @@ -1,18 +0,0 @@ -# Thank you! – everyone that help! - -Here is a list of MUCH-APPRECIATED CONTRIBUTORS -- -people who laid the groundwork, have written code, reported bugs, added -documentation, helped answer questions, and generally made **OS2compliance** that much -better: - -* **Nina Birthe Sørensen** - Came up with the idea for the project, laid all the groundwork, designed it, and answered developers' questions day and night. -* **OS2 Project** -For making this and many other projects possible. -* **Ishøj, Gentofte, Svendborg and Lolland municipalities** -For taking part in the development process. - - -A big THANK YOU goes to: - -All municipalities who initiated the project: Ishøj, Jammerbugt, Gentofte, Lolland, Norddjurs, Svendborg, Brøndby, Lyngby-Taarbæk, Viborg, Syddjurs, Herning, Favrskov, Faxe, Kalundborg diff --git a/CHANGELOG.md b/CHANGELOG.md deleted file mode 100644 index 0fe2c92..0000000 --- a/CHANGELOG.md +++ /dev/null @@ -1,8 +0,0 @@ -# Change Log in OS2 projects/products - -All notable changes to the project MUST be documented in this file. - -The format can be based on [Keep a Changelog](http://keepachangelog.com/) -and this project adheres to adher to [Semantic Versioning](http://semver.org/). - -## [Unreleased] \ No newline at end of file diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md deleted file mode 100644 index e5702de..0000000 --- a/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,7 +0,0 @@ -# Code of Conduct - -In the interest of fostering an open and welcoming environment we pledge to making participation in our project and our community a harassment-free experience for everyone. - -Please refer to the general [Code of Conduct for OS2](https://os2.eu/side/code-conduct) - -If the project is in need of a project specific CoC you can refer to [Contributor Covenant](https://www.contributor-covenant.org/) \ No newline at end of file diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md deleted file mode 100644 index 2970b54..0000000 --- a/CONTRIBUTING.md +++ /dev/null @@ -1,29 +0,0 @@ -# Contribution guidelines for *OS2compliance* - -If you want to contribute to *OS2compliance*, we ask you to follow these guidelines. - -## Reporting bugs -If you have encountered a bug in *OS2compliance*, please check if an issue already exists in the list of existing [issues](https://os2web.atlassian.net/), if such an issue does not exist, you can create one [here](https://os2web.atlassian.net/). When writing the bug report, try to add a clear example that shows how to reproduce said bug. - -## Adding new features -Before making making changes to the code, we advise you to first check the list of existing [issues](https://os2web.atlassian.net/) for OS2compliance to see if an issue for the suggested changes already exists. If such an issue does not exist, you can create one [here](https://os2web.atlassian.net/). Creating an issue gives an opportunity for other developers to give tips even before you start coding. If you are in the early idea phase, or if your feature requires larger changes, you can discuss it with the [projects coordination group](https://os2.eu) or by [contacting OS2 directly](https://os2.eu/kontakt) to make sure you are heading in the right direction. - -### Code style -There is no enforced coding style at this time, but we encourage you to follow the [Google Java Style Guide](https://google.github.io/styleguide/javaguide.html) - -### Forking the repository -In order to implement changes to *OS2compliance* when you do not have rights for the required repository, you must first fork the repository. Once the repository is forked, you can clone it to your local machine. - -### Making the changes -On your local machine, create a new branch, and name it like: -- `feature/some-new-feature`, if the changes implement a new feature -- `issue/some-issue`, if the changes fix an issue - -Once you have made changes or additions to the code, you can commit them (try to keep the commit message descriptive but short). If an issue exists in the issue list for the changes you made, be sure to format your commit message like `"Fixes # -- description of changes made`, where `"` corresponds to the number of the issue on Jira or GitHub. To demonstrate that the changes implement the new feature/fix the issue, make sure to also add tests. - -### Making a pull request -If all changes have been committed, you can push the branch to your fork of the repository and create a pull request to the `master` branch of the *OS2compliance* repository. Your pull request will be reviewed, if applicable feedback will be given and if everything is approved, it will be merged. - -### Reviews on releases - -All pull requests will be reviewed before they are merged to a release branch. As well as being reviewed for functionality and following the code style they will be checked with the steering committee and/or the coordination group for the project. \ No newline at end of file diff --git a/GOVERNANCE.md b/GOVERNANCE.md deleted file mode 100644 index 0503fb7..0000000 --- a/GOVERNANCE.md +++ /dev/null @@ -1,18 +0,0 @@ -# Governance in the project - -The product/project is part of OS2's portfolio and is maintained according to the model defined by the association OS2. - -## Definitions - -### Project - -### Product - -### Users -are those whose primary relationship to the product/project is to consume/use it's code and othere results. - -### Contributors -are those who make contributions to the product/project, ranging from casual to significant, but who aren't responsible for it's overall success. - -### Maintainers -are those who are responsible for the future of a project's repository (or respositories), whoses decisions affect the project laterally. Maintainers can be thought of as "trustees" or stewards of the project/product. diff --git a/LICENSE b/LICENSE deleted file mode 100644 index 7d510d0..0000000 --- a/LICENSE +++ /dev/null @@ -1,21 +0,0 @@ -MIT License - -Copyright (c) 2022 just-the-docs - -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: - -The above copyright notice and this permission notice shall be included in all -copies or substantial portions of the Software. - -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. diff --git a/README.md b/README.md deleted file mode 100644 index 3f24e15..0000000 --- a/README.md +++ /dev/null @@ -1,25 +0,0 @@ -# OS2compliance -OS2compliance er en komplet ISMS-løsning der udvikles med det formål at skabe et simpelt kommunespecifikt værktøj, der understøtter kommunernes komplekse setup med mange IT-systemer og mange behandlingsaktiviteter. - -Udgangspunktet for designet er en naturlig sammenhæng mellem modulerne, så der skabes et godt overblik og det sikres, at viden er, hvor man har behov for den. Sammenhæng vil være i fokus, så der sikres så få klik som muligt. - -Løsningen skal kunne rumme at være fagsystem for Informationssikkerhedsteamet, kontrolværktøj for de decentrale enheder og rapporteringsværktøj for ledelsen. Et samlet sted for arbejdet med compliance vedr. informationssikkerhed, som er udviklet til og af kommunerne. - -Løsningen vil være bygget med mulighed for tilpasning, så man arbejder med compliance på kommunens aktuelle modenhedsniveau. -Videre vil løsningen have relevante integrationer, herunder AD-integration, KITOS-integration og CVR-integration, så tiden bruges på compliance og ikke vedligeholdelse af organisationsopsætning eller indtastning af aktiver. - -OS2compliance tilgås via en browser. - -## Documentation -[Authors](AUTHORS.md) -[Changelog](CHANGELOG.md) -[Code of Conduct](CODE_OF_CONDUCT.md) -[Contribution guidelines](CONTRIBUTING.md) -[Developer Guide](DEVELOPER_GUIDE.md) -[Governance in the project](GOVERNANCE.md) -[OS2compliance security policies](SECURITY.md) - -*Only in danish* -[Original løsningsbeskrivelse](doc/Løsningsbeskrivelse.docx) -[OS2compliance - AD FS opsætning]() -[OS2compliance - OS2faktor opsætning]()