search

JWillow / nabaztag-source-code

Automatically exported from code.google.com/p/nabaztag-source-code
0 stars 0 forks source link

Source repository #2

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Please provide the real source code repository (for the Nab Hardware, and the 
server) by releasing the whole internal repository, not a snapshot that can be 
a really old version.

Please release too the media specific for the nabaztag, I.E. all audio files 
used for the clock and all other speaking capabilities for the nabs.

Original issue reported on code.google.com by godzi...@gmail.com on 28 Jul 2011 at 9:23

GoogleCodeExporter commented 8 years ago 
I joined the IRC channel and grabbed the SVN source. I've never contributed to 
a project like this but it seems absurd that the repository is 3 files (a 1mb 
zip, a 650zip, and a 175mb tgz).  I tried pinging on IRC and no one responded. 
I've worked in software for 13 years but am new to collaborating on distributed 
projects and svn, but if I can figure out how to turn the SVN distribution into 
not giant monolithic files, and unless someone advises that this would be the 
wrong decision, I'd like to try to do that (it took me 3 or 4 attempts just to 
successfully sync).

Thanks in advance for any feedback!
- patrick

Original comment by h...@psoul.com on 20 Aug 2011 at 2:04

GoogleCodeExporter commented 8 years ago 
The mains problem is not to transfer what they put as a real SVN/GIT/Whatever 
repository, but to have access to the real repository with all commits and 
revisions that was made before these backup, (if mindscape have it btw, they 
can be lost during the violet to mindscape migration..)

Here we have only one revision of the repository, and surely not the latest 
one, and this is not a good option. It better than nothing, that's true, but 
having the real repository, may help to understand why some parts are made like 
they are.

Original comment by godzi...@gmail.com on 22 Aug 2011 at 11:26