Skip to content
View winterrocks's full-sized avatar

Organizations

@todogroup

Block or report winterrocks

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Please don't include any personal information such as legal names or email addresses. Maximum 100 characters, markdown supported. This note will be visible to only you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
winterrocks/README.md

Hi there πŸ‘‹

This is my initial personal readme, using the ideas from the template.

πŸ”­ I’m currently working on

  • OSPO stuff

🌱 I’m currently learning

  • Software Architecture
    • Microservices
    • Domain-Driven Design (DDD)
    • Cloud Architecture
    • Enterprise Architecture
    • Microservices security
    • Breaking a Monolith into Microservices
  • :octocat: GH
    • EMU, etc.
  • Contributions for an organization
  • InnerSourcing, e.g. from ISC
  • SCA tooling
  • OpenChain and ISO 5230
  • SBOMs

πŸ‘― I’m looking to collaborate on

  • OSS Licensing
  • SW Strategies and how OSS plays a role in it

πŸ€” I’m looking for help with

πŸ’¬ Ask me about

  • OSS Licensing
  • OSPOs
  • Open Source Due Diligence
    • Experience especially from the buyer side, but knowing the buyer side is useful for the seller side too

✨ Webinars and conference talks (in chronological order)

If borrowing content from the slides, an attribution would be nice, but not mandatory.

πŸ“‚ Posts about Open Source License issues remediation ideas

Below are a bit older but still valid posts about ideas on how to remediate Open Source Licensing issues. The posts were originally done on LinkedIn, but they are now buried under many other posts, so difficult to find.

As a bonus, there was also a post about Linux Kernel Loadable Modules (KLM) a.k.a. Loadable Kernel Modules (LKM):

πŸ‘ I also encourage people to check the original LinkedIn posts because there are some very good comments from some of the industry leaders.

πŸ“« How to reach me:

πŸ˜„ Pronouns:

  • hΓ€n/he/him

⚑ Fun fact:

  • Obviously, I'm not a great snowboarder πŸ‚, but I still do it. Injuries so far:
    • Broken ribs many times
    • Dislocated shoulder x 4 and shoulder has been operated x 2 now:
  • The music I listen tends to be on the harder side of the spectrum: (melodic) death metal, thrash metal, doom metal, black metal, ... I guess that you got the point πŸ˜„

πŸ“„ Acronyms used above

Acronym Spell out
CC-BY-SA Creative Commons Attribution Share Alike
DDD Domain-Driven Design
EMU Enterprise Managed Users
GH GitHub
GPL General Public License
ISC InnerSource Commons
KLM Kernel Loadable Module
LKM Loadable Kernel Module
M&A Mergers & Acquisitions
OSPO Open Source Program Office
OSS Open Source Software
SBOM Software Bill of Materials
SCA Software Composition Analysis
SPDX Software Package Data Exchange
SW Software

Popular repositories Loading

  1. winterrocks winterrocks Public

    My personal repository

    1

  2. ospo101 ospo101 Public

    Forked from todogroup/ospo-career-path

    OSPO 101 Training Modules

  3. todogroup.org todogroup.org Public

    Forked from todogroup/todogroup.org

    The group for companies that run open source programs

    SCSS

  4. ospology ospology Public

    Forked from todogroup/ospology

    πŸ“– OSPOlogy - The Study of OSPOs

    HTML

  5. Font-Awesome Font-Awesome Public

    Forked from FortAwesome/Font-Awesome

    The iconic SVG, font, and CSS toolkit

    JavaScript

  6. OSLC-handbook OSLC-handbook Public

    Forked from finos/OSLC-handbook

    A data store and handbook of practical information about complying with the most common open source licenses.

    HTML