I'm just asking, because for example the previous projects, that i was a mentor
of: iotdb and answer, who's email lists I used to follow, are completely closed
to me now. During my job at timcho I was able to access their feishu insurance
and participate. Now, I'm just as cut off as anyone else.
Hi Chris,
Thanks for stepping in as a Mentor.
You point out a common problem in the project community in China.
There are some cultural differences between Chinese and OSS. Daniel
and I gave a presentation[1] last year at the OSS Summit EU to explain
them.
I have to admit that WeChat is so powerf
Hi everyone,
Thanks to Willem for introducing the project and me to the ASF Incubator
community.
Here’s my addition to JB’s first question:
BifroMQ has no direct relationship with existing Apache MQ projects that
support MQTT communication. Although the “MQ” in its name might suggest
it’s jus
Hi JB，
Please take a look at my answers below.
On Tue, Mar 25, 2025 at 5:07 PM Jean-Baptiste Onofré wrote:
>
> Hi Willem
>
> The proposal is interesting.
>
> I have two questions:
> - any relation with existing MQTT brokers (Apache ActiveMQ, etc) ?
Quick answer, BifroMQ is a distributed MQTT br
Hi,
[x] Download links are valid.
[x] Checksums and signatures.
[x] LICENSE/NOTICE files exist
I can not compile the source from on my mac m1. The error messages:
make build
rm -fr ./dist
mkdir -p ./dist
CGO_ENABLED=0 go build -ldflags "-X main.Branch= -X main.Revision= -X
main.Version= -extldfl
Putting it into the maturity model may be “best practices”, but it gets treated
as “policy”
>> We could possibly add an extra item to the maturity model [3] along the
>> lines of “TB50. The project and third parties do not refer to anyone as “the
>> creator/founder of Apache Foo”. with a link t
Hi,
The incubator isn’t creating any new policy here. We need to follow what M&P
comes up with and ensure podlings know about it. The current policy is here
[1], if you want to discuss the changes, bring that up in the draft document or
board list [2], M&P are unlikely to see the conversation h
Hi PJ & list,
We have now reviewed the remaining dependency licenses to our
satisfaction. Everything is in accordance with the Third Party
Licensing Policy. I have updated the proposal accordingly.
I have also taken out incubator. of the repo and mailing list
names.
We are ready to go now, but h
> On Mar 25, 2025, at 6:09 AM, Bertrand Delacretaz
> wrote:
>
> On Tue, Mar 25, 2025 at 11:31 AM Paul King wrote:
>> ...For me the wording is critical. If the wording is "original
>> creator of the technology behind Apache Foo" or similar I have less
>> concern, assuming it is true...
>
> I
On Tue, Mar 25, 2025 at 11:31 AM Paul King wrote:
> ...For me the wording is critical. If the wording is "original
> creator of the technology behind Apache Foo" or similar I have less
> concern, assuming it is true...
Indeed, for me the rule is simply to state facts and nothing else.
Adding rul
The policy proposed here, IMO, is not about silencing the fact, but
about avoiding exclusive expression.
However, I may consider developing different recommendations rather
than adding "original"—perhaps "We're Apache Foo experts, contributing
back and evolving with the upstream."
IIUC people cal
I agree with Julian's word and would like to share a previous thread
[1]: A page telling the project history would be better than "I'm an
original creator of Apache Foo"
[1] https://lists.apache.org/thread/b0ygk9y38t8yyfhz7sfpo0yh0xbfhk7s
I respect people who contribute and dedicate a lot to the
Hi all,
I agree … a full-blown MQTT broker fits perfectly into the landscape of IoT
projects. Especially as MQTT is currently really starting to gain a lot of
traction in the Industry (At least here in Germany).
I would generally be willing to step in as Mentor.
However, I have seen with many
Hi,
As Paul said, the current M&P policy asks to use “original owner” rather than
“owner”. The current suggested changes would only allow this for two years
after becoming a top-level project, after which “owner” current or otherwise,
could not be able to be used, but this is still a work in pr
Yes, I agree to some degree with the points that Cédric and Julian are
making. For me the wording is critical. If the wording is "original
creator of the technology behind Apache Foo" or similar I have less
concern, assuming it is true, but I also see wording sometimes that
causes confusion or dimi
I would like to introduce some nuance here, because like Julian I think
moral rights is an important topic. I'd like to make a difference between
stating _facts_, that is "XY was at the origin of creation of ASF Foo" and
explicitly promoting XY as the creator of ASF Foo. In other words, I think
tha
I don’t think it’s a great idea. It curtails an important aspect of
intellectual property called "moral rights" — the right to be recognized for
things one has created.
I get why ASF wants to do this, given that companies are inclined to make
expansive claims and imply that they control a proje
Hi Willem
The proposal is interesting.
I have two questions:
- any relation with existing MQTT brokers (Apache ActiveMQ, etc) ?
- do you have plans to grow the community, especially "outside" of Asia ?
Regards
JB
On Tue, Mar 25, 2025 at 1:29 AM Willem Jiang wrote:
>
> Hi everyone,
>
> I’m exci
Hi Justin
About Nemo, I already recommended to discuss about retirement, I don't
see a lot of activity.
About Livy, we have activity on the project (contributions), but we
should have a more strong activity on release. We discussed about
retirement while ago but the community stepped up and Livy
Hi Justin,
That sounds reasonable to me to add in the maturity model.
Regards
JB
On Tue, Mar 25, 2025 at 6:56 AM Justin Mclean wrote:
>
> Hi,
>
> There’s a discussion on the board list about using "creator of Apache Foo”.
> [1] Also, see the current policy on it. [2] (i.e “original creator” ca
Hello Incubator PMC and Community,
The vote to Release Apache OzHera (incubating) 2.2.5-incubating-rc5 has passed
with 3 +1 binding votes and no -1 votes.
(+1 binding)
- PJ Fanning
- Kevin Ratnasekera
- Duo Zhang
Voting thread:https://lists.apache.org/thread/r2frpbhbytd2c2z6h07nvtdk28n3ymdt
Th
On Thu, 20 Mar 2025 at 07:41, tison wrote:
>
> Do we have an introductory about how Pony Mail works?
>
> Yes I noticed that https://lists.apache.org/ and willing to take a
> look. But the last few times I jump into the code [1], I can't find a
> way to understand how it works, how to set up a dev
22 matches
Mail list logo
