spdx / spdx/LicenseListPublisher
Timestamp updates for unchanged data complicates usage, especially caching
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 23
- Forks
- 29
- Avg merge
- 6h 31m
- Merged PRs (30d)
- 2
Description
The publisher updates timestamps of data files even if no other information has changed.
See this PR for an example:
https://github.com/spdx/license-list-data/commits/6552b858c0f9224be9ed38ad8e941f662a4496ab/json/licenses.json
This creates needless churn in downstream systems that cache this information. It would be more useful to have a modification timestamp.
cc: @danielmachlab
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the json/licenses.json history at commit 6552b858c0f9224be9ed38ad8e941f662a4496ab and tracing how the publisher assigns timestamps. Determine how an unchanged data file should retain its timestamp while exposing a modification timestamp, then verify that repeated generation does not create needless downstream churn.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100