Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Get rid of modules.json and use the artifact from the source-bugzilla-info task instead

Open
#180 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
python

Research direction

Start by finding where modules.json is consumed and inspect the source-bugzilla-info task artifact mentioned in the issue. Compare that source with the proposed moz.build-based generation approach, then define how the old file and its update process should be replaced. Done means the project uses the maintained artifact instead of the stale modules.json.

Written by the indexing model from the issue text.

Description

The current modules.json file is 4 years old. It needs to be updated. I couldn't figure out how it was generated in the first place, so it's unclear how to update it. Further, this module should be updated on a regular basis.

How was modules.json generated?

Is there a better source for this information? Could it or something like it be generated from moz.build files in mozilla-central and parked somewhere?

Dominant language
Python
Stars
12
Forks
19
Avg merge
1d 17h
Merged PRs (30d)
1

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mozilla/libmozdata

All issues in mozilla/libmozdata

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.