Volute transferOptions for transferring Volute from GoogleCode to GitHub. | ||||||||
Added: | ||||||||
> > | ||||||||
Headline figures, based on disc usagevolute-complete - 825MSvn checkout of everything in the repository.svn checkout https://volute.googlecode.com/svn/trunk/ volute-complete du -h volute-complete > complete-original.txt volute-noextern - 764MSvn checkout, without resolving the extern references.svn checkout --ignore-externals https://volute.googlecode.com/svn/trunk/ volute-noextern du -h volute-noextern > noextern-original.txt volute-export - 391MSvn export, a snapshot of the current state with no commit history.svn export --ignore-externals https://volute.googlecode.com/svn/trunk/ volute-export du -h volute-export > export-original.txtOf the 391M in the exported snapshot, the top 8 projects are :
Maximal transferIf we just press the 'export to GitHub' button, then everything will get transferred, including the commit history. I have seen this work on a small project, and everything just worked. On a large project like ours the process will probably take a while. I have not heard of any reports of anything going wrong with the automatic transfer process. With a total size of 825M we are close to the GitHub 1Gbyte per repository limit, which may cause problems later on. The only unusual thing I found was that the email telling you the process has completed will be sent to the email address linked to your GitHub account, not to your Google account. See: GitHubExporterIVOA organizationIf we want our GitHub repository to be owned by the IVOA organization in GitHub, you can do the transfer to a private account, and then transfer ownership to the IVOA organization afterwards. See: Migrate to an OrganizationMinimal snapshot transferIf we skip the svn history and just take a snapshot of where we are now, then we have less than 400M to transfer. We would have to do the transfer manually, exporting a local copy from svn, and then importing it into a new GitHub repository.git clone https://github.com/YOUR-USERNAME/YOUR-REPOSITORY local-repo svn export --ignore-externals https://volute.googlecode.com/svn/trunk/ local-repo pushd local-repo git add . git commit -m 'Initial import from svn' git push popd Space limitsGitHub doesn't have a hard limit on the size of a repository, but they do recomend a limit of 1GB per repository.We recommend repositories be kept under 1GB each. This limit is easy to stay within if large files are kept out of the repository. If your repository exceeds 1GB, you might receive a polite email from GitHub Support requesting that you reduce the size of the repository to bring it back down.See: What is my disk quota ? I contacted GitHub to see if there would be an issue with us using more than 1Gbyte of space. I got the following reply from a member of their team : Hi Dave, Thanks for reaching out! We strongly recommend keeping repositories under 1GB in size. Additionally, to ensure that repository performance is optimal, only files less than 100MB in size can be pushed to GitHub.com. More information about this can be found here: https://help.github.com/articles/what-is-my-disk-quota The good news is that in order to make working with large files better, we recently published an extension to Git called Git Large File Storage, and support for Git LFS is currently in early access on GitHub.com. You can check it out at http://git-lfs.github.com and sign up for early access at https://github.com/early_access/large_file_storage I hope this information helps, please let us know if you have any questions! Cheers, Rachel Large filesI suspect that due to the way that we use volute, the Large File Storage extension will be of limited value to us. In the current version of the Git LFS extension you can't select which files should be stored separately based on file size. The file selection criteria is based purely on file path and type. A number of people have been asking for selection by size, but it does not look like it will be available soon. This means that in order for it to be useful in reducing the size of our repository, we would need to identify which files we wanted to be handles using the LFS extension before they were added to the repositiory. In reality, some of our users would be extremely careful about making sure everypdf and doc file in their project was listed, even the ones that
were less than 1Mbyte.
Other users would just want to be able to commit and push a whole directory
tree and leave it up to the software to sort out which files need to be
handled differently.
The LFS extension was designed to enable Git to handle things like binary
image files, e.g. jpeg , png , svg , using the file path and type to
identify which files should be stored externally.
Looking the files in our current volute repository, we have a wide variety
of different file types and sizes, and it would be difficlut to define a
reliable selection criteria to identify which files should be handled by LFS.
html and xml files, generated
by our modelling tools. Equally, some of our smallest files are also html
and xml files.
We would need to be careful to ensure that none of the html or xml
source files for our documents ended up being stored as binary files rather
than version controlled text files.
Space constraintsThe reason for trying to minimize the space required for our documents repository is not just due to the GitHub recommendation to limit repositories to 1G byte. Due to the way that git itself works, it is better to have many small repositories rather than one large one. With the current svn repository we can selectively check out just a small part of the overall repository. For eaxample, if we want to edit one of the text files for the current TAP specification, then we only need to check out just that small section of the repository that contains those files.
Project typesLooking at the current contents volute, we have several different project types.Theory projectsIt looks like the theory projects contain a relativley small number of human edited source files, and the majority of the space is taken up by machine generated files.
Data modelsFour of the data model projects are directly related to the standard documents defining the corresponding data model.
doc , pdf and png files. | ||||||||
Added: | ||||||||
> > |
VO-DML | |||||||
The fith data model project is for the VO Data Modelling Language, VO-DML.
This project accounts for over 100M of the 126M of space used by the data
model projects, and is the third largest project in the volute repository.
doc , pdf and png files.
Although this project is related to the VO-DML and UTYPE specifications,
there is a case for exporting it as a separate separate GitHub repository.
In addition to the documents for the VO-DML and UTYPE specifications the
vo-dml project also contains definitions of the models plus the source
code for the tools for validating the models and for building derived data
products from them.
VOSpace serviceWe have one project that contains code for a program, donated by Rick Wagner at UC San Diego.
= PHP VOSpace Endpoint = VOSpace endpoint building on top of the [http://www.irods.org iRODS] client, Prods. Requires Prods, which is part of the iRODS distributions (under clients). Also uses [http://simpletest.sf.net SimpleTest] for unit tests. Configure the locations in config.inc. Rick Wagner http://lca.ucsd.edu/projects/rpwagner rwagner@physics.ucsd.eduAs a self-contained source code project there is a case good case for exporting this as a separate GitHub repository. VocabulariesThe vocabularies project contains the build tree for the IVOA vocabulary SKOS files. Although this project is relatively small, 3.4M, it is not directly related to an IVOA document or standard. As a self-contained source code project there is a case good case for exporting this as a separate GitHub repository.Documents and standardsEverything else in our repository are either source text for our documents or tools for creating documents.Proposed structureIf we take a copy of the exported snapshot and split out the projects identified as candidates for separate GitHub repositories. The we get the following set of candidate GitHub repositories:
Historical versionsIt would be possible to further reduce the size of the ivoa-documents repository by excluding some of the the historical versions of documents currently stored in our repository. Several of our IVOA standards store collections of previous versions of the document as binary files.
Commit historyThe automated 'export everything to GitHub' button will preserve the svn commit history. The simple 'snapshot transfer' of a svn export will not preserve the svn commit history. There are a number of tools that should enable us to preserve the svn commit history intact during the transfer. The two main examples are :
References |