Sharing Open Source License and Copyright Data with SPDX

Organizations across the globe are creating and distributing products that include open source software. To ensure compliance with the open source licenses, each company needs to evaluate exactly what open source licenses and copyrights are included - resulting in duplicated effort and redundancy. This talk will provide an overview of a new Software Package Data Exchange (SPDX) specification. This specification will provide a common format to share information about the open source licenses and copyrights that are included in any software package, with the goal of saving time and improving data accuracy. This talk will review the progress of the initiative; discuss the benefits to organizations using open source and share information on how you can contribute.

FOSS License Selection and Code Management

With nearly 2,000 free and open source software (FLOSS) licenses, software license proliferation¿ can be a major headache for software development organizations trying to speed development through software component reuse, as well as companies redistributing software packages as components of their products. Scope is one problem: from the Free Beer license to the GPL family of licenses to platform-specific licenses such as Apache and Eclipse, the number and variety of licenses make it difficult for companies to ¿do the right thing¿ with respect to the software components in their products and applications. In addition to the sheer number of licenses, each license carries within it the author¿s specific definition of how the software can be used and re-used. Permissive licenses like BSD and MIT make it easy; software can be redistributed and developers can modify code without the requirement of making changes publicly available. Reciprocal licenses, on the other hand, place varying restrictions on re-use and redistribution. Woe to the developer who snags a bit of code after a simple web search without understanding the ramifications of license restrictions.

Update on FOSS before the courts

The presentation reflects on French and Italian case law that, in recent years, has dealt with free software from two different angles: public procurement and consumer protection against joint sales of hardware and software.

F/OSS to promote vendor independence/avoid lock-in in the enterprise

This paper focuses on the use of FLOSS to promote vendor independence/avoid lock-in in the enterprise. It looks at how FLOSS projects follow open standards, how forking prevents lock-in if a project threatens to migrate to a closed-source strategy and how FLOSS lowers the barrier to entry for SMEs wishing to implement and support software. However it also looks at how the adoption of policies mandating open standards instead of FLOSS and how the success of cloud computing threatens to erode those benefits. It discusses ways in which cloud computing can be adopted in the enterprise without forfeiting those advantages and urge corporate and government policy makers to mandate FLOSS rather than be satisfied with open standards.

Legal issues in promoting FOSS in R+D projects - Policy, Organisation and Management

Creating and using FLOSS in R+D projects raises several legal issues, which need to be managed as soon as possible - preferably during the project planning stage. Challenges in the areas of project structure and policy, licenses and licensing, exploitation strategies, community management, and FLOSS-friendliness in general all have their legal aspects, which are commented here. Some recommendations are made for assisting in the use of FLOSS in R+D projects, especially in multiple party consortiums.

Licensing Review in R+D Projects

FOSS packages are becoming ever more present in R&D projects carried out a variety of entities, including large corporations. I will focus on how legal risks associated with the use of FOSS licenses can be assessed and discuss measures directed to risk mitigation.

Warranties used as a mean to promote commercial FOSS

From a business standpoint, this paper describes the point of view on the question of warranties of a FOSS editor doing business in a risk-averse market segment. It is based on 15-years experience of AdaCore in the safety-critical embedded industry. However, it is not only the point of view of a provider, as it also aims at demonstrating that the interests of providers and users are aligned in this area. From a legal point of view, the enforceability of these warranties will be partly covered, as well as the articulation between the license and the warranties on one hand, and the articulation between the license and the other contracts that can be created in a business relationship on the other hand.

GPL license compliance

The enormous success of Linux in the consumer electronics industry has unfortunately led to a dramatic increase in license violations in devices. In this talk we will shortly look at the backgrounds of these violations, tooling to help uncover violations and what is needed to prevent future violations from happening.

Installation Information requirements in the GPLv3 and LGPLv3

One of the major changes introduced in the GPLv3 and LGPLv3 is the clause preventing "tivoisation". Richard Stallman defines Tivoisation as "the practice of designing hardware so that a modified version cannot function properly". In this presentation we will go through the reasons of why the information installation requirement was introduced, how you can comply with this requirement and why you may want to think about it now rather than later.

Managing FOSS during development: preventive and curative approaches

Today, most software development teams use free and open source software (FOSS) components, because it increases the speed and the quality of the development. Many open source components are the de facto standard of their category. However, FOSS has licensing restrictions, and corporate organizations usually maintain a list of allowed and forbidden licenses. But how do you enforce this policy? How can you make sure that ALL files in your source depot, either belong to you, or fit your licensing policy? A first, preventive approach is to train and increase the awareness of the development team to these licensing issues. Depending on the size of the team, it may be costly but necessary. However, this does not ensure that a single individual will not commit a forbidden icon or library, and jeopardize the legal status of the whole release... if not the company, since software is becoming more and more a critical asset. Another approach is to verify what is included in the source repository, and check whether it belongs to the open-source world. This can be done on-the-fly, whenever a new file is added into the source depot. It can also be part of the release process, as a verification step before publishing the release. In both cases, there are some tools and databases to automate the detection process. We will present the various options regarding FOSS detection, how this process can be integrated in the "software factory", and how the results can be displayed in a usable and efficient way.

Sistema de detecció de moviments sísmics per a dispositius mòbils

Sistema per a la detecció de moviments sísmics mitjançant dispositius mòbils amb capacitat de transferència de les deteccions a un servidor.

La ciudad en el contexto de la Internet de las cosas

Obtención y publicación web de magnitudes físicas procedentes de todo tipo de dispositivos, como teléfonos móviles, para mejorar la gestión y desarrollo de las ciudades desde una perspectiva sostenible.

Implementació de millores per a un sistema de control d'assistència a Moodle

Projecte que presenta una proposta de solució global al problema del control d'assistència, aprofitant l'arquitectura de l'entorn virtual d'aprenentatge Moodle, augmentant la capacitat d'interconnexió i millorant les interfícies existents.