Difference between revisions of "Improve the Vault (GSoC task)"
(Created page with "The Software Heritage archive allows retrieval of archived objects of different formats. Once an object has been chosen for retrieval, it can be "cooked" using the [https://do...") |
|||
| Line 9: | Line 9: | ||
* use our in-memory graph database [https://docs.softwareheritage.org/devel/swh-graph/index.html swh-graph] to speed up fetching the necessary subgraphs. | * use our in-memory graph database [https://docs.softwareheritage.org/devel/swh-graph/index.html swh-graph] to speed up fetching the necessary subgraphs. | ||
* write cookers to output new formats (e.g git tarballs/git bundles or even other VCS?) | * write cookers to output new formats (e.g git tarballs/git bundles or even other VCS?) | ||
| − | * improve end-to-end testing | + | * improve unit and end-to-end testing |
* other general code improvements (better progress/error reporting in the frontend, etc.) | * other general code improvements (better progress/error reporting in the frontend, etc.) | ||
[[Category:GSoC task]] | [[Category:GSoC task]] | ||
Revision as of 13:38, 12 February 2020
The Software Heritage archive allows retrieval of archived objects of different formats. Once an object has been chosen for retrieval, it can be "cooked" using the Software Heritage Vault.
Right now the Vault has several limitations: it only handles two kinds of objects (revisions and directories), it requires recursively requesting the database to get the full subgraph of an object, and it generates revisions in an unpractical format (git fast-import).
Several improvements are possible:
- add coverage for new kinds of objects (releases, snapshots and even origins?)
- use our in-memory graph database swh-graph to speed up fetching the necessary subgraphs.
- write cookers to output new formats (e.g git tarballs/git bundles or even other VCS?)
- improve unit and end-to-end testing
- other general code improvements (better progress/error reporting in the frontend, etc.)
