Make this a Google Doc
pbreit opened this issue · 12 comments
Seems like Google Docs is perfect for this sort of thing.
they are open sourcing this spreadsheet so that you can modify it and send pull requests....
How is a pull request supposed to work with a binary file? There can be no changeset to apply. There is no diff.
Github is a stupid place to host this.
github for storing binary files? use dropbox, google drive, a webserver... or if you need forum features, use any other ALM or ticket handler
How is a pull request supposed to work with a binary file? There can be no changeset to apply. There is no diff.
Github is a stupid place to host this.
While a diff can't be seen.. you can make a fork and have it be referred back to a version here. Two way reference. Can't do that with other document sharing platforms... Those are meant to keep one timeline and only one most recent.
Git allows for branches of timelines.
branches of timelines? - in case of a binary file. it is called folders of specific timelines you can do many folders in dropbox, google drive, etc.
fork? - that is called copy, or share
you can have free stuff without using github - which is a version control system - for text files.
branches of timelines? - in case of a binary file. it is called folders of specific timelines you can do many folders in dropbox, google drive, etc.
fork? - that is called copy, or share
you can have free stuff without using github - which is a version control system - for text files.
The reason for git to exist is to avoid the age old behavior of devs creating many folders for different versions manually. Imagine the clutter of 100 folders vs 1 git repository.
In your case branches are just folders - if you cannot use the real features of branches.
Now you creating 100 branches for different version of a binary file. And that is all.
Sorry, git exists for storing different version of a text file on different branches - to able to merge them or get a commit from one to another, etc.
please tell me what you can do with binary files, except doing the old behavior of devs.
@laplasz dude, why are you giving them such a hard time? If they want to use it, let them use it...
To be fair they should be using releases to mark versions.. Right now to get to previous versions you gotta go through miscellaneous commits.
You can always download raw spreadsheet in previous versions and do a compare yourself. There is no diff capability.. but it is no less useful than 100 folders approach.
Google Sheets won't solve the need for README... and having a separate google docs mean two separate "commits" with inexact timestamps.
I think the fork ability of GitHub far outweighs any of @laplasz complaints. There is no simple way to replicate it. Otherwise everyone who "fork" will need write access to write somewhere they had forked the documents.
if something is open sourced the place you only have to credit the source is in your version of the document/project.
Cheers
if something is open sourced the place you only have to credit the source is in your version of the document/project.
Cheers
But that is one way reference. If I started at upstream and want to find downstream it's not as easy without access to fork members