WWW: Republish selected blog posts

[mjherzog]

We should republish selected blog posts from the current aboutcode.org website. For each post we will want to review the content and update it since most are from 2023 or earlier.

Some candidates are:

• P1 https://aboutcode.org/2023/purl-universal-software-package-identification/
• P1https://aboutcode.org/2023/non-vulnerable-dependency-resolution/
• P1 https://aboutcode.org/2023/curated-licenses-public-database-scancode-licensedb/
• https://aboutcode.org/2023/what-is-a-dual-license-anyway/
• https://aboutcode.org/2022/software-versioning/
• https://aboutcode.org/2022/scancode-license-clarity-scoring/
• https://aboutcode.org/2023/update-copyright-each-new-year/
• PI https://aboutcode.org/2021/copyleft_licensed_software_java_app/
• https://aboutcode.org/2020/snippet-matching-for-software-provenance-analysis/
• https://aboutcode.org/2016/software-dependencies-guide/
• https://aboutcode.org/2013/datatables-and-healthcare-gov-oss-attribution-case-study/ - keep as-is for historical context as our first blog post?

This list represents about half of the historical posts. If we do not modify the content I suppose that we can/should (?) keep the original publication date.
I did not include any posts related to Open Source Stack Exchange.

[johnmhoran]

I've checked ^ two posts I just finished reconstructing and a third I'm starting, all in a local, not-yet-pushed branch. I'm also updating tags.yml and adding tags to posts where appropriate. [and a few more . . . .]

[mjherzog]

@johnmhoran The migrated posts look very good. I did not check all URLs but the ones I checked looked good.
The one change needed is to update https://aboutcode-org.github.io/www.aboutcode.org/blog/scancode-licensedb to make it a current post with:

• updated screenshot showing the current license count
• update statistics in the text to match
• possible other changes
  @DennisClark Please provide a new screenshot and any other changes to the text that make sense as a 2026 post instead of 2023

[johnmhoran]

Thanks @mjherzog . BTW, I have checked every URL in each republished post before pushing and have updated or removed as needed.

[johnmhoran]

@mjherzog Re updating the LicenseDB post to be current, what date shall I assign to it? The other post that needs that adjustment is @TG1999 's from a few days ago so I'll use the actual date.

(If no date is defined, e.g., name the file 2026-01-24-a-new-post.md, it seems Docusaurus assigns the current date (UTC?) to each undated post each time there's a new deployment.)

[mjherzog]

Original date for Tushar's post seems good. For LicenseDB we should use the current date after Dennis helps you update the content to be current.

[johnmhoran]

OK -- thanks.