Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

github workflows : check licensing of *.j2 files #828

Open
giem-git opened this issue Dec 22, 2023 · 0 comments
Open

github workflows : check licensing of *.j2 files #828

giem-git opened this issue Dec 22, 2023 · 0 comments
Assignees

Comments

@giem-git
Copy link
Contributor

Jinja template files (*.j2) should have a copyright header as follows :

{#                               
# Copyright 2022 TOSIT.IO
# SPDX-License-Identifier: Apache-2.0
#}  

For most j2 files this header should simply be added and it will not change the final file content.

Some template files are derived from original configuration files and already have an Apache Software Foundation license block :

# Licensed to the Apache Software Foundation (ASF) under one
# or more contributor license agreements.  See the NOTICE file
# distributed with this work for additional information
# regarding copyright ownership.  The ASF licenses this file
# to you under the Apache License, Version 2.0 (the
# "License"); you may not use this file except in compliance
# with the License.  You may obtain a copy of the License at
#
#     http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.

How should we handle these files ?

@giem-git giem-git self-assigned this Dec 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant