Skip to content

Revise partner reference requirements in terms and conditions#307

Open
ebullient wants to merge 3 commits into
mainfrom
all-or-none
Open

Revise partner reference requirements in terms and conditions#307
ebullient wants to merge 3 commits into
mainfrom
all-or-none

Conversation

@ebullient
Copy link
Copy Markdown
Member

@ebullient ebullient commented Apr 16, 2026

🗳️ Vote progress

Updated partner reference guidelines to require mentioning all vendors providing EOL support.

voting group: @commonhaus/cf-egc

Do one of the following:

  • React with 👍 (:+1:) or Approve a review if it looks good to you
  • React with 👀 (:eyes:) if you're "ok" with it (it may not be your favorite)
  • If you think it needs discussion or revision:
    • Create a review, add your comments and require changes
    • Use the +- button to make a suggestion (instead of just adding a comment).

@ebullient ebullient added the vote/open Vote open label Apr 16, 2026
@ebullient ebullient requested a review from a team as a code owner April 16, 2026 17:59
@haus-rules-bot haus-rules-bot Bot added the notice Notice (review, announcement); EGC attention label Apr 16, 2026
@haus-rules-bot
Copy link
Copy Markdown

haus-rules-bot Bot commented Apr 16, 2026

🗳️ 11 of 20 members of @commonhaus/cf-egc have voted (reaction or review, quorum=2/3).

Reaction Total Team Voting members
approve 11 9 FDelporte, Naros, aalmiray, cealsair, ebullient, henri-tremblay, kenfinnigan, marc0der, tristantarrant
ok 2 2 criccomini, gavinking

Additional input (🙏 🥰 🙌):
dmlloyd(👍), eitch(👍)

The following votes were not counted (duplicates):
Naros(👍), cealsair(👍)

A vote manager comment containing vote::result will close the vote.

Copy link
Copy Markdown
Member

@yrodiere yrodiere left a comment

Choose a reason for hiding this comment

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

I think "fair" kind of implies "mention everyone" already, but okay, more clarity is better :)

@gavinking
Copy link
Copy Markdown
Member

I think "fair" kind of implies "mention everyone" already, but okay, more clarity is better :)

Actually I think "all vendors" is too strong; we should be allowed to exclude vendors we think are spammy or scammy.

@yrodiere
Copy link
Copy Markdown
Member

I think "fair" kind of implies "mention everyone" already, but okay, more clarity is better :)

Actually I think "all vendors" is too strong; we should be allowed to exclude vendors we think are spammy or scammy.

"all vendors which provide EOL support" is meant as "all vendors which are part of the open-source sustainability initiative", I believe. I agree we want to avoid spammy/scummy vendors, but if these manage to be part of that initiative, we've failed elsewhere...

@gavinking
Copy link
Copy Markdown
Member

"all vendors which provide EOL support" is meant as "all vendors which are part of the open-source sustainability initiative", I believe.

If that's what it means then that's what it should say, no?

Comment thread agreements/project-contribution/terms-and-conditions.md Outdated
Comment thread agreements/project-contribution/terms-and-conditions.md
ebullient and others added 3 commits April 22, 2026 11:48
Updated partner reference guidelines to require mentioning all vendors providing EOL support.
Co-authored-by: Yoann Rodière <yoann@hibernate.org>
**Partner support references:**
Projects are not required to name individual OSSI partners on project pages. A link to the Foundation’s OSSI page is sufficient.
If a project chooses to reference individual partners, it should do so in a fair and non-misleading manner consistent with the Foundation’s Trademark Policy and Code of Conduct.
If a project chooses to reference an individual partner, it must also reference all other OSSI partners that provide EOL support for that project, in a fair and non-misleading manner consistent with the Foundation’s Trademark Policy and Code of Conduct.
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

If someone is offering paid EOL support for your project, you will know. They will ask to be listed. ;)

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Thanks - how about removing the burden of discovery from the different projects, by going with something like all other OSSI partners who request to be listed for an individual project, and provide EOL support for that project. Otherwise I might worry I haven't listed everyone due to not knowing because it does say must?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Again.. if someone adds support for your project, they will let you know. They will want to be listed. And in that case, you must list them.

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Well, it might just be me and maybe this is how documents of this type are written, but I would say if it says "must do something" we need to try to take reasonable steps to do that. Hence I was trying to reduce the burden on the project needing to seek out those people they should list. I wouldn't know how to find that. I think you are saying that we don't need to seek people out and just respond when asked, that is fine for me and I think the wording I suggested would then make it clear it's not my responsibility to find them.

So it's clear, I propose to change If a project chooses to reference an individual partner, it must also reference all other OSSI partners that provide EOL support for that project, in a fair and non-misleading manner consistent with the Foundation’s Trademark Policy and Code of Conduct. to If a project chooses to reference an individual partner, it must also reference all other OSSI partners who request to be listed for an individual project, and provide EOL support for that project, in a fair and non-misleading manner consistent with the Foundation’s Trademark Policy and Code of Conduct. Or maybe it's better as: If a project chooses to reference an individual partner, it must also reference all other OSSI partners that provide EOL support for that project and who request to be listed for an individual project, in a fair and non-misleading manner consistent with the Foundation’s Trademark Policy and Code of Conduct.

However, it might be that the foundation is fine for us to that that approach (needing to be informed before we can fulfil the obligation) and will be understanding of projects that have not fulfilled this requirement (because of the need to list "vendor x" not having been clear to them).

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

I think the latter interpretation is correct. If you didn't list them because you didn't know, that is easy to correct as soon as you do.

**Partner support references:**
Projects are not required to name individual OSSI partners on project pages. A link to the Foundation’s OSSI page is sufficient.
If a project chooses to reference individual partners, it should do so in a fair and non-misleading manner consistent with the Foundation’s Trademark Policy and Code of Conduct.
If a project chooses to reference an individual partner, it must also reference all other OSSI partners that provide EOL support for that project, in a fair and non-misleading manner consistent with the Foundation’s Trademark Policy and Code of Conduct.
Copy link
Copy Markdown

@tomjenkinson tomjenkinson May 1, 2026

Choose a reason for hiding this comment

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

fair and non-misleading
Does this mean more all earlier in the sentence? If not, is there some guidance on what that means from a trademark point of view (maybe it's in https://github.com/commonhaus/foundation/blob/72228fb0c5f145f33fecebe4e7196079e3c22096/policies/trademark-guidelines.md somewhere?) or the Code of Conduct (https://www.commonhaus.org/policies/code-of-conduct/).

How about just:
If a project chooses to reference an individual partner, it must also reference all other OSSI partners that provide EOL support for that project in a manner consistent with the Foundation’s Trademark Policy and Code of Conduct.
?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

This is more about avoiding endorsement or preference. You could list all with an obvious bias toward one...

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Also: it is "individual partners" because you could start with two, and "individual partner or partners" is unnecessarily wordy.

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

Labels

notice Notice (review, announcement); EGC attention vote/open Vote open

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants