Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
34 changes: 26 additions & 8 deletions config.toml
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,6 @@ theme = ["docsy"]
# Language settings
contentDir = "content/en"
defaultContentLanguage = "en"
defaultContentLanguageInSubdir = false
# Useful when translating.
enableMissingTranslationPlaceholders = true

Expand All @@ -14,7 +13,7 @@ enableRobotsTXT = true
# Will give values to .Lastmod etc.
enableGitInfo = true

disableKinds = ["taxonomy", "taxonomyTerm"]
disableKinds = ["taxonomy"]

# Highlighting config
pygmentsCodeFences = true
Expand All @@ -28,14 +27,33 @@ resampleFilter = "CatmullRom"
quality = 75
anchor = "smart"

defaultContentLanguage = "en"
defaultContentLanguageInSubdir = true

[languages]
[languages.en]
title = "Eclipse SW360"
description = "Eclipse SW360 official website"
languageName = "English"
# Weight used for sorting.
weight = 1
[languages.en]
languageName = "English"
weight = 1
contentDir = "content/en"

[languages.fr]
languageName = "Français"
weight = 2
contentDir = "content/fr"

[languages.ja]
languageName = "日本語"
weight = 3

[languages.vi]
languageName = "Tiếng Việt"
weight = 4

[languages.zh]
languageName = "中文"
weight = 5



[markup]
[markup.goldmark]
Expand Down
4 changes: 3 additions & 1 deletion content/en/docs/Deployment/Legacy/Deploy-Natively-11.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,9 @@ description:

## Introduction

We are covering the update for ubuntu 18.04 LTS here, because that is our main / agreed base system for running sw360. sw360 may run on a varienty of other linux distributions or OSes such as macosx, but in order to avoid problem we agreed on having a reference OS, which are the ubuntu long term releases. The author of this guide also uses macosx and homebrew which also works fairly well.
We are covering the update for Ubuntu 18.04 LTS here because it is our main and agreed-upon base system for running SW360. While SW360 may run on a variety of other Linux distributions or operating systems such as macOS, we have agreed to use Ubuntu Long-Term Releases as a reference OS to avoid compatibility issues. The author of this guide also uses macOS with Homebrew, which works fairly well.



Please note that during the time, the dependencies are updated and the version info might change.

Expand Down
69 changes: 69 additions & 0 deletions content/fr/_index.html
Original file line number Diff line number Diff line change
@@ -0,0 +1,69 @@
+++
title = "SW360"
linkTitle = "Eclipse SW360"
+++

{{<blocks/cover image_anchor="center" height="full">}}
<div class="row align-items-center">
<div class="col-lg-6">
<h4>
{{< figure src="/sw360/img/logos/logo_full.svg" width="400">}}
<p class="display-2 mb-0">
Software supply chain management done right !
</p>
</h4>
</div>
<div class="col-lg-6 mt-5 mt-lg-3 d-sm-block" style="display: none">
{{< figure src="/sw360/img/sw360screenshots/sw360screenshot-home.png"
width="500" >}}
</div>
</div>

<div class="display-cover mt-5">
<p>
SW360 is an open source software project licensed under the EPL-2.0 that
provides both a web application and a repository to collect, organize and
make available information about software components. It establishes a
central hub for software components in an organization.
</p>
</div>

<div class="mx-auto mt-5">
<a class="btn btn-lg btn-primary mr-3 mb-4" href="#vision-section">
<span style="font-size: larger; font-weight: bolder;">Our Vision</span>
</a>
</div>

{{</blocks/cover>}}


<a id="vision-section" class="td-offset-anchor"></a>
<section class="row td-box td-box--secondary td-box--gradient td-box--height-auto">
<div class="col">
<div class="row">
{{% blocks/vision title="Central SW Component Database" %}}
360 degree coverage for SW development beside the ‚Coding‘ as the Central SW
component database
{{% /blocks/vision %}}

{{% blocks/vision title="E2E Integration for Software Compliance" %}}
Having a stable, precise, transparent, controllable and easy extendable OSS toolchain for
long term running
{{% /blocks/vision %}}

</div>
<div class="row">
{{% blocks/vision title="Long Term Controlled OSS Toolchain" %}}
As automated
as possible, end-to-end compliance (Legal, Security/SBOM, Export Control)
tool-chain, seamlessly integrated in the SW development process (e.g.
DevOps)
{{% /blocks/vision %}}

{{% blocks/vision title="Embracing New Technologies" %}}
Enable easy onboarding of
new technolgies and new tools (e.g. container, new kind of packages)
{{% /blocks/vision %}}
</div>
</div>
</section>
40 changes: 40 additions & 0 deletions content/fr/about/index.md
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Based on multiple AI-assisted reviews of the French translation, I would like to share the following comments.
If you find these suggestions reasonable, please go ahead and apply the necessary corrections.
As mentioned earlier, I do not have knowledge of French myself.

🔍 Suggested Edits

Terminology Consistency:
If terms like “logiciel libre” and “open source” are used interchangeably, it would be helpful to clarify how each term is used within the project. This will make it easier for readers to understand.

Use of Polite Language:
If the target audience includes general users, using polite expressions (e.g., “Veuillez consulter...”) can help make the tone more approachable and user-friendly.

Grammar and Syntax Check:
Some sentences may need attention to subject-verb agreement or proper use of prepositions. For example, ensure correct structures such as “Les utilisateurs peuvent accéder à leurs données.”

Translation Consistency:
If the same terms or phrases are translated differently in various parts of the document, try to maintain consistency throughout.

Original file line number Diff line number Diff line change
@@ -0,0 +1,40 @@
---
title: "À propos d'Eclipse SW360"
linkTitle: À propos
menu:
main:
weight: 10

---

{{< blocks/cover image_anchor="top" height="sm" color="primary" >}}
{{< page/header >}}
{{< /blocks/cover >}}

<div class="container l-container--padded">


<div class="row">
<div class="col-12 col-lg-8">

Aujourd'hui, dans la plupart des cas, les logiciels ne sont pas créés à partir de zéro, mais plutôt assemblés à partir de divers composants logiciels tiers préemballés. Par conséquent, les organisations sont confrontées aux défis suivants :

* Vérifier différents aspects de la conformité lors de l'utilisation de composants logiciels tiers : conformité des licences, contrôles ECC, évaluations de propriété intellectuelle, etc.
* Partager les connaissances sur les composants logiciels et leurs qualités. Par exemple, quels composants logiciels devraient être recommandés, lesquels devraient être abandonnés selon quels critères ?
* Fournir une vue d'ensemble des composants utilisés : une organisation et sa gestion de la chaîne d'approvisionnement doivent disposer d'informations sur les actifs intégrés dans quels produits ou solutions.

Ces trois cas d'utilisation principaux ciblent différents rôles dans une organisation : responsables qualité, développeurs de logiciels, conseillers juridiques, architectes logiciels, responsables R&D, etc. Cependant, tous ces cas d'utilisation partagent un besoin commun d'un hub central qui gère les informations sur les composants logiciels.

SW360 est un projet logiciel open source sous licence EPL-2.0 qui fournit à la fois une application web et un référentiel pour collecter, organiser et rendre disponibles les informations sur les composants logiciels. Il établit un hub central pour les composants logiciels dans une organisation. SW360 permet de :

* suivre les composants utilisés par un projet/produit,
* évaluer les vulnérabilités de sécurité,
* maintenir les obligations de licence,
* appliquer des politiques, et
* générer des documents juridiques.

Par exemple, SW360 peut déclencher un processus de vérification dans l'outil de conformité open source FOSSology et importer le rapport de vérification résultant. Les données sont soit stockées dans la base de données de SW360, soit importées à la volée depuis des sources externes. À l'avenir, nous prévoyons d'avoir des fédérations d'instances SW360 qui partagent des informations sélectionnées. Outre son interface utilisateur web, toutes les fonctionnalités de SW360 sont disponibles via une API qui permet une intégration dans les outils devops existants.
</div>

</div>
</div>
Loading
Loading