-
-
Notifications
You must be signed in to change notification settings - Fork 6
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
Comments
Legal:
|
Hall of fame:
|
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 anawesome-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 ...
The text was updated successfully, but these errors were encountered: