Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
A
apertis-website
Manage
Activity
Members
Labels
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Operate
Environments
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
docs
apertis-website
Commits
767c369e
Commit
767c369e
authored
3 years ago
by
Guy Lunardi
Committed by
Emanuele Aina
3 years ago
Browse files
Options
Downloads
Patches
Plain Diff
export-controls: Minor tweaks
parent
ca65fe07
No related branches found
Branches containing commit
No related tags found
1 merge request
!394
export-controls: Minor tweaks
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
content/concepts/export-controls.md
+4
-3
4 additions, 3 deletions
content/concepts/export-controls.md
with
4 additions
and
3 deletions
content/concepts/export-controls.md
+
4
−
3
View file @
767c369e
...
...
@@ -5,7 +5,8 @@ outputs = [ "html", "pdf-in",]
date = "2021-09-26"
+++
Apertis targets a global community developing global products, and this
Apertis targets a global community, developing products with international reach, and this
necessarily makes it interact with the legislation regulating the export of
goods, software and technology. In particular, Apertis can be used on products
that fall under the "dual-use" categorization since they can be used for both
...
...
@@ -708,8 +709,8 @@ provided since in some cases they need to change depending on how the final
product is distributed: for instance, software under 5D002 may need to be
reclassified as 5D992 when distributed under the mass-market provisions.
It
's
responsibility of the maintainer of each software components to assess
which export control restriction apply to their packages and manually capture
It
is the
responsibility of the maintainer of each software components to assess
which export control restriction
s
apply to their packages and manually capture
the output in the packages metadata.
The metadata is used when deployable software images and updates are built, to
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment