diff --git a/projects/one-logging-bridge-per-language.md b/projects/one-logging-bridge-per-language.md
new file mode 100644
index 000000000..9979867aa
--- /dev/null
+++ b/projects/one-logging-bridge-per-language.md
@@ -0,0 +1,42 @@
+### Description
+
+During the joint TC/GC call on Jan 11, we agreed on a few items we'd like to accomplish this year. One such item was creating at least one logging bridge per Language SIG, so that our end-users can start using OTLP Logging natively on their applications.
+
+We'll strive to get at least one logging bridge for each supported language. Language SIGs will be free to decide which bridge to implement based on the needs of their audiences.
+
+### Project Board
+
+To be created.
+
+### Deliverables
+
+For each one of the following languages, there should be at least one logging bridge available, either as part of their core repository or as part of their contrib repository. Usage of such bridge should be documented on opentelemetry.io's website.
+
+Languages (100% of the languages available when this issue was created):
+
+- [ ] One Logging Bridge per language - C++
+- [ ] One Logging Bridge per language - .NET
+- [ ] One Logging Bridge per language - Erlang
+- [ ] One Logging Bridge per language - Go
+- [ ] One Logging Bridge per language - Java
+- [ ] One Logging Bridge per language - JavaScript
+- [ ] One Logging Bridge per language - PHP
+- [ ] One Logging Bridge per language - Python
+- [ ] One Logging Bridge per language - Ruby
+- [ ] One Logging Bridge per language - Rust
+
+### Staffing / Help Wanted
+
+We anticipate that Language SIG maintainers will share the vision that having at least one bridge, hopefully for the most used logging API for the language, is important for the SIG, and therefore, we don't anticipate new staffing requirements. However, we'll try to recruit new contributors to work on this once we have a few examples to follow.
+
+#### Required staffing
+
+@jpkrohling is the sponsor for this project and will work with the individual Language SIGs to implement this.
+
+### Meeting Times
+
+We'll use the regular Language SIGs meetings, as well as the maintainer's meeting on Monday.
+
+### Timeline
+
+We aim to complete this project by the end of 2024.
\ No newline at end of file