ungoogled-software/ungoogled-chromium

Better coordination for Chromium updates

Open

#1,043 opened on May 22, 2020

View on GitHub
 (18 comments) (2 reactions) (0 assignees)Python (771 forks)batch import
enhancementhelp wantedmeta

Repository metrics

Stars
 (18,674 stars)
PR merge metrics
 (Avg merge 1d 11h) (9 merged PRs in 30d)

Description

There are several developers who provide updates to new Chromium, but we don't have a way of coordinating them.

I think a simple way to solve this is to create issues titled "Updating to Chromium x.x.x.x" requesting for someone to claim it (perhaps pinning the issue too). Additionally, this can serve as a thread to discuss issues or questions while updating.

Ideally, these issues should be auto-generated whenever a new stable version of Chromium releases (as shown on https://omahaproxy.appspot.com, for example). I'd like an automated way of creating these issues, preferably using a free service. Anyone have ideas?

Contributor guide

Research direction
Investigate how to automate the creation of GitHub issues for new Chromium stable releases using GitHub Actions or similar tools. Look into the omahaproxy.appspot.com API to fetch the latest version and trigger issue creation.
Tech stack
python
Domain
devopsbuild systemrelease
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitGitHub
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70