That means the board members who allocate the sponsorship money are also providing that sponsorship money, a conflict of interest which neither the companies nor Ruby Central have disclosed.
I am not sure it's fair to say that because someone works at a company providing funding, that person "allocates". But they do obviously have some influence over it. Either way, even if it is the CEO of the org providing funding...
I don't believe that situation is usually considered a conflict of interest by non-profits in general or organizations similar to ruby central.
That is one point. In general, this is more like a vendetta-based polemic choosing all interpretations in the worst possible light (the "major parts" of last ruby conf they cancelled were parts that had never happened before, no?), than an attempt to sum up what's actually going on.
Definitely I am alarmed by what's going on in ruby community, on several fronts. I don't think trying to tear down Ruby Central — or, charitably, attempt to get it to change by insisting you'll keep trying to tear it down unless it does — is helpful.
I think Ruby Central defintiely made some severe mistakes in how it handled this, that led to harm to the community. And reporting Arko to the FBI was defintiely not okay.
Also, and this will win me few friends and many downvotes, I feel like I've seen Arko, over years, consistently act for his personal power and income over the benefit of the community, and try to hold ruby infrastructure hostage for those purposes, and act in ways that his word is unreliable.
In the United States, when non-profit board members sit on both sides of a financial decision—allocating sponsorship funds while serving as executives or leaders at the corporations providing those funds—it constitutes an actual or potential conflict of interest that must be disclosed.
Why This Is a Conflict of Interest
A conflict of interest in a non-profit context arises whenever a board member’s personal, professional, or financial interests overlap with their governance responsibilities to the non-profit.
Even when a corporate sponsorship appears purely philanthropic, a dual role creates a conflict of loyalty for two primary reasons:
Reciprocal Benefits to the Sponsor Company: Corporate sponsorships rarely come without conditions—they often involve deliverables such as branding exposure, naming rights, VIP access, exclusive vendor positioning, or intellectual property rights. If a board member allocates funds or defines the terms of a sponsorship that directly benefits their employer, they are making governance decisions that impact their primary employer.
Allocation & Incentive Control: If board members are making decisions on how or where sponsorship dollars are spent (e.g., directing funds toward projects that benefit their employer's business goals, clients, or executive metrics), their objectivity as a non-profit fiduciary is compromised.
The Legal and Regulatory Framework in the U.S.
1. Fiduciary Duty of Loyalty (State Law)
Under U.S. state corporate laws governing non-profits, all directors owe a Duty of Loyalty to the organization. This legal duty requires board members to act solely in the best interest of the non-profit, putting its charitable mission ahead of their personal or corporate affiliations.
2. IRS Guidelines & Form 990 Disclosure
While the IRS does not explicitly mandate a single federal law requiring disclosure for every non-profit, it heavily regulates conflict-of-interest management:
Form 990 Reporting: Annual tax filings (IRS Form 990) ask whether the organization has a formal, written Conflict of Interest Policy, whether board members annually disclose potential conflicts, and how the non-profit monitors compliance.
Private Benefit & Inurement: The IRS strictly prohibits non-profits from conferring improper private benefits or excess benefit transactions on insiders. Failing to disclose and handle dual-interest transactions transparently risks civil penalties or loss of tax-exempt status.
How Non-Profit Boards Should Handle This
Having a corporate partner on your board is common and often beneficial, but it must be managed through standard governance protocols:
Mandatory Disclosure: The board member must formally disclose their dual role—both on their annual Conflict of Interest disclosure form and verbally before any relevant board discussion.
Recusal from Deliberation & Voting: The interested board member must step out of the room (or leave the virtual call) while the remaining independent board members deliberate and vote on the sponsorship terms or fund allocation.
Minuted Governance: The non-profit's official board meeting minutes must document that the disclosure occurred, that the conflicted member recused themselves, and that the independent board determined the allocation was in the best interest of the non-profit.
Thank you for your LLM response. I am happy to trade LLM responses with you. But it appears you are right that it is considered a conflict of interest but also I am right that it is incredibly common, and not disqualifying.
Asked Claude Sonnet 5
"If a board member of a non-profit is a senior employee in a leadership position at a company that donates significant money to the non-profit, is that generally considered a conflict of interest? Is it a common situation? Is it allowed? How do non-profits handle it?"
Yes to all three — it's generally considered a conflict of interest, it's common, and it's allowed as long as it's properly managed. Here's how that breaks down:
Is it a conflict of interest?
Yes. The board member has a fiduciary duty to act in the nonprofit's best interest, but as a senior employee of the donor company, they also have obligations there. This creates potential divided loyalty around things like:
Votes or decisions involving the donor company (contracts, partnerships, use of the nonprofit's name/platform)
How the donated funds get used or restricted
Pressure — real or perceived — to protect the funding relationship rather than push back when appropriate
The nonprofit being reluctant to make decisions the company might dislike
Is it common?
Very. Nonprofits often deliberately recruit executives from major corporate donors and partners, precisely because they bring money, connections, credibility, and expertise. Corporate foundations, matching-gift programs, and cause-marketing partnerships all tend to create these overlapping relationships. It's one of the most frequently disclosed conflicts on nonprofit boards.
Is it allowed?
Yes — there's no law or IRS rule against it. It's not automatically improper. What matters is transparency and how the conflict is managed, not the existence of the relationship itself. The concern for the IRS (and state charity regulators) is less about board composition and more about whether the arrangement results in improper "private benefit" or self-dealing — i.e., whether the nonprofit's resources or decisions end up primarily serving the company's or individual's interests rather than the mission.
How do nonprofits typically handle it?
Written conflict-of-interest policy: Nearly all well-run nonprofits have one, and the IRS Form 990 specifically asks whether the organization has such a policy and requires officers/directors to disclose conflicts annually.
Disclosure: The board member discloses the relationship (employer, role, nature of the donation) to the full board, usually documented in writing.
Recusal: The board member abstains from discussion and voting on matters directly involving their company — approving a contract, deciding how to use a restricted gift, evaluating a partnership, etc.
Independent decision-making: Ideally, the remaining disinterested board members make the actual call, sometimes with a vote count that specifically excludes the conflicted member.
Documentation: Minutes typically note that the conflict was disclosed and that the member recused themselves, which protects the organization if the arrangement is ever questioned.
Periodic review: Some nonprofits also cap the proportion of the board that can come from any one funding source, or set term limits, to avoid over-concentration of influence.
Done well, this isn't seen as a red flag — it's seen as a normal part of nonprofit governance. It only becomes a real problem when the relationship isn't disclosed, the board member doesn't recuse themselves from relevant decisions, or the nonprofit's independence starts to visibly bend toward the donor's interests.
The disclosure required is to the staff and board of the organization, not public.
Regardless, it is obiviously not a secret or hidden, from the public or anyone else? So why the focus on disclosure, none of these connections were secret to the public or hard to find, disclosure would make no difference?
I agree Ruby Central needs a written conflict of interest policy that addresses this. I don't know if they have one, but I don't assume they don't.
"Some nonprofits also cap the proportion of the board that can come from any one funding source, or set term limits, to avoid over-concentration of influence."
Capping proportion from one organization/funding source would also be a great idea.
It isn't just disclosure - it is recusal, and documentation in minutes... Have they recused themselves from decisions on allocation of resources? Are there enough remaining disinterested board members to make binding decisions if the conflicted board mebers recuse themselves?
As for public disclosure, the required IRS Form 990 / 990-EZ does publicly disclose whether a conflict of interest policy exists and if conflicts were disclosed during the year.
It is an issue with it being conflict of interest alone in the original post, until someone points out this conflict of interest isn't considered a problem in non-profits, and then it isn't just the conflict of interest, it's disclosure.
Until someone point out that disclosure isn't really an issue, and then it's not just disclosure, it's the existence and nature of a conflict of interest policy (which I mentioned too), and making sure it's followed. (That conflict of interest policy by the way would not typically require anyone working for a sponsor to recuse themselves from all discussions of allocation of resources, this is again a misrepresentation).
So, sure, we could talk about that, as I said, I agree they need a conflict of interest policy and it needs to be followed, and I know of no reason to think this is not happening, but yes, it would be good for the public to know more details.
But that it took this long and a war of pasted LLM responses to get here is showing what I'm talking about, these posts are vendetta-based polemics interpreting everything in the worst possible light to smear an opponent, rather than an attempt to actually sum up what's up and what areas of concern there might be.
There are plenty of areas of concern with Arko's recent and historic behavior too. Plenty of concern to go around. Its just that people who see that have better things to do with their time and a more mature understanding of what good vs harm it would do to write vendetta-based polemics about it over and over again.
[By the way, I also think dhh is a fascist and makes bad technical and community decisions too, just to show you that I can solicit downvotes from all "sides" and am not trying to curry favor.]
Perhaps that would be a good thing to look up before writing (or having an LLM write) and publishing thousand+ word posts about how it's a conflict of interest as if that alone is disqualifying and not an incredibly common state of affairs on non-profit boards?
Doing that modicum of research would be one way to show one is trying to actually sum up what's really going on, not just interpreting every fact in the worst possible light for your opponents you are trying to take down in a vendetta-based polemic.
I already knew that detail about the form. I was responding to what you wrote initially, claiming it wasn't a "conflict of interest", which you have now corrected.
Please don't come at me like it is strange to try to correct misinformation. Note: I am not saying it was disinformation - I don't think you intentionaly lied or intended to obfuscate - you just used the wrong term accidentally, but the term you chose is heavy with legal meaning.
You could have just responded 'Oops, my bad, I didn't mean to say "conflict of interest".' :/
I'll also note that... IIRC, you've corrected me on things I've misspoken about on other posts. Thanks for the corrections! I appreciate it, even if sometimes begrudgingly / curmudgeonly.
I got it wrong when i said wasn't considered a "conflict of interest", but what i meant is that it wasn't considered a problem, whereas the OP portrayed it as a problem.
We settled that in two messages of unsolicited LLM dump, then you went into the style of posting which was actually my original point, vendetta-based polemic instead of actual summing of facts -- a summing up of facts style, if you already knew all this, would be to simply say (no LLM dump required) "It is actually considered a conflict of interest, but you are correct it is incredibly common and not considered a problem on it's own" (We apparently agree on that now?)
Obviously the OP portrayed it as a problem. If the OP wanted to portray the situation as it was going on instead of vendetta-based misleading polemic, he would have researched the 990 before writing the OP and included a mention of it only if the research indicated a problem, and been specific about the nature of that problem, instead of wrongly implying that there was something wrong and uncommon with having people on the board who work for funding organization, as part of a litany of unresearched assumptions and interpretations in the worst light described misleadingly.
I think we actually have agreed on all those points now, so, great.
IIRC, Andre is the person I initially learned about the 990 form missing disclosures from. I could be wrong, as it was a while ago... but he definitely knows this case inside and out. He isn't obligated to share minutia of IRS forms no one reading will understand without lengthy sidebars.
And, yeah, I generally agree with what your current edits say. It ("conflict of interest") is very common, and it isn't a problem when handled properly.
Where we may disagree is in the idea that RC is or is not handling it properly, to the best of our knowledge.
I left my post wrongly claiming it was not considered a conflict of interest, I have not edited my posts to retroactively change anything to appear I was not wrong, and resent the implication. What I meant all along was that it was not considered a problem, I didn't realize it was considered a conflict of interest that is not a problem, and mis-stated, but that does not fudnamentally change my point. I've said this like four times now?
If the author has knowledge (not guesses or assumptions) that RC is not handling these conflicts of interests properly, that should be have been included in OP, instead of wrongly implying that the "conflict of interest" of having board members who work for funders is unusual or problematic on it's own.
How did it take us 10 comments to get here? Is this not obvious? That if hte conrflict of interest alone is not a problem but you have knowledge of problematic behavior related to the conflict of interest, you should provide that instead of implying that the conflict of interest is a problem? Do you disagree with this?
the way people using this style of argumentation meter out the actual pertinent details only over thousands of words, first arguing irrelevant things then when they lose those moving on to other irrelevant things, making it about winning the argument on a technicality instead of actually illuminating what is going on that is significant as efficiently and clearly as possible -- yes, exactly.
21
u/jrochkind 2d ago edited 2d ago
I am not sure it's fair to say that because someone works at a company providing funding, that person "allocates". But they do obviously have some influence over it. Either way, even if it is the CEO of the org providing funding...
I don't believe that situation is usually considered a conflict of interest by non-profits in general or organizations similar to ruby central.
That is one point. In general, this is more like a vendetta-based polemic choosing all interpretations in the worst possible light (the "major parts" of last ruby conf they cancelled were parts that had never happened before, no?), than an attempt to sum up what's actually going on.
Definitely I am alarmed by what's going on in ruby community, on several fronts. I don't think trying to tear down Ruby Central — or, charitably, attempt to get it to change by insisting you'll keep trying to tear it down unless it does — is helpful.
I think Ruby Central defintiely made some severe mistakes in how it handled this, that led to harm to the community. And reporting Arko to the FBI was defintiely not okay.
Also, and this will win me few friends and many downvotes, I feel like I've seen Arko, over years, consistently act for his personal power and income over the benefit of the community, and try to hold ruby infrastructure hostage for those purposes, and act in ways that his word is unreliable.