PostgreSQL ties community event recognition to trademark authorization
The July trademark statement separates compliance with event guidelines from permission to use the project name. Its practical consequence is a decision about community recognition and website links.
Following most of a project's event guidelines does not automatically authorize an organizer to use its trademarks. The PostgreSQL Community Association makes that distinction explicit in its July 11 statement about an event organized by Fundación PostgreSQL. According to the association, the event satisfies most community-event guidelines but lacks authorization to use the disputed POSTGRES mark. The resulting decision affects whether the event can claim community-conference status and receive a link from the project website.
The July statement presents the association's position during continuing court proceedings in Spain. Its descriptions of infringement and the other organization's conduct are claims made by the association. The statement does not report a final court judgment resolving the dispute. That distinction matters because the immediate project decisions are concrete even while the legal dispute remains ongoing.
I default to PostgreSQL for relational systems, so the continuity of the project behind the database matters to me. Clear ownership of shared project identifiers helps users understand which organizations speak for the project and which operate independently. That is an operational concern about dependable information, without requiring a position on every allegation in a dispute.
Event quality and permission answer different questions
The July announcement says PostgreSQL has community-event guidelines intended to support a consistent experience across events. It also says events following those guidelines can use PostgreSQL trademarks under the trademark policy. The disputed case illustrates why the policy condition cannot be reduced to checking the event's agenda or organization alone.
The association says Fundación PostgreSQL continues to defend registration of a mark confusingly similar to the community's registrations. It identifies the event's use of POSTGRES as part of that dispute. The problem described in the statement is therefore the organizer's authorization to use the mark, even though the event follows most of the event guidelines.
Following legal advice, the Core Team declines to authorize the event's claim to be a community conference. It also asks the website team not to link to it. These are the announcement's immediate changes in project behavior. Neither decision establishes that people cannot meet to discuss PostgreSQL, and the statement does not announce a change to database functionality or software licensing.
Community recognition conveys information. A link from an official project site can reasonably look like endorsement by that project, particularly when the event itself claims community status. Withholding the link limits that implied relationship while the association says trademark authorization is absent. That interpretation follows from the action described, rather than from any reported measurement of audience confusion.
The responsibility predates this event
The September 2021 statement supplies the earlier public account. It says the nonprofit PostgreSQL Community Association of Canada manages the PostgreSQL trademark, other intellectual property and domain names at the Core Team's request. It describes the trademark policy as an attempt to permit broad use while avoiding confusion about project identity.
That statement dates the Core Team's awareness of the initial applications to 2020. According to its account, Fundación PostgreSQL sought registrations in the European Union and United States and already held registrations in Spain. The Core Team and association said they had not received advance notice of the applications. They described subsequent discussions and the decision by the Canadian association and PostgreSQL Europe to file official disputes.
The same earlier account says further POSTGRES applications came to the association's attention in 2021. It presents control of the names and related project resources as the reason for resisting the applications. These details explain why an event-name decision in July 2023 belongs to an existing dispute, rather than a new objection to an isolated conference title.
The earlier statement also distinguishes other trademarks containing the PostgreSQL wordmark that do not claim the community's identity. That distinction is useful context. The stated policy concern is not simply the presence of a familiar database name in every independently registered name. The announcement focuses on potentially conflicting representations of the community and control over its identifiers.
The statement leaves a route to recognition
The association says it remains willing to support the event if the organizer ends the alleged infringement and complies with community policies. It identifies withdrawal of the POSTGRES registration from the Spanish trademark office and discontinuation of the disputed use as the requested actions. Those are the association's proposed conditions, not an announcement that the other organization has accepted them. The source therefore describes both the present refusal of recognition and the policy compliance that could change it.
My preference is for official project communication to make these conditions public. Users can then distinguish the quality of an event from the project's authorization of its branding. The July statement supplies that distinction and names the Core Team's resulting website decision while leaving the court proceedings unresolved.