Skip to content

docs: sponsorship blog#299

Open
lprimak wants to merge 4 commits intomainfrom
add-sponsorship-blog
Open

docs: sponsorship blog#299
lprimak wants to merge 4 commits intomainfrom
add-sponsorship-blog

Conversation

@lprimak
Copy link
Copy Markdown
Contributor

@lprimak lprimak commented Apr 2, 2026

Add blog about community-maintained and sponsorship that's needed

@lprimak lprimak requested review from bmarwell and fpapon April 2, 2026 15:26
@lprimak
Copy link
Copy Markdown
Contributor Author

lprimak commented Apr 2, 2026

Copy link
Copy Markdown
Member

@jbonofre jbonofre left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I understand the purpose of this blog. But I'm not sure I understand the goal.

We have two cases:

  1. A vendor can sponsor the foundation, with target sponsoring (https://www.apache.org/foundation/sponsorship.html#targeted-sponsorship)
  2. A vendor is paying individuals to contribute on project. That's fine, but no need to have a blog or anything in the project itself (it's up to the vendor).

Can you clarify what is the problem statement and the purpose of this blog post ?

Let’s make sure Shiro continues to be a project worth relying on.

== What you can do right now
* Consider link:/commercial-support.html[sponsoring] the project to ensure its sustainability
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is fine and acceptable, but for "commercial support" purposes.


For years, Shiro has quietly powered authentication, authorization, cryptography, and session management for countless applications around the world. Its simplicity and flexibility made it a favorite among developers who needed security without unnecessary complexity.

Today, with the conclusion of past corporate sponsorships, the project is maintained entirely by dedicated volunteers who believe in its mission and its value to the ecosystem.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would remove "with the conclusion of past corporate sponsorships". Shiro is fully community driven, by individuals.
Even if kind of true, I would remove this part of the sentence ti "invite" everyone to contribute and join (individuals, not vendor affiliated).


Today, with the conclusion of past corporate sponsorships, the project is maintained entirely by dedicated volunteers who believe in its mission and its value to the ecosystem.

Open source has always thrived on community ownership. Some of the most resilient and innovative projects exist because individuals and organizations stepped up when it mattered most. Shiro is now at that moment.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here, that's not fully true for Apache projects (again community driven).

== What’s Needed Now

* Contributors to help with development, testing, and documentation
* Organizations willing to link:/commercial-support.html[financially sponsor] ongoing work
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is fine, but I would emphasize on "commercial support", to not give the feeling that the contributions are driven by vendors.

* Organizations willing to link:/commercial-support.html[financially sponsor] ongoing work
* Advocates who believe in sustainable open source

If your company relies on Shiro—even indirectly—this is the time to invest in its future. Sponsorship isn’t just support; it’s a way to ensure the tools you depend on remain secure, modern, and well-maintained.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

-1 for that.

I agree we should encourage contributions. But at the ASF, we are all contributing as individuals (affiliation doesn't matter). Vendors don't decide of the governance and contributions, the individuals do.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Gotcha.

@jbonofre
Copy link
Copy Markdown
Member

jbonofre commented Apr 2, 2026

This also should be discussed between the PMC (and approved).

@lprimak
Copy link
Copy Markdown
Contributor Author

lprimak commented Apr 2, 2026

JB, thank you for your valuable comments

This also should be discussed between the PMC (and approved).

Yes, this is what I am trying to do :)

@lprimak
Copy link
Copy Markdown
Contributor Author

lprimak commented Apr 2, 2026

Well, primary goal is to encourage financial support for organizations contributing to Shiro, from organizations who are using Shiro.
Secondary is to encourage code and documentation contribution to Shiro.
I am not sure Targeted Contribution applies here.

@lprimak
Copy link
Copy Markdown
Contributor Author

lprimak commented Apr 2, 2026

Hopefully looks better for you @jbonofre - thank you!

Copy link
Copy Markdown
Member

@jbonofre jbonofre left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the update on the phrasing. It looks better to me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants