diff --git a/.github/workflows/codeql-analysis.yml b/.github/workflows/codeql-analysis.yml
deleted file mode 100644
index 7a94836c5a761092bcb1d9b840b093e958604bd4..0000000000000000000000000000000000000000
--- a/.github/workflows/codeql-analysis.yml
+++ /dev/null
@@ -1,73 +0,0 @@
-# For most projects, this workflow file will not need changing; you simply need
-# to commit it to your repository.
-#
-# You may wish to alter this file to override the set of languages analyzed,
-# or to provide custom queries or build logic.
-#
-# ******** NOTE ********
-# We have attempted to detect the languages in your repository. Please check
-# the `language` matrix defined below to confirm you have the correct set of
-# supported CodeQL languages.
-#
-name: "CodeQL"
-
-on:
- push:
- branches: [ master ]
- pull_request:
- # The branches below must be a subset of the branches above
- branches: [ master ]
- schedule:
- - cron: '39 23 * * 1'
-
-jobs:
- analyze:
- name: Analyze
- runs-on: ubuntu-latest
-
- strategy:
- fail-fast: false
- matrix:
- language: [ 'java', 'javascript' ]
- # CodeQL supports [ 'cpp', 'csharp', 'go', 'java', 'javascript', 'python' ]
- # Learn more:
- # https://docs.github.com/en/free-pro-team@latest/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#changing-the-languages-that-are-analyzed
-
- steps:
- - name: Checkout repository
- uses: actions/checkout@v2
-
- # Initializes the CodeQL tools for scanning.
- - name: Initialize CodeQL
- uses: github/codeql-action/init@v1
- with:
- languages: ${{ matrix.language }}
- # If you wish to specify custom queries, you can do so here or in a config file.
- # By default, queries listed here will override any specified in a config file.
- # Prefix the list here with "+" to use these queries and those in the config file.
- # queries: ./path/to/local/query, your-org/your-repo/queries@main
-
- ## Required to run in Quarkus, as it has a minimum Java version of 11 (1.8 is provided OOTB)
- - name: Setup Java JDK
- uses: actions/setup-java@v1.4.3
- with:
- java-version: 11
-
- # Autobuild attempts to build any compiled languages (C/C++, C#, or Java).
- # If this step fails, then you should remove it and run the build manually (see below)
- - name: Autobuild
- uses: github/codeql-action/autobuild@v1
-
- # â„¹ï¸ Command-line programs to run using the OS shell.
- # 📚 https://git.io/JvXDl
-
- # âœï¸ If the Autobuild fails above, remove it and uncomment the following three lines
- # and modify them (or add more) to build your code if your project
- # uses a compiled language
-
- #- run: |
- # make bootstrap
- # make release
-
- - name: Perform CodeQL Analysis
- uses: github/codeql-action/analyze@v1
diff --git a/.github/ISSUE_TEMPLATE/adopter_request.md b/.gitlab/issue_templates/adopter_request.md
similarity index 100%
rename from .github/ISSUE_TEMPLATE/adopter_request.md
rename to .gitlab/issue_templates/adopter_request.md
diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.gitlab/issue_templates/bug_report.md
similarity index 100%
rename from .github/ISSUE_TEMPLATE/bug_report.md
rename to .gitlab/issue_templates/bug_report.md
diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md
index 5987884b23ee828a4863992c855ccc1c86c65d29..e2746c29daa15b3e18a2abf33bea31e49216b024 100644
--- a/CODE_OF_CONDUCT.md
+++ b/CODE_OF_CONDUCT.md
@@ -1,72 +1,43 @@
# Community Code of Conduct
+Version 1.2
+August 19, 2020
-**Version 1.1
-October 21, 2019**
+##Our Pledge
-## Our Pledge
+In the interest of fostering an open and welcoming environment, we as community members, contributors, committers, and project leaders pledge to make participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
-In the interest of fostering an open and welcoming environment, we as
-contributors and maintainers pledge to make participation in our project and
-our community a harassment-free experience for everyone, regardless of age, body
-size, disability, ethnicity, sex characteristics, gender identity and expression,
-level of experience, education, socio-economic status, nationality, personal
-appearance, race, religion, or sexual identity and orientation.
+## Our Standards
-## Our Standards
+Examples of behavior that contributes to creating a positive environment include:
-Examples of behavior that contributes to creating a positive environment
-include:
-
-* Using welcoming and inclusive language
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy towards other community members
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
Examples of unacceptable behavior by participants include:
-* The use of sexualized language or imagery and unwelcome sexual attention or
- advances
-* Trolling, insulting/derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or electronic
- address, without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
- professional setting
+* The use of sexualized language or imagery and unwelcome sexual attention or advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
## Our Responsibilities
+With the support of the Eclipse Foundation staff (the “Staffâ€), project committers and leaders are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Project committers and 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, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies within all project spaces, and it also applies when an individual is representing the Eclipse Foundation project or its community in public spaces. Examples of representing a project or community include posting via an official social media account, or acting as a project representative at an online or offline event. Representation of a project may be further defined and clarified by project committers, leaders, or the EMO.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the Staff at codeofconduct@eclipse.org. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The Staff is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
-Project maintainers are responsible for clarifying the standards of acceptable
-behavior and are expected to take appropriate and fair corrective action in
-response to any instances of unacceptable behavior.
-
-Project maintainers 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, or to ban temporarily or
-permanently any contributor for other behaviors that they deem inappropriate,
-threatening, offensive, or harmful.
-
-## Scope
-
-This Code of Conduct applies within all project spaces, and it also applies when
-an individual is representing the project or its community in public spaces.
-Examples of representing a project or community include using an official
-project e-mail address, posting via an official social media account, or acting
-as an appointed representative at an online or offline event. Representation of
-a project may be further defined and clarified by project maintainers.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting the project team at codeofconduct@eclipse.org. All
-complaints will be reviewed and investigated and will result in a response that
-is deemed necessary and appropriate to the circumstances. The project team is
-obligated to maintain confidentiality with regard to the reporter of an incident.
-Further details of specific enforcement policies may be posted separately.
-
-Project maintainers who do not follow or enforce the Code of Conduct in good
-faith may face temporary or permanent repercussions as determined by other
-members of the project's leadership.
+Project committers or leaders who do not follow the Code of Conduct in good faith may face temporary or permanent repercussions as determined by the Staff.
## Attribution
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 41be85137ceb132a5c1a10f794911d84c57569f6..b76f086c1bf0301b69876e8155bcf5c0bcf53cff 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -3,15 +3,15 @@
Thanks for your interest in this project.
## Project description
-Adopters are organizations that voluntarily show their support for the Eclipse IoT projects they have adopted .
+Adopters are organizations that voluntarily show their support for the Eclipse projects they have adopted .
-* https://github.com/eclipsefdn/eclipsefdn-project-adopters
+* https://gitlab.eclipse.org/eclipsefdn/it/api/eclipsefdn-project-adopters
## Developer resources
The project maintains the following source code repositories
-* https://github.com/eclipsefdn/eclipsefdn-project-adopters
+* https://gitlab.eclipse.org/eclipsefdn/it/api/eclipsefdn-project-adopters
## Eclipse Contributor Agreement
diff --git a/NOTICE.md b/NOTICE.md
index 825bbfe4cc659ffe964016526c3edaba707d0aa7..db59bd4c93f67cdb97fed026342032634b1c28b2 100644
--- a/NOTICE.md
+++ b/NOTICE.md
@@ -2,7 +2,7 @@
This content is produced and maintained by the Eclipse Foundation. Trademarks are the property of their respective owners.
-* Project home: https://github.com/eclipsefdn/eclipsefdn-project-adopters
+* Project home: https://gitlab.eclipse.org/eclipsefdn/it/api/eclipsefdn-project-adopters
## Trademarks
diff --git a/README.md b/README.md
index 36e06693386b931523606f531bcca24f0b6ad4bb..c4ba64fd4a3294c873f3b9b49323a6d5c043acf6 100644
--- a/README.md
+++ b/README.md
@@ -10,8 +10,8 @@ npm install && hugo server
## Contributing
-1. [Fork](https://help.github.com/articles/fork-a-repo/) the [EclipseFdn/eclipsefdn-project-adopters](https://github.com/EclipseFdn/eclipsefdn-project-adopters) repository
-2. Clone repository: `git clone https://github.com/[your_github_username]/eclipsefdn-project-adopters.git`
+1. [Fork](https://docs.gitlab.com/ee/user/project/repository/forking_workflow.html) the [EclipseFdn/eclipsefdn-project-adopters](https://gitlab.eclipse.org/eclipsefdn/it/api/eclipsefdn-project-adopters) repository
+2. Clone repository: `git clone https://gitlab.eclipse.org/[your_eclipsefdn_username]/eclipsefdn-project-adopters.git`
3. Create your feature branch: `git checkout -b my-new-feature`
4. Commit your changes: `git commit -m 'Add some feature' -s`
5. Push feature branch: `git push origin my-new-feature`
@@ -23,7 +23,7 @@ Does your organization use Eclipse projects? Organizations — whether they are
Adopters are organizations that voluntarily show their support for the Eclipse projects they have adopted (i.e. shipping commercial products based on the projects and/or using the projects for non-commercial or internal reasons). On this website, adopters are displayed under the [/adopters](https://eclipsefdn-project-adopters/adopters/) virtual path.
-You can add your organization logo to our list of adopters by submitting a pull request or by creating an [issue](https://github.com/EclipseFdn/eclipsefdn-project-adopters/issues/new?template=adopter_request.md). You can attach files to an issue by dragging and dropping them in the text editor of the form.
+You can add your organization logo to our list of adopters by submitting a pull request or by creating an [issue](https://gitlab.eclipse.org/eclipsefdn/it/api/eclipsefdn-project-adopters/-/issues/new?issuable_template=adopter_request.md). You can attach files to an issue by dragging and dropping them in the text editor of the form.
If you plan on submitting a pull request, you will need to make the following changes to the website's codebase:
diff --git a/package.json b/package.json
index 51e121b586bb10cb23a6b806db1232c9eaa7f0b0..255d190c6f524cc0c878722e95230c9fb65a43b8 100644
--- a/package.json
+++ b/package.json
@@ -5,11 +5,11 @@
"license": "EPL-2.0",
"version": "0.0.1",
"bugs": {
- "url": "https://github.com/EclipseFdn/eclipsefdn-project-adopters/issues"
+ "url": "https://gitlab.eclipse.org/eclipsefdn/it/api/eclipsefdn-project-adopters/-/issues"
},
"repository": {
"type": "git",
- "url": "git://github.com/EclipseFdn/eclipsefdn-project-adopters.git"
+ "url": "git://gitlab.eclipse.org/eclipsefdn/it/api/eclipsefdn-project-adopters.git"
},
"scripts": {
"test": "jsonlint config/adopters.json",