All images and other medias centralized in GitHub
Today, images and other media are saved at different places : BG-6 Sources, BG-7 Photos and videos, BG-9 Media coverage, and on contributors' computers. Google Drive does not offer the best experience to synchronize documents and to trace changes.
I propose to keep Google Drive for documents only and to transfer all images, videos and other media to GitHub. Media concerning a game will be saved in the game folder, other media will be saved in a general repository (general artwork for website, presentations ; 3d goodies, images of mouthpieces, lungs, breathing systems, partners logos, people, third part devices and games, etc.).
Poll Created Tue 26 Jan 2016 3:45PM
I agree to switch all non text documents to GitHub Closed Fri 29 Jan 2016 3:08PM
Results
Results | Option | % of points | Voters | |
---|---|---|---|---|
|
Agree | 50.0% | 1 | |
Abstain | 50.0% | 1 | ||
Disagree | 0.0% | 0 | ||
Block | 0.0% | 0 | ||
Undecided | 0% | 12 |
2 of 14 people have participated (14%)
Bob Haugen
Tue 26 Jan 2016 3:52PM
I'm not much of a participant, so I'll abstain, but you might also want to look at https://www.gitbook.com/ for text documents.
John Danger Thu 28 Jan 2016 4:45PM
when you say Medias are saved in differents places, I don't agree, it's just on differents folders on Drive. I found the BG Drive pretty orginized (even if it could be still improved).
It's really easy to drop new media or documents on it, like litterally : drag and drop.
Using Github for the code makes sense, because devlopper are familiair with it. But if you're not it's like 15 to 25min of youtube tutorial to get through.
++ it's free
Moving all the media from drive to Gitbook doesn't make sens to me, it's really not user friendly for everyone and it's not free. (it's free only for personnal use)
So yeah we could move all the code part to github, but I'd prefer to stay on Drive for documentations & medias.
Bob Haugen Thu 28 Jan 2016 4:56PM
Moving all the media from drive to Gitbook doesn't make sens to me, it's really not user friendly for everyone and it's not free. (it's free only for personnal use)
Oops, sorry, I didn't look closely enuf. Got a nice review from a friend, should have done more investigation.
Fabio Balli Tue 2 Feb 2016 6:22PM
So status quo.
@johndanger it's not about Gitbook it's about Github and it is free for open source projects. The code is already on GitHub. :-)
I agree that the wording of GitHub is quite weird but it can easily be explained with one slide (you create your own version of the work with "add a branch", inform people about changes you made on your version with commit, and transfer the improvements you did from your version to the common work with "pull").
Drive is long to load, and creates problems in sync : many loads are required sometimes to see the new files such as with Alex and Annick, and some deleted documents reappear without notice - such as when Yannick uploaded his Win version, it just updated BG with old files.
Jim Anastassiou · Thu 28 Jan 2016 4:20PM
I've been using github more and more and love it. The problem I see is with the learning curve to properly using the tools for someone not in software dev.