Japan MB's Reportossforum.jp/jossfiles/WG3-report.pdf · 11/20/2014 · Status Report WG3:...

Status ReportWG3: Study on Standardization & Certification

2014-11-20

NEA OSS Promotion Forum

Table of Contents

Copyright (C) NEA OSS Promotion Forum WG3

1.RepOSS2.Open Source Software Governance Framework3.Future Work: Software Package Data Exchange

(SPDX)

1.RepOSS

The RepOSS’s history

FY2010

FY2011

FY2012

FY2013

- Study on some assessment methodologies.-- like the Qualipso, QSOS, OpenBRR, and more.

- Classification of Open Source Software projects.-- Categorized about 300 Open Source Software.

- Attributes for evaluation of Open Source Software.-- Assessment 55 Items.

-- Case study and trial about 120 software.

- Public presentation of our result as .

- Attributes for evaluation is further strengthened. -- Assessment 89 items.

-- Case study and trial about 340 software.

- Assessment Methodologies mapping onto RepOSS.-- QSOS and OpenBRR

- Registered its trademark in all member nations.

- Improvement of the system by a user's feedback.

- Evaluation of 23 open source software.-- which had been strongly leading “Cloud”, “Big Data”, “Mobile” markets.

-- Proposal of new assessment items like Google Trends.

The problem of RepOSS

• The newest software is insufficient.

– New open source software appears one after another, especially in

“Cloud”, “Big Data”, “Mobile”, and “Social” markets.

– We need to correspond to the changes of open source software.

• Assessment items are insufficient.

– The development style of open source software is also changing.

– In some communities, Twitter and Facebook are actively used rather

than e-mail.

This year’s activities

• Study on the method of automatic collection.

Services & Software & Distributions

Repository

Collector

The RepOSS Collector collects the newest information automatically.

The image of RepOSS Collector

CollectorConfiguration

(YAML)

Output

Repository

Collection

Package Information

Analyze

1-1. Localization (China)

RepOSS in China

• Current lifecycle phase project is in:

Deployment phase

Integration Deployment LocalizationTest

MaintenancePromotion

1-2. Localization (Korea)

System Architecture of Korea RepOSS

Web Sever(Apache)

VM(KVM)

CMS(Wordpress)

PHP, HTML, CSS, Java Script, JQuery

RepOSS(Web APP)

DBMS(MySQL)

OS(Linux)

Analytics(Infobright)

Roadmap (3 years)

• Deploy & Develop Korea Style RepOSS System• Apply Static Contents & UX• Develop User Mgmt System• Apply OSMAAM

2014• Enhance UX & Update contents• Apply FOSS Governance • Apply Statistics(Access, Usage, Region …)

• Develop User Centered OSMAAM System - TBD• Develop Automatic Contents Mgmt System• Analytics : infobright …• Apply SPDX

• Activities delay issues

– Internal : Downsize the workforce due to budget

– External : The government scale down support(inc. budget)

• Adjust development scope & schedule

– Developing User Centered OSMAAM System

• Will be starting after 2015

• Progress

– Contents update -> Promotion -> Statistics

• Objectives & Scope 2014

– Update contents & enhance UX

– Applying FOSS Governance Framework

– Applying website statistics – Web analytics & Reporting

Objectives & Scope - 2014

• Requirements Analysis

– UX

• Enhance Site layout & design

• Apply preference survey

• Goto top

– Develop user communication channel

• Blog, forum, BBS …

– Consider developing a Korean or an English website

– Update the contents - OSS Project List

• Update periodically: old data

• Discuss update automation

• Discuss RepOSS Process : Need CJK WG3 discussion

– Applying FOSS Governance Framework

– Statistical Analysis(if possible using plugin)

• Access

• Search

– Marketing

• Using major portal site

• E-mail marketing

: National IT Industry Promotion Agency

• Cooperation of the agencies concerned

2. Open Source Software

Governance Framework

About TTA

• The purpose of TTA is to contribute to the advancement of

technology and the promotion of information and

telecommunications services and industry as well as the

development of national economy, by effectively establishing and

providing technical standards that reflect the latest domestic and

international technological advances, needed for the planning,

design and operation of global end-to-end telecommunications and

related information services, in close collaboration with companies,

organizations and groups concerned with information and

telecommunications such as network operators, service providers,

equipment manufacturers, academia, R&D institutes, etc.

DEC 1988 TTA(Telecommunications Technology Association) Established by Civil Law

Purpose of Standard

• The purpose of this standard is to provide OSS users with a

standard framework of OSS governance which contributes to

minimizing compliance risks and maximizing usage benefits.

Summary of Contents

• The OSS governance framework is categorized into three phases

according to the flow of OSS in the echo system. The first phase is for

internal usage in which OSS is used in an organization. The second

phase is for distribution where OSS is sent outside of an

organization. The last phase is for external service where an

organization provides OSS customers with technical support services.

Action items and check lists are defined as standard elements for

OSS governance with respect to the characteristics of each phase.

OSS Governance Framework

Open Source Community

Internal

External

Service

Distribut

Using OSS only

within

organization.

Using OSS on

product or

solution for sale

or delivery to

customers and

users.

Using OSS for

network service

to customers

and users(Cloud,

portal, banking

service and etc)

Consulting

Policy Establishment

Composition of Organization

Requirements Analysis

Research

Analysis

Contract

Design

Development

Installation

Operation

Maintenance

Technical Support

Community

Packaging

Testing

Distribution

Assesment

Life Cycle using OSS

OSS Governance Activity Elements

Policy Acquisition DeploymentOperation & Maintenance

Training MonitoringCompliance

Management and Improvement

Standard Activity Elements of OSS

Activity Elements Features Description

1. Research

Sequential

Find a new or suitable OSS for the particular fields.

2. Analysis Identify properties and analyze status or level of OSS.

3. AssessmentGrading each attribute by grant a weighted value and apply an assessment model.

4. RequirementAnalysis

Analysis worries and requirements of customer or user.

5. DesignDesigning the functions and configurations regarding the needs analysis result in advance.

6. DevelopmentModifying the OSS program.

7. TestTest the quality and performance whether meets the required level or not.

8. PackagingPackage into a single program for easy installation of OSS.

9. Contract

Sequential

Make a contract about providing service with deploy of OSS.

10. Distribution Deliver the OSS via storage, website, equipment etc.

11. Installation Porting to the OSS capable equipment.

12. OperationExecuting OSS and run consistently as normal state.

13. MaintenanceCarrying out prerequisite works for maintain the best operating conditions.

14. Technical Support

Service an OSS technology such as reflect additional requirements or solve disability.

15. MonitoringUnderstand the situation after applying of the OSS and receive feedback.

16. Organization

Non-Sequential

/ Occasional

Presenting the operational plan in accordance with the roles, responsibilities and staffing efficiently.

17. TrainingProviding knowledge to enhance understanding and improve technology.

18. ConsultingProviding advisory services for strategic planning and OSS.

19. PolicyEstablish rules and guidelines that must be followed in accordance with the objectives and strategies.

20. CommunitySuggest source code contribution, financial support, activity exchanges, participation methods.

21. ComplianceResolving legal issues and license compliance obligations.

3. Future Work

Software Package Data Exchange (SPDX)

SPDX® Group

• A working group of Linux Foundation and a key pillar in Linux

Foundation’s

• Goal

– Create a defined format for a file of license fact information describing a

software package

• History

– A grass roots effort started by corporate counsels, business leads, and

release managers responsible for ensuring release compliance with

applicable licenses of FOSS included in the release

• Operation

– Open participation through www.spdx.org

– Very inclusive process

A range of organizations and roles

Systems

OS Distributions

Applications

Integration & Services

Device OEMs

End-Users

Semiconductor Vendors

Open Source Organizations

…and others

Status

• Version 1.0 – Released August 2011

• Version 1.1– Q2 2012

• Version 2.0– Targeted for end of 2012

http://www.spdx.org

What SPDX® Means for You

Embedded & SW

Supply Chains

Save Time/Money

Better Compliance

Open Source

Developers

Help Users Comply

With Your Licenses

Consumers of

SW & OSS

Understand Licensing

of the Code You Use

The SPDX® License List

SPDX® license repo• List of most common

licenses (150+)

• Standardized license

• Exact text of licenses

• Guidelines for matching

• Available on SPDX®

website – URLs won’t

change

• Short names adopted

by OSI

The SPDX® File

Package identification, copyright and

licensing

Text of licenses that are not in

SPDX™ license list

SPDX version and SPDX data license

How, when, who

Log of 3rd party reviews

File is in RDF/XML or tag value form; can be

converted to/from spreadsheets.

Per-file identification, copyright and

licensing

Package Info

Licensing Info

File Info

Review

Document & Creation Info

Tools for SPDX®

• Open Source Tools (git.spdx.org)

– Viewer (reads RDF/XML format)

– Translate from

• RDF to Spreadsheet

• Tag/Value to Spreadsheet

• Spreadsheet to RDF or Tag/Value

– SPDX spreadsheet template

• Commercial Tools

– Scanning tools to provide SPDX™ support

Thank You !

Japan MB's Reportossforum.jp/jossfiles/WG3-report.pdf · 11/20/2014 · Status Report WG3:...

Documents

WG3 – General information on work progress

WG3 Quin CERES CALIPSO dust cloud

Done VIP Summary Ar4 Wg3 Ts

Napoli October 2007 WG3 - Pierre Edelbruck FAZIA WG3 – Front End Electronics

Reporte WG3 PM2.5 Monterrey

Outline WG2 (bank of pure isotopes) WG3 (theory) WG3 (Neodimium project - preliminary tests on Nd crystals) WG4 (cosmogenics - code survey - exposure

BETTY WG3-Languages State of the Art Reportyoshida/WG3/BETTY_WG3_state_of_art.pdf · BETTY WG3 - Languages State of the Art Report Giuseppe Castagna Luca Padovani Nobuko Yoshida (editors)

ATNP/WG 3 WG3/17-DP1 AERONAUTICAL … Meeting... · Of 17th Meeting, Gran Canaria ATNP/WG 3 WG3/17-DP1 AERONAUTICAL TELECOMMUNICATIONS NETWORK (ATN) WG3 - (ATN Applications and Upper

Ipcc wg3 ar5_final-draft_postplenary_chapter16

ISO/IEC SC25 WG3 - IEEEgrouper.ieee.org/groups/802/3/cg/public/Jan2017/iec sc25 wg3 overv… · ISO/IEC SC25 WG3 Recent Deliverables Reference Title Approved ISO/IEC TR 24750 Supporting

HERA-LHC Workshop, DESY, 21-24.03.2005 WG3 - Heavy Quarks 1 HERA and the LHC Workshop WG3 – Heavy Quarks Summary WG3 Conveners: M.Cacciari, M.Corradi,

WG3 Flexible Generation - ETIP SNET

WG3 Summary

HTML5 Security API’s Proposal WG3 Report Section IV.A 1 DSTAC WG3 Report HTML5 Security API’s Proposal

MDWG-ASBU WG3 Report (final) - 14Jan15 - ICAO

AIOTI WG3 IoT Standardisationiot-week.eu/wp-content/uploads/2015/06/11-AIOTI-WG3-introductionv2.… · AIOTI WG3 IoT Standardisation ... Huawei, IBM, Ifinity, IKEA, ... mapping of

WG3 release Giovanna Valverde 16 apr 2014

WG3 - Folder

WG3 Session#1 Monday PM :

IEC TC82 WG3 WG6 동향보고서 - koreascience.or.kr