Difference between revisions of "Improve and extend the archive Web UI (GSoC task)"
(factor out from main GSoC page) |
|||
| Line 11: | Line 11: | ||
* 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 | ||
* 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] | ||
[[Category:GSoC task]] | [[Category:GSoC task]] | ||
Revision as of 13:50, 10 February 2020
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.
Several improvements are possible on the archive Web interface and would make 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)
- improve accessibility
- display metadata we already mined from the archive
- help us design and implement our next API version
