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

(Feedback wanted) Community scenes repository idea #12

Open
Tremeschin opened this issue Feb 6, 2025 · 2 comments
Open

(Feedback wanted) Community scenes repository idea #12

Tremeschin opened this issue Feb 6, 2025 · 2 comments

Comments

@Tremeschin
Copy link
Member

Tremeschin commented Feb 6, 2025

I want to create a repository that people can send pull requests for adding their own work to showcase it like on shadertoy website. A couple of thoughts of how it could go:

Technical:

  • Users must have full control over their own username folder, the PR must obviously be reviewed for any malicious content beforehand, ideally automatically approved or not

    • This can also be done by adding people's submodules to the repository, so they have the freedom to work with their own repo and send PR updating the references to a commit. This is harder to review, and better if they squash commits on merge imo

    • This can also be done by people having their own shaderflow-$username PyPI packages and aggregating links on an awesome-shaderflow like repository (versioning could go terrible, see next point)

  • Developers and trusted users should have the rights to fix / port / improve other people's work if anything breaks, internals gets renamed or find better ways to do stuff, keeping the author's copyright

  • The code infrastructure to find the scenes must be improved due the large amount of scenes being listed, maybe adding many sub-commands per folder, or use as shaderflow community/username scene ...

@Tremeschin Tremeschin added this to Tasks Feb 6, 2025
@Tremeschin Tremeschin moved this to Planned in Tasks Feb 6, 2025
@Tremeschin
Copy link
Member Author

Legal:

  • The boundaries of copyright must be well-defined, contributors decides and keeps their own license/copyright, common metadata should be logged on screen (author, license, sponsoring, etc)

  • I strongly oppose non-commercial licenses, it limits opportunity for everyone, even a modest return from successful users would likely outweigh solo gains. It smells like source-available BSL, find a way to encourage CC-BY-SA 4.0 and separate it from others (NON_COMMERCIAL=1?)

  • If creators want to profit from their work, which they are encouraged to, the non-commercial terms could be lifted up by the users sponsoring the authors (for a lower entry point, only after certain revenue amount). It would be fair to return a small percentage to the platform, as they were also being in showcase and maintained

@Tremeschin
Copy link
Member Author

Hall of fame:

  • There could be a voting system of some sort, like starring the creator's fork of this repo, for the top % creators to be showcased on the official website at brokensrc.dev (or after a certain star amount), perhaps even a sub mkdocs website dedicated to it at some sub domain explaining it better (rip github api limits)

  • Users can have readmes in their folders showcasing githubassets videos of their work!, perhaps even automate this task or scrap information out of the scene file for generating the website (one of the reasons for a centralized repo)

@Tremeschin Tremeschin pinned this issue Feb 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Planned
Development

No branches or pull requests

1 participant