Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🗽 Migrate to segregated content license #17

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

JFWooten4
Copy link
Member

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.

@bobmahalo
Copy link
Contributor

Ok.

@bobmahalo
Copy link
Contributor

OK

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants