Skip to content

Commit 2d27bc4

Browse files
committed
add basic content from proposal
1 parent b0ba398 commit 2d27bc4

11 files changed

Lines changed: 180 additions & 26 deletions

File tree

site/_config.yml

Lines changed: 10 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -18,14 +18,19 @@
1818
# You can create any custom variable you would like, and they will be accessible
1919
# in the templates via {{ site.myvariable }}.
2020

21-
title: Your awesome title
21+
title: ODAI-LIB Challenge 2026
22+
subtitle: 'FSE/AIWare On-Demand Library Generation, Sun 5 - Thu 9 July 2026 Montreal, Canada'
2223
email: your-email@example.com
2324
description: >- # this means to ignore newlines until "baseurl:"
2425
Write an awesome description for your new site here. You can edit this
2526
line in _config.yml. It will appear in your document head meta (for
2627
Google search results) and in your feed.xml site description.
2728
twitter_username: jekyllrb
28-
github_username: jekyll
29+
github_username: odai-lib
30+
31+
nav-links:
32+
- title: FSE 2026
33+
url: https://conf.researchr.org/home/fse-2026
2934

3035
# Build settings
3136
theme: minima
@@ -54,3 +59,6 @@ url: "" # the base hostname & protocol for your site, e.g. http://example.com
5459
# - vendor/cache/
5560
# - vendor/gems/
5661
# - vendor/ruby/
62+
63+
sass:
64+
quiet_deps: true

site/_includes/header.html

Lines changed: 38 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,38 @@
1+
<!--Copied from Minima-2.5.2-->
2+
3+
<header class="site-header" role="banner">
4+
5+
<div class="wrapper">
6+
{%- assign default_paths = site.pages | map: "path" -%}
7+
{%- assign page_paths = site.header_pages | default: default_paths -%}
8+
<a class="site-title" rel="author" href="{{ "/" | relative_url }}">{{ site.title | escape }}</a>
9+
{%- if site.subtitle -%}
10+
<br><span class="site-subtitle">{{ site.subtitle | escape }}</span>
11+
{%- endif -%}
12+
13+
{%- if page_paths -%}
14+
<nav class="site-nav">
15+
<input type="checkbox" id="nav-trigger" class="nav-trigger" />
16+
<label for="nav-trigger">
17+
<span class="menu-icon">
18+
<svg viewBox="0 0 18 15" width="18px" height="15px">
19+
<path d="M18,1.484c0,0.82-0.665,1.484-1.484,1.484H1.484C0.665,2.969,0,2.304,0,1.484l0,0C0,0.665,0.665,0,1.484,0 h15.032C17.335,0,18,0.665,18,1.484L18,1.484z M18,7.516C18,8.335,17.335,9,16.516,9H1.484C0.665,9,0,8.335,0,7.516l0,0 c0-0.82,0.665-1.484,1.484-1.484h15.032C17.335,6.031,18,6.696,18,7.516L18,7.516z M18,13.516C18,14.335,17.335,15,16.516,15H1.484 C0.665,15,0,14.335,0,13.516l0,0c0-0.82,0.665-1.483,1.484-1.483h15.032C17.335,12.031,18,12.695,18,13.516L18,13.516z"/>
20+
</svg>
21+
</span>
22+
</label>
23+
24+
<div class="trigger">
25+
{%- for path in page_paths -%}
26+
{%- assign my_page = site.pages | where: "path", path | first -%}
27+
{%- if my_page.title -%}
28+
<a class="page-link" href="{{ my_page.url | relative_url }}">{{ my_page.title | escape }}</a>
29+
{%- endif -%}
30+
{%- endfor -%}
31+
{%- for link in site.nav-links -%}
32+
<a class="page-link" href="{{ link.url | relative_url }}">{{ link.title | escape }}</a>
33+
{%- endfor -%}
34+
</div>
35+
</nav>
36+
{%- endif -%}
37+
</div>
38+
</header>

site/_layouts/home.html

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
---
2+
layout: default
3+
---
4+
5+
{{ content }}

site/about.markdown

Lines changed: 0 additions & 18 deletions
This file was deleted.

site/assets/images/logo.png

456 KB
Loading

site/assets/main.scss

Lines changed: 30 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,30 @@
1+
---
2+
# Only the main Sass file needs front matter (the dashes are enough)
3+
---
4+
5+
@import "minima";
6+
7+
.site-subtitle {
8+
display:inline-block;
9+
font-size: 15px;
10+
color: $grey-color;
11+
}
12+
13+
.site-nav {
14+
float: none;
15+
line-height: 30px
16+
}
17+
18+
.site-nav .page-link{
19+
color: $grey-color;
20+
font-size: 13px;
21+
}
22+
23+
.page-content img {
24+
display: block;
25+
margin: auto;
26+
}
27+
28+
.page-content{
29+
font-size: 15px;
30+
}

site/call.md

Lines changed: 69 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,69 @@
1+
---
2+
layout: page
3+
title: Call for Participation
4+
---
5+
6+
## Important Dates
7+
8+
| Date | Event |
9+
|-|-|
10+
| January 1st, 2026 – February 27th, 2026 | Rolling Abstract Period |
11+
| March 21st, 2026 | Full Paper Deadline |
12+
| March 27th, 2026 | Full Paper Notification |
13+
| April 2nd, 2026 | Camera-ready |
14+
| July 6th, 2026 | On-site Competition Event at FSE/AIWare 2026 |
15+
16+
## Background and Motivation
17+
18+
It is now common for developers to adopt libraries that aid their software development. Libraries provide pre‑tested, high‑quality functionality that can be easily integrated. Evidence of this trend is reflected in the vast number of libraries available on GitHub. For example, Python developers often import libraries such as NumPy for statistical computations and ggplot for visualizations.
19+
20+
These libraries frequently depend on other libraries, creating a complex web of interdependencies—a hallmark of the software ecosystem. The primary problems associated with libraries are bugs and, more importantly, security vulnerabilities. Studies have shown that outdated libraries pose significant risks to attackers, giving rise to initiatives such as the Global Software Supply Chain (GSSC) to protect libraries from supply‑chain attacks.
21+
22+
With the rise of generative AI in the developer workflow, tools like ChatGPT, Gemini and others are increasingly used to assist with daily tasks. However, using pre‑trained models presents challenges related to contextual understanding. Even agentic models often produce numerous errors during generation, potentially incurring significant time and monetary costs for developers.
23+
24+
Bringing together the Mining Software Repositories, Program Comprehension, and AIware software engineering communities, we invite students and researchers to put their knowledge of new GenAI techniques to generate software libraries.
25+
26+
## Competition Format
27+
28+
### Task
29+
30+
The competition challenges participants to design and present different GenAI techniques capable of generating software libraries. The goal is to evaluate how current AI models and workflows perform when asked to reproduce or adapt the behavior, structure, or interface of an existing library. Participants are asked to complete the following task:
31+
32+
> *Generate a library software repository that is functionality similar or better to the human-written repository. Demonstrate that this approach can be used for different programming languages.*
33+
34+
Note that the measurement of functionality or better can be proposed by the competitors. During the competition, participants must reproduce the results as a demonstration.
35+
36+
### Dataset
37+
38+
We will provide a listing of all package libraries from seven ecosystems (Crates, Go, Maven, NPM, PHP, PyPI, RubyGems). Participants are also encouraged to bring their own domain-specific data. Participants may extend or refine the evaluation, but the official scripts will be used during final judging.
39+
40+
| Ecosystem | Packages | Source |
41+
|-|-|-|
42+
| Crates | 207,981 | https://crates.io |
43+
| Go | 2,214,193 | https://index.golang.org |
44+
| Maven | 657,929 | https://zenodo.org/records/7553341 |
45+
| NPM | 3,706,503 | https://zenodo.org/records/7553341 |
46+
| PHP | 431,456 | https://packagist.org |
47+
| PyPI | 705,908 | https://pypi.org/simple |
48+
| RubyGems | 188,204 | https://rubygems.org/names |
49+
| **Total** | 8,112,179 | -- |
50+
51+
### Tools and Techniques
52+
53+
Participants may use any GenAI or strategies they prefer—fine-tuning, prompting strategies, program synthesis, RAG pipelines, multi-agent architectures, or any hybrid approach. The competition encourages creativity and experimentation.
54+
55+
Participants will develop demos for and end-to-end generation, testing, and maintenance of these AI-generated libraries, and to quantitatively compare their performance and quality against human-written counterparts.
56+
57+
### Submission Requirements
58+
59+
Each team must submit a short abstract and a mandatory video (up to 5 minutes) demonstrating their technique. The video should show the key techniques used and the end-to-end generation. Optional links to repositories or demos are welcome.
60+
61+
### On site event
62+
63+
The competition will be held as a half-day event at FSE/AIWare 2026. Accepted teams will first present their approach through posters and open demo sessions, allowing attendees to interact with the tools and ask questions about the method. After the presentations, organizers will randomly select a set of libraries from the dataset. Teams will then attempt to apply their technique to these unseen targets. This live generation challenge is designed to test the robustness and generality of the proposed workflows.
64+
65+
Teams are encouraged to use their own resources (local or cloud), but for inclusiveness, we are open to providing cloud-computing resources for under-represented groups. We may also consider online participation for under-represented groups.
66+
67+
### Judging and Awards
68+
69+
Judges from the program committee will evaluate submissions based on novelty, feasibility of execution, similarity to human-written library and presentation. The assessment will consider both the submitted materials and the on-site performance. A combination of committee judgement and on-site voting may be used to recognise excellence. The best contributions will receive a certificate from the competition chairs.

site/index.markdown

Lines changed: 0 additions & 6 deletions
This file was deleted.

site/index.md

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
---
2+
# Feel free to add content and custom Front Matter to this file.
3+
# To modify the layout, see https://jekyllrb.com/docs/themes/#overriding-theme-defaults
4+
5+
layout: home
6+
---
7+
{% assign call_page = site.pages | where:"title", "Call for Participation" | first %}
8+
9+
<img src="{{ '/assets/images/logo.png' | relative_url }}" alt="ODAI-LIB Logo" style="max-width: 300px;">
10+
11+
This competition aims to address challenges arising from software ecosystem dependencies by introducing a novel approach: On-Demand Library Generation (ODAI-LIB). Instead of relying on vast, complex, and potentially vulnerable external repositories, contestants will focus on dynamically generating small, context-specific, and high-quality libraries precisely when they are needed within a project. The participants will leverage prior experience in software ecosystems and have already compiled an initial dataset of software libraries and performed preliminary comparative analyses of human-generated versus AI-generated code.
12+
13+
{{ call_page.content }}

site/organising-committee.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
---
2+
layout: page
3+
title: Organising Committee
4+
---
5+
6+
- Raula Gaikovina Kula (The University of Osaka, Japan)
7+
- Olivier Nourry (The University of Osaka, Japan)
8+
- Brittany Reid (Nara Institute of Science and Technology, Japan)
9+
- David Moreno-Lumbreras (Universidad Rey Juan Carlos, Spain)

0 commit comments

Comments
 (0)