Search results

• Create search ranking (GSoC task)
  Make the software heritage search better by creating a better ranking for results. Metadata can be used to improve results. Some criteria for result ranking could be
  553 bytes (83 words) - 20:29, 15 February 2022
• Source code search engine prototype (internship)
  ...gine] supports searching archived projects (or "origins") via their URL or metadata. Indexing all source code files archived by Software Heritage (~500-600 TB) is a major undertaking in terms of indexing time and
  1 KB (204 words) - 15:11, 4 February 2024
• Crawling project metadata (internship)
  '''Contexte''': [https://www.softwareheritage.org/ Software Heritage], projet ...': vous serez en immersion totale avec l'équipe qui construit l'archive de Software Heritage, et vous aurez la possibilité d'observer de près la construction
  3 KB (488 words) - 13:34, 26 September 2018
• Schema.org
  ...f the involved companies (e.g., GMail, Google Calendar) exploit Schema.org metadata to provide added value features (e.g., automatically interpreting reservati ...a.org ontology] has, at the time of writing, relatively little support for software-related entities, most notably:
  5 KB (522 words) - 15:07, 25 April 2017
• WG/Scientific API
  The data collected by Software Heritage is harvested from a diverse set of origins, This uniformity of access to all the contents turns the Software Heritage
  2 KB (331 words) - 13:46, 31 July 2016
• Google Summer of Code 2019
  This page is the central point of information for [[Software Heritage]] participation into the [https://summerofcode.withgoogle.com/ Goo ...Heritage. Each student works with mentors from the community to complete a software project.
  9 KB (1,314 words) - 07:29, 15 June 2021
• Improve the Code Scanner (GSoC task)
  The Software Heritage archive is the most comprehensive open data knowledge base about s ...ct which parts of it come from public code, including Free and Open Source Software.
  3 KB (403 words) - 16:30, 13 February 2022
• Glossary
  This glossary contains the definition of common terms used in the Software Heritage project. ...ect), are associated to a number of human-meaningful metadata, and release software products via Origins.
  2 KB (358 words) - 09:52, 5 April 2018
• Phabricator callsign naming convention
  Here is the ''callsign naming convention'' adopted by [[Software Heritage]]. ** A: non-software Annexes (e.g., raw data), including Git annexes
  3 KB (344 words) - 10:38, 14 February 2023
• Talks
  In this page we keep track of the past and upcoming talks about [[Software Heritage]], in various venues. |[http://seminairetransverse.wp.tem-tsp.eu/2017/10/11/software-heritage-la-bibliotheque-dalexandrie-du-code-source-roberto-di-cosmo/ Sémi
  12 KB (1,346 words) - 12:21, 1 December 2017
• Google Summer of Code 2020
  ...2020; this page is only kept as an archive. Thank you for your interest in Software Heritage, and you are welcome to apply for an [[internship]] instead. This page is the central point of information for [[Software Heritage]] participation into the [https://summerofcode.withgoogle.com/ Goo
  5 KB (762 words) - 07:30, 15 June 2021

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)