License stewards permalink

[ajolo2ky]

Description

Hi team,

We just realized the stewards' slug is under /blog, whereas it should be under /licenses:
https://opensource.org/blog/steward/apache-software-foundation -> https://opensource.org/licenses/steward/apache-software-foundation

Steps to reproduce

No response

What you expected to happen

https://opensource.org/blog/steward/apache-software-foundation -> https://opensource.org/licenses/steward/apache-software-foundation

And let's keep the redirect from the older one to the new format, because they've been indexed by search engines already.

What actually happened

No response

[melindahelt]

Posting here as well as in Nick's email for discussion:

A few clarification questions:

• Are we correct in assuming that you'd like the steward slug for licenses to go from being a sub-category under blog to instead be a sub-category under the CPT of licenses?

• And then after that, you'd like for https://opensource.org/blog/steward/* to then redirect to https://opensource.org/licenses/steward/*

Currently, we noticed that https://opensource.org/licenses/steward/apache-software-foundation redirects to https://open-source-initiative-development.mystagingwebsite.com/press-mentions/apache-software-foundation-announces-keynote-speakers-for-community-over-code-north-america-flagship-event-for-asf-covers-breadth-of-topics-impacting-the-open-source-community-including-big-data-fint

When we implement the new redirects above, what is the expected behavior for the press post above?

[kathrynwp]

Noting some clarifications that came in via email:

Q. Are we correct in assuming that you'd like the steward slug for licenses to go from being a sub-category under blog to instead be a sub-category under the CPT of licenses?

A. Yes, these "steward" pages are totally unrelated to our blogs. A license steward is an organization responsible for the license. Although not exactly a licenses CPT, it feels this is the best path. I'm adding Stefano Maffulli who can confirm.

---

Q. And then after that, you'd like for https://opensource.org/blog/steward/* to then redirect to https://opensource.org/licenses/steward/*

A. Yes. These are high traffic links and we don't want to break them.

---

Q. Currently, we noticed that https://opensource.org/licenses/steward/apache-software-foundation redirects to https://open-source-initiative-development.mystagingwebsite.com/press-mentions/apache-software-foundation-announces-keynote-speakers-for-community-over-code-north-america-flagship-event-for-asf-covers-breadth-of-topics-impacting-the-open-source-community-including-big-data-fint

When we implement the new redirects above, what is the expected behavior for the press post above?

A. None of these steward links should redirect to a press or blog post. They should also live under licenses.

---

Additional information provided:

None of the custom CPTs should have have /blog in their URL. This issue was fixed in the past and reappeared recently. We need a solution that lasts for all the CPTs we have.

The steward can either be listed at the root, like opensource.org/steward/mit or in the path of /license/ as in opensource.org/license/steward/mit. Either way works, whatever is simple.

Press mentions is a separate CPT, it should have its own URL structure.

Hope this clarifies things. Can you please review all the CPTs and make sure they all have their own archive url, separate from /blog/

[smaffulli]

I think all the custom taxonomies have the same issue. I was curious and looked at the code

• https://opensource.org/blog/status/board-member
• https://opensource.org/blog/seat-type/individual
• https://opensource.org/blog/steward/apple
• https://opensource.org/blog/publication/recreate-coalition

these are all wrong. All these taxonomies should drop the /blog part.

Ideally, it'd be better to assign each custom taxonomy to their respective CPT:

• https://opensource.org/blog/status/board-member -> https://opensource.org/board-member/status/*
• https://opensource.org/blog/seat-type/individual -> https://opensource.org/board-member/seat-type/*
• https://opensource.org/blog/steward/apple -> - https://opensource.org/license/steward/*
• https://opensource.org/blog/publication/recreate-coalition -> https://opensource.org/press-mention/publication/*

If that's too hard to maintain, it's ok to simply remove the /blog/ part and leave

• https://opensource.org/status
• https://opensource.org/seat-type/
• https://opensource.org/steward/
• https://opensource.org/publication/

What is the cleanest way to achieve this?

[Ninodevo]

Hi!

https://opensource.org/blog/status/board-member -> https://opensource.org/board-member/status/*
https://opensource.org/blog/seat-type/individual -> https://opensource.org/board-member/seat-type/*
https://opensource.org/blog/steward/apple -> - https://opensource.org/license/steward/*
https://opensource.org/blog/publication/recreate-coalition -> https://opensource.org/press-mention/publication/*

I've updated the custom taxonomy permalink bases to:

Status -> https://opensource.org/board-member/status/
Seat Type -> https://opensource.org/board-member/seat-type/
Steward -> https://opensource.org/license/steward/
Category -> https://opensource.org/license/category/
Publication -> https://opensource.org/press-mention/publication/

Additionally, I've added the redirects from the old URLs to the new ones. It can be tested on staging. If everything is okay, I can do the same for production.

[smaffulli]

these seem to be working as expected on staging, thanks.

…

On Mon, Aug 25, 2025 at 4:14 PM Nino Mihovilic ***@***.***> wrote: *Ninodevo* left a comment (OpenSourceOrg/dotOrg#195) <#195 (comment)> Hi! https://opensource.org/blog/status/board-member -> https://opensource.org/board-member/status/* https://opensource.org/blog/seat-type/individual -> https://opensource.org/board-member/seat-type/* https://opensource.org/blog/steward/apple -> - https://opensource.org/license/steward/* https://opensource.org/blog/publication/recreate-coalition -> https://opensource.org/press-mention/publication/* I've updated the custom taxonomy permalink bases to: Status -> https://opensource.org/board-member/status/ Seat Type -> https://opensource.org/board-member/seat-type/ Steward -> https://opensource.org/license/steward/ Category -> https://opensource.org/license/category/ Publication -> https://opensource.org/press-mention/publication/ Additionally, I've added the redirects from the old URLs to the new ones. It can be tested on staging <https://open-source-initiative-development.mystagingwebsite.com/>. If everything is okay, I can do the same for production. — Reply to this email directly, view it on GitHub <#195 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAKJJADMXIBAPEHYHI67G4L3PMK4PAVCNFSM6AAAAAB552C44CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTEMRQGQ3TMNZZG4> . You are receiving this because you commented.Message ID: ***@***.***>

[Ninodevo]

Nice, it's pushed to production and redirects have been added.

[nickvidal]

Thank you @Ninodevo