IdeaWell

Project ideas from Hacker News discussions.

Google has stopped pushing Git tags for some Android source code

Original Article

Hacker News Discussion

📝 Discussion Summary (Click to expand)

3 Predominant Themes

1. Google’s new source‑code request workflow is seen as slow and cumbersome

"Initially, Google would usually provide access to the tarballs within a couple hours. Lately, they're often taking weeks to get back to us." – HarlequinHair

2. The method raises questions about GPL compliance, especially the definition of a “medium customarily used for software interchange”

"If filling out the source code request form via Google Forms ... requires the requester to run non‑free ... JavaScript, then maybe it is in violation of section 6 of the GPLv2." – logological

3. Google is criticized for making source access needlessly difficult, harming projects like GrapheneOS and the broader open‑source ethos

"It means Google is making it harder than it needs to be to obtain source code. It's a dick move, and the only plausible interpretations are that it will get harder still." – Zigurd

🚀 Project Ideas

Generating project ideas…

AOSP Instant Mirror

Summary

  • Provides a no‑form, instant download mirror of all GPL‑covered AOSP releases.
  • Eliminates weeks‑long waits by delivering source tarballs via a public, wget‑able URL.

Details

Key Value
Target Audience Developers of custom ROMs, security‑focused OSes, and researchers needing GPL source quickly
Core Feature Automated mirroring pipeline that synchronizes official AOSP releases and serves them on a CDN with direct download links
Tech Stack Python/Scrapy backend, Cloudflare Workers for front‑end, PostgreSQL for metadata, Docker/Kubernetes for orchestration
Difficulty Medium
Monetization Hobby

Notes

  • HN commenters complained that “weeks to get back to us” and form‑based requests are a “dick move” – this solves that pain.
  • A public mirror is technically feasible and aligns with GPL’s “medium customarily used for software interchange”.

GPLRequestBot

Summary

  • Automates the entire Google source‑request workflow: submits forms, manages follow‑ups, and fetches Drive links without user intervention.
  • Removes manual bottlenecks for projects that must obtain GPL source code from Google.

Details

Key Value
Target Audience Maintainers of GPL‑licensed Android components (e.g., GrapheneOS, custom kernels) who need reliable source access
Core Feature API + CLI tool that authenticates to Google Forms, tracks request IDs, and pulls generated Drive URLs programmatically
Tech Stack Node.js for CLI, Google Drive API v3, SQLite for state storage, serverless Lambda functions for scaling
Difficulty High
Monetization Revenue-ready: Subscription $5/mo for hosted instance, $50/mo for enterprise tier

Notes

  • Users like “petcat” noted “They could just as easily require requests … through regular mail” – a bot bypasses this friction.
  • The service directly addresses the “very slow” and “form‑based” frustrations voiced in the thread.

GPLCompliance Tracker

Summary

  • Public dashboard that logs and visualizes GPL source release timelines for Android modules, flagging delays.
  • Turns hidden compliance delays into transparent data for the community.

Details

Key Value
Target Audience Developers, legal teams, and open‑source advocates monitoring GPL adherence by Google
Core Feature Aggregates public request timestamps, compares against GPL “reasonable time” expectations, and generates alerts
Tech Stack React front‑end, GraphQL API pulling from GitHub issue data and custom request logs, PostgreSQL backend, scheduled Python scrapers
Difficulty Low
Monetization Hobby

Notes

  • Commenters like “shevy-java” urged “Google needs to lose in court here” – tracking creates public pressure and evidence.
  • Provides actionable insight that can inform discussions, legal strategies, and community advocacy.

Read Later