+- Forums (https://www.vdrift.net/Forum)
+-- Forum: Project (https://www.vdrift.net/Forum/forumdisplay.php?fid=4)
+--- Forum: Development (https://www.vdrift.net/Forum/forumdisplay.php?fid=9)
+--- Thread: VDrift Data on GitHub (/showthread.php?tid=1660)
VDrift Data on GitHub - BiGBeN87 - 08-30-2012
Hello everyone,
there was recently a discussion on GitHub about handing over my experimental VDrift-Data repository to the official VDrift account. Although this has been mentioned in this forum, I thought I should plug it here, since the original discussion has run dry.
As far as I see, these are the prerequisites to make the transition:
- VDrift's project lead needs to be willing to make this transition.
- The actual content creators need to accept it.
- From a freeze-point on no further commits may be made against the svn repository at Sourceforge.
- For a regression-free translation, we need a complete list of all svn committers with email addresses.
- Someone from the VDrift organization needs to accept and handover my repository at GitHub.
RE: VDrift Data on GitHub - NaN - 08-30-2012
(08-30-2012, 01:15 PM)BiGBeN87 Wrote: Hello everyone,
there was recently a discussion on GitHub about handing over my experimental VDrift-Data repository to the official VDrift account. Although this has been mentioned in this forum, I thought I should plug it here, since the original discussion has run dry.
As far as I see, these are the prerequisites to make the transition:
- VDrift's project lead needs to be willing to make this transition.
- The actual content creators need to accept it.
- From a freeze-point on no further commits may be made against the svn repository at Sourceforge.
- For a regression-free translation, we need a complete list of all svn committers with email addresses.
- Someone from the VDrift organization needs to accept and handover my repository at GitHub.
Yeah, now that the sim branch is merged I think we are ready to move. I(logzero) can handle the github handover.
@joevenzon Are you OK with this? Is it eventually possible to notify sourceforge data committers (no idea whether sourceforge has this functionality)?
RE: VDrift Data on GitHub - joevenzon - 08-31-2012
@logzero if you think it's a good idea and want to handle the switch over, I'm OK with it, though make sure you disable (or remove from the UI) the auto-update stuff, since that scrapes the SVN repo.
RE: VDrift Data on GitHub - NaN - 08-31-2012
(08-31-2012, 12:29 AM)joevenzon Wrote: @logzero if you think it's a good idea and want to handle the switch over, I'm OK with it, though make sure you disable (or remove from the UI) the auto-update stuff, since that scrapes the SVN repo.I'd prefer to keep auto-update functionality, make it a blocker for data to github move.
@BiGBeN87 We need to add github support to auto update. Any ideas or maybe even a patch?
I've been playing a bit with github:
Code:
Get data content:
curl -k https://api.github.com/repos/bigben87/VDrift-Data/git/trees/master
Parse cars directory url:
{
"type": "tree",
"path": "cars",
"mode": "040000",
"url": "https://api.github.com/repos/bigben87/VDrift-Data/git/trees/de24ce5756a6e05d380f76a294d952592ce411cb",
"sha": "de24ce5756a6e05d380f76a294d952592ce411cb"
}
Get car directory content:
curl -k https://api.github.com/repos/bigben87/VDrift-Data/git/trees/de24ce5756a6e05d380f76a294d952592ce411cb
Compare SHA hashes to find modified cars.Btw ptree_inf is "almost" json. Adding a ptree_json to process github output should be quite simple. Or we could add a json lib as dependency.
RE: VDrift Data on GitHub - antoniovazquez - 08-31-2012
Maybe testing tags... That should allow you to make commits without updating data untill a new tag is created...
This may help...
http://developer.github.com/v3/
RE: VDrift Data on GitHub - NaN - 08-31-2012
(08-31-2012, 04:05 PM)antoniovazquez Wrote: Maybe testing tags... That should allow you to make commits without updating data untill a new tag is created...
This may help...
http://developer.github.com/v3/
Git master is stable. Testing, development should happen in branches.
As I wrote in the post above all we need is to fetch two json files and get the car/track hashes from them. It is not much different to current svn update code. We wont have the nice increasing version numbers. But then I don't think they matter much.
RE: VDrift Data on GitHub - BiGBeN87 - 08-31-2012
I do not know C++ and can therefore not supply patches. The SHA1-hashes used by Git and exported by GitHub's API are but perfectly good for identifying versions of content. I proofed the concept of matching local (unversioned) content against Git before by implementing a tool that calculates git-compatible hashes for all of VDrift's Data. Using GitHub's API seems the right way to get the remote hashes and since there seems to exist no client library for the GitHub API in C++, using cURL seems sane. Since all responses of by GitHub's API are valid JSON, using a library to parse them seems to be a fail-safe approach.