Skip to main content
Category

News

OpenChain OSPO Subgroup Meeting / TODO Local Meetup 2023-02-10 – Minutes

By News

Original document here:

Want to be part of the next meeting? Join the mailing list:

participant:

  • Real: Owada, Shima, Kato, Koizumi, Handa, Fukuchi, Motai, Suzuki, Kuwata
  • Online: Hayashi, Iwami, Yoshida, Yamazaki, Watanabe, Daikoku, Ohyagi, Sado, Ninjouji

Date and time:

  • Friday, February 10, 2023 15:00-16:00

place:

  • Real: Socionext Shin-Yokohama Office

Contents:

■ Mapping issues to OSPO maturity stages

  • Not good mindset/attitude like:
  • ◇1. use
    • It’s okay if you can use it without permission
    • There was a time like this in the past, but it seems to have passed
  • ◇2. Compliance
    • It seems that they worked hard on the site, it is not an issue for the entire company
    • see it as a legal issue
  • ◇3. Participation
    • Misunderstandings that rely on others
    • Maintained even if left alone
    • No need to keep up with upgrades
  • ◇4. Co-creation (collaboration)
    • Contribute only when you can afford it
    • No immediate effect
  • ◇5. Strategy
    • we don’t have to do it ourselves

■OSPO GGI Mapping

  • ◇OSS business strategy
    • OSS activities are positioned as part of the business, and targets are set with both the business and the community in mind.
    • OSPO representatives are able to communicate at C-Level regular meetings
    • Some employees do not understand the OSS business model
    • I’m trying to get the conversation across
    • There are contributors, but they are not in a form that leads to business
    • Classified as Strategy goal activities
    • Mapping to maturity level 5 could not be assigned
    • C) I felt that even at the maturity level they were going as far as strategy
      • Isn’t it that there are things that are done and things that are not done?
      • A) Communication at the top is done, but there are some areas such as education that are lacking
  • ◇OSS hosting
    • Develop product A with OSS
      • Became a sponsor of the base OSS PJ and has also contributed
      • It is open on Github, but the problem is that there are few external contributors and users
      • There is no internal system in place to deal with the increase in external
    • Product B Source released, development closed
      • Activities to revitalize the user community have been activated
      • There are also users who customize
      • Categorized as Engagement goal activities
    • Maturity level is weak in Leadership Community Education Engagement
    • C) be able to act as a leader, but not able to engage
  • ◇OSS contribution
    • I want a more influential approach to the community
    • It would be good if we could accumulate know-how on how to do this within the company.
    • We also support private and open source activists
    • I can get information and I can visualize it
    • Some people don’t want to be open as individuals and don’t want support
    • I’m trying to automate and collect contribution logs
    • I want to make use of the experience and know-how of employees who are responsible for board members
    • Classification is Engagement gaol activities maturity level
  • ◇ What we want to do at TODO Group Japan
    • OSS Business strategy area
      • Not enough things that are organized in Japanese
      • Isn’t it easier to talk if you have something to show?
      • Combination of support type and open core type,
      • I think it would be easier to apply OSS to business if there is a place to analyze and discuss such things, such as using paid services as users use OSS.
    • OSS hosting area
      • It’s out there, but it’s revitalizing and gathering people
      • Know-how and best practices should be created
  • C) I would like to work with someone who is interestedI want to be able to bring out the results from Japan to the world.
  • C) Posing a very good challenge
    • there are many people who are interested in
      • Some people may be interested but unable to contribute
    • There was a company analysis at OSSJ, so It might be useful
      • thinking about doing it broadly or deeply.
  • Q) There was talk of researching external community contributions. how it ultimately intends to use the results
    • A) The company is happy to know individual skills
    • You can’t just get results
    • We provide financial support when making presentations at overseas events.
    • We want to create a win-win relationship from both sides
  • C) Motivation seems to increase
    • A) Incorporating skill development leave, we have prepared a system that allows you to go without using your paid leave.
  • Q) Is it better to set up a sub-work or continue here?
    • A) I don’t know the framework yet, but I want to do it

■ Issue mapping by OSPO maturity level and individual ⇔ company/OSPO scope

  • The usage status of Open Source can be grasped at the project level for the purpose of satisfying compliance, but it is not grasped in the necessary form when considering strategic utilization throughout the company.
  • I have mapped to 2 compliance and 3 participation in the OSPO maturity levels, but the objectives are 5 strategies and I feel that the OSPO maturity levels will come and go rather than monotonously climb
    • C) Issues that do not allow you to jump into the community as your own matter and issues such as being recognized by your superiors and improving the personnel system are related
  • Is there a link between individual issues and organizational issues?
  • The timing of individual motivation and organizational motivation is out of sync
  • want to raise my personal motivation, even if it’s just a little
  • If you try to make it fair, you can’t make it
  • Value standards such as the size of the community and the number of committed lines are difficult
  • OSS activities are not recognized by the company
  • are introducing new technology
  • Some people have good networks and some people don’t.
  • Individual study until community feedback is available
  • OSS activities are far away
  • Is the introduction of new technology evaluated?
  • OSS is even more unacceptable if it is not evaluated
  • A place to discuss careers
  • Individuals are not necessarily part of a community associated with the company
  • I want to promote it, but it is difficult to evaluate
  • Difficult in business evaluation
  • Establish other forms of awards or rewards
  • The next time you start working on your company’s business
  • SW human resource development
  • eventually return to business
  • Business is difficult if you don’t understand it
  • After all, SW is a human resource.
  • Scale of support for individuals
  • For example, overseas events are big, or they are paying attention to technology

■ Other

  • ◇ Relationship with legal
    • Q) Are legal people familiar with OSS licenses and able to intervene?
    • C) Isn’t it an area that has been talked about in Open Chain?
    • C) We also aim to cooperate with legal affairs
    • I hold study sessions and get involved
    • No one understands OSS in ordinary company legal affairs
    • C) No legal involvement
    • Since it starts with compliance, it starts with a legal proposal, but the legal department cannot handle it, so the open source team is supposed to take responsibility.
    • C) The parent company is doing well, so we can do commercial distribution from there, but there are cases where we can’t do it ourselves.
  • ◇ SBOM and department in charge, procurement contract text
    • Q) Is the procurement department in charge of SBOM or is the project doing it?
    • A) It is in the form that the place requested from procurement takes responsibility
    • It is supposed to be included in the instructions at the time of procurement, but the requesting department is supposed to include it
    • C) I think that the OSPO functions in the LF organizational form.
    • I think there are various ways to actually do it, but I was wondering if I would intervene or get involved
    • C) There are various aspects, SBOM can not do even if they know the law
    • Tooling is essential, OSPO’s position needs to be promoted when introducing Tooling
    • I can’t understand the contents of the software unless I’m on site,
    • collaboration is needed
    • C) OSPO is being asked to wield the flag, but there are various ways to do it, such as creating a new mechanism
    • C) It doesn’t matter if OSPO is a departmental organization or a company organization
    • Small steps to try to do things right together
    • C) SBOM does not proceed unless C-Level thinks SBOM is necessary
    • There are still not many companies that think that they have to do it desperately while thinking that it is exciting
    • C) There are many parts that move in the security system
    • that one is more motivational
    • C) The word SBOM stands alone, and the image differs from person to person
    • Security is shifting from the purpose of checking what license is included
    • It will also be used to understand the information we are using to make strategic decisions.
    • It will be different depending on what you emphasize, but it will be easier to talk if you use a common language
    • C) Concerning procurement, OSPO also participates in the preparation of the template and incorporates the conditions of OSS.
    • Regarding SBOM, the product security unit has started to move mainly in cooperation with OSPO.
    • With the cooperation of LF, we are planning an in-house lecture by asking the GM of OpenSSF and SPDX.

OpenChain Monthly Meeting 2023-02-21 (North America and Asia) – Recording

By Featured, News

Our latest monthly meeting for North America / Asia continues where we left off on the North America / Europe call earlier this month (see https://www.openchainproject.org/news/2023/02/10/monthly-meeting-2023-02-07-recording). The focus was work around the next generation of the Security Assurance Specification.

Watch Our Meeting

On this call we addressed the following issues with the Security Assurance Specification 2.0 Draft:

  1. We prepared and refined definitions of remediation and mitigation:
    https://github.com/OpenChain-Project/Security-Assurance-Specification/issues/22
  2. We included “remediation” and “mitigation” in Section 3.1.5:
    https://github.com/OpenChain-Project/Security-Assurance-Specification/issues/25
  3. We included “mitigation” in Section 3.3.2:
    https://github.com/OpenChain-Project/Security-Assurance-Specification/issues/26
  4. We clarified the “Get Customer” requirement in Section 3.3.2 to make the logic clearer:
    https://github.com/OpenChain-Project/Security-Assurance-Specification/issues/27

All of the issues appear “done” but naturally you can access, review and reopen on GitHub. We will also be speaking about these topics on the next call for North America / Europe on the 1st Tuesday of March. See our Global Calendar for the precise schedule:
https://www.openchainproject.org/participate

Review Our Slides

OpenChain Education Work Group Meeting 2023-02-09 – Recording

By News

Nathan continues to lead collaboration around the OpenChain education material. We have a lot of reference material, ranging from self-certification to training to policy material, and the community is currently preparing updates to help people get started more quickly. Our goal is not only to make adopting our license compliance and security assurance standards easier, but also to provide great material that can be repurposed for other aspects of open source management.

Yes Security is the latest OpenChain ISO/IEC 5230 Conformant Organization

By Featured, News

Yes Security…

… aims to offer high quality, performance and reliable products, ensuring the protection, security and productivity of its customers. The provision of personalized services, in an agile and assertive way is one of our main focuses, acting in the identification and resolution of problems, guiding the IT professional on the functionalities of the tools, ensuring the full use of the resources offered by it. With a close relationship with manufacturers and distributors it is possible to offer affordable projects that suit the needs of each company.

Learn More

OpenChain Korea Work Group Meeting #17 – First Physical Meeting Since COVID! – 2023-03-28

By Featured, News

The OpenChain Korea Work Group is holding its 17th meeting between 14:00 and 16:00 on the 28th of March 2023. This will be the first physical meeting of the work group since COVID hit in 2020. Learn more at the event link:
https://openchain-project.github.io/OpenChain-KWG/meeting/17th/

안녕하세요, OpenChain KWG 멤버 여러분! 장학성입니다.
새로운 한해를 뜻깊게 시작하고 계신가요?

2023년 1분기 모임을 코로나 이후 처음으로 다시 오프라인으로 모입니다. 두근두근!:
https://openchain-project.github.io/OpenChain-KWG/meeting/17th/

  • 일시 : 2023년 3월 28일 (화), 오후 2시~4시
  • 장소 : 라인플러스 (분당구 서현동)
    세부 장소는 추후 공지 드리겠습니다. (장소를 제공해주신 라인플러스 이서연님 감사합니다! ^^)

Webinar: GPLv2 Licensing History

By community, Featured, legal, licensing, News, Webinar

This OpenChain Webinar features an overview of GPLv2 licensing fragmentation based on research initiated by Philippe Ombredanne of NexB and continued by Armijn Hemel of Tjaldur Software Governance Solutions. The key takeaway is that a significant number of variations exist (40 “vanilla” copies from the FSF or GNU website, 12 with the Linux kernel linking exception in the Linux kernel), but the impact of these variations is nuanced. The requirements do not change but the variability may throw errors for automation and review. Process awareness is required.

Check Out All Our Past Webinars Here:

Check Out The Rest Of Our Webinars

This is OpenChain Webinar #48, released on 2023-02-15.

Panx Project is the latest OpenChain ISO/IEC 5230 Conformant Organization

By Featured, News

Panx Project is:

A digital consultancy and community solutions organization. Each year we launch projects aimed to address a social, technological, or economical issue. Working with and training job seekers, startups, NGOs and enterprises on developing their own framework to leverage the latest industry standards and cutting-edge technology. Some of these clients include: Mumm, Zoho and Monginis.

Learn More

OpenChain Monthly Meeting North America – Europe – 2023-02-07 – Recording

By Featured, News

We had a fantastic meeting focused on editing previously submitted scope suggestions from ISO/IEC WG/SC 27 (Information Technology Security). This time we went over issues submitted by reviewer CERT. In addition to this, we closed an open issue syncing the definition of Open Source between the licensing (ISO 5230) and security specifications.

Co-chairs Helio and Chris lead the discussion, and we had some great contributions from the audience. It is clear that there is significant interest in reviewing the draft 3rd generation licensing standard and 2nd generation security standard. You are reminded that everyone is invited to participate on the monthly calls and via our main or specification mailing lists.

Specifically..

We closed this open source definition issue:
https://github.com/OpenChain-Project/Security-Assurance-Specification/issues/20

We set this action item based on a suggestion by CERT:
https://github.com/OpenChain-Project/Security-Assurance-Specification/issues/22

We decided not to pursue this suggestion by CERT:
https://github.com/OpenChain-Project/Security-Assurance-Specification/issues/23

We decided not to pursue this suggestion by CERT:
https://github.com/OpenChain-Project/Security-Assurance-Specification/issues/24

Watch The Recording

Check Out Our Meeting Slides

Join Our Specification Mailing List

See When Our Next Monthly Calls Take Place

OpenChain Japan Work Group Meeting #26 (Hybrid #1) – 2023-02-09 15:00-17:00 JST

By Featured, News

The first face-to-face OpenChain Japan Work Group meeting in three years is being hosted by Hitachi Solutions and will feature our usual exceptional schedule of case studies and discussion. Big thank you to Ayumi and team for providing a great place to bring the community together. Virtual attendees are also being supported via Zoom.

OpenChain Japan Work Group【第26回全体会合】【第1回ハイブリッド会合】
 ★2023年2月9日(木)15:00-17:00 JST
 ★ハイブリッド形式(リアル会場+オンライン参加)
 ★リアル会場:日立大森ビル
 ★オンライン会場:
   https://zoom.us/j/4377592799
 ★東芝さんの事例紹介2件と日立ソリューションズさんのOSSツール紹介1件を企画しています。
アジェンダ:
15:00 – 15:01  Opening
15:01 – 15:10  Keynote by Shane Coughlan
15:10 – 15:20  OpenChain Japan WGについて
15:20 – 15:30  日立ソリューションズのOSSへの取り組み 渡邊 
15:30 – 15:45  OSS紹介:「SPDX用拡張機能 on VSCode」明石(日立ソリューションズ)
15:45 – 15:55  休憩
15:55 – 16:25  事例紹介:「オープンソースコンプライアンスのためのプロセスマネジメント標準ISO/IEC 5230の適合に向けて」忍頂寺、樽家(東芝)
16:25 – 16:55  事例紹介:「OSSライセンスコンプライアンスを遵守するためのOSS教育の整備と全社展開」小山(東芝)
16:55 Closing

TIMETOACT GROUP Offers Open Source Certification Based On ISO/IEC 5230

By Featured, News

IT company deepens partnership with OpenChain Project and expands open source software offering.

TIMETOACT GROUP is now an official third-party certifier for the ISO/IEC 5230 standard managed by OpenChain, enabling it to offer official certifications in addition to consulting services on open source license compliance. With the deepening of the partnership between OpenChain and TIMETOACT, customers have even more choice around services available for open source software.

The use of open source software – just like proprietary software – is based on various license terms. It is important to maintain these requirements in order to ensure smooth business operations and avoid conflicts with third parties. The OpenChain ISO/IEC 5230 international standard aims to identify the key requirements for a high-quality open source license compliance program. It enables companies to reduce their risk potential by adapting the standard through self-certification, independent assessment or third-party certification such as TIMETOACT GROUP. Within TIMETOACT GROUP, ARS software engineering specialists provide the certifications.

“We are happy to join OpenChain’s certifier network, thus providing companies of all sizes and industries with the critical components for successful open source compliance programs. This partnership grants our customers added value through the opportunity to obtain the OpenChain ISO/IEC 5230 certification seal,“ says Simon Pletschacher, Manager IT Performance Strategy at TIMETOACT GROUP.

“We are delighted to welcome TIMETOACT GROUP to our comprehensive network of certifiers, allowing us to provide companies of all sizes and industries with easy access to the essential components of superior open source compliance programs,“ says Shane Coughlan, General Manager OpenChain.

About TIMETOACT GROUP

TIMETOACT GROUP modernizes and integrates IT applications for upper mid-sized companies and corporations in order to increase their agility, efficiency and transparency. For innovative customers, TIMETOACT GROUP also develops and implements digital business models and opens up new market opportunities.

Services include: Consulting, Cloud Transformation, Data, Software and Systems Engineering in the area of Employee Experience, Business Applications and Customer Experience.

For more information see www.timetoact-group.com/en or www.timetoact-group.com/en/details/open-source-license-management 

About OpenChain

The OpenChain Project has an extensive global community that involves thousands of companies collaborating to make the supply chain quicker, more effective and more efficient. We do this by maintaining ISO/IEC 5230:2020, the International Standard for open source license compliance, and our Security Assurance Reference Specification. We also have a large global community where knowledge is shared to reduce friction and increase efficiency across all aspects of open source process management.

About The Linux Foundation

The Linux Foundation is the organization of choice for the world’s top developers and companies to build ecosystems that accelerate open technology development and industry adoption. Together with the worldwide open source community, it is solving the hardest technology problems by creating the largest shared technology investment in history. Founded in 2000, The Linux Foundation today provides tools, training and events to scale any open source project, which together deliver an economic impact not achievable by any one company. More information can be found at www.linuxfoundation.org

The Linux Foundation has registered trademarks and uses trademarks. For a list of trademarks of The Linux Foundation, please see our trademark usage page: https://www.linuxfoundation.org/trademark-usage

Linux is a registered trademark of Linus Torvalds.

Press contact TIMETOACT GROUP:

Christin Louise Weber

christin.weber@timetoact.de