DebConf is an annual developers’ conference organized by the Debian Project. Although it has a long history, it has never been held in Japan. Is that because Debian GNU/Linux is unpopular here? Not necessarily. There were times when the prospect of gathering several hundred Debian developers looked attractive to Japanese companies, and Japan did explore bidding for DebConf more than once. Yet, as far as I know, every plan stalled at the conceptual stage. The fundamental problem is that meeting DebConf’s hosting requirements in Japan is exceptionally difficult.

DebConf itself spans roughly two weeks, bringing Debian Project members together from around the globe. What used to be a single-week DebConf now includes a preceding week-long “DebCamp.” Unlike a typical tech conference, DebConf is a hackers’ event that assumes an extended stay and intensive collaborative development.

Because of that character, the host must provide not only large lecture halls but also small talk rooms and 24-hour hack spaces, each with abundant power outlets and robust network connectivity. In addition, the organizers must support attendees—who pay their own travel expenses—with meals and accommodation for up to two weeks. While money can in principle secure a venue that meets those conditions, factors such as securing the site for such a long period, facility security restrictions, and a wide gap between costs and budget have led to the conclusion that hosting DebConf in Japan is exceedingly difficult.

Still, it would be premature to say there is no hope. Companies or municipal training centers might be willing to rent their facilities at low cost, and with Japan no longer as expensive as it once was, the idea may warrant another look. Regional universities may present an even better option—ideally those strong in computer science and equipped with dormitories, which are often vacant during the summer break that coincides with DebConf’s usual schedule. To give two concrete examples, the Japan Advanced Institute of Science and Technology (JAIST) and the Nara Institute of Science and Technology (NAIST) would be ideal—though, given the pressures on universities today, the hurdles remain high even if a few adventurous professors are willing.

I was prompted to revisit this topic after overhearing rumors that some people are once again exploring a Japanese DebConf bid. The notion of gathering hundreds of Debian developers—free-spirited, almost hippie-like hackers—in Japan strikes me as simply fascinating. Even in an era when Big Tech chases enormous profits, many domestic systems rest on Debian’s achievements, and exposing more Japanese people to the lives of those who underpin their infrastructure would be meaningful.

Personally, I find this seemingly reckless plan—or daydream—very appealing, and I sincerely hope DebConf will come to Japan within the next few years.

original story: https://shujisado.com/2025/06/23/debconf_in_japan/

Tracing Creative Commons Licenses Across AI: Training Data, Models, Outputs

Copyright issues in AI model training and generated outputs are widely discussed, but less attention is paid to how copyright licenses, the actual mechanism for granting permission, shape these workflows. Unlike traditional software, which is often described as a one-to-one relationship between source code and executable code, AI involves three interlocking layers: input data, the…

The Hidden Risks of NVIDIA’s Open Model License

Recently, regarding the open-weights AI model “Nemotron 3” released by NVIDIA, there are scattered media reports mistakenly describing it as open source. Because there is concern that these reports encourage ignoring the usage risks of the NVIDIA Open Model License Agreement (version dated October 24, 2025; hereinafter referred to as the NVIDIA License), which is…

The Current State of the Theory that GPL Propagates to AI Models Trained on GPL Code

When GitHub Copilot was launched in 2021, the fact that its training data included a vast amount of Open Source code publicly available on GitHub attracted significant attention, sparking lively debates regarding licensing. While there were issues concerning conditions such as attribution required by most licenses, there was a particularly high volume of discourse suggesting…

The Legal Hack: Why U.S. Law Sees Open Source as “Permission,” Not a Contract

In Japan, the common view is to treat an Open Source license as a license agreement, or a contract. This is also the case in the EU. However, in the United States—the origin point for almost every aspect of Open Source—an Open Source license has long been considered not a contract, but a “unilateral permission”…

Evaluating OpenMDW: A Revolution for Open AI, or a License to Openwash?

Although the number of AI models distributed under Open Source licenses is increasing, it can be said that AI systems in which all related components, including training data, are open are still in a developmental stage, even as a few promising systems have emerged. In this context, this past May, the Linux Foundation, in collaboration…

A Curious Phenomenon with Gemma Model Outputs and License Propagation

While examining the licensing details of Google’s Gemma model, I noticed a potentially puzzling phenomenon: you can freely assign a license to the model’s outputs, yet depending on how those outputs are used, the original Terms of Use might suddenly propagate to the resulting work. Outputs vs. Model Derivatives The Gemma Terms of Use distinguish…

Should ‘Open Source AI’ Mean Exposing All Training Data?

DeepSeek has had a major global impact. This appears to stem not only from the emergence of a new force in China that threatens the dominance of major U.S. AI vendors, but also from the fact that the AI model itself is being distributed under the MIT License, which is an Open Source license. Nevertheless,…

Significant Risks in Using AI Models Governed by the Llama License

Although it has already been explained that the Llama model and the Llama License (Llama Community License Agreement) do not, in any sense, qualify as Open Source, it bears noting that the Llama License contains several additional issues. While not directly relevant to whether it meets Open Source criteria, these provisions may nonetheless cause the…