<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/314be2433b0a4232a44c35d01332499f&quot; frameborder=&quot;0&quot; width=&quot;1280&quot; height=&quot;960&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>960</height><width>1280</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>960</thumbnail_height><thumbnail_width>1280</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/314be2433b0a4232a44c35d01332499f-00001.gif</thumbnail_url><duration>1253.577</duration><title>GIT-SUM: A Solution for Readme Summarization 📝</title><description>Hi, my name is Tu and in this video, I will be presenting GIST-SUM, an approach to summarizing GitHub repositories. We all know that GitHub is the most popular platform for storing code, but for large projects, the readme file can be lengthy and time-consuming to read. That&apos;s why we need to summarize the repository. Our approach is based on text summarization techniques, specifically attractive summarization, which involves selecting important key phrases from the readme file to produce a summary without generating any new text. We used Transformers as our classification engine and fine-tuned it on our own dataset collected from GitHub. We compared our approach with ITAP and achieved better performance in all metrics. Our solution helps reduce time and effort for developers when exploring a new project for the first time. We plan to evaluate GIST-SUM with more data collected from GitHub in the future.</description></oembed>