🗽 Migrate to segregated content license #17
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Re ongoing developments to update this into a growing podcast reference, I think we should use a more creator-friendly tool for the content. This will be of growing importance once the feed lives here and we have a place for others to reference direct episodes freely. That kind of collaboration is difficult for the GFDL, which was originally implemented with a much narrower view of the repo.
Namely, I hypothesized that we could use this as a future-looking planning repo alone. Ideally, there could be preset topics and discussions looking weeks into the future so that we can properly segment guests without a central planner. This is still a key part of the vision, but I've seen much conversation outside of the actual "code" here, which is covered by the text-heavy license.
This change aims to free us up for further development amid an expanding repository that acts more like a functional website program, while discussions take place in actual forums. As much as I love the transparency of Git, it seems more prudent to keep high-level chats where they can best garner attention from relevant audiences. All this should be much easier to implement with a policy that makes our work easier to share while still ensuring its perpetual growing freedom.
Action Asks
Would the three other contributors to this repository so far: @BibicJr @bobmahalo @tehchives please verbally OK this change in the comments below? This way we can make sure everyone afflicted by the present settings is on the same page. In the future, perhaps we'd use DUNA votes for material policy changes like these when the number of participants greatly exceeds reasonably-accessible groups.