1. Technology Partnering and Software Licensing: The practical TT channels of CERN's IT Department François Fluckiger

2. 2 François Fluckiger CERN IT event 27th May 2004 Information Technology Department n Mission n Physics Computing n General Purpose and Administrative Computing n Projects n With Physics community (LCG) n With Industry (openlab) n EU-funded (EGEE) More?http://cern.ch/it-dep/what-we-do

3. 3 François Fluckiger CERN IT event 27th May 2004 Areas of ICT Expertise n High-performance computing n Mix of cutting-edge / commodity technologies n Large-scale integration n Operation n Large-scale, round the clock n Innovative administrative computing solutions n Work-flows, HR management, … n Innovative general-purpose computing solutions n Web, email, desktop services, … n Software n Large-scale development, distributed SW engineering

4. 4 François Fluckiger CERN IT event 27th May 2004 The Scope of Technology Transfer n TT Objective "To make known and available to third parties under agreed conditions, technical developments achieved in fulfilling the laboratory's mission in fundamental research" n Transfer of expertise, know-how to n industry n academia n public institutions n the society at large More?http://cern.ch/it-tt

5. 5 François Fluckiger CERN IT event 27th May 2004 The Need for Collaboration n IT Department activities n focus on fast changing technologies n often require that developments are conducted in collaboration with external partners n As a result, the main channels for TT in the Department are collaboration and partnering with external organizations

6. 6 François Fluckiger CERN IT event 27th May 2004 Collaborations via Projects Collaborations With Industry With Physics Community Projects Via EU Projects openlabLCGEGEE

7. 7 François Fluckiger CERN IT event 27th May 2004 What is the openlab? n A framework for “R&D” in collaboration with Industry n Partner commitments n 3 years n Contributions may be a mix of n In kind (HW, SW, services, …) n In cash (in general for fellows) openlab framework n Contributor commitments n 1 year n Lower level

8. 8 François Fluckiger CERN IT event 27th May 2004 What are we doing in the openlab? n Evaluate and Integrate cutting edge solutions n Current project: opencluster n IA-64 Compute farm (Intel + HP) n 10 Gb Ethernet (Enterasys + Intel) n Storage (IBM) n 10g servers (Oracle) n Infiniband (Voltaire, contributor) openlab framework opencluster project

9. 9 François Fluckiger CERN IT event 27th May 2004 What is new with the openlab? n Is it really different from conventional n joint projects with industry? n field tests? n openlab is not a collection of disjoint bi-lateral evaluations n It implies n A common "agreement" framework n A common technical objective n An active collaboration between all parties

10. 10 François Fluckiger CERN IT event 27th May 2004 Collaborations on Software Collaboration With Industry With Physics Community Projects Via EU Projects openlabLCGEGEESoftwareBilateral Collab. Agreements Open- source Licensing "Nice""EDG""CASTOR"

11. 11 François Fluckiger CERN IT event 27th May 2004 Making SW available to the outside Binary only Source Publicly available Downloadable External SW Bilateral Collaboration Agreements Publicly available Open Source

12. 12 François Fluckiger CERN IT event 27th May 2004 Bilateral vs. "Open Source" Features Bilateral Agreements Publicly Available Development style Developed within CERN Developed with external partners Motivations for external release Improvements available to CERN Improvements available to partners Scaling Does not scale Scales well Source Publicly available "Open source" Bilateral Agreements

13. 13 François Fluckiger CERN IT event 27th May 2004 Making SW publicly available "Open Source" (Free Software) does not mean Public Domain

14. 14 François Fluckiger CERN IT event 27th May 2004 Publicly Available vs. Public Domain Binary only Source Publicly available Downloadable Open source "External" Public Domain Retain IPR Relinquish IPR

15. 15 François Fluckiger CERN IT event 27th May 2004 Open Source principles n Author keeps copyright n to prevent third parties to turn free software into proprietary software, and deny users the rights to freely use the material n Author gives a free of charge, perpetual license to anyone run, copy, modify, … the software n Licensees may only publish (modified) versions under same open source conditions

16. 16 François Fluckiger CERN IT event 27th May 2004 Distribution of CERN WWW software Francois Fluckiger (fluckiger@vscrna.cern.ch) Tue, 15 Nov 1994 23:05:59 +0100fluckiger@vscrna.cern.ch  Messages sorted by: [ date ][ thread ][ subject ][ author ][ date ][ thread ][ subject ][ author ]  Next message: David Koblas: "How about an "IF" markup construct..."David Koblas: "How about an "IF" markup construct..."  Previous message: dolesa@smtp-gw.spawar.navy.mil: "Windows Help to HTML conversion"dolesa@smtp-gw.spawar.navy.mil: "Windows Help to HTML conversion" Dear Colleagues, Some of you asked about the conditions for the distribution of new versions of the CERN WWW Library of Common Code (libwww), the CERN Line Mode Browser (www) and the WWW HTTP Daemon (httpd). The new versions will remain freely available, for general use, and at no cost. The only change is that the material distributed will remain copyrighted by CERN. As a consequence, a copyright notice will have to appear in copies, but also, the rights of the users will be protected, in particular by preventing third parties to turn free software into proprietary software, and deny the users the rights to freely use the material. These principles are those used by most distributors of free software, including the X consortium. The proper copyright notice is being ratified and will be available in a few days. We hope all those who have trusted CERN WWW software will continue to do so, and will appreciate that these conditions not only maintain the free distribution but better protect it. Francois Fluckiger Leader, WWW development, CERN  Next message: David Koblas: "How about an "IF" markup construct..."David Koblas: "How about an "IF" markup construct..." Previous message: dolesa@smtp-gw.spawar.navy.mil: "Windows Help to HTML conversion"dolesa@smtp-gw.spawar.navy.mil: "Windows Help to HTML conversion" A (small) piece of history

17. 17 François Fluckiger CERN IT event 27th May 2004 Copyright Statement Open-Source Distribution Conditions Distribution Conditions Disclaimer n Part of open-source license n Establish rights and duties of the licensee n Rights to n run, copy, change, improve, correct, incorporate into other programs, publish, distribute, charge, sell verbatim, sell modified, sell services, … n Duties to n perpetuate copyright, publish modifications, publish derivative work, document changes, … License

18. 18 François Fluckiger CERN IT event 27th May 2004 Licenses for "Open Source" at CERN n Either a CERN specific licence n e.g. EDG license n Or a Public License n e.g. GPL, LGPL BinarySource Publicly available Downloa dable Publicly available "Open source" Bilateral Collaboration agreements "External"

19. 19 François Fluckiger CERN IT event 27th May 2004 Conventional SW Licensing to Industry Collaboration With Industry With Physics Community Projects Software Via EU Projects Bilateral Collab. Agreements Open- source Licensing openlabLCGEGEE"Nice""EDG""CASTOR" Licensing to Industry

20. 20 François Fluckiger CERN IT event 27th May 2004 Conventional SW Licensing to Industry n Though less frequent, conventional licensing / IPR transfer to industry is in no way ruled out n Several examples in particular in Administrative Computing n Note: Open Source licensing does not preclude licensing to industry for commercial exploitation n A given SW module may be open-source licensed as well as licensed bilaterally to a partner, allowing the distribution of modified versions under proprietary license

21. 21 François Fluckiger CERN IT event 27th May 2004Conclusion Transfer is by doing things together The major - though non exclusive - IT channels for Technology Transfer are based on collaborations with external partners