Difference between revisions of "Improve and extend the archive Web UI (GSoC task)"

From Software Heritage Wiki
Jump to: navigation, search
(add links to other tasks)
Line 1: Line 1:
 +
== Introduction ==
 +
 
As you probably know already, The Software Heritage archive can be
 
As you probably know already, The Software Heritage archive can be
 
[https://archive.softwareheritage.org browsed on the Web]. The
 
[https://archive.softwareheritage.org browsed on the Web]. The
Line 4: Line 6:
 
interface is a Django application that also implements a
 
interface is a Django application that also implements a
 
[https://archive.softwareheritage.org/api/ Web API].
 
[https://archive.softwareheritage.org/api/ Web API].
 +
 +
== Task description ==
  
 
Several improvements are possible on the archive Web interface and would make
 
Several improvements are possible on the archive Web interface and would make
 
great GSoC projects, some ideas to whet your appetite:
 
great GSoC projects, some ideas to whet your appetite:
  
* add new source code search criteria and improve the search interface
 
 
* add developer-oriented features, e.g., source file history, blame/praise interface, in-browser edit (with patch download), ... (note that this will also require backend design and implementation)
 
* add developer-oriented features, e.g., source file history, blame/praise interface, in-browser edit (with patch download), ... (note that this will also require backend design and implementation)
 
* improve [https://www.w3.org/WAI/ accessibility]
 
* improve [https://www.w3.org/WAI/ accessibility]
 
* display metadata we already mined from the archive
 
* display metadata we already mined from the archive
 
* help us design and implement our [https://forge.softwareheritage.org/T1805 next API version]
 
* help us design and implement our [https://forge.softwareheritage.org/T1805 next API version]
 +
 +
== Other relevant (but independent) tasks ==
 +
 +
[[Improve project search engine (GSoC task)]] is an independent task,
 +
which may or may not involve improvements to the Web UI, depending on
 +
you tastes.
 +
 +
While this task can be about displaying metadata we already mined,
 +
you may also be interested in [[Mine information from archived content (GSoC task)]]
 +
and [[Mine information from external sources (GSoC task)]] to mine more
 +
of this metadata; but those are completely independent tasks.
  
 
[[Category:GSoC task]]
 
[[Category:GSoC task]]

Revision as of 12:27, 10 February 2021

Introduction

As you probably know already, The Software Heritage archive can be browsed on the Web. The code powering that interface is a Django application that also implements a Web API.

Task description

Several improvements are possible on the archive Web interface and would make great GSoC projects, some ideas to whet your appetite:

  • add developer-oriented features, e.g., source file history, blame/praise interface, in-browser edit (with patch download), ... (note that this will also require backend design and implementation)
  • improve accessibility
  • display metadata we already mined from the archive
  • help us design and implement our next API version

Other relevant (but independent) tasks

Improve project search engine (GSoC task) is an independent task, which may or may not involve improvements to the Web UI, depending on you tastes.

While this task can be about displaying metadata we already mined, you may also be interested in Mine information from archived content (GSoC task) and Mine information from external sources (GSoC task) to mine more of this metadata; but those are completely independent tasks.