Menu

Making a portfolio of open public-sector projects that keeps itself honest
📰

Making a portfolio of open public-sector projects that keeps itself honest

DEV Community: github·Emanuel Silva (Em)·about 2 hours ago
#e1Tec5CD
#devtogithub#technology#devto#dev#list
Reading 0:00
15s threshold

Emanuel Silva (Em)

I maintain ten open projects on data and AI for UK public services. The hard part isn't building them. It's keeping the list of them accurate: which exist, what state each is in, what licence it's under, and when it last changed.

This post covers the routines that now do that work, and the one rule they all follow: they propose, and a person merges.

  1. A daily discovery routine compares my public repositories with the launchpad's project list. For a new repository, it drafts a card from what the repository says about itself, labels anything it can't know, and puts the draft on a branch for review.
  2. The profile README rebuilds itself from that list once a change is merged.
  3. A GitHub Project board is refreshed daily from each repository's activity: last change by a person, latest release, open issues and pull requests.
  4. Each card's licence is checked against the licences the project states in its own publiccode.yml. That check caught two cards that were wrong.