OSPOlogy Follow-up: A legal guide to open works

[anajsana]

Discuss with the community topics related to the upcoming OSPOlogy meeting:

📅 February, 15th ➡️ A Legal Guide To Open Works

Join Zoom Link: TBD

In this open space, people can:

• Ask questions prior to the meeting starts
• Share notes from the conversation
• Make proposals for new initiatives that can help the OSPO Ecosystem
• Add useful links and resources related to the topic
• Connect with mentors involved in OSPOs and/or Open Source Management

Intro Presentation Slides: https://docs.google.com/presentation/d/1WkEBmokx_l3Y6GbPBwCFz8uwGmyJoKgUhBpolr-UoiU/edit?usp=sharing

PDF TBD

[anajsana]

Question from the chat:

In the US Federal Government, Plain Language is becoming an increasingly more popular and understood strategy for the accessibility of policy. https://www.plainlanguage.gov/

Is there a similar national policy for you folks?

[anajsana]

Question from the chat:

The guide explains how a developer can evaluate License Compliance when they are using third-party dependencies. For example: a dev writing a script in python using a third party package with an AGPL (or some other license). The guide explains to the dev how to proceed?

[anajsana]

future guide's roadmap to have the compliance part: https://www.mancomun.gal/documento/matriz-de-compatibilidade-de-licenzas-de-software-libre/

[anajsana]

comment in the chat:

The license compatibility matrix is super helpful! I’ve used these types of resources in other OSPOs often!