Re: JIRA email notification

Hi, > Individual notifications should be working now but I'm still not seeing > mails to issues@dubbo.a.o yet. I’m seeing them. Thanks, Justin

Re: JIRA email notification

HI, > There were three issues. > 1. Dubbo had not be assigned a notification scheme. > 2. j...@apache.org was not on the allow list for issues@dubbo.a.o > 3. The permission scheme was set incorrectly which was preventing mail > from being sent to issues@dubbo.a.o This was set up via the infra se

Re: Private channel for reporting security issues

Hi, > Thanks for the information. > In that case, I am +1 for secur...@dubbo.apache.org. Requested and the email list should be created soon. > Further question: if the venerability report is related to some > project Dubbo depends on, what kind of action should Dubbo security > team take? > Sho

Re: [Draft] Dubbo Incubator Report - March 2018

Hi, > Three most important issues to address in the move towards graduation: > > 1. Get 6 ICLA signed of 9 initial comitters. > 2. Create mailing list(including security@, dev@, issues@, commits@), JIRA These have been created. Perhaps change this to getting community to sign up and move disc

Re: On double dubbo starters

Hi, > I think Mark means you could publish dubbo starter(also same for dubbo in > another discussion) with ‘old’ group and ‘old’ name before transition to the > ASF. Yes that is what Mark means and is fine as long as it’s not branded as an Apache release. Thanks, Justin

Re: How to add Apache license head to the files of hessian-lite sub project

Hi, > The text from section 3 should appear in the NOTICE file. It seems to be a combination of a BSD license and Apache which is slightly confusing. IMO nothing needs to go in NOTICE but we probably need to look into it in a little more detail. Thanks, Justin

Re: How to add Apache license head to the files of hessian-lite sub project

Hi, > Should the author info be removed? @author Scott Ferguson I’d leave any existing author tags in but not add any new ones. Thanks, Justin

Re: How to add Apache license head to the files of hessian-lite sub project

Hi, > It seems to be a combination of a BSD license and Apache which is slightly > confusing. IMO nothing needs to go in NOTICE but we probably need to look > into it in a little more detail. Which is what The Apache 1.1 license is (i.e. a modified BSD one) it’s been a while since I’ve looked

Re: Suggestions on the organizational form of the code repository after confirming the submission of the dubbo code to apache

Hi, >> Are you looking to continue to use github as the primary repository >> location, or switch to our internal git? I'd recommend github since you're >> already there. > > +1 stick to github, just transfer to github/apache after the IP Clearance > sort of things With my mentors hat on I thin

Re: Suggestions on the organizational form of the code repository after confirming the submission of the dubbo code to apache

Hi, > 1. Can we put the project at > https://github.com/apache/ ？ > > for example: > a. alibaba/dubbo move to https://github.com/apache/incubator-dubbo > b. dubbo/dubbo.github.io move to > https://github.com/apache/incubator-dubbo-website > c. d

Re: How to add Apache license head to the files of hessian-lite sub project

Hi, > Then we need to rollback what we made in hessian-lite module and keep the > original license/author info as is. As Justin suggested, pls. also cross > check LICENSE file. Don’t be too concern about what goes in LICENCE and NOTICE right now we can fix that up before the first release. Th

Re: Prepare for release of v2.6.1

HI, This is not going o be an official Apache release is it? Thanks, Justin

Re: Suggestions on the organizational form of the code repository after confirming the submission of the dubbo code to apache

Hi, > They are release individually. Is it a problem after moving to ASF? No issue at all. Thanks, Justin

Re: Prepare for release of v2.6.1

Hi, > I have learned in the previous mail that we can still release as usual before > transfer to apache officially. An official Apache release should follow > another process, right? Yep all good. Thanks, Justin

Re: dubbo.io is not accessible, working to fix it

Hi, > dubbo.io is not accessible right now, because the code repo has been > transferred to Apache repo, we are working to fix it. At some point it would be best to transfer the information from dubbo.io to dubbo.apache.org. I assume that is the intention? Thanks, Justin

Re: dubbo.io is not accessible, working to fix it

Hi, > Right now I think it is better to keep both since dubbo.io is already > widely known. I suggest you read up on ASF branding policy in particular [1] and [2]. While there have been a couple of exceptions to this it’s probably best to migrate that content over to the apache.org site. Thank

Re: dubbo.io is not accessible, working to fix it

Hi, >> A suggestion is that we host all web resources to dubbo.apache.org, and >> also keep dubbo.io by redirecting dubbo.io to dubbo.apache.org because of >> the existing users. > > +1 for that. > > Reading the branding policy shows that it is possible to keep dubbo.io > by redirecting to dubbo

Re: Prepare for release of v2.6.1

Hi, > As we are going to move the repo to Apache, will that block your release? I don’t believe so. As long as it not advertised as an Apache release IMO all is good. Thanks, Justin

Re: Website Branding Policy

Hi, > 1. Gitter channel: https://gitter.im/alibaba/dubbo, is it necessary to > change to https://gitter.im/apache/incubator-dubbo? Necessary probably not, a good idea to do so yes. > 2. At the bottom of the page, there is a link to promote EDAS, which a > product in Alibaba Cloud, is that prope

Re: Website Branding Policy

Hi, > It isn't required legally but it is ASF policy. See: > http://www.apache.org/foundation/marks/pmcs#graphics " it includes a small "TM" symbol in the graphic or immediately adjacent to it.” Interesting. I had always thought it's more the later than former Thanks, Justin.

Re: Website Branding Policy

Hi, Some suggestions: - I’d remove the download .zip and download .tar.gz buttons. [1] - Add to the footer word to the effect of "Apache and the Apache feather logo are trademarks of The Apache Software Foundation” Thanks, Justin 1. http://www.apache.org/legal/release-policy.html#publication

Re: Delete the two duplicated projects: (dubbo/dubbo and dubbo/dubbo.github.io)？

Hi, If dubbo.github.io is redirecting to dubbo.apache.opg then there's no need to have any of the old content in the https://github.com/dubbo/dubbo.github.io repo right? We may still need the repo for the redirect but the content in the repo can be removed? Perhaps it would be a good idea to a

Re: Where is the document for the restful configuration?

Hi, > Unfortunately it is under Creative Commons 3.0 which is incompatible > with (category X) Apache. There’s a lot of variation in CC licenses and not all are Category X in this case it’s CC BY-ND 3.0 which would indeed be category X (mostly because of the no derivatives part). Thanks, Justi

Re: How do we judge whether SGA is need for a contribution?

Hi, > Actually I am curious about how to judge whether a SGA is needed for a > contribution. > How do we define the amount of code that will meet the criteria? There’s no exact limit IMO if it just changes a few lines then no SGA is needed and an ICLA may not be needed, if it change dozens of f

Re: [DISCUSS] Dubbo Release schedule

Hi, > 0. Should we have release manager for these artifacts? Is there any > committer volunteer to be release manager? In general Apache project do have release managers. > 1. Should we keep the release cycle for 2.6.x? Our first Apache > release might take some time because we have bunch of th

Re: [DISCUSS] Dubbo Release schedule

Hi, > It is not mandatory to change the project groupId to org.apache.dubbo in > the first release. Is that right? We will finished it before graduating. It a good idea to change it but some Apache projects never change it as it would break too much existing user code. In Dubbo's case as the pa

Re: Suggestions collection for release of dubbo v2.6.2

Hi, How is the IP clearance progressing? Do we have a list of the contributors who have signed a ICLA? Thanks, Justin 1. https://issues.apache.org/jira/browse/DUBBO-3

Re: Suggestions collection for release of dubbo v2.6.2

Hi, This is the best guide. [1] Please don’t follow what some TLPs have done like Apache Spark or Apache Hadoop as they have way far too much information in their NOTICE files. Thanks, Justin 1. http://www.apache.org/dev/licensing-howto.html

Re: Set up Nexus staging profile for Dubbo (Incubating)

Hi, > We are preparing for the first apache incubating release for dubbo, turns out > we lack of some nexus permissions, this blocks our process. The offical release area is not nexus it on the Apache mirrors so this (while inconvenient) isn’t a blocker to making an release. Thanks, Justin

Re: [DRAFT] Incubator PMC Board Report - May 2018

Hi, > We have 2 podlings missing reports, and 3 podlings missing sign offs. They > are all CC'd. I’ve signed off the report if the other mentors could do so that would be great. Thanks, Justin

Re: Set up Nexus staging profile for Dubbo (Incubating)

Hi, > Most of the dubbo users depend on the maven artifact, therefore I > think a maven artifact is mandatory from Dubbo's point of view, > although it is not mandatory according to ASF release policy. Is it something you could possibly put off until your second ASF second release? > Can we make

Re: Set up Nexus staging profile for Dubbo (Incubating)

Hi, > I don't think so, I think each Dubbo release should contain a maven artifact. Projects can also release convenience binary artefacts at the same time of a source release. It’s a good idea to vote on both at the same time. [1][2] > That will be great, so after the Apache release, we can pu

Re: Set up Nexus staging profile for Dubbo (Incubating)

Hi, > So that means it is better to publish both the source and binary > artifact to the Apache mirror system and vote them there. > The only thing that block us is we can not publish to > https://repository.apache.org (since our group id not starting with > org.apache), then to nexus, we want to

Re: Publishing Maven artifacts under third-party coordinates (was: Set up Nexus staging profile for Dubbo ...)

Hi, > But nothing prevents Alibaba from publishing under coordinates that they > control. > > It needs to be clear however that it is alibaba publishing there, not > Apache. The has been discussed on list with Dubbo and that’s the approach they are going to take with their first release. They a

Re: Set up Nexus staging profile for Dubbo (Incubating)

Hi, > Was there discussion somewhere that decided to allow an Apache project to > publish coordinates using com.alibaba? The maven artefacts would not be an ASF release only the source release would be and published and named as such is my understanding. Maven artefacts are not not offical rel

Re: Publishing Maven artifacts under third-party coordinates (was: Set up Nexus staging profile for Dubbo ...)

Hi, > Maybe the first release should be Apache for the source with Alibaba making > the binary release through their current Maven release process. Which is my understanding of what they are going to do. They were also going to vote on the binary to check it’s OK but not have that as part of th

Re: Publishing Maven artifacts under third-party coordinates (was: Set up Nexus staging profile for Dubbo ...)

Hi, >> ...The maven artifact is the most significant for most of the Dubbo >> users, so we want to include a maven artifact in the release > > Binaries are NOT part of Apache Releases, as mentioned earlier in this thread. Apache Dubbo is aware of that and it has been made clear on the dev li

Re: Publishing Maven artifacts under third-party coordinates (was: Set up Nexus staging profile for Dubbo ...)

Hi, > There is NO WAY to verify a binary. Even compiling from source to binary on > your machine, and trying to compare against a target binary will generally > fail since timestamps are embedded. Or maybe there are different compilers > being used. As per ASF policy a connivance binary can be re

Re: Publishing Maven artifacts under third-party coordinates (was: Set up Nexus staging profile for Dubbo ...)

Hi, >> As a mentor, I strongly advise against podlings making binary releases, >> especially for the first release. >> It’s difficult enough to get L&N correct for source releases, and when a >> binary release is being make >> at the same time with necessarily different L&N, the PPMC tend to get

Dubbo release candidate

Hi, I saw that a release candidate has been put up here [1] and I had a quick look at it. It looks good to me with a couple of minor issues: - The binary LICENSE fails to mention FastJSON (but as this is ALv2 it’s not required) Not this will make the connivance binary LICENSE file different to

Re: Publishing Maven artifacts under third-party coordinates (was: Set up Nexus staging profile for Dubbo ...)

Hi, Looking at the release candidate just made both the license and notice for the source release and the connivance binary are going to be just about identical as there's only 2 3rd party jars included and none of the other jars contain 3rd party code (other than what is mentioned in LICENSE),

Re: Dubbo release candidate

Hi, > Just a quick question, should the LICENSE and NOTICE file in META-INF > only contain information in this specific jar, or should contain > information of the entire binary? I’d go with what is in the jar as per [1] (as I jar could be pulled out and used on it’s own) but it’s not a big deal

Re: Dubbo release candidate

Hi, >> - The binary LICENSE fails to mention FastJSON (but as this is ALv2 it’s not >> required) Not this will make the connivance binary LICENSE file different to >> the source LICENSE file > > FastJSON should not be part of the binary release, should be caused by a bug > of filters, i will r

Re: Dubbo release candidate

Hi, > hessian-lite-3.2.2.jar is a part of this release, both resource and binary > should include hessian-lite. So now we need add clarification of hessian-lite > in the LICENSE and NOTICE files in libs, right? It’s ALv2 and from what I can see there no notice file. Is that correct? If so it c

Re: Moving hessian-lite from Dubbo codebase to eco-system

Hi, > Now we are considering that moving it to Dubbo eco-system, which is > https://github/dubbo. > > How do you think about this? I don’t know the history here so the answer to these questions may be obvious to someone eon the project. What do the owner / maintainers of hessian-lite think abo

[Mentors] IP clearance

Hi, A lot of work has been done on the IP clearance. [1] IMO given the 4 people mention in the JIRA to be contacted has all contributed less than 10 lines of code each I don't see this as holding up the release while we wait for a reply / ICLA from them. Absolute worse case code can be removed

Re: [VOTE]: Release Apache Dubbo (Incubating) 2.6.2 [RC1]

HI, > I don’t think we need to change the release tag hash. Tag ‘dubbo-2.6.2’ has > never changed, so the source release, binary release and the release tag are > still in consistent to each other. Be aware that CHANGES.md only exists in > the ‘2.6.2-release’ branch, a branch we used for rele

Re: [VOTE]: Release Apache Dubbo (Incubating) 2.6.2 [RC1]

Hi, +1 (binding) I checked: - Incubating in name - Signatures and hashes good - DISCLAIMER exists - LICENSE and NOTICE good - A number of pom.xml and log4j.xml files haven’t had their headers changed to the standard ASF one and are still copyright Alibaba (about 14 files) e.g [4][5] - A couple o

Re: [Suggestion] Add maven wrapper

Hi, Just be aware you can’t put maven-wrapper.jar in a source release as it’s compile code. Thanks, Justin

Re: Release notification of Apache Dubbo (Incubating) V2.6.2.

HI, > One more thing to do: we need to using the Apache download link[1] for > download. I am going to add it to website. Yes that required. > The current Github release note contains a download link [2], can we > change that? Basically you shouldn't use github releases, but it’s not IMO a big

Re: [Call for talks]: Dubbo Shanghai meetup

Hi, > Please submit your ideas before June 13rd by sending email to > priv...@dubbo.apache.org I don't see that this would be private. Any reason for that suggestion? Thanks, Justin

Re: Planing to rename dubbo package to org.apache

Hi, > I suggest that we have to freeze new comming PR after notification community. Up to the PMC but I think this will cause more issues than it will solve. Lets see what other people say in this thread. Thanks, Justin

Re: Dubbo new logo and new website

Hi, The "Alibaba folks" should be doing the work on this list as individuals in the open. Doing the development off list then putting in a github repo once done is not how Apache works. Ideally they should be making PRs against the existing web site. The community should also be involved in the d

Re: Dubbo new logo and new website

Hi, > Designing a new logo requires skills which the committers might lack of. They might they may not or they may know people who help, several projects I know have gotten a new logo this way. Thanks, Justin

Re: [VOTE]: Release Apache Dubbo (Incubating) 2.6.3 [RC3]

Hi, Having extra information in license or notice is unfortunate but IMO it's just a documentation issue rather than a licensing error. I think it can be fixed in the next release. Thanks, Justin On Wed., 8 Aug. 2018, 11:36 am jun liu, wrote: > > Each package MUST provide a LICENSE file and a

Re: [incubator-dubbo-website] branch asf-site updated: Google Analytics support

Hi, I know of other Apache projects that also use google analytics, that’s not to say it right to do so, but currently we don’t really have any direction or policy on this so it’s hard to know what to do. Thanks, Justin

Re: Use of "Team N" in issues and PRs

Hi, Thanks Mark for the great advice here in this thread. Just about every time I see something I should respond to Mark gets there first and puts it way better than I could. :-) > PS I see there is a Dubbo session at ApacheCon NA. I'd be more than > happy to sit down with anyone that is intere

Re: [Help Wanted] A tricky issue when preparing for 2.6.3 Apache release vote.

Hi, > We got a tricky problem when preparing for v2.6.3 release RC4, and we need > more inputs for what to do next. The problem is: > While we are preparing for the RC4 Apache release vote, we found that the > binary maven release has been deployed to the central repository IMO I’d remove it r

Re: [Help Wanted] A tricky issue when preparing for 2.6.3 Apache release vote.

Hi, Also what can do done to stop this happening accidentally in the future? Thanks, Justin

Re: [DRAFT] Dubbo incubator Report - September 2018

Hi, > * The following projects has been added to Dubbo ecosystem: >* dubbo-php-frmework >* dubbo-serialiazation-avro >* dubbo-sentinel-support >* Intellij IDEA plugin >* dubbo-rpc-native-thrift I have some concerns with what is happening here. This is at https://github.com/du

Re: [DRAFT] Dubbo incubator Report - September 2018

HI, Just a couple of questions below for people to ponder and I think it worth having a discussion on list about this. I don’t think having this external repo is a bad idea or against ASF policy but long term it could harm the project. For instance only contributions to the Apache project can b

Re: [VOTE]: Release Apache Dubbo (Incubating) 2.6.3 [RC5]

Hi, It’s best to keep votes open for a minimum of 72 hours before announcing the results. Thanks, Justin

Re: [DRAFT] Dubbo incubator Report - September 2018

Hi, I note under "How has the community developed since the last report?” you have. * The following projects has been added to Dubbo ecosystem: * dubbo-php-frmework * dubbo-serialiazation-avro * dubbo-sentinel-support * Intellij IDEA plugin * dubbo-rpc-native-thrift As these

Re: MODERATE for dev@dubbo.apache.org

Hi, > I am not sure why this can't be sent to dev mailing list, even I've accepted > it. Thanks for that. I can see the report has already been changed. I sent it form the wrong address I’ll try not to do that in future. Thanks, Justin

Re: Meet Dubbo

Hi, Nice article and I like the story you tell in going from user to contributor to committer and how developing open source code using the Apache Way involves the community. (I read it via google translate.) Thanks, Justin

Re: The chats must be public

Hi, I suggest you don't use slack or any other instant message as doing will exclude some people due to the platform used or time zone they are in or language used. Also these conversations can be hard to search and may not be archived. All decisions need be made in publc on the mailing list and

Re: The chats must be public

Hi, > But it is a different story for Dubbo users. You should be asking the users to use the mailing list as well. Users become contributors become committers. > What I am worrying is where we could group them all together in one single > place. If the user traffic gets too large for this lis

Re: NOTICE file enhancement

Hi, >>> This product contains code derived from Google Guava project, which is >>> available under a "Apache License 2.0" license. >>> (https://github.com/google/guava ). >>> >>> This product contains code derived from the Netty Project, which is >>> available und

Re: [Discuss]Prepare for the next release v2.6.4

Hi, > Yes, I think we need a new manager to do the next release, to get familiar > with and improve the release process. > But I'm not sure if anyone has committer privilege is allowed to be the > release manager or only PMCs are allowed. Anyone can be a release manager, but in practical term y

Re: [DISCUSS] A metric to measure the response time to issues/prs

HI, > I'd suggest not worrying about the metric and concentrating on growing > the community. Look for people who contribute and keep the bar low for > committership. +1 (again) to what Mark said. I like metrics, and they can be useful for discover issues, or tracking X over time to see how thi

Re: Podling Report Reminder - September 2018

Hi, Sorry please ignore this, it was sent in error. Thanks, Justin

Re: NOTICE file enhancement

Hi, The link provided is not that useful as it doesn't take into consideration ASF policy on licensed and notice files. I suggest you read [1]. IMO it does need to be included. Thanks, Justin 1. http://www.apache.org/dev/licensing-howto.html#mod-notice

Re: NOTICE file enhancement

Hi, Btw the source bundle does include Netty code. So it's not just the binary that needs it. Thanks Justin

Re: NOTICE file enhancement

Hi, All mostly correct and I’ve clarified a few things where needed. > Because the bundled Google Guava and Netty both contain no bundled > subcomponents under other licenses Well Netty does contain 3rd party bundled sub component but it incorrectly list then in NOTICE not LICENSE. I don't thin

Re: A little thought about the offline meetup

Hi, > Yesterday Alibaba Group held a small offline meetup, I was fortunate to > participate and did some communication with Justin. I’m glad you found it helpful, if you have any other questions please ask them here. > The discussion in the mailing list should not be limited to dubbo's issue >

Re: Meetup in Hangzhou

Hi, Actually I strongly suggest we should do it in a more open way next > time, e.g. announce the meetup, and call for talks from the mailing list. > I strongly suggest you also do this. Why is the "meetup management committee" not discussing this on list? and why are they separate from the PPMC

Re: Meetup in Hangzhou

Hi, > For some private information, at least they should contact the > @private list. Why does any of this need to be private? Open transparent discussion that involves all of the community is the goal here. If it’s the speaker selection that the issue then that could be done by the PMC on the

Incubator Podling Report (Due 5th December)

Hi, The incubator PMC would appreciated if you could complete the podling report on time it's due on 5th December in a few days. It takes time to prepare the incubator report, have your mentors sign off the report and for the board to review it, so it's best if you can get it in early. Thanks,

Re: [DRAFT] Dubbo incubator Report - December 2018

Hi, While the statistic are interesting it’s better to tell the story behind them and why they have changed. For instance the mail and GitHub stats don’t really mean much on their own, but it would be nice to know why there’s been an increase in closed PRs (I don’t know). Or why that their been

Naming of non-ASF releases

HI, From Mark: > On a related topic, if this component is remaining outside the ASF it > will need to change its name. Looking up a couple of directories I can see a large number of releases using the dubbo name: dubbo-bom/ dubbo-bootstrap/ dubbo-cluster/ dubbo-common/ dubbo-config/ dubbo-confi

Re: Naming of non-ASF releases

Hi, > Where did you get the list? http://central.maven.org/maven2/com/alibaba/ > Most of them are Apache Dubbo modules. I assumed some may be left over from the donation / old releases predating apache donation but not 100% sure if that accounts for all of them. Thanks, Justin

Re: Naming of non-ASF releases

Hi, > I checked the list, excepted for the dubbo-registry-nacos, all of them are > Apache Dubbo modules. Except that they are not still under Alibaba package and have been updated recently. I would understand if there has been no updates but that doesn't seem to the the case. If they are old a

Re: Naming of non-ASF releases

Hi, > @huxing, I think we should re-organize the ecosystem module release in Dubbo > community. @Justin, I also have a question, consider we have so many modules > in podling stage, everyone has its own release cycle, Is there a more > convenient way to do these releases, especially to push the

Re: Naming of non-ASF releases

Hi, > First, all the artifacts, except dubbo-registry-nacos, are only > updated when there is an official release. I didn't see any unexpected > behavior there. Taking one at random [1] I see: 2.6.1 2018-03-15 2.6.2 2018-06-05 2.6.3 2018-08-05 2.6.4 2018-10-08 2.6.5 2018-11-13 2.6.2 was rel

Re: Naming of non-ASF releases

Hi, > Regarding 2.6.3, it is due to some tricky issues described here[3]. > > Regarding 2.6.5, I am not quite sure but I suspect the same reason as 2.6.3. Thanks for the explanation, that looks like something that needs to be kept an eye on. You don’t wan to making releases before the vote is o

Re: Donate dubbo-registry-nacos

Hi, Out of interest have the 2 contributors signed ICLAs? Thanks, Justin

Re: Donate dubbo-registry-nacos

Hi, > Yes, both of them are Dubbo ppmc member.cI think we need a software grant > here, shall we? Give both people involved have signed ICLAs and the code in Apache licensed it’s probably not required. It may depend on who actually owns the code (usually the company those people work for but i

Re: [Notification of V2.7.0] Status, TODOs, Possible Release Schedules.

Hi, > You may need to update the NOTICE file. There’s no need as it has no NOTICE file [1]. (It’s license file isn’t correct either but that’s not Dubbo’s issue). Thanks, Justin 1. https://github.com/alibaba/fastjson

Re: Junit5 source file, do I need to mark it in the LICENSE file?

Hi, > I have a question :I ues junit-jupiter5.3.2, but for some test cases, I > copied some source code from junit 5.4.0.M1 , the files are as follow : >org.junit.jupiter.api.support.io.TempDirectory.java > > org.junit.jupiter.api.MethodDescriptororg.junit.jupiter.api.TestMethodOrderorg.junit

Re: Junit5 source file, do I need to mark it in the LICENSE file?

Hi, > if it was the connivance binary then yes you would need to put it in the > LICENSE. Sorry I mean “convenience binary” i.e. a binary made fro a source package for the convenience of users who don’t want to compile the source code. Justin

Re: [VOTE]: Release Apache Dubbo Spring Boot Project (Incubating) 0.2.1 and 0.1.2 [RC1]

Hi, > - I found .png file in source release, which is a binary file, it that > allowed? Did not confirm with ASF release policy yet. just confirming this is fine. It’s any binary that contains compiled code that's not allowed cos then it would not be open source. Thanks, Justin

Re: [VOTE]: Release Apache Dubbo OPS(Incubating) 0.1[RC2]

Hi, > Regarding the NOTICE file, I found there is no NOTICE for google fonts > roboto, but there is a COPYRIGHT.txt[1] file there, therefore I think > it is better to include it in the NOTICE file. I’ve not looked in detail but in general license info goes in LICENSE not NOTICE. Please don’t pu

Re: [VOTE]: Release Apache Dubbo OPS(Incubating) 0.1[RC2]

Hi, > Because what is included in the source release is several font files, > font files can not have source headers. So I think the COPYRIGHT.txt > is a variant of header-existing-copyright. According to [1], we should > move it to NOTICE. The copyright only get listed in NOTICE if it come from

Non-apache releases and old releases

HI, i was looking at the releases here [1] and not there was two unapproved releases made after you entered incubation dubbo-2.6.1 and dubbo-2.5.10. 2.6.1 has come up in conversion on this list before but not the previous release. It not clear on the GitHub page what isn Apache release and what

Re: Non-apache releases and old releases

Hi, > Just come back from Chinese Spring Festival. I have renamed all releases > after 2.6.1 so now they have the prefix of apache-dubbo to distinguish from > the previous releases, for example: from dubbo-2.7.0 to apache-dubbo-2.7.0. That will cause less confusion with user of Apache Dubbo. Tha

Re: Proposal for releasing hessian-lite 3.2.5

Hi, > +1. It is not a ASF project, so I don't think it should follow the ASF > release process. How is that possible if it in a ASF repo?? [1] Thanks, Justin 1. https://github.com/dubbo/hessian-lite/

Re: Proposal for releasing hessian-lite 3.2.5

Hi, > It is not in a ASF repo, what is your concern on this?\ I have no concerns, sorry for the noise. Thanks, Justin

Re: Fix dubbo ops binary license issue

Hi, > > EPL v1.0 and LGPL 2.1 > > The following components are provided under the EPL v1.0 and LGPL 2.1. > See project link for details. > The text of e

Re: Fix dubbo ops binary license issue

Hi, > I think there are 2 things that need to be checked: > a) ensure all the binary dependencies are listed in LICENSE, this > includes jar files under BOOT-INF/lib, and javascript dependencies > which can be found in package.json Dependancies should not be listed just what in included in the re

Re: Fix dubbo ops binary license issue

Hi, > For javascript it is a bit more tricky, because all the javascript > dependencies will be merged into one single and minimized javascript. Yep JS causes all sort of issues, also that some JS file are not obviously licensed, and they are often missing license headers. > I doubt this can be

  1   2   3   >