Issue: 331 image host ideas #391
Conversation
|
|
||
|
|
||
| ## Image Hosting Guidelines | ||
| Currently, this project utilizes the Tessel Project Imgur, older image assets are on AWS from Technical Machine days, and we have a few miscellaneously hosted images too. |
There was a problem hiding this comment.
Markdown needs an extra newline in order to make this a paragraph break
CONTRIBUTING.md
Outdated
|
|
||
| ## Image Hosting Guidelines | ||
| Currently, this project utilizes the Tessel Project Imgur, older image assets are on AWS from Technical Machine days, and we have a few miscellaneously hosted images too. | ||
| Moving forward, our process will be to streamline image hosting through Tessel Project's Imgur. Older assets on AWS and elsewhere can be retroactivley moved over in the future. The Imgur should have folders per project/feature/whatever the image is of. |
There was a problem hiding this comment.
Overall this is a good idea but it does create an access bottleneck; only a few people have keys to the Tessel Imgur account, and I'd love to decentralize more. Two other ideas: what if the images were hosted on a specific Tessel repo that people could PR? Or, what if images were hosted on anyone's imgur account (and thus just public links)? Curious about tradeoffs, e.g. the Github hosting would be annoying to clone down, but Github now has a pretty slick in-browser file upload so maybe that's a non-issue now?
|
i like the specific repo one - it makes it easy for anyone with access and does not really affect the main project |
|
Looks great! I just made a (very basic) repo if you want to change it to link to that: https://github.com/tessel/image-host |
|
added link |
I added in the Contributing.MD file some ideas that can solve Issue #331