2. Presentation plan
Alcatel-Lucent background
FOSS Strategy
Open Source Initiative & FSF
FOSS use in Alcatel-Lucent
Contribution
FOSS Obligations
Legal aspects
FOSS assessment process
FOSS usage in Product Life Cycle
New Challenges
2 Alcatel-Lucent
3. ALCATEL-LUCENT
BACKGROUND
% revenues
N. America: ~36% Europe: ~32% Asia Pacific: ~18% Rest of world: ~14%
•
Sells anything in the network •
79 000+ employees
for communication •
27 900 active patents
Russia
Network access
Romania
Ireland •
Present in more than
Poland
Core network UK Slovakia
Canada Belgium 130 countries
Transmission technologies France
Applications
Germany •
600+ new development Korea
Turkey South
USA Netherlands
Professional services
Italy projects per year China
Israel
Spain •
NumerousIndia suppliers and
Taiwan
•
Customers outsourced developments
Network operators Singapore
•
Several acquisitions of
(around 1500 in the world)
companies per year
Strategic industries Brazil
•
Product life can be from Australia
Enterprises
Executive Business Centers to 20 years
1
Indirectly: end users Research Centers
Product & Solution
Development Centers
6. Free and Open Source Software (FOSS)
FSF => Free Software Foundation OSI => Open Source Initiative
GPL (GNU Public license):
The freedom to run the program, for Cover all major licenses
any purpose (freedom 0). No discrimination against person/groups
The freedom to study how the program No discrimination against field of
works, and adapt it to your needs endeavor
(freedom 1). Access to the source code
License must not be specific to a product
is a precondition for this.
License must not restrict other software
The freedom to redistribute copies so
you can help your neighbor (freedom 2). License must be technology neutral...
The freedom to improve the program,
and release your improvements to the
public, so that the whole community
benefits (freedom 3). Access to the
source code is a precondition for this.
6 Alcatel-Lucent
9. Ensure FOSS Obligations are Met!
When packaging an Alcatel-Lucent product & documentation all FOSS licenses
obligations must be respected
Source code of FOSS software that has to be made available MUST be made
available.
Necessary acknowledgement must be done according to the license: in the
distribution or in the documentation or at run time
Licenses must be propagated with the distribution
Disclaimer must be propagated if need be
…
9 Alcatel-Lucent
10. Alcatel-Lucent FOSS policy
Alcatel-Lucent policy is to strictly
respect FOSS license philosophies
If you cannot respect them, do not
use them
10 Alcatel-Lucent
12. License Agreement
License
It is an agreement: created when an
Downloading FOSS
offer is accepted
When downloading/using a FOSS the
downloader generally implicitly signs
It defines the rights and obligations for the contract represented by the
using, copying, modifying, re- license.
distributing, sub-licensing the software
Not respecting a license is like a
breach of contract
The offer containing the license terms
is made by the copyright holder: if you
accept it, a legally valid contract is
created
12 Alcatel-Lucent
13. Breach of Contract Risks
Breach of a license contract means you are not licensed - copyright holder can
pursue you as infringer.
Money damages
Pay a fee to copyright holder
Injunctive relief
Stop selling a product
Criminal fine for the company
Management can be criminally liable under the copyright law
Other potential consequences
Bad image
No right to use anymore some open source
If your customer is sued by copyright holder because the product you delivered
is infringing, you may have to cover his costs and what he has to pay in
damages
13 Alcatel-Lucent
16. Alcatel-Lucent FOSS Review Procedure
FOSS Evaluators
Initiator, e.g. Product
Management or advanced
procurement Can you
confirm that B is a
Check A, B, C library ?
Core team
Support for
Evaluators
Add B Set B
risks difficult
FOSS Expert evaluations
Evaluate B
A is OK, C is Lawyers
forbidden, B is
not described in
the DB
FOSS
Purchasing
Database
FOSS Executive
Committee
16 Alcatel-Lucent
20. Alcatel-Lucent FOSS Process in PLC
Before DR1, all FOSS At DR1, A FOSS expert
planned to be used in an must check that for
Alcatel-Lucent product each FOSS planned to be
must be identified. used, conform to what is
authorized in the FOSS
A new entry request must DB.
be issued (preferably) by
the FOSS expert if the FOSS At DR4, a check must
is not registered in the When packaging the
be performed to ensure
database. Alcatel-Lucent product, all all FOSS license
FOSS license obligations obligations are met.
must be respected.
DR0 DR1 DR2 DR4 DR5 DR6
Execution
Volume End of
Planning Design and Limited
Implementatio Validation Deployment Deployment Life
Opportunity n DR3
Definition FOSS request: if a FOSS is not in the database or if
the FOSS version is not covered by the Database
Sales & Marketing
Preparation Fill a form for the FOSS and all dependencies
(all included FOSS)
Between D1 and DR4
check ALU code with Explain the nature of the software (with
FOSS detector respect to GPL obligations) and the way of use
20 Alcatel-Lucent
21. Packaging an ALU product
Make the list of all FOSS with their license
Create a directory “License” in the binary distribution
Copy all Licenses in this directory.
If there are some licenses that require source code availability upon
distribution burn a CD with source code of ALL FOSS and put it in ALU
catalogue of orderable items
Write in the documentation of the ALU product that source code of FOSS is
available in the ALU catalog.
21 Alcatel-Lucent
22. FOSS detector
Black Duck’s Protex is a software tool for FOSSology.
checking FOSS presence in target software Tool to detect copyright and licensing
It compares target code to a database information in source code
of hundreds of thousands of FOSS
packages Complementary with Black Duck
generates a bill of material of FOSS Allow to detect potential dependencies
with a list of FOSS obligations inside an Open source
Installed on server Available on a server
BD representatives trained for its use
Evaluate other competitor tools (e.g.
from Palamida)
22 Alcatel-Lucent