Skip to content

Commit 38e4d96

Browse files
kateribkaterib
committed
Update README
1 parent 6162a2e commit 38e4d96

File tree

1 file changed

+139
-0
lines changed

1 file changed

+139
-0
lines changed

‎README.md‎

Lines changed: 139 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,139 @@
1+
2+
3+
# Congressional Hackathon 7.0
4+
5+
## Coding Breakout Group
6+
7+
The coding breakout session will take place in the United States Capitol Visitor Center room CVC 217. See **[Event Details](#event-details)** below for more information.
8+
9+
Happy hacking! 🏛️💻
10+
11+
## Before You Begin
12+
13+
1. **Sign the required forms**: All participants must sign the **[Participation Agreement and IP Disclaimer](https://forms.cloud.microsoft/g/S1ZZEiN25V)** before contributing any code.
14+
15+
1. **Fork this repository**: Fork this repository into your own GitHub account to work on coding. When you're ready to merge changes back into this repository, create a pull request. Instructions for forking a repository and creating pull requests can be found here: [Fork a repository](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/fork-a-repo).
16+
17+
1. Check out **[Legislative Branch Data Map](Legislative-Branch-Data-Map.md)** for a list of resources to get you started!
18+
19+
## Contributing
20+
21+
This repository is publicly readable, so anyone can read and clone it. **Be mindful of sensitive information** - never commit API keys, passwords, or other secrets to the repository. A basic `.gitignore` has been provided, but more templates are linked in the **[Resources](#resources)** section below.
22+
23+
1. Clone this repository:
24+
25+
```bash
26+
git clone https://github.com/LibraryOfCongress/Congressional-Hackathon-2025.git
27+
cd Congressional-Hackathon-2025
28+
```
29+
30+
1. Each team in the coding breakout will be given their own branch to push code to. Pull your team's branch:
31+
32+
```bash
33+
git pull <team-1-branch-name>
34+
```
35+
36+
1. Work in your team's branch. Write clear, well-documented code and try to include a README file for your specific project.
37+
38+
1. To push code, commit it (with a commit message!) and push it to your branch!
39+
40+
```bash
41+
git commit -am "My awesome commit"
42+
git push origin <team-1-branch-name>
43+
```
44+
45+
### Importing Work from Another Repository
46+
47+
If you would like to bring work from another repository into this one, follow the steps below:
48+
49+
```bash
50+
# 1) Be in this hackathon repo
51+
cd /path/to/Congressional-Hackathon-2025
52+
53+
# 2) (optional) Create/switch to a branch for clarity
54+
git switch -c imported-work-branch
55+
56+
# 3) Add the other repo as a new remote
57+
git remote add other-repo git@github.com:<org-or-user>/other-repo.git
58+
# or: git remote add other-repo https://github.com/<org-or-user>/other-repo.git
59+
60+
# 4) Fetch the other repository's branches
61+
git fetch other-repo
62+
63+
# 5) Merge or cherry-pick the work you want
64+
git merge other-repo/main
65+
# or cherry-pick specific commits:
66+
# git cherry-pick <commit-hash>
67+
68+
# 6) Push your branch with the imported work
69+
git push -u origin imported-work-branch
70+
```
71+
72+
## Event Details
73+
74+
**Location:** United States Capitol Visitor Center, Room CVC 217
75+
76+
**Date:** Wednesday, September 17, 2025
77+
78+
**Time:** 9:00am – 5:00pm ET
79+
80+
**Registration link:** https://forms.cloud.microsoft/g/S1ZZEiN25V
81+
82+
**Things to bring/prepare in advance:**
83+
84+
* A laptop and charger (wi-fi will be provided)
85+
86+
* Create a GitHub account (free)
87+
88+
* API keys for public APIs (see a list below)
89+
90+
* Your preferred AI coding assistant
91+
92+
### Agenda
93+
94+
| Time | Activity |
95+
|---|---|
96+
| 9:00 AM | Introduction, overview and brief level-setting and affinity mapping exercise to identify key areas of interest among the coding participants. (CVC 217) |
97+
| 9:15 AM | Break into small groups based on areas of interest and start hacking! |
98+
| 12:00 Noon | Lunch! |
99+
| 1:00 PM | Opening Remarks (CVC Auditorium) |
100+
| 1:30 PM | Lightning Round Presentations (CVC Auditorium) |
101+
| 3:00 PM | Breakout Groups |
102+
| 4:00 PM | Prepare coding breakout presentations|
103+
| 4:30 PM | Breakout Group Presentations (CVC Auditorium)|
104+
| 5:00 PM | CVC 217 closes - head to Hackathon Reception (HVC 201) |
105+
106+
## Breakout Topics
107+
108+
Coding breakout groups will choose a topic of particular interest to them and explore ways they can use their talents to address the issue. The following problem statement illustrates an example of the kind of problem a group might choose to take on.
109+
110+
### Sample Problem Statement
111+
112+
Both Congressional staff and the public would benefit from rapid access to Congressional hearing transcripts. The official transcripts are produced very meticulously before publication to ensure complete accuracy for the public record, but unfortunately this attention to detail requires a great deal of time. Now that we have access to Large Language Models (LLMs) and high-quality automated transcription, is it possible to automatically generate a transcript within minutes of the end of a hearing, rather than weeks or months?
113+
114+
##### Participants could investigate the following:
115+
116+
* Determine how & where to source audio and/or transcripts from House & Senate committee meetings;
117+
* Investigating effective methods of diarization (distinguishing between speakers) and speaker identification (putting names to each voice);
118+
* Generate succinct, useful and accurate summaries for the events;
119+
* Create an interface or way of presenting the transcripts and summaries to their intended audience (Congressional staff, the public, etc.)
120+
121+
A JSON-formatted list of all Committee YouTube Channels can be found in this repo here: [Committee-Youtube-Channels.json](https://github.com/LibraryOfCongress/Congressional-Hackathon-2025/blob/main/Committee-Youtube-Channels.json).
122+
123+
##### What some other countries are doing:
124+
* [Digitalization of the Hansard, beyond automatic transcriptions](https://events.bussola-tech.co/modernisation-of-hansard)
125+
* [Artificial Intelligence in Parliaments - Implementation of Speech to Text Technologies in Hansard](https://events.bussola-tech.co/modernizing-hansard-with-ai)
126+
* [Multilingual parliaments powered by AI](https://library.bussola-tech.co/p/multilingual-parliaments-powered)
127+
128+
### Code of Conduct
129+
130+
Everyone who participates in the Coding Breakout group must sign the Participation Agreement and IP Disclaimer and abide by our Code of Conduct during the event to help create a welcoming, respectful, and friendly event based on mutual respect, trust, and goodwill:
131+
132+
* Be Respectful - treat others with respect in what you say and do. Be open to giving and receiving feedback kindly. Avoid language that differentiates anyone based on their background or identity. Be considerate of the needs and boundaries of others.
133+
134+
* Be Mindful – remember that we are privileged to be coming together in the Capitol to work on issues that matter to the public and our nation. Keep the focus on the institutions and traditions that unite us, and keep the environment open and courteous by refraining from politics and other controversial topics.
135+
136+
* Be Welcoming - be supportive, encouraging, and open to learning from the expertise and perspectives of others. Assume that everyone brings valuable lived experiences and good intentions to the event.
137+
138+
* Be Helpful – the goal of the Hackathon is to bring people together to see how we can all work together to build civic technologies that serve Congress and the public. You don’t have to be an expert on everything to participate; listening, sharing resources, and offering your perspective all count. Every contribution matters.
139+
 

0 commit comments

Comments
 (0)