Practical AI
Practical AI

The ins and outs of open source for AI

Daniel and Chris get you Fully-Connected with open source software for artificial intelligence. In addition to defining what open source is, they discuss where to find open source tools and data, and how you can contribute back to the open source AI community. Sponsors: * Linode – Our cloud of choic

Featured Speakers

Daniel Whitenack GuestChris Benson Guest

Topics Discussed

Episode Summary

Executive Summary: Chris Benson and Daniel Whitenack explore how open-source software, data, and models underpin modern AI. They clarify licensing considerations, discuss how to discover trustworthy tools and datasets, and recommend isolated environments such as Docker or Colab for experimentation. They also encourage practical contributions—code, documentation, examples, data, and respectful collaboration—to strengthen a broader AI community.

Main Topics: Open source foundations and licensing: The hosts explain that open source generally makes source code available under a license, and that license terms differ in how they allow reuse, modification, and commercial distribution. They discuss permissive licenses such as Apache 2.0 and MIT, as well as open-core business models and the need to check organizational policies. Data and model licensing in AI: AI workflows depend on both code and data, including trained models, which are themselves stored as data. Dataset and model use can carry specific restrictions, such as Mozilla Common Voice's condition against attempting to identify speakers; the hosts note that model-download licensing can be unclear when detached from a repository. Finding AI tools, data, and expertise: The hosts recommend starting with trusted documentation and established ecosystems such as TensorFlow, PyTorch, NVIDIA tools, spaCy, pandas, and scikit-learn. They also mention Papers with Code for papers, implementations, and task leaderboards; Google Dataset Search for datasets; and Semantic Scholar for research. Reproducible experimentation and environment management: Dependency conflicts can make local experimentation difficult. Chris recommends Docker containers to reproduce tutorial environments or match deployment constraints, while Daniel favors Google Colab for quickly testing multiple approaches without disrupting a local setup. Both value Colab's ease of use. Ways to contribute to open-source AI: Useful contributions include code, documentation, examples, data discovery, and write-ups that explain real workflows. Contributors should communicate respectfully with maintainers, ask what help is needed, and use issues and pull requests constructively—even small documentation fixes can be valuable. Building a broader AI community: The hosts argue that AI needs a shared community culture that spans individual frameworks and datasets, similar to the established norms of open-source software. Model hubs and projects such as Hugging Face illustrate how contributors beyond a core team can accelerate development.

Key Arguments: Open-source AI is not just about code: datasets and trained models are essential parts of the workflow and may have their own licensing and responsible-use conditions. A repository's software license may not clearly settle the terms for a separately hosted model or dataset, so users should inspect the relevant terms and seek clarification where needed. Starting from reputable documentation, established tools, research indexes, and dataset search services can help newcomers build domain knowledge and choose suitable components. Isolated environments reduce dependency conflicts: Docker is useful for controlled learning or deployment-aligned setups, while Colab enables quick, low-friction comparisons. Open-source participation is accessible beyond core coding: documentation, examples, data resources, and practical blog posts can materially improve usability. Respectful, solution-oriented engagement helps maintainers; contributors should offer changes or ask how to help rather than simply demand features. The AI field would benefit from a stronger cross-project community culture, supported by shared hubs and contributions from people beyond project teams.

Data Points: Example model size: 300 million parameters - Daniel uses this as an example of a model large enough that its parameters are stored in a data file. Podcast episode referenced: Episode 322 - The hosts recommend a Changelog episode about Dgraph's licensing and relicensing discussion. Hugging Face team members cited: 25 - A tweet by Clem describes the project's core team size at the time. Open-source contributors cited: 400 - The same tweet credits contributors alongside the Hugging Face team with rapid machine-learning technology development.

Pivotal Quotes: "Data really drives how code operates in the world of AI." — Daniel Whitenack: He distinguishes AI workflows from conventional software workflows and emphasizes the importance of data distribution and use. "If you don't feel that code is where you should make your contribution, then going and figuring out how to use the tool or offering up your insights from using the tool into documentation or create examples." — Chris Benson: He broadens the idea of contribution beyond writing core software. "I think that we're not there yet with AI." — Chris Benson: He argues that AI still needs a general, cross-project open-source community culture comparable to the software community.

Implications: AI practitioners should evaluate licenses for code, data, and models separately; use reproducible environments; and contribute practical improvements, not just code. Stronger shared norms and hubs can make AI tools easier to discover, reuse, and improve.

🔓 Sign Up for Unlimited Episode Search

About Practical AI

View all episodes from Practical AI