Hi BifroMQ PPMC and mentors,
This is the second quarterly report for BifroMQ, covering the progress made
over the past three months. I have already updated the wiki. Any
feedback/concerns are appreciated.

## BifroMQ

BifroMQ is a Java-based, high-performance, distributed MQTT broker
with native multi-tenancy support, designed for large-scale
connections and message delivery.

BifroMQ has been incubating since 2025-04-22.

### Three most important unfinished issues to address before graduating:
  1. Increase public exposure to expand the community user base and
improve project visibility.
  2. Continue delivering regular releases, streamline the release
management process, and rotate the Release Manager role among key
contributors.
  3. Grow community participation beyond the original contributors,
including attracting new reviewers and contributors.

### Are there any issues that the IPMC or ASF Board need to be aware of?
We understand that the trademark transfer has been completed based on
publicly available trademark ownership information (e.g. via
https://aiqicha.baidu.com/mark/s?q=BIFROMQ&t=7).
However, we would appreciate receiving an official confirmation from
ASF (a scanned copy of the signed transfer agreement would be
sufficient) so that our company can properly archive the transfer
documentation for internal compliance purposes.
### How has the community developed since the last report?
We have observed increasing activity on GitHub and the dev mailing list.
Our mentor (Chris) helped initiate a valuable discussion with the
Apache IoTDB community, which may lead to potential collaboration
between the two projects.
We have set up a WeChat Account (“BifroMQ”) to publish Chinese
translations of release announcements. All published content is
derived from or links back to the official Apache BifroMQ website, and
the account is not used for community discussions.
### How has the project developed since the last report?
We completed our first incubating release after 3 RC votes.

### How would you assess the podling's maturity?
Please feel free to add your own commentary.

  - [ ] Initial setup
  - [ ] Working towards first release  - [X] Community building
  - [ ] Nearing graduation
  - [ ] Other:

### Date of last release:
  2026-01-28

### When were the last committers or PPMC members elected?None so far

### Have your mentors been helpful and responsive?Are things falling
through the cracks? If so, please list any
open issues that need to be addressed.
Our mentors have been helpful and responsive.

### Is the PPMC managing the podling's brand / trademarks?
Are 3rd parties respecting and correctly using the podlings
name and brand? If not what actions has the PPMC taken to
correct this? Has the VP, Brand approved the project name?
We attempted to rename our WeChat account by adding the “Apache”
prefix, based on PPMC consensus reached on the private mailing list.
However, the request was rejected by the WeChat platform due to
tightened naming policies, which now require an official authorization
document from ASF to use “Apache” as an account prefix.
We would appreciate guidance on whether there is a formal ASF process
to request such an authorization letter for external platform
compliance purposes.

Reply via email to