...
Official development guides of ONAP: Development Guides
Contribution
license guideline
ONAP FUSS guide lines: Rules for implementing FOSS in a project
Clarification
any file that is being committed must have a a licensing header based on the ONAP guideline.
as SDC seed code came from AT&T
almost all the licensing headers will look in the following meaner:
| Info |
|---|
|
/*
* Copyright (c) 2018 AT&T Intellectual Property.
* * Licensed 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.
*/
|
in case you are modifying an existing file you will need to add the flowing to the license header:
| Info |
|---|
| title | Modified license header |
|---|
|
/*
* Copyright (c) 2018 AT&T Intellectual Property.
* Modifications Copyright (c) 2018 <Company copy right> Property. * Licensed 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.
*/
|
Automatic copy right addition:
Eclipse
Intlij
Code guide lines TBD
Role of SDC in ONAP - component use cases
...