GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Exempt our meeting mechanics documents from the CC-BY-SA part and turn them into CC-BY or even CC-0 · Issue #514 · InnerSourceCommons/InnerSourceLearningPath

Exempt our meeting mechanics documents from the CC-BY-SA part and turn them into CC-BY or even CC-0 #514

New issue
Copy link
New issue
Copy link
Open
Open
Exempt our meeting mechanics documents from the CC-BY-SA part and turn them into CC-BY or even CC-0#514
Copy link
Labels
MetaMeta tasks related to production of the Learning Path but not actually directly creating contentMeta tasks related to production of the Learning Path but not actually directly creating content

Description

@lenucksi
lenucksi
opened on Nov 21, 2022
Issue body actions

The meeting mechanism we use in the learning path (shaped by @rrrutledge and many others) has proven to work really well over time and people.
It turns out to be even valuable for other non learning path groups (e.g. our foundation board meetings).

However, the material is still CC-BY-SA licensed and thus would need to return changes back to its origin. Which some people might not be comfortable with for their corporate changes.
While I fully stand behind our choice of CC-BY-SA for the learning path material, I would like to ask to change the license for the above mentioned material to CC-BY (only attribution) or even CC-0 (as public domain as it gets, EU/DE just doesn't know the US public domain concept).

Git says that there is at least on-the-record contribution to it by @rrrutledge, @tsadler1988, @fioddor and of course @arnom-ms (and me, but I'm asking for the change, so count me as "for"). What do you think about this change?

How could we do it:

  • Add a note to our README document and add the chosen license as a file to the meeting folder. We could also add Markdown comments indicating the license to those documents.
Reacted by Igor Zubiaurre

Activity

  1. lenucksi
    added
    MetaMeta tasks related to production of the Learning Path but not actually directly creating contentMeta tasks related to production of the Learning Path but not actually directly creating content
    on Nov 21, 2022
  2. rrrutledge commented on Nov 21, 2022

    @rrrutledge
    rrrutledge
    on Nov 21, 2022
    Contributor
    More actions

    Fine for my part.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    MetaMeta tasks related to production of the Learning Path but not actually directly creating contentMeta tasks related to production of the Learning Path but not actually directly creating content

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.