Open Stack

I'm not really active in Oslo these days, but I can provide a couple of 
general answers below.

On 11/8/22 03:38, 韩光宇 wrote:
> Hi,
> 
> Wang and me are colleagues in a team.
> 
> I would like to ask, put aside the working process of NATS and look at
> Rocketmq independently, if we want to do the work of adding
> Rocketmq[1] drivers, is the community welcome?
> 
> We have already seen the oslo driver policy[2] in the documentation. I
> also want to ask, if the community is willing to accept the Rocketmq
> driver, whether we need to do other efforts besides the development
> task itself. For example, I see that "Must have at least two
> individuals from the community committed to triaging and fixing bugs,
> and responding to test failures in a timely manner".
> 
> I want to ask:
> （1）Is the current policy still

If it's still in the docs then it is. If policy changes are desired then 
a patch should be proposed to the docs.

> （2）Are there community members willing to take responsibility for
> this, or is it okay if we commit to triaging and fixing bugs, and
> responding to test failures in a timely manner by ourselves

The policy was primarily intended to ensure there was enough support 
behind a driver that it wouldn't bitrot and become a maintenance burden 
on the wider Oslo team. If you're willing to support the driver I think 
that satisfies the requirements.

> 
> Cheers,
> Han
> 
> [1] https://github.com/apache/rocketmq
> [2] https://docs.openstack.org/oslo.messaging/latest/contributor/supported-messaging-drivers.html
> 
> 
> Christian Rohmann <christian.rohmann at inovex.de> 于2022年11月2日周三 18:20写道：
>>
>> On 01/11/2022 10:06, 王坤田 wrote:
>>
>> I want to develop a new driver for oslo.messaging to use rocketmq in openstack environment. I wonder if the community need this new driver？
>>
>>
>> There is a larger discussion around adding a driver for NATS (https://lists.openstack.org/pipermail/openstack-discuss/2022-August/030179.html).
>> Maybe the reasoning, discussion and also the PoC there is helpful to answer your question. I suppose you are also "not happy" with using RabbitMQ?
>>
>>
>>
>> Regards
>>
>>
>> Christian
>