Improve the Vault (GSoC task) - Revision history

Vlorentz: /* Potential mentors */

2021-03-02T10:33:28Z

Potential mentors

← Older revision		Revision as of 10:33, 2 March 2021
Line 25:		Line 25:
	== Potential mentors ==		== Potential mentors ==

	* Nicolas Dandrimont		* Nicolas Dandrimont (olasd on [[IRC]])
	* Stefano Zacchiroli <zack@upsilon.cc>		* Stefano Zacchiroli <zack@upsilon.cc> (zack on [[IRC]])
	* Valentin Lorentz		* Valentin Lorentz (vlorentz on [[IRC]])

	[[Category:GSoC task]]		[[Category:GSoC task]]

Vlorentz: Add olasd

2021-03-02T10:21:34Z

Add olasd

← Older revision		Revision as of 10:21, 2 March 2021
Line 25:		Line 25:
	== Potential mentors ==		== Potential mentors ==

			* Nicolas Dandrimont
	* Stefano Zacchiroli <zack@upsilon.cc>		* Stefano Zacchiroli <zack@upsilon.cc>
	* Valentin Lorentz		* Valentin Lorentz

	[[Category:GSoC task]]		[[Category:GSoC task]]

Vlorentz: add skills & mentors

2021-03-02T10:08:03Z

add skills & mentors

@@ Line 15: / Line 15: @@
 * improve unit and end-to-end testing
 * other general code improvements (better progress/error reporting in the frontend, etc.)
 [[Category:GSoC task]]

Vlorentz at 12:27, 10 February 2021

2021-02-10T12:27:35Z

← Older revision		Revision as of 12:27, 10 February 2021
Line 1:		Line 1:
			== Introduction ==

	The Software Heritage archive allows retrieval of archived objects of different formats.		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://docs.softwareheritage.org/devel/swh-vault/index.html Software Heritage Vault].		Once an object has been chosen for retrieval, it can be "cooked" using the [https://docs.softwareheritage.org/devel/swh-vault/index.html Software Heritage Vault].

			== Task description ==

	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).		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).

Vlorentz at 13:38, 12 February 2020

2020-02-12T13:38:46Z

← Older revision		Revision as of 13:38, 12 February 2020
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]]

StefanoZacchiroli: 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..."

2020-02-10T09:09:02Z

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..."

New page

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://docs.softwareheritage.org/devel/swh-vault/index.html 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 [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?)
* improve end-to-end testing
* other general code improvements (better progress/error reporting in the frontend, etc.)

[[Category:GSoC task]]