Re:Re:Re: [DISCUSS] Migrating projects under dubbo group
I am the owner of egg-dubbo-rpc & dubbo-remoting-js. After discussion with our team members, we decide to transfer the two projects back to eggjs(https://github.com/eggjs) group，and I will finish it by this weekend thanks a lot At 2019-04-26 11:04:28, "Peter" wrote: I am the owner of egg-dubbo-rpc & dubbo-remoting-js. After discussion with our team members, we decide to transfer the two projects back to eggjs(https://github.com/eggjs) group. thanks a lot At 2019-04-26 10:52:03, "Huxing Zhang" wrote: >On Thu, Apr 25, 2019 at 4:02 PM Huxing Zhang wrote: >> >> Hi All, >> >> As is discussed in the graduation proposal in general@ mailing list, >> the github.com/dubbo group has some potential branding issue. To avoid >> it completely, we need to decide the short-term plan and long-term >> plan. >> >> For the short-term plan, there are two way proposed: >> >> 1. Rename dubbo group to another one, let's say A. >> 2. Create a new group A, and migrate all the project to under A, and >> keep the dubbo group empty. The purpose is to avoid someone to abuse >> it in the future. >> >> I am leaning towards option 2. But I'd like to hear what other may think. >> >> The next step is to decide what A is. Actually naming a thing is one >> of the most difficult thing to do... I am trying to find something >> related. I checked the wikipedia page for Dubbo[1], in the history >> section, it says Dubbo is now thought to be a mispronunciation of the >> local Wiradjuri word "Thubbo" or "Tubbo". >> >> I think thubbo and tubbo both are good. thubbo is more different to >> dubbo than tubbo. So I prefer thubbo. How do you think? >> >> >> For the long-term plan: >> >> 1. Like discussed before, all projects under group A are expected to >> be transferred to Apache (if the owner) agree with an ETA. I talked to >> most of the owners and they basically agree, the multi-language >> project are TODOs. I am trying to pull them onto list. >> >> This projects that still listed under dubbo group includes: >> >> * js-for-apache-dubbo >> * py-client-for-apache-dubbo >> * rpc-xmlrpc-for-apache-dubbo >> * jmeter-plugins-for-apache-dubbo >> * go-for-apache-dubbo >> * php-framework-for-apache-dubbo >> * dotnet-for-apache-dubbo >> * serialization-native-hessian-for-apache-dubbo >> * jms-for-apache-dubbo >> * dubbo.github.io >> * metrics >> * hessian-lite >> * dubbo-sentinel-support >> * awesome-dubbo >> * dubbo-remoting-js >> * egg-dubbo-rpc >> * rpc-native-thrift-for-apache-dubbo >> * intellij-idea-plugin >> * initializr >> >> >> If you are the project owner, could you please confirm that: >> >> 1) are you willing to transferred to ASF or not. >> 2) if so, please give an estimated time when will you can finish transfer. >> What you will need to do includes: >> - Find the all the contributors and ask them to sign the Apache >> ICLA[2], if the contribution is trivial, this can be ignore >> - If the code belongs to your company, you need to sign the SGA[3] >> - request ASF infra to transfer the project >> 3) if not, please indicate that which group you will transfer to. >> >> 2. Gain write access to your project after transfer >> >> If your project has been transferred to ASF, you will lose write >> access temporally. The Dubbo community will vote you in as committer >> by following standard ASF way. This means you have to contribute to >> the project for some time in order to earn enough merit. >> >> 3. After the transition is done, delete group A. >> >> The community will summarize and keep track of the status here[4]. >> >> >> [1] https://en.wikipedia.org/wiki/Dubbo >> [2] >> http://dubbo.apache.org/en-us/docs/developers/contributor-guide/cla-signing-guide_dev.html >> [3] >> http://dubbo.apache.org/en-us/docs/developers/contributor-guide/software-donation-guide_dev.html >> [4] >> https://github.com/apache/incubator-dubbo/wiki/Apache-Dubbo-external-ecosystem-status >> >> >> >> -- >> Best Regards！ >> Huxing > > > >-- >Best Regards！ >Huxing
Re: [DISCUSS] Migrating projects under dubbo group
Hi all, After make a discussion with my team members, we decide to delay about 2 months(until 2019/06/30) to donate the go-for-apache-dubbo. Because there so many features to be implemented. 原始邮件 发件人: Huxing Zhang 收件人: dev 发送时间: 2019年4月26日(周五) 08:35 主题: Re: [DISCUSS] Migrating projects under dubbo group Hi, On Fri, Apr 26, 2019 at 12:54 AM 凝雨 mailto:ningbe...@163.com>> wrote: > > Hi there, > > > I'm the author of jmeter-plugins-for-apache-dubbo. I'd like to transfer the > project to ASF. > > > 1) are you willing to transferred to ASF or not. > > > Yes > > > > 2) if so, please give an estimated time when will you can finish transfer. > > What you will need to do includes: > > - Find the all the contributors and ask them to sign the Apache > > ICLA[2], if the contribution is trivial, this can be ignore > > > I seem to have signed ICLA. Please check it. If you have already signed, there is no need to sign it again. However since you have going transfer to ASF, you might need to sign the SGA. Besides, could you give when will you plan to finish it transfer? No need to be very accurate, just a rough estimation will be ok. > On 04/25/2019 16:02, Huxing Zhang wrote: > Hi All, > > As is discussed in the graduation proposal in general@ mailing list, > the github.com/dubbo group has some potential branding issue. To avoid > it completely, we need to decide the short-term plan and long-term > plan. > > For the short-term plan, there are two way proposed: > > 1. Rename dubbo group to another one, let's say A. > 2. Create a new group A, and migrate all the project to under A, and > keep the dubbo group empty. The purpose is to avoid someone to abuse > it in the future. > > I am leaning towards option 2. But I'd like to hear what other may think. > > The next step is to decide what A is. Actually naming a thing is one > of the most difficult thing to do... I am trying to find something > related. I checked the wikipedia page for Dubbo[1], in the history > section, it says Dubbo is now thought to be a mispronunciation of the > local Wiradjuri word "Thubbo" or "Tubbo". > > I think thubbo and tubbo both are good. thubbo is more different to > dubbo than tubbo. So I prefer thubbo. How do you think? > > > For the long-term plan: > > 1. Like discussed before, all projects under group A are expected to > be transferred to Apache (if the owner) agree with an ETA. I talked to > most of the owners and they basically agree, the multi-language > project are TODOs. I am trying to pull them onto list. > > This projects that still listed under dubbo group includes: > > * js-for-apache-dubbo > * py-client-for-apache-dubbo > * rpc-xmlrpc-for-apache-dubbo > * jmeter-plugins-for-apache-dubbo > * go-for-apache-dubbo > * php-framework-for-apache-dubbo > * dotnet-for-apache-dubbo > * serialization-native-hessian-for-apache-dubbo > * jms-for-apache-dubbo > * dubbo.github.io > * metrics > * hessian-lite > * dubbo-sentinel-support > * awesome-dubbo > * dubbo-remoting-js > * egg-dubbo-rpc > * rpc-native-thrift-for-apache-dubbo > * intellij-idea-plugin > * initializr > > > If you are the project owner, could you please confirm that: > > 1) are you willing to transferred to ASF or not. > 2) if so, please give an estimated time when will you can finish transfer. > What you will need to do includes: > - Find the all the contributors and ask them to sign the Apache > ICLA[2], if the contribution is trivial, this can be ignore > - If the code belongs to your company, you need to sign the SGA[3] > - request ASF infra to transfer the project > 3) if not, please indicate that which group you will transfer to. > > 2. Gain write access to your project after transfer > > If your project has been transferred to ASF, you will lose write > access temporally. The Dubbo community will vote you in as committer > by following standard ASF way. This means you have to contribute to > the project for some time in order to earn enough merit. > > 3. After the transition is done, delete group A. > > The community will summarize and keep track of the status here[4]. > > > [1] https://en.wikipedia.org/wiki/Dubbo > [2] > http://dubbo.apache.org/en-us/docs/developers/contributor-guide/cla-signing-guide_dev.html > [3] > http://dubbo.apache.org/en-us/docs/developers/contributor-guide/software-donation-guide_dev.html > [4] > https://github.com/apache/incubator-dubbo/wiki/Apache-Dubbo-external-ecosystem-status > > > > -- > Best Regards！ > Huxing -- Best Regards！ Huxing
Re: [DISCUSS] Migrating projects under dubbo group
At 2019-04-26 08:35:42, "Huxing Zhang" wrote: >Hi, > >On Fri, Apr 26, 2019 at 12:54 AM 凝雨 wrote: >> >> Hi there, >> >> >> I'm the author of jmeter-plugins-for-apache-dubbo. I'd like to transfer the >> project to ASF. >> >> >> 1) are you willing to transferred to ASF or not. >> >> >> Yes >> >> >> > 2) if so, please give an estimated time when will you can finish transfer. >> > What you will need to do includes: >> > - Find the all the contributors and ask them to sign the Apache >> > ICLA[2], if the contribution is trivial, this can be ignore >> >> >> I seem to have signed ICLA. Please check it. > >If you have already signed, there is no need to sign it again. >However since you have going transfer to ASF, you might need to sign the SGA. >Besides, could you give when will you plan to finish it transfer? No >need to be very accurate, just a rough estimation will be ok. It takes about a month, at the end of May. Best regards, ningyu
Re: Dubbo with Erlang language implementation.
Hi, On Fri, Apr 26, 2019 at 12:39 AM 生校 wrote: > > Hi, > Maybe it can modify the project name to erlang-for-apache-dubbo like other > languages implemented(go,dotnet),and I am happy donate to ASF. Glad to here that! Just as discussed in an spearate email about migrating project under dubbo group, if you are willing to donate to ASF. There are few things to do: - Find the all the contributors and ask them to sign the Apache ICLA[1], if the contribution is trivial, this can be ignore - If the code belongs to your company, you need to sign the SGA[2] - request ASF infra to transfer the project - give an estimated time when will you can finish transfer. The ICLA and SGA guide both has a Chinese version if you wish to have. If your project has been transferred to ASF, you will lose write access temporally. The Dubbo community will vote you in as committer by following standard ASF way. This means you have to contribute to the project for some time in order to earn enough merit. > If appropriate, I will continue to improve the project code to accommodate > this change. There is no rush on your side, you can decide when you are ready to donate. Before that you can do plenty of things you wish to do. I will be better that you could provide a plan about when you can finish the transfer. [1] http://dubbo.apache.org/en-us/docs/developers/contributor-guide/cla-signing-guide_dev.html [2] http://dubbo.apache.org/en-us/docs/developers/contributor-guide/software-donation-guide_dev.html > > Thanks > > > 在 2019年4月25日，09:34，Huxing Zhang 写道： > > > > Hi, > > > >> On Wed, Apr 24, 2019 at 5:05 PM Jun Liu wrote: > >> > >> I think the most preferable way would be to donate this erlang project to > >> ASF directly. If put this project somewhere outside ASF, in this case > >> https://github.com/dubbo, then we need to avoid using a name like > >> ‘dubbo-erlang’, but use ‘erlang-for-dubbo’ or something like that. > > > > +1 to donate to ASF. The branding issue for dubbo group is still being > > discussed. I think before that it is better not to add any new > > project. > > > >> > >> Ken > >> > >>> On Apr 24, 2019, at 2:17 PM, ShengXiao Xie wrote: > >>> > >>> I agree with your concerns. > >>> It would be better to change it to dubbo-erlang and transfer to Dubbo > >>> group first. > >>> Maybe we can wait for a suitable time to transfer the project to ASF. > >>> > >>> @ > >>> > On Apr 24, 2019, at 12:42 PM, Justin Mclean > wrote: > > Hi, > > > I agree to modify the project name to apache-dubbo-erlang. > > If it not hosted at the ASF then this may not be a suitable name. > > Thanks, > Justin > > > > > > -- > > Best Regards！ > > Huxing > > -- Best Regards！ Huxing
Re: [DISCUSS] Migrating projects under dubbo group
Hi, On Fri, Apr 26, 2019 at 12:54 AM 凝雨 wrote: > > Hi there, > > > I'm the author of jmeter-plugins-for-apache-dubbo. I'd like to transfer the > project to ASF. > > > 1) are you willing to transferred to ASF or not. > > > Yes > > > > 2) if so, please give an estimated time when will you can finish transfer. > > What you will need to do includes: > > - Find the all the contributors and ask them to sign the Apache > > ICLA[2], if the contribution is trivial, this can be ignore > > > I seem to have signed ICLA. Please check it. If you have already signed, there is no need to sign it again. However since you have going transfer to ASF, you might need to sign the SGA. Besides, could you give when will you plan to finish it transfer? No need to be very accurate, just a rough estimation will be ok. > On 04/25/2019 16:02, Huxing Zhang wrote: > Hi All, > > As is discussed in the graduation proposal in general@ mailing list, > the github.com/dubbo group has some potential branding issue. To avoid > it completely, we need to decide the short-term plan and long-term > plan. > > For the short-term plan, there are two way proposed: > > 1. Rename dubbo group to another one, let's say A. > 2. Create a new group A, and migrate all the project to under A, and > keep the dubbo group empty. The purpose is to avoid someone to abuse > it in the future. > > I am leaning towards option 2. But I'd like to hear what other may think. > > The next step is to decide what A is. Actually naming a thing is one > of the most difficult thing to do... I am trying to find something > related. I checked the wikipedia page for Dubbo[1], in the history > section, it says Dubbo is now thought to be a mispronunciation of the > local Wiradjuri word "Thubbo" or "Tubbo". > > I think thubbo and tubbo both are good. thubbo is more different to > dubbo than tubbo. So I prefer thubbo. How do you think? > > > For the long-term plan: > > 1. Like discussed before, all projects under group A are expected to > be transferred to Apache (if the owner) agree with an ETA. I talked to > most of the owners and they basically agree, the multi-language > project are TODOs. I am trying to pull them onto list. > > This projects that still listed under dubbo group includes: > > * js-for-apache-dubbo > * py-client-for-apache-dubbo > * rpc-xmlrpc-for-apache-dubbo > * jmeter-plugins-for-apache-dubbo > * go-for-apache-dubbo > * php-framework-for-apache-dubbo > * dotnet-for-apache-dubbo > * serialization-native-hessian-for-apache-dubbo > * jms-for-apache-dubbo > * dubbo.github.io > * metrics > * hessian-lite > * dubbo-sentinel-support > * awesome-dubbo > * dubbo-remoting-js > * egg-dubbo-rpc > * rpc-native-thrift-for-apache-dubbo > * intellij-idea-plugin > * initializr > > > If you are the project owner, could you please confirm that: > > 1) are you willing to transferred to ASF or not. > 2) if so, please give an estimated time when will you can finish transfer. > What you will need to do includes: > - Find the all the contributors and ask them to sign the Apache > ICLA[2], if the contribution is trivial, this can be ignore > - If the code belongs to your company, you need to sign the SGA[3] > - request ASF infra to transfer the project > 3) if not, please indicate that which group you will transfer to. > > 2. Gain write access to your project after transfer > > If your project has been transferred to ASF, you will lose write > access temporally. The Dubbo community will vote you in as committer > by following standard ASF way. This means you have to contribute to > the project for some time in order to earn enough merit. > > 3. After the transition is done, delete group A. > > The community will summarize and keep track of the status here[4]. > > > [1] https://en.wikipedia.org/wiki/Dubbo > [2] > http://dubbo.apache.org/en-us/docs/developers/contributor-guide/cla-signing-guide_dev.html > [3] > http://dubbo.apache.org/en-us/docs/developers/contributor-guide/software-donation-guide_dev.html > [4] > https://github.com/apache/incubator-dubbo/wiki/Apache-Dubbo-external-ecosystem-status > > > > -- > Best Regards！ > Huxing -- Best Regards！ Huxing
Re: Dubbo with Erlang language implementation.
Hi, Maybe it can modify the project name to erlang-for-apache-dubbo like other languages implemented(go,dotnet),and I am happy donate to ASF. If appropriate, I will continue to improve the project code to accommodate this change. Thanks > 在 2019年4月25日，09:34，Huxing Zhang 写道： > > Hi, > >> On Wed, Apr 24, 2019 at 5:05 PM Jun Liu wrote: >> >> I think the most preferable way would be to donate this erlang project to >> ASF directly. If put this project somewhere outside ASF, in this case >> https://github.com/dubbo, then we need to avoid using a name like >> ‘dubbo-erlang’, but use ‘erlang-for-dubbo’ or something like that. > > +1 to donate to ASF. The branding issue for dubbo group is still being > discussed. I think before that it is better not to add any new > project. > >> >> Ken >> >>> On Apr 24, 2019, at 2:17 PM, ShengXiao Xie wrote: >>> >>> I agree with your concerns. >>> It would be better to change it to dubbo-erlang and transfer to Dubbo group >>> first. >>> Maybe we can wait for a suitable time to transfer the project to ASF. >>> >>> @ >>> On Apr 24, 2019, at 12:42 PM, Justin Mclean wrote: Hi, > I agree to modify the project name to apache-dubbo-erlang. If it not hosted at the ASF then this may not be a suitable name. Thanks, Justin > > > -- > Best Regards！ > Huxing
Re: [DISCUSS] Migrating projects under dubbo group
> rpc-native-thrift-for-apache-dubbo This is going to be merged into incubator-dubbo: ETA is May 15. Eric Zhao 于2019年4月25日周四 下午7:43写道： > Hi, > > > How soon will to finish signing SGA? Could you please give an ETA? > > I've finished signing both the ICLA and SGA. Please check. > > > I can help to request the INFRA to transfer, I am thinking to group > them together. > > Thanks! > > > -- > Best Regards, > Eric > > Huxing Zhang 于2019年4月25日周四 下午5:37写道： > > > Hi, > > > > On Thu, Apr 25, 2019 at 5:28 PM Eric Zhao wrote: > > > > > > Hi there, > > > > > > I'm the author of dubbo-sentinel-support. I'd like to transfer the > > project > > > to ASF. > > > > > > 1) are you willing to transferred to ASF or not. > > > > > > Yes > > > > Nice. > > > > > > > > > 2) if so, please give an estimated time when will you can finish > > transfer. > > > > What you will need to do includes: > > > > - Find the all the contributors and ask them to sign the Apache > > > > ICLA[2], if the contribution is trivial, this can be ignore > > > > > > I'll sign the ICLA today. > > > > > > > > > - If the code belongs to your company, you need to sign the SGA[3] > > > > - request ASF infra to transfer the project > > > > How soon will to finish signing SGA? Could you please give an ETA? > > > > > > > > Seems that I don't have the permission to transfer the project. Could > you > > > please help me to transfer the project? > > > > I can help to request the INFRA to transfer, I am thinking to group > > them together. > > > > > > > > --- > > > Best Regards, > > > Eric > > > > > > Huxing Zhang 于2019年4月25日周四 下午4:25写道： > > > > > > > Hi, > > > > > > > > > > > > On Thu, Apr 25, 2019 at 4:02 PM Huxing Zhang > > wrote: > > > > > > > > > > Hi All, > > > > > > > > > > As is discussed in the graduation proposal in general@ mailing > list, > > > > > the github.com/dubbo group has some potential branding issue. To > > avoid > > > > > it completely, we need to decide the short-term plan and long-term > > > > > plan. > > > > > > > > > > For the short-term plan, there are two way proposed: > > > > > > > > > > 1. Rename dubbo group to another one, let's say A. > > > > > 2. Create a new group A, and migrate all the project to under A, > and > > > > > keep the dubbo group empty. The purpose is to avoid someone to > abuse > > > > > it in the future. > > > > > > > > > > I am leaning towards option 2. But I'd like to hear what other may > > think. > > > > > > > > > > The next step is to decide what A is. Actually naming a thing is > one > > > > > of the most difficult thing to do... I am trying to find something > > > > > related. I checked the wikipedia page for Dubbo[1], in the history > > > > > section, it says Dubbo is now thought to be a mispronunciation of > > the > > > > > local Wiradjuri word "Thubbo" or "Tubbo". > > > > > > > > > > I think thubbo and tubbo both are good. thubbo is more different to > > > > > dubbo than tubbo. So I prefer thubbo. How do you think? > > > > > > > > > > > > > > > For the long-term plan: > > > > > > > > > > 1. Like discussed before, all projects under group A are expected > to > > > > > be transferred to Apache (if the owner) agree with an ETA. I talked > > to > > > > > most of the owners and they basically agree, the multi-language > > > > > project are TODOs. I am trying to pull them onto list. > > > > > > > > > > This projects that still listed under dubbo group includes: > > > > > > > > > > * js-for-apache-dubbo > > > > > * py-client-for-apache-dubbo > > > > > * rpc-xmlrpc-for-apache-dubbo > > > > > * jmeter-plugins-for-apache-dubbo > > > > > * go-for-apache-dubbo > > > > > * php-framework-for-apache-dubbo > > > > > * dotnet-for-apache-dubbo > > > > > * serialization-native-hessian-for-apache-dubbo > > > > > * jms-for-apache-dubbo > > > > > * dubbo.github.io > > > > > > > > I suggest to redirect dubbo.io directly to dubbo.apache.org from DNS > > > > and remote this project. I think it can be done before May 31. > > > > > > > > > * metrics > > > > > > > > This project has no strong relation to Dubbo, I suggest to move it to > > > > alibaba group, I think it can be done before May 10. > > > > > > > > > * hessian-lite > > > > > > > > This project has no strong relation to Dubbo, I suggest to move it to > > > > alibaba group, I think it can be done before May 10. > > > > > > > > > * dubbo-sentinel-support > > > > > * awesome-dubbo > > > > > > > > I suggest to transfer to ASF, most of the contributors are Dubbo > PPMC. > > > > I think it can be done before May 31. > > > > > > > > > * dubbo-remoting-js > > > > > * egg-dubbo-rpc > > > > > * rpc-native-thrift-for-apache-dubbo > > > > > * intellij-idea-plugin > > > > > * initializr > > > > > > > > I suggest to go to ASF if license is OK, otherwise go to alibaba. > > > > Depending on the case, I think it can be done before May 31. > > > > > > > > > > > > > > > > > > > If you are the project owner, could you please confirm that: > > > > > > > > > > 1) are you willing to
Re: [DISCUSS] Migrating projects under dubbo group
Hi, > How soon will to finish signing SGA? Could you please give an ETA? I've finished signing both the ICLA and SGA. Please check. > I can help to request the INFRA to transfer, I am thinking to group them together. Thanks! -- Best Regards, Eric Huxing Zhang 于2019年4月25日周四 下午5:37写道： > Hi, > > On Thu, Apr 25, 2019 at 5:28 PM Eric Zhao wrote: > > > > Hi there, > > > > I'm the author of dubbo-sentinel-support. I'd like to transfer the > project > > to ASF. > > > > 1) are you willing to transferred to ASF or not. > > > > Yes > > Nice. > > > > > > 2) if so, please give an estimated time when will you can finish > transfer. > > > What you will need to do includes: > > > - Find the all the contributors and ask them to sign the Apache > > > ICLA[2], if the contribution is trivial, this can be ignore > > > > I'll sign the ICLA today. > > > > > > - If the code belongs to your company, you need to sign the SGA[3] > > > - request ASF infra to transfer the project > > How soon will to finish signing SGA? Could you please give an ETA? > > > > > Seems that I don't have the permission to transfer the project. Could you > > please help me to transfer the project? > > I can help to request the INFRA to transfer, I am thinking to group > them together. > > > > > --- > > Best Regards, > > Eric > > > > Huxing Zhang 于2019年4月25日周四 下午4:25写道： > > > > > Hi, > > > > > > > > > On Thu, Apr 25, 2019 at 4:02 PM Huxing Zhang > wrote: > > > > > > > > Hi All, > > > > > > > > As is discussed in the graduation proposal in general@ mailing list, > > > > the github.com/dubbo group has some potential branding issue. To > avoid > > > > it completely, we need to decide the short-term plan and long-term > > > > plan. > > > > > > > > For the short-term plan, there are two way proposed: > > > > > > > > 1. Rename dubbo group to another one, let's say A. > > > > 2. Create a new group A, and migrate all the project to under A, and > > > > keep the dubbo group empty. The purpose is to avoid someone to abuse > > > > it in the future. > > > > > > > > I am leaning towards option 2. But I'd like to hear what other may > think. > > > > > > > > The next step is to decide what A is. Actually naming a thing is one > > > > of the most difficult thing to do... I am trying to find something > > > > related. I checked the wikipedia page for Dubbo[1], in the history > > > > section, it says Dubbo is now thought to be a mispronunciation of > the > > > > local Wiradjuri word "Thubbo" or "Tubbo". > > > > > > > > I think thubbo and tubbo both are good. thubbo is more different to > > > > dubbo than tubbo. So I prefer thubbo. How do you think? > > > > > > > > > > > > For the long-term plan: > > > > > > > > 1. Like discussed before, all projects under group A are expected to > > > > be transferred to Apache (if the owner) agree with an ETA. I talked > to > > > > most of the owners and they basically agree, the multi-language > > > > project are TODOs. I am trying to pull them onto list. > > > > > > > > This projects that still listed under dubbo group includes: > > > > > > > > * js-for-apache-dubbo > > > > * py-client-for-apache-dubbo > > > > * rpc-xmlrpc-for-apache-dubbo > > > > * jmeter-plugins-for-apache-dubbo > > > > * go-for-apache-dubbo > > > > * php-framework-for-apache-dubbo > > > > * dotnet-for-apache-dubbo > > > > * serialization-native-hessian-for-apache-dubbo > > > > * jms-for-apache-dubbo > > > > * dubbo.github.io > > > > > > I suggest to redirect dubbo.io directly to dubbo.apache.org from DNS > > > and remote this project. I think it can be done before May 31. > > > > > > > * metrics > > > > > > This project has no strong relation to Dubbo, I suggest to move it to > > > alibaba group, I think it can be done before May 10. > > > > > > > * hessian-lite > > > > > > This project has no strong relation to Dubbo, I suggest to move it to > > > alibaba group, I think it can be done before May 10. > > > > > > > * dubbo-sentinel-support > > > > * awesome-dubbo > > > > > > I suggest to transfer to ASF, most of the contributors are Dubbo PPMC. > > > I think it can be done before May 31. > > > > > > > * dubbo-remoting-js > > > > * egg-dubbo-rpc > > > > * rpc-native-thrift-for-apache-dubbo > > > > * intellij-idea-plugin > > > > * initializr > > > > > > I suggest to go to ASF if license is OK, otherwise go to alibaba. > > > Depending on the case, I think it can be done before May 31. > > > > > > > > > > > > > > > If you are the project owner, could you please confirm that: > > > > > > > > 1) are you willing to transferred to ASF or not. > > > > 2) if so, please give an estimated time when will you can finish > > > transfer. > > > > What you will need to do includes: > > > > - Find the all the contributors and ask them to sign the Apache > > > > ICLA[2], if the contribution is trivial, this can be ignore > > > > - If the code belongs to your company, you need to sign the SGA[3] > > > > - request ASF infra to transfer the project > > > > 3) if not, please
Re: [DISCUSS] Migrating projects under dubbo group
Hi all, I am the author of go-for-apache-dubbo 1) are you willing to transferred to ASF or not. Yes 2) if so, please give an estimated time when will you can finish transfer. What you will need to do includes: - Find the all the contributors and ask them to sign the Apache ICLA[2], if the contribution is trivial, this can be ignore - If the code belongs to your company, you need to sign the SGA[3] - request ASF infra to transfer the project 3) if not, please indicate that which group you will transfer to. Maybe two weeks. 原始邮件 发件人: hufeng 收件人: dev 发送时间: 2019年4月25日(周四) 17:00 主题: Re: [DISCUSS] Migrating projects under dubbo group On 2019/04/25 08:02:11, Huxing Zhang mailto:h...@apache.org>> wrote: > Hi All,> > > As is discussed in the graduation proposal in general@ mailing list,> > the github.com/dubbo group has some potential branding issue. To avoid> > it completely, we need to decide the short-term plan and long-term> > plan.> > > For the short-term plan, there are two way proposed:> > > 1. Rename dubbo group to another one, let's say A.> > 2. Create a new group A, and migrate all the project to under A, and> > keep the dubbo group empty. The purpose is to avoid someone to abuse> > it in the future.> > > I am leaning towards option 2. But I'd like to hear what other may think.> > > The next step is to decide what A is. Actually naming a thing is one> > of the most difficult thing to do... I am trying to find something> > related. I checked the wikipedia page for Dubbo[1], in the history> > section, it says Dubbo is now thought to be a mispronunciation of the> > local Wiradjuri word "Thubbo" or "Tubbo".> > > I think thubbo and tubbo both are good. thubbo is more different to> > dubbo than tubbo. So I prefer thubbo. How do you think?> > > > For the long-term plan:> > > 1. Like discussed before, all projects under group A are expected to> > be transferred to Apache (if the owner) agree with an ETA. I talked to> > most of the owners and they basically agree, the multi-language> > project are TODOs. I am trying to pull them onto list.> > > This projects that still listed under dubbo group includes:> > > * js-for-apache-dubbo> > * py-client-for-apache-dubbo> > * rpc-xmlrpc-for-apache-dubbo> > * jmeter-plugins-for-apache-dubbo> > * go-for-apache-dubbo> > * php-framework-for-apache-dubbo> > * dotnet-for-apache-dubbo> > * serialization-native-hessian-for-apache-dubbo> > * jms-for-apache-dubbo> > * dubbo.github.io> > * metrics> > * hessian-lite> > * dubbo-sentinel-support> > * awesome-dubbo> > * dubbo-remoting-js> > * egg-dubbo-rpc> > * rpc-native-thrift-for-apache-dubbo> > * intellij-idea-plugin> > * initializr> > > > If you are the project owner, could you please confirm that:> > > 1) are you willing to transferred to ASF or not.> > 2) if so, please give an estimated time when will you can finish transfer.> > What you will need to do includes:> > - Find the all the contributors and ask them to sign the Apache> > ICLA[2], if the contribution is trivial, this can be ignore> > - If the code belongs to your company, you need to sign the SGA[3]> > - request ASF infra to transfer the project> > 3) if not, please indicate that which group you will transfer to.> > > 2. Gain write access to your project after transfer> > > If your project has been transferred to ASF, you will lose write> > access temporally. The Dubbo community will vote you in as committer> > by following standard ASF way. This means you have to contribute to> > the project for some time in order to earn enough merit.> > > 3. After the transition is done, delete group A.> > > The community will summarize and keep track of the status here[4].> > > > [1] https://en.wikipedia.org/wiki/Dubbo> > [2] > http://dubbo.apache.org/en-us/docs/developers/contributor-guide/cla-signing-guide_dev.html> > [3] > http://dubbo.apache.org/en-us/docs/developers/contributor-guide/software-donation-guide_dev.html> > [4] > https://github.com/apache/incubator-dubbo/wiki/Apache-Dubbo-external-ecosystem-status> > > > > -- > > Best Regards！> > Huxing> >
Re: [DISCUSS] Migrating projects under dubbo group
Hi, > * rpc-xmlrpc-for-apache-dubbo This is going to be merged into incubator-dubbo: https://github.com/apache/incubator-dubbo/pull/3775 ETA is May 10. -- Best Regards！ Huxing
Re: [DISCUSS] Migrating projects under dubbo group
Hi, On Thu, Apr 25, 2019 at 5:28 PM Eric Zhao wrote: > > Hi there, > > I'm the author of dubbo-sentinel-support. I'd like to transfer the project > to ASF. > > 1) are you willing to transferred to ASF or not. > > Yes Nice. > > > 2) if so, please give an estimated time when will you can finish transfer. > > What you will need to do includes: > > - Find the all the contributors and ask them to sign the Apache > > ICLA[2], if the contribution is trivial, this can be ignore > > I'll sign the ICLA today. > > > - If the code belongs to your company, you need to sign the SGA[3] > > - request ASF infra to transfer the project How soon will to finish signing SGA? Could you please give an ETA? > > Seems that I don't have the permission to transfer the project. Could you > please help me to transfer the project? I can help to request the INFRA to transfer, I am thinking to group them together. > > --- > Best Regards, > Eric > > Huxing Zhang 于2019年4月25日周四 下午4:25写道： > > > Hi, > > > > > > On Thu, Apr 25, 2019 at 4:02 PM Huxing Zhang wrote: > > > > > > Hi All, > > > > > > As is discussed in the graduation proposal in general@ mailing list, > > > the github.com/dubbo group has some potential branding issue. To avoid > > > it completely, we need to decide the short-term plan and long-term > > > plan. > > > > > > For the short-term plan, there are two way proposed: > > > > > > 1. Rename dubbo group to another one, let's say A. > > > 2. Create a new group A, and migrate all the project to under A, and > > > keep the dubbo group empty. The purpose is to avoid someone to abuse > > > it in the future. > > > > > > I am leaning towards option 2. But I'd like to hear what other may think. > > > > > > The next step is to decide what A is. Actually naming a thing is one > > > of the most difficult thing to do... I am trying to find something > > > related. I checked the wikipedia page for Dubbo[1], in the history > > > section, it says Dubbo is now thought to be a mispronunciation of the > > > local Wiradjuri word "Thubbo" or "Tubbo". > > > > > > I think thubbo and tubbo both are good. thubbo is more different to > > > dubbo than tubbo. So I prefer thubbo. How do you think? > > > > > > > > > For the long-term plan: > > > > > > 1. Like discussed before, all projects under group A are expected to > > > be transferred to Apache (if the owner) agree with an ETA. I talked to > > > most of the owners and they basically agree, the multi-language > > > project are TODOs. I am trying to pull them onto list. > > > > > > This projects that still listed under dubbo group includes: > > > > > > * js-for-apache-dubbo > > > * py-client-for-apache-dubbo > > > * rpc-xmlrpc-for-apache-dubbo > > > * jmeter-plugins-for-apache-dubbo > > > * go-for-apache-dubbo > > > * php-framework-for-apache-dubbo > > > * dotnet-for-apache-dubbo > > > * serialization-native-hessian-for-apache-dubbo > > > * jms-for-apache-dubbo > > > * dubbo.github.io > > > > I suggest to redirect dubbo.io directly to dubbo.apache.org from DNS > > and remote this project. I think it can be done before May 31. > > > > > * metrics > > > > This project has no strong relation to Dubbo, I suggest to move it to > > alibaba group, I think it can be done before May 10. > > > > > * hessian-lite > > > > This project has no strong relation to Dubbo, I suggest to move it to > > alibaba group, I think it can be done before May 10. > > > > > * dubbo-sentinel-support > > > * awesome-dubbo > > > > I suggest to transfer to ASF, most of the contributors are Dubbo PPMC. > > I think it can be done before May 31. > > > > > * dubbo-remoting-js > > > * egg-dubbo-rpc > > > * rpc-native-thrift-for-apache-dubbo > > > * intellij-idea-plugin > > > * initializr > > > > I suggest to go to ASF if license is OK, otherwise go to alibaba. > > Depending on the case, I think it can be done before May 31. > > > > > > > > > > > If you are the project owner, could you please confirm that: > > > > > > 1) are you willing to transferred to ASF or not. > > > 2) if so, please give an estimated time when will you can finish > > transfer. > > > What you will need to do includes: > > > - Find the all the contributors and ask them to sign the Apache > > > ICLA[2], if the contribution is trivial, this can be ignore > > > - If the code belongs to your company, you need to sign the SGA[3] > > > - request ASF infra to transfer the project > > > 3) if not, please indicate that which group you will transfer to. > > > > > > 2. Gain write access to your project after transfer > > > > > > If your project has been transferred to ASF, you will lose write > > > access temporally. The Dubbo community will vote you in as committer > > > by following standard ASF way. This means you have to contribute to > > > the project for some time in order to earn enough merit. > > > > > > 3. After the transition is done, delete group A. > > > > > > The community will summarize and keep track of the status here[4]. > > > > > > > > > [1]
Re: [DISCUSS] Migrating projects under dubbo group
Hi there, I'm the author of dubbo-sentinel-support. I'd like to transfer the project to ASF. 1) are you willing to transferred to ASF or not. Yes > 2) if so, please give an estimated time when will you can finish transfer. > What you will need to do includes: > - Find the all the contributors and ask them to sign the Apache > ICLA[2], if the contribution is trivial, this can be ignore I'll sign the ICLA today. > - If the code belongs to your company, you need to sign the SGA[3] > - request ASF infra to transfer the project Seems that I don't have the permission to transfer the project. Could you please help me to transfer the project? --- Best Regards, Eric Huxing Zhang 于2019年4月25日周四 下午4:25写道： > Hi, > > > On Thu, Apr 25, 2019 at 4:02 PM Huxing Zhang wrote: > > > > Hi All, > > > > As is discussed in the graduation proposal in general@ mailing list, > > the github.com/dubbo group has some potential branding issue. To avoid > > it completely, we need to decide the short-term plan and long-term > > plan. > > > > For the short-term plan, there are two way proposed: > > > > 1. Rename dubbo group to another one, let's say A. > > 2. Create a new group A, and migrate all the project to under A, and > > keep the dubbo group empty. The purpose is to avoid someone to abuse > > it in the future. > > > > I am leaning towards option 2. But I'd like to hear what other may think. > > > > The next step is to decide what A is. Actually naming a thing is one > > of the most difficult thing to do... I am trying to find something > > related. I checked the wikipedia page for Dubbo[1], in the history > > section, it says Dubbo is now thought to be a mispronunciation of the > > local Wiradjuri word "Thubbo" or "Tubbo". > > > > I think thubbo and tubbo both are good. thubbo is more different to > > dubbo than tubbo. So I prefer thubbo. How do you think? > > > > > > For the long-term plan: > > > > 1. Like discussed before, all projects under group A are expected to > > be transferred to Apache (if the owner) agree with an ETA. I talked to > > most of the owners and they basically agree, the multi-language > > project are TODOs. I am trying to pull them onto list. > > > > This projects that still listed under dubbo group includes: > > > > * js-for-apache-dubbo > > * py-client-for-apache-dubbo > > * rpc-xmlrpc-for-apache-dubbo > > * jmeter-plugins-for-apache-dubbo > > * go-for-apache-dubbo > > * php-framework-for-apache-dubbo > > * dotnet-for-apache-dubbo > > * serialization-native-hessian-for-apache-dubbo > > * jms-for-apache-dubbo > > * dubbo.github.io > > I suggest to redirect dubbo.io directly to dubbo.apache.org from DNS > and remote this project. I think it can be done before May 31. > > > * metrics > > This project has no strong relation to Dubbo, I suggest to move it to > alibaba group, I think it can be done before May 10. > > > * hessian-lite > > This project has no strong relation to Dubbo, I suggest to move it to > alibaba group, I think it can be done before May 10. > > > * dubbo-sentinel-support > > * awesome-dubbo > > I suggest to transfer to ASF, most of the contributors are Dubbo PPMC. > I think it can be done before May 31. > > > * dubbo-remoting-js > > * egg-dubbo-rpc > > * rpc-native-thrift-for-apache-dubbo > > * intellij-idea-plugin > > * initializr > > I suggest to go to ASF if license is OK, otherwise go to alibaba. > Depending on the case, I think it can be done before May 31. > > > > > > > If you are the project owner, could you please confirm that: > > > > 1) are you willing to transferred to ASF or not. > > 2) if so, please give an estimated time when will you can finish > transfer. > > What you will need to do includes: > > - Find the all the contributors and ask them to sign the Apache > > ICLA[2], if the contribution is trivial, this can be ignore > > - If the code belongs to your company, you need to sign the SGA[3] > > - request ASF infra to transfer the project > > 3) if not, please indicate that which group you will transfer to. > > > > 2. Gain write access to your project after transfer > > > > If your project has been transferred to ASF, you will lose write > > access temporally. The Dubbo community will vote you in as committer > > by following standard ASF way. This means you have to contribute to > > the project for some time in order to earn enough merit. > > > > 3. After the transition is done, delete group A. > > > > The community will summarize and keep track of the status here[4]. > > > > > > [1] https://en.wikipedia.org/wiki/Dubbo > > [2] > http://dubbo.apache.org/en-us/docs/developers/contributor-guide/cla-signing-guide_dev.html > > [3] > http://dubbo.apache.org/en-us/docs/developers/contributor-guide/software-donation-guide_dev.html > > [4] > https://github.com/apache/incubator-dubbo/wiki/Apache-Dubbo-external-ecosystem-status > > > > > > > > -- > > Best Regards！ > > Huxing > > > > -- > Best Regards！ > Huxing >
Re: [DISCUSS] Migrating projects under dubbo group
for hessian-lite, we could transfer it to ASF and rename it as dubbo-hessian-lite. -Ian. On Thu, Apr 25, 2019 at 5:24 PM Huxing Zhang wrote: > Hi, > > On Thu, Apr 25, 2019 at 5:00 PM Justin Mclean wrote: > > > > Hi, > > > > >> * metrics > > >> * hessian-lite > > > > Didn’t both of these already get transferred to the ASF? > > metrics is not transferred. > hessian-lite is separated from incubator-dubbo. Yes it is transferred > before. Is it a problem? > If it is required, no object to transfer to ASF. Assuming no IP > issues, the transfer should be quick. May 10 looks good. > If transfer to ASF, then things need to be done, like package rename > from com.alibaba to org.apache, etc. > Does other project other than Dubbo depend on it? > > > > > > Thanks, > > Justin > > > > -- > Best Regards！ > Huxing >
Re: [DISCUSS] Migrating projects under dubbo group
Hi, On Thu, Apr 25, 2019 at 5:00 PM Justin Mclean wrote: > > Hi, > > >> * metrics > >> * hessian-lite > > Didn’t both of these already get transferred to the ASF? metrics is not transferred. hessian-lite is separated from incubator-dubbo. Yes it is transferred before. Is it a problem? If it is required, no object to transfer to ASF. Assuming no IP issues, the transfer should be quick. May 10 looks good. If transfer to ASF, then things need to be done, like package rename from com.alibaba to org.apache, etc. Does other project other than Dubbo depend on it? > > Thanks, > Justin -- Best Regards！ Huxing
Re: [DISCUSS] Migrating projects under dubbo group
+1 to the proposal. On Thu, Apr 25, 2019 at 4:25 PM Huxing Zhang wrote: > Hi, > > > On Thu, Apr 25, 2019 at 4:02 PM Huxing Zhang wrote: > > > > Hi All, > > > > As is discussed in the graduation proposal in general@ mailing list, > > the github.com/dubbo group has some potential branding issue. To avoid > > it completely, we need to decide the short-term plan and long-term > > plan. > > > > For the short-term plan, there are two way proposed: > > > > 1. Rename dubbo group to another one, let's say A. > > 2. Create a new group A, and migrate all the project to under A, and > > keep the dubbo group empty. The purpose is to avoid someone to abuse > > it in the future. > > > > I am leaning towards option 2. But I'd like to hear what other may think. > > > > The next step is to decide what A is. Actually naming a thing is one > > of the most difficult thing to do... I am trying to find something > > related. I checked the wikipedia page for Dubbo[1], in the history > > section, it says Dubbo is now thought to be a mispronunciation of the > > local Wiradjuri word "Thubbo" or "Tubbo". > > > > I think thubbo and tubbo both are good. thubbo is more different to > > dubbo than tubbo. So I prefer thubbo. How do you think? > > > > > > For the long-term plan: > > > > 1. Like discussed before, all projects under group A are expected to > > be transferred to Apache (if the owner) agree with an ETA. I talked to > > most of the owners and they basically agree, the multi-language > > project are TODOs. I am trying to pull them onto list. > > > > This projects that still listed under dubbo group includes: > > > > * js-for-apache-dubbo > > * py-client-for-apache-dubbo > > * rpc-xmlrpc-for-apache-dubbo > > * jmeter-plugins-for-apache-dubbo > > * go-for-apache-dubbo > > * php-framework-for-apache-dubbo > > * dotnet-for-apache-dubbo > > * serialization-native-hessian-for-apache-dubbo > > * jms-for-apache-dubbo > > * dubbo.github.io > > I suggest to redirect dubbo.io directly to dubbo.apache.org from DNS > and remote this project. I think it can be done before May 31. > > > * metrics > > This project has no strong relation to Dubbo, I suggest to move it to > alibaba group, I think it can be done before May 10. > > > * hessian-lite > > This project has no strong relation to Dubbo, I suggest to move it to > alibaba group, I think it can be done before May 10. > > > * dubbo-sentinel-support > > * awesome-dubbo > > I suggest to transfer to ASF, most of the contributors are Dubbo PPMC. > I think it can be done before May 31. > > > * dubbo-remoting-js > > * egg-dubbo-rpc > > * rpc-native-thrift-for-apache-dubbo > > * intellij-idea-plugin > > * initializr > > I suggest to go to ASF if license is OK, otherwise go to alibaba. > Depending on the case, I think it can be done before May 31. > > > > > > > If you are the project owner, could you please confirm that: > > > > 1) are you willing to transferred to ASF or not. > > 2) if so, please give an estimated time when will you can finish > transfer. > > What you will need to do includes: > > - Find the all the contributors and ask them to sign the Apache > > ICLA[2], if the contribution is trivial, this can be ignore > > - If the code belongs to your company, you need to sign the SGA[3] > > - request ASF infra to transfer the project > > 3) if not, please indicate that which group you will transfer to. > > > > 2. Gain write access to your project after transfer > > > > If your project has been transferred to ASF, you will lose write > > access temporally. The Dubbo community will vote you in as committer > > by following standard ASF way. This means you have to contribute to > > the project for some time in order to earn enough merit. > > > > 3. After the transition is done, delete group A. > > > > The community will summarize and keep track of the status here[4]. > > > > > > [1] https://en.wikipedia.org/wiki/Dubbo > > [2] > http://dubbo.apache.org/en-us/docs/developers/contributor-guide/cla-signing-guide_dev.html > > [3] > http://dubbo.apache.org/en-us/docs/developers/contributor-guide/software-donation-guide_dev.html > > [4] > https://github.com/apache/incubator-dubbo/wiki/Apache-Dubbo-external-ecosystem-status > > > > > > > > -- > > Best Regards！ > > Huxing > > > > -- > Best Regards！ > Huxing >
Re: [DISCUSS] Migrating projects under dubbo group
Hi all, I am the author of js-for-apache-dubbo 1) are you willing to transferred to ASF or not. Yes 2) if so, please give an estimated time when will you can finish transfer. What you will need to do includes: - Find the all the contributors and ask them to sign the Apache ICLA[2], if the contribution is trivial, this can be ignore - If the code belongs to your company, you need to sign the SGA[3] - request ASF infra to transfer the project 3) if not, please indicate that which group you will transfer to. Maybe two weeks. On 2019/04/25 08:02:11, Huxing Zhang wrote: > Hi All,> > > As is discussed in the graduation proposal in general@ mailing list,> > the github.com/dubbo group has some potential branding issue. To avoid> > it completely, we need to decide the short-term plan and long-term> > plan.> > > For the short-term plan, there are two way proposed:> > > 1. Rename dubbo group to another one, let's say A.> > 2. Create a new group A, and migrate all the project to under A, and> > keep the dubbo group empty. The purpose is to avoid someone to abuse> > it in the future.> > > I am leaning towards option 2. But I'd like to hear what other may think.> > > The next step is to decide what A is. Actually naming a thing is one> > of the most difficult thing to do... I am trying to find something> > related. I checked the wikipedia page for Dubbo[1], in the history> > section, it says Dubbo is now thought to be a mispronunciation of the> > local Wiradjuri word "Thubbo" or "Tubbo".> > > I think thubbo and tubbo both are good. thubbo is more different to> > dubbo than tubbo. So I prefer thubbo. How do you think?> > > > For the long-term plan:> > > 1. Like discussed before, all projects under group A are expected to> > be transferred to Apache (if the owner) agree with an ETA. I talked to> > most of the owners and they basically agree, the multi-language> > project are TODOs. I am trying to pull them onto list.> > > This projects that still listed under dubbo group includes:> > > * js-for-apache-dubbo> > * py-client-for-apache-dubbo> > * rpc-xmlrpc-for-apache-dubbo> > * jmeter-plugins-for-apache-dubbo> > * go-for-apache-dubbo> > * php-framework-for-apache-dubbo> > * dotnet-for-apache-dubbo> > * serialization-native-hessian-for-apache-dubbo> > * jms-for-apache-dubbo> > * dubbo.github.io> > * metrics> > * hessian-lite> > * dubbo-sentinel-support> > * awesome-dubbo> > * dubbo-remoting-js> > * egg-dubbo-rpc> > * rpc-native-thrift-for-apache-dubbo> > * intellij-idea-plugin> > * initializr> > > > If you are the project owner, could you please confirm that:> > > 1) are you willing to transferred to ASF or not.> > 2) if so, please give an estimated time when will you can finish transfer.> > What you will need to do includes:> > - Find the all the contributors and ask them to sign the Apache> > ICLA[2], if the contribution is trivial, this can be ignore> > - If the code belongs to your company, you need to sign the SGA[3]> > - request ASF infra to transfer the project> > 3) if not, please indicate that which group you will transfer to.> > > 2. Gain write access to your project after transfer> > > If your project has been transferred to ASF, you will lose write> > access temporally. The Dubbo community will vote you in as committer> > by following standard ASF way. This means you have to contribute to> > the project for some time in order to earn enough merit.> > > 3. After the transition is done, delete group A.> > > The community will summarize and keep track of the status here[4].> > > > [1] https://en.wikipedia.org/wiki/Dubbo> > [2] > http://dubbo.apache.org/en-us/docs/developers/contributor-guide/cla-signing-guide_dev.html> > > [3] > http://dubbo.apache.org/en-us/docs/developers/contributor-guide/software-donation-guide_dev.html> > > [4] > https://github.com/apache/incubator-dubbo/wiki/Apache-Dubbo-external-ecosystem-status> > > > > > -- > > Best Regards！> > Huxing> >
Re: [DISCUSS] Migrating projects under dubbo group
Hi, >> * metrics >> * hessian-lite Didn’t both of these already get transferred to the ASF? Thanks, Justin
Re: [DISCUSS] Migrating projects under dubbo group
Hi, On Thu, Apr 25, 2019 at 4:02 PM Huxing Zhang wrote: > > Hi All, > > As is discussed in the graduation proposal in general@ mailing list, > the github.com/dubbo group has some potential branding issue. To avoid > it completely, we need to decide the short-term plan and long-term > plan. > > For the short-term plan, there are two way proposed: > > 1. Rename dubbo group to another one, let's say A. > 2. Create a new group A, and migrate all the project to under A, and > keep the dubbo group empty. The purpose is to avoid someone to abuse > it in the future. > > I am leaning towards option 2. But I'd like to hear what other may think. > > The next step is to decide what A is. Actually naming a thing is one > of the most difficult thing to do... I am trying to find something > related. I checked the wikipedia page for Dubbo[1], in the history > section, it says Dubbo is now thought to be a mispronunciation of the > local Wiradjuri word "Thubbo" or "Tubbo". > > I think thubbo and tubbo both are good. thubbo is more different to > dubbo than tubbo. So I prefer thubbo. How do you think? > > > For the long-term plan: > > 1. Like discussed before, all projects under group A are expected to > be transferred to Apache (if the owner) agree with an ETA. I talked to > most of the owners and they basically agree, the multi-language > project are TODOs. I am trying to pull them onto list. > > This projects that still listed under dubbo group includes: > > * js-for-apache-dubbo > * py-client-for-apache-dubbo > * rpc-xmlrpc-for-apache-dubbo > * jmeter-plugins-for-apache-dubbo > * go-for-apache-dubbo > * php-framework-for-apache-dubbo > * dotnet-for-apache-dubbo > * serialization-native-hessian-for-apache-dubbo > * jms-for-apache-dubbo > * dubbo.github.io I suggest to redirect dubbo.io directly to dubbo.apache.org from DNS and remote this project. I think it can be done before May 31. > * metrics This project has no strong relation to Dubbo, I suggest to move it to alibaba group, I think it can be done before May 10. > * hessian-lite This project has no strong relation to Dubbo, I suggest to move it to alibaba group, I think it can be done before May 10. > * dubbo-sentinel-support > * awesome-dubbo I suggest to transfer to ASF, most of the contributors are Dubbo PPMC. I think it can be done before May 31. > * dubbo-remoting-js > * egg-dubbo-rpc > * rpc-native-thrift-for-apache-dubbo > * intellij-idea-plugin > * initializr I suggest to go to ASF if license is OK, otherwise go to alibaba. Depending on the case, I think it can be done before May 31. > > > If you are the project owner, could you please confirm that: > > 1) are you willing to transferred to ASF or not. > 2) if so, please give an estimated time when will you can finish transfer. > What you will need to do includes: > - Find the all the contributors and ask them to sign the Apache > ICLA[2], if the contribution is trivial, this can be ignore > - If the code belongs to your company, you need to sign the SGA[3] > - request ASF infra to transfer the project > 3) if not, please indicate that which group you will transfer to. > > 2. Gain write access to your project after transfer > > If your project has been transferred to ASF, you will lose write > access temporally. The Dubbo community will vote you in as committer > by following standard ASF way. This means you have to contribute to > the project for some time in order to earn enough merit. > > 3. After the transition is done, delete group A. > > The community will summarize and keep track of the status here[4]. > > > [1] https://en.wikipedia.org/wiki/Dubbo > [2] > http://dubbo.apache.org/en-us/docs/developers/contributor-guide/cla-signing-guide_dev.html > [3] > http://dubbo.apache.org/en-us/docs/developers/contributor-guide/software-donation-guide_dev.html > [4] > https://github.com/apache/incubator-dubbo/wiki/Apache-Dubbo-external-ecosystem-status > > > > -- > Best Regards！ > Huxing -- Best Regards！ Huxing
[DISCUSS] Migrating projects under dubbo group
Hi All, As is discussed in the graduation proposal in general@ mailing list, the github.com/dubbo group has some potential branding issue. To avoid it completely, we need to decide the short-term plan and long-term plan. For the short-term plan, there are two way proposed: 1. Rename dubbo group to another one, let's say A. 2. Create a new group A, and migrate all the project to under A, and keep the dubbo group empty. The purpose is to avoid someone to abuse it in the future. I am leaning towards option 2. But I'd like to hear what other may think. The next step is to decide what A is. Actually naming a thing is one of the most difficult thing to do... I am trying to find something related. I checked the wikipedia page for Dubbo[1], in the history section, it says Dubbo is now thought to be a mispronunciation of the local Wiradjuri word "Thubbo" or "Tubbo". I think thubbo and tubbo both are good. thubbo is more different to dubbo than tubbo. So I prefer thubbo. How do you think? For the long-term plan: 1. Like discussed before, all projects under group A are expected to be transferred to Apache (if the owner) agree with an ETA. I talked to most of the owners and they basically agree, the multi-language project are TODOs. I am trying to pull them onto list. This projects that still listed under dubbo group includes: * js-for-apache-dubbo * py-client-for-apache-dubbo * rpc-xmlrpc-for-apache-dubbo * jmeter-plugins-for-apache-dubbo * go-for-apache-dubbo * php-framework-for-apache-dubbo * dotnet-for-apache-dubbo * serialization-native-hessian-for-apache-dubbo * jms-for-apache-dubbo * dubbo.github.io * metrics * hessian-lite * dubbo-sentinel-support * awesome-dubbo * dubbo-remoting-js * egg-dubbo-rpc * rpc-native-thrift-for-apache-dubbo * intellij-idea-plugin * initializr If you are the project owner, could you please confirm that: 1) are you willing to transferred to ASF or not. 2) if so, please give an estimated time when will you can finish transfer. What you will need to do includes: - Find the all the contributors and ask them to sign the Apache ICLA[2], if the contribution is trivial, this can be ignore - If the code belongs to your company, you need to sign the SGA[3] - request ASF infra to transfer the project 3) if not, please indicate that which group you will transfer to. 2. Gain write access to your project after transfer If your project has been transferred to ASF, you will lose write access temporally. The Dubbo community will vote you in as committer by following standard ASF way. This means you have to contribute to the project for some time in order to earn enough merit. 3. After the transition is done, delete group A. The community will summarize and keep track of the status here[4]. [1] https://en.wikipedia.org/wiki/Dubbo [2] http://dubbo.apache.org/en-us/docs/developers/contributor-guide/cla-signing-guide_dev.html [3] http://dubbo.apache.org/en-us/docs/developers/contributor-guide/software-donation-guide_dev.html [4] https://github.com/apache/incubator-dubbo/wiki/Apache-Dubbo-external-ecosystem-status -- Best Regards！ Huxing
Re: [DISCUSS] Graduate Apache Dubbo (incubating) as a Top Level Project
Hi, On Thu, Apr 25, 2019 at 2:10 PM Ian Luo wrote: > > Dave & Others, > > This "3rd party" site (https://github.com/dubbo) is used for building > Dubbo's eco-system. Just as you said, It contains both the projects which > will be donated and which may not, so the final goal for this "3rd party" > site is pretty clear: it will contain and only contain projects won't > donate, and if there's no project left eventually, this site does not > necessarily exist. > > What we're doing now is to solve the potential branding issues, in order to > answer the challenges from whom wearing the trademark committee hat. It is > an ad-hoc actions since we need to solve this particular issue as quickly > as possible. Here're what we are doing as short-term actions: > > 1. Rename dubbo group to other name. - not yet Or create a new group and move all the projects to it, left dubbo as an empty group. (The purpose is just to ensure nobody is trying to abuse it) > 2. Stop using Dubbo logo as group's avatar - done > 3. Rename all project names in compliance with the policies - ongoing +1 > > > At the same time, I strongly agree with what Dave suggested for the long > run plan. Here's what I propose (certainly this plan needs to be vote in > dubbo's mailing list): > > 1. All projects will be transferred to Apache group with ETA I will try to discuss this with the project owners and Dubbo community to work out a ETA. > 2. After that, all members in this group will be join Apache if they are > willing to (after they go through the vote certainly) As long as the project is under ASF, anyone can become committer by earning enough merit. > 3. After the transition is done, this particular group will be deleted +1. > > I will init the vote for the long term plan in dubbo's community today, and > we will get back with the concrete transition plan with ETA to the board > meeting as soon as possible. I hope we can satisfy the IPMC by doing this. > Pls. let me know if this is sufficient. We can adjust the plan if any > further suggestion comes up. I think the Dubbo community can deliver an improved version of [1] to IPMC, by filling all the blanks and with a new column ETA. [1] https://github.com/apache/incubator-dubbo/wiki/Apache-Dubbo-external-ecosystem-status > > Regards, > -Ian. > > > On Thu, Apr 25, 2019 at 12:29 AM Dave Fisher wrote: > > > Hi - > > > > (With trademark committee hat) > > > > Trademark resources can all be found from here: > > Trademark resources sitemap: > > http://www.apache.org/foundation/marks/resources > > PMC responsibility: http://www.apache.org/foundation/marks/responsibility > > Improper third party uses: > > http://www.apache.org/foundation/marks/responsibility#police > > Formal policy: http://www.apache.org/foundation/marks/ > > > > I don’t think that there is a formal policy to handle the situation where > > a transitional, "3rd party” site controlled by the PMC exists that will be > > phased out. Generally trademarks is looking for that PMC to be working with > > and engaging 3rd parties to fix any branding issues. > > > > I think it is important to know what the goal is for the "3rd party" site > > is and when that will be achieved. > > > > (Dubbo mentor hat) > > > > I think that rather than quickly responding by fixing various issues in an > > ad hoc manner it would be good to present the long term plan and then agree > > on the needed language on the “3rd party site” > > > > For example, the treatment of “product” that will be donated into the > > project codebase differs from “product” that won’t be. The “for Apache > > Dubbo” makes no sense for product that will be moved into Dubbo. > > > > The next board meeting is May 15th and there is time to carefully address > > the plan to the satisfaction of the IPMC. > > > > Regards, > > Dave > > > > > On Apr 24, 2019, at 8:51 AM, Sheng Wu wrote: > > > > > > Hi > > > > > >> Could somebody point me to Apache documentation that indicates that > > > such use of names of Apache projects is not ok? I might need that > > > information soon-ish myself, thanks. > > > > > > I used to read this from incubator discussions. Zipkin and SkyWalking > > were > > > facing that question. Could someone help about this? > > > > > > Sheng Wu 吴晟 > > > > > > Apache SkyWalking, ShardingSphere, Zipkin > > > Twitter, wusheng1108 > > > > > > > > > Jan Piotrowski 于2019年4月24日周三 下午11:29写道： > > > > > >> Semi OT: > > >> Could somebody point me to Apache documentation that indicates that > > >> such use of names of Apache projects is not ok? I might need that > > >> information soon-ish myself, thanks. > > >> > > >> -J > > >> > > >> Am Mi., 24. Apr. 2019 um 17:07 Uhr schrieb Sheng Wu < > > >> wu.sheng.841...@gmail.com>: > > >>> > > >>> Hi, > > >>> > > >>> 4. We plan to rename all projects in this organization to > > xxx-for-apache-dubbo > > >>> > > >>> The rename makes sense for ecosystem projects, especially for these > > >> three. > > >>> I also used to see the
Re: [DISS] Some thoughts on some trends Dubbo should follow.
I didn't thought in a roadmap level when bringing up this discussion, but I agree with you for the community to reach a consensus on this year’s roadmap. I can help to draft one based on my knowledge and understanding of this project, hopefully it can serve as a basis for people to present different opinions. For the HTTP/2 support and Cloud Native proposals, I am still working them, they should be available in a few days. Ken > On Apr 22, 2019, at 1:49 PM, Ian Luo wrote: > > HTTP/2 support and Cloud Native Microservices are definitely two important > goals we should achieve in this year, and I am looking forward to reading > your proposal. Meanwhile, I think we should discuss and come up with a > draft roadmap for the incoming whole year so that it will make the > community easier to participate. > > What do you think, Jun? > > Thanks, > -Ian. > > > On Thu, Apr 18, 2019 at 9:46 PM Jun Liu wrote: > >> Hi, All >> >> I am writing this mail to discuss about our work in the next stage, some >> trends we should follow, or even what Dubbo should be next. >> >> Approximately from last year, there have been some discussions and >> thoughts in the community about how Dubbo should following or leading the >> tech trend in its area. With this goal in mind, I recently spent some time >> trying to dive deep in some related techs. Here I want to express some of >> my points regarding the two most discussed topics in our community, they >> are, HTTP/2 protocol and Cloud Native. >> >> 1. http/2. Considering that gRPC has done a great job upon HTTP/2 and the >> extraordinary influence it achieved in the industry. I think it should be a >> non-negligible part for us to take into consideration when talking about >> this topic. Actually, I would suggest we first consider integrating gRPC >> into our framework to 1. to leverage Dubbo's more powerful service >> management ability 2. quickly bring Dubbo HTTP/2 support. This is suitable >> to be done in 2.7.x. In the long run, I think we may need to provide >> built-in HTTP/2 support, which may require a standard HTTP/2 application >> layer protocol (compatible with GRPC can be an option), and introduce >> application level streaming semantics. This is suitable to be done in 3.x. >> >> 2. Microservices and Cloud Native. When comes to this topic, the most >> obvious thing to notice is the mismatch of the service model between Dubbo >> and Microservices architecture. Our definition of services is based on >> Interface, one Interface is intercepted as a service, while the >> Microservices architecture, Application is the first-class citizen, you >> can consider an Application as a service, interfaces are only see as >> metadas inside the service. This mismatch makes service discovery, service >> management and any introps very difficult or even impossible. I like the >> Microservice's model more than Dubbo's and I think we should start >> reconsidering our service model. I would restrict the discussion about >> Cloud Native to K8S here, I continuely see issue asking about Dubbo running >> on K8S. I think this question on root is about how to leverage the service >> discovery and container orchestration capabilities provided by K8S. >> >> This time I think we should not just stay in discussion, instead, we need >> to go to the next phase to come up with some practical solutions, make them >> part of our milestone and realize them. If you agree with the opinions I >> put forward above, I am glad to try to write down some of my recent >> researchs into a draft proposal. Then we can further discuss on some of the >> details and finally make it a practical one. >> >> Ken >> >>
