Re: the case of the maven wrapper

[Christofer Dutz]

So now the files in the maven-wrapper have all the correct headers?

So all I need to do is replace the versions in the Apache repos with that 
version and add something to the Notice and/or license and we're all good?

I knew that binary files can't be checked in, therefore I wrote that pr that 
eliminates the need of binary files.

So what would be the set of steps be to be correct and nice? Would rather do 
that than discuss in lengthy threads how to avoid that.

Chris

Outlook für Android herunterladen


From: Paul King 
Sent: Tuesday, February 19, 2019 4:38:16 AM
To: general@incubator.apache.org
Subject: Re: the case of the maven wrapper

For anyone who is interested from the Gradle side of things, you can look
at what we do for the Groovy project. We do include the (Gradle) wrapper
files in our git repo but NOT in our source distribution zip. There is one
extra step in our build process/line in our README that explains how to
populate the correct wrapper files using an existing gradle install and
after which the wrapper can then be used. I don't know if something similar
is currently possible with the Maven wrapper. Great if so, but if not, it
might prove to be a useful direction to head.

Cheers, Paul.

On Tue, Feb 19, 2019 at 10:54 AM Adrian Cole 
wrote:

> The request to donate the wrapper was closed won't fix (they did
> adjust the license headers)
>
> I've made a comment on a 3+ year old issue on maven itself, which had
> excluded the wrapper due to perceived problems in performing change
> inside the ASF
>
>
> https://issues.apache.org/jira/browse/MNG-5937?focusedCommentId=16771456=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16771456
>
> On Thu, Feb 14, 2019 at 4:18 PM Adrian Cole 
> wrote:
> >
> > FYI I've asked takari to donate the wrapper to the ASF. It is
> > important but tiny
> > https://github.com/takari/takari-maven-plugin/issues/18
> >
> > Meanwhile, we will remove the wrapper from the source distribution as
> > putting it in the NOTICE file is something off-putting to a few of our
> > contributors. We can build without the wrapper and it isn't worth
> > making a commitment to the NOTICE file for what seems not thought
> > through.
> >
> > If the enforcement rules loosen back to where we don't need to do
> > this, or the plugin or a copy of it is donated to the ASF, we'll
> > likely put it back into the source distribution.
> >
> > On Thu, Feb 14, 2019 at 3:29 PM Justin Mclean 
> wrote:
> > >
> > > Hi,
> > >
> > > > If we all say fine.. let's just throw more paperwork at it, I would
> ask you
> > > > to help draft a line for the NOTICE of what we would do. suppose we
> would
> > > > also have to do this for gradle etc.
> > >
> > > You would need to do this for any 3rd party file bundled with a
> release and yes sometimes this is complex and takes time. See for example
> Apache Newt. [1]
> > >
> > > > So basically if we accept that the new norm is this level of detail
> on
> > > > incidental files,
> > >
> > > It’s a 3rd party file not an incidental file and the ASF has policy
> around what to do when including 3rd party files which a (P)PMC and
> releases need to comply with. [2][3]
> > >
> > > To comply however is a simple change that needs to be made once to
> clearly inculcate the IP province and license of that file to users of the
> projects.
> > >
> > > > would it be "this includes source generated by the takari maven
> plugin"?
> > > > and of course if we say this, the next cruft is explaining gradle
> etc.
> > >
> > > If you don’t know what to do ask you mentors or the IPMC for help. If
> you disagree with advice given then clarify on legal-discuss.
> > >
> > > Thanks,
> > > Justin
> > >
> > > 1. https://github.com/apache/mynewt-newt/blob/master/LICENSE
> > > 2. http://www.apache.org/dev/release-publishing.html#goal
> > > 3. http://www.apache.org/dev/release-publishing.html#valid
> > >
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [Cava] Suitable name search

[Greg Stein]

On Mon, Feb 18, 2019 at 9:52 PM Kenneth Knowles  wrote:

> I think Kava is enough of a conflict that it will need to change,
> eventually. I think it is OK to keep it as Cava for entry into the
> incubator since it already exists but change ASAP:
>

Changing names is a real Pain for the Infra team. If you *know* you will
change it, then do that before we set stuff up for you, please.

Regards,
Greg Stein
Infrastructure Administrator, ASF

Re: [Cava] Suitable name search

[Kenneth Knowles]

I think Kava is enough of a conflict that it will need to change,
eventually. I think it is OK to keep it as Cava for entry into the
incubator since it already exists but change ASAP:

 - Talk about "Apache Cava (incubating)" will not build the new project's
reputation as well (for example, I actually missed the switch from Onyx to
Nemo so it took me some time to take a look)
 - As a practical matter, a name change may (eventually) lead to various
code namespace moves. In some projects it happens ASAP and some never move
due to a large install base they don't want to disrupt. I think Cava seems
like the former.

Kenn

On Mon, Feb 18, 2019 at 10:28 AM Antoine Toulme  wrote:

> First, a heartfelt thank you to all for participating in this discussion.
>
> I am tempted to keep Cava _for now_ given this late feedback, and proceed
> to proposing the project.
> To be more precise, I recommend we get the project into the incubator with
> this name. We can change the name of the project 3 to 6 months in.
>
> We have so far received significant interest from the Apache community and
> others, and it looks like we can go from there.
>
> John, good point on this website, kava.io. I note the company is named
> Kava Labs Inc. and their GitHub is Kava-Labs.
> https://github.com/Kava-Labs
> It also looks like their code is in the crypto domain, but more on the
> interchange/wallet side and written in Go and TypeScript.
> I’ll add them to the list when performing the suitable name search item on
> Jira.
>
> I am going to give everyone 48 hours to voice strong opinions against this
> approach.
>
> Cheers,
>
> Antoine
>
> > On Feb 18, 2019, at 9:04 AM, John D. Ament 
> wrote:
> >
> > If the project is already known as Cava and is looking to move to
> Apache, I
> > would recommend starting off as Cava.  I can see that there's already a
> > presence for it - https://github.com/ConsenSys/cava
> >
> > However, I can see there's a pretty strong conflict on the name -
> > https://kava.io/
> >
> > John
> >
> > On Mon, Feb 18, 2019 at 11:43 AM Serge Huber  wrote:
> >
> >> I agree that it doesn't matter if it "meant" something, you can simply
> >> forget the original meaning.
> >>
> >> So it could mean "Cryptographic Java"
> >>
> >> Here are other suggestions, because I like have the block and/or in the
> >> name :)
> >>
> >> - Blockava
> >> - Blockva
> >> - Chainava
> >>
> >> Please note I didn't do any proper name search for the above :)
> >>
> >> Regards,
> >>  Serge...
> >>
> >> On Mon, Feb 18, 2019 at 5:32 PM Jim Jagielski  wrote:
> >>>
> >>> Consensus Java :)
> >>>
>  On Feb 16, 2019, at 1:59 PM, Antoine Toulme 
> >> wrote:
> 
>  I explained it in the proposal and the original thread, Cava stands
> >> for “ConsenSys Java”, after Guava.
> 
>  It’s not a bad name per se, so let’s add it to the proposals.
> 
> > On Feb 16, 2019, at 9:58 AM, Henry Saputra 
> >> wrote:
> >
> > From last thread, I was not sure why Cava was not a suitable name?
> >
> > If there is a concern about trademarked name, the community can
> >> always go
> > with Apache Cava name.
> >
> > - Henry
> >
> > On Fri, Feb 15, 2019, 5:21 PM Antoine Toulme  >> wrote:
> >
> >> Thank you Anu.
> >>
> >> I’ll add your proposal to mine and start a vote Monday if that’s
> >> agreeable.
> >>
> >> Cheers,
> >>
> >> Antoine
> >>
> >>> On Feb 13, 2019, at 12:03 PM, Anu Engineer <
> >> aengin...@hortonworks.com>
> >> wrote:
> >>>
> >>> I would like to suggest “Jal”, in reference to Indra’s net (or
> Indra
> >> jal) https://en.wikipedia.org/wiki/Indra%27s_net
> >>>
> >>> From the link:
> >>> "Imagine a multidimensional spider's web in the early morning
> >> covered
> >> with dew drops. And every dew drop contains the reflection of all
> >> the other
> >> dew drops.
> >>> And, in each reflected dew drop, the reflections of all the other
> >> dew
> >> drops in that reflection. And so ad infinitum. That is the Buddhist
> >> conception of the universe in an image." –Alan Watts[1]
> >>>
> >>> And for what it is worth, it is the ultimate connected chain or
> >> graph (
> >>>
> >>> --Anu
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> On 2/13/19, 10:58 AM, "Antoine Toulme" 
> wrote:
> >>>
> >>> Hello all,
> >>>
> >>> As discussed previously, Cava is not a proper name for the proposal
> >> discussed last week on this list and published to the wiki [0].
> >>>
> >>> I humbly would like to ask the community for feedback and proposals
> >> on a suitable name for this proposal, in line with the guidelines
> >> [1].
> >>>
> >>> In preparation for this search, I have put together a list of
> >> names:
> >>>
> >>> - Rainbow (after the name of my kid’s favorite toy, and in line
> >> with
> >> the crypto community unicorn punk theme [2].
> >>> - Winch (a 

Re: the case of the maven wrapper

[Paul King]

For anyone who is interested from the Gradle side of things, you can look
at what we do for the Groovy project. We do include the (Gradle) wrapper
files in our git repo but NOT in our source distribution zip. There is one
extra step in our build process/line in our README that explains how to
populate the correct wrapper files using an existing gradle install and
after which the wrapper can then be used. I don't know if something similar
is currently possible with the Maven wrapper. Great if so, but if not, it
might prove to be a useful direction to head.

Cheers, Paul.

On Tue, Feb 19, 2019 at 10:54 AM Adrian Cole 
wrote:

> The request to donate the wrapper was closed won't fix (they did
> adjust the license headers)
>
> I've made a comment on a 3+ year old issue on maven itself, which had
> excluded the wrapper due to perceived problems in performing change
> inside the ASF
>
>
> https://issues.apache.org/jira/browse/MNG-5937?focusedCommentId=16771456=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16771456
>
> On Thu, Feb 14, 2019 at 4:18 PM Adrian Cole 
> wrote:
> >
> > FYI I've asked takari to donate the wrapper to the ASF. It is
> > important but tiny
> > https://github.com/takari/takari-maven-plugin/issues/18
> >
> > Meanwhile, we will remove the wrapper from the source distribution as
> > putting it in the NOTICE file is something off-putting to a few of our
> > contributors. We can build without the wrapper and it isn't worth
> > making a commitment to the NOTICE file for what seems not thought
> > through.
> >
> > If the enforcement rules loosen back to where we don't need to do
> > this, or the plugin or a copy of it is donated to the ASF, we'll
> > likely put it back into the source distribution.
> >
> > On Thu, Feb 14, 2019 at 3:29 PM Justin Mclean 
> wrote:
> > >
> > > Hi,
> > >
> > > > If we all say fine.. let's just throw more paperwork at it, I would
> ask you
> > > > to help draft a line for the NOTICE of what we would do. suppose we
> would
> > > > also have to do this for gradle etc.
> > >
> > > You would need to do this for any 3rd party file bundled with a
> release and yes sometimes this is complex and takes time. See for example
> Apache Newt. [1]
> > >
> > > > So basically if we accept that the new norm is this level of detail
> on
> > > > incidental files,
> > >
> > > It’s a 3rd party file not an incidental file and the ASF has policy
> around what to do when including 3rd party files which a (P)PMC and
> releases need to comply with. [2][3]
> > >
> > > To comply however is a simple change that needs to be made once to
> clearly inculcate the IP province and license of that file to users of the
> projects.
> > >
> > > > would it be "this includes source generated by the takari maven
> plugin"?
> > > > and of course if we say this, the next cruft is explaining gradle
> etc.
> > >
> > > If you don’t know what to do ask you mentors or the IPMC for help. If
> you disagree with advice given then clarify on legal-discuss.
> > >
> > > Thanks,
> > > Justin
> > >
> > > 1. https://github.com/apache/mynewt-newt/blob/master/LICENSE
> > > 2. http://www.apache.org/dev/release-publishing.html#goal
> > > 3. http://www.apache.org/dev/release-publishing.html#valid
> > >
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: the case of the maven wrapper

[Adrian Cole]

The request to donate the wrapper was closed won't fix (they did
adjust the license headers)

I've made a comment on a 3+ year old issue on maven itself, which had
excluded the wrapper due to perceived problems in performing change
inside the ASF

https://issues.apache.org/jira/browse/MNG-5937?focusedCommentId=16771456=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16771456

On Thu, Feb 14, 2019 at 4:18 PM Adrian Cole  wrote:
>
> FYI I've asked takari to donate the wrapper to the ASF. It is
> important but tiny
> https://github.com/takari/takari-maven-plugin/issues/18
>
> Meanwhile, we will remove the wrapper from the source distribution as
> putting it in the NOTICE file is something off-putting to a few of our
> contributors. We can build without the wrapper and it isn't worth
> making a commitment to the NOTICE file for what seems not thought
> through.
>
> If the enforcement rules loosen back to where we don't need to do
> this, or the plugin or a copy of it is donated to the ASF, we'll
> likely put it back into the source distribution.
>
> On Thu, Feb 14, 2019 at 3:29 PM Justin Mclean  
> wrote:
> >
> > Hi,
> >
> > > If we all say fine.. let's just throw more paperwork at it, I would ask 
> > > you
> > > to help draft a line for the NOTICE of what we would do. suppose we would
> > > also have to do this for gradle etc.
> >
> > You would need to do this for any 3rd party file bundled with a release and 
> > yes sometimes this is complex and takes time. See for example Apache Newt. 
> > [1]
> >
> > > So basically if we accept that the new norm is this level of detail on
> > > incidental files,
> >
> > It’s a 3rd party file not an incidental file and the ASF has policy around 
> > what to do when including 3rd party files which a (P)PMC and releases need 
> > to comply with. [2][3]
> >
> > To comply however is a simple change that needs to be made once to clearly 
> > inculcate the IP province and license of that file to users of the projects.
> >
> > > would it be "this includes source generated by the takari maven plugin"?
> > > and of course if we say this, the next cruft is explaining gradle etc.
> >
> > If you don’t know what to do ask you mentors or the IPMC for help. If you 
> > disagree with advice given then clarify on legal-discuss.
> >
> > Thanks,
> > Justin
> >
> > 1. https://github.com/apache/mynewt-newt/blob/master/LICENSE
> > 2. http://www.apache.org/dev/release-publishing.html#goal
> > 3. http://www.apache.org/dev/release-publishing.html#valid
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Podlings not following ASF release policy

[Thejas Nair]

Hi Justin,
Can you please elaborate on release policy issues with Singa ?
I checked a few things but couldn't find the issue.

Thanks,
Thejas





On Fri, Feb 8, 2019 at 5:51 PM Justin Mclean 
wrote:

> Hi,
>
> So I just checked the next bunch of podlings to report to see if we have
> any other issues with ASF releases policy and sadly we do and again it
> larger than I expected. Some of these are minor issues and easily fixed,
> some are not. In a couple of cases I may not of looked deeply enough into
> the issue and it may actually be fine, if so apologies in advance for
> listing you here. In a couple of cases (e.g. Zipkin) I can see it’s been
> discussed on the list but there’s more to do.
>
> Podlings having one or more issues with ASF release policy include:
> - Crail
> - Daffodil
> - Dlab
> - Druid
> - Dubbo
> - Hivemall
> - Marvin-ai
> - Memo
> - Omid
> - Openwhisk
> - Pinot
> - Ponymail
> - Singa
> - Skywalking
> - Zipkin
>
> Projects that I will be following up with include Dlab, Druid, Dubbo,
> Openwhisk, Singa, Skywalking and Zipkin.
>
> If you are the mentors of these projects please take a look and see what
> you can do to improve the situation and educate your podling on proper
> release policy. If you can’t find the issue ping me and I’ll send an email
> with what I think it is to your private list. There is probably things I’ve
> missed as well, often were there’s one issue there’s others.
>
> Please include something in the next podling report on this.
>
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

[VOTE] Release Apache OpenWhisk Composer (incubating) 0.10.0

[David P Grove]

The Apache OpenWhisk community has voted to release Apache OpenWhisk
Composer (incubating) version 0.10.0.  The voting thread can be found here:
https://lists.apache.org/thread.html/801edac7a4d58436a5411fc1fbca523f24056195bdb149f9c2cdc2b8@%3Cdev.openwhisk.apache.org%3E

We request that IPMC Members please review and vote on this incubator
release.

This release comprises of source code distribution only. There is only one
module within this release number 0.10.0. The artifact were built from the
following Git commit IDs:
* openwhisk-composer: 96ccab9c5cfab6f98ce564166f63f22b244a47fd

The source code artifact of openwhisk composer can be found at:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.10.0-incubating-rc1/openwhisk-composer-0.10.0-incubating-sources.tar.gz



The SHA-512 checksum for the artifact of openwhisk composer is
openwhisk-composer-0.10.0-incubating-sources.tar.gz:
B81C71F4 7BF01403 28D5FC80 888FC76D 59A24AB1 59C0FADC 097B0909 BD76AEB9
BFA309D3
 C2C443AE 2EC3DC50 0474B607 E9A20B73 8D993F51 4DEFEE5A 05C1AE00

which can can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.10.0-incubating-rc1/openwhisk-composer-0.10.0-incubating-sources.tar.gz.sha512



The signature of the artifact of openwhisk composer can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.10.0-incubating-rc1/openwhisk-composer-0.10.0-incubating-sources.tar.gz.asc


KEYS file is available here:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/KEYS

Please vote on releasing this package as Apache OpenWhisk
0.10.0-incubating:
OpenWhisk Composer

The vote will be open for at least 72 hours.
[ ] +1 Release as Apache OpenWhisk 0.10.0-incubating: openwhisk composer
[ ] +0 no opinion
[ ] -1 Do not release and the reason

Checklist for reference:
[ ] Download links are valid.
[ ] Checksums and PGP signatures are valid.
[ ] DISCLAIMER is included.
[ ] Source code artifacts have correct names matching the current release.
[ ] LICENSE and NOTICE files are correct for each OpenWhisk repository.
[ ] All files have license headers if necessary.
[ ] No compiled archives bundled in source archive.

regards,

--dave

Re: [Proposal] Apache TVM

[Tianqi Chen]

Thanks, everyone for helpful feedbacks. I would like to clarify a few
points being raised so far on behalf of the current TVM PMC.

> PMC vs PMC member

Thanks for pointing it out. This is something we overlooked and will update
the proposal to make the change accordingly.

> Champion

Markus has been actively engaging with the TVM community and helped the
community start the incubation process. These efforts include:
- Introduce the Apache way to in the TVM conference last Dec
   -
https://sampl.cs.washington.edu/tvmconf/slides/Markus-Weimer-TVM-Apache.pdf
- Help the community to start the incubation conversation(also Thanks to
Sebastian and Gon)
   - https://github.com/dmlc/tvm/issues/2401
- Watch the pre-incubation private list, and give helpful feedback

While we do not expect our mentor to actively watch the community on the
daily basis(many of our committers only contribute a few days in a week),
he has been very responsive and helped us to shape the incubation proposal
and most importantly be a strong advocate of the Apache way. I personally
think he is more than qualified as our champion:)

> Hardware artifact

INAL, however, given that Apache only releases source code and our source
code is in the form of software source code (HLS C and we are moving to
Chisel-(scala) ). Then anyone can take the software source code and
generate unofficial hardware release.

Tianqi


On Mon, Feb 18, 2019 at 6:44 AM Bertrand Delacretaz <
bdelacre...@codeconsult.ch> wrote:

> Hi,
>
> On Mon, Feb 18, 2019 at 11:44 AM Justin Mclean 
> wrote:
> > > If the Apache License works for those artifacts I think that's fine...
> >
> > It probably doesn’t, but it's complex and INAL, but I have touched on
> this about this in IoT talks at previous ApacheCons...
>
> FWIW the prior discussions that I mentioned are linked below - from
> board@ so accessible for ASF Members of Officers only, but we can
> distill them as needed if a concrete need appears with TVM.
>
> We didn't go past the discussions stage at that time (2011) but if
> there's another case of hardware at the ASF I'm willing to help
> restart those discussions to move this forward. Either to define which
> additions to the Apache License are required, or to clarify that it's
> ok as is.
>
> So unless there are specific objections about accepting a project
> which includes hardware as a software artifact I'm in favor of
> accepting TVM and sorting out these things during incubation.
>
> -Bertrand
>
> Prior board@ discussions at https://s.apache.org/hw2011_1 and
> https://s.apache.org/hw2011_2
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Incubator Git vs SVN

[Lars Francke]

I'm trying to read up as much as I can on the Incubator (podling startup)
processes and it took me surprisingly long to find the podlings.xml file
that's referred to in some places.

This lead me to dig into the SVN structure and I found that the Incubator
also has a Git repository.

Can someone clarify whether the content in SVN is still being used for the
website?

I find it confusing to find information about the Incubator source control
in "PMC Guides -> Updating the top-level Incubator website" as it contains
more information than just website related stuff.

In my opinion the Incubator should follow the model of most/lots of
projects which have a "Community", "Development", "General Information"
etc. menu which lists all the information for a project in a single place:
Issue tracking, version control, mailing lists, etc.

If other agree I can try to change this when I have time.

Thanks,
Lars

Re: Fwd: [DISCUSS] can we use weex.io as the short domain namefortheapache project

[Mark Thomas]

All,

ASF policy states that:

"Apache projects must host official website content on an apache.org domain"

That said, if there are issues with access speeds from some locations 
I'd strongly urge affected projects to engage with our infrastructure 
team to find a solution. Maybe we can set up a www/TLP mirror in China. 
I have no idea how practical that is or if a better solution is 
available. The infrastructure folks are the ones to talk to.


Mark



On 18/02/2019 13:02, 申远 wrote:
Actually, with the tool provided by https://ping.chinaz.com/, there is 
huge difference of network speed between https://weex.apache.org/ and 
https://weex.io/ , though their content is totally the same.


The average speed for https://weex.io/ is *65ms* from 142 different IP 
address, while it is *271ms* for https://weex.apache.org/


But if using another domain is against the rule of Apache, I think I can 
live with it and redirect https://weex.io/ to https://weex.apache.org/


Best Regards,
YorkShen

申远


吴晟 Sheng Wu mailto:wu.sh...@foxmail.com>> 于 
2019年2月18日周一 下午5:16写道：


 > weex.apache.org  is fast too from my
network environment now.


The Chinese network status is strange, we all know. :) Right?

 > We had received several complaint years ago from Chinese users that
weex.apache.org  is slow, so we launched
weex-project.io  with the same
content of weex.apache.org . If this is
against rules, I think we can make
it redirect to weex.apache.org , not sure
whether we would receive complaint
again.

In my mind, redirect is better. You could try, and listen to the
community.


If really need some another, I suggest you to talk with Brand
Management Committee.[1]


Maybe publish an website, but don't use `weex` in name and say
clearly, this is not Apache Weex official documents,
just documents maintained by volunteers. This is not so cool, I know.


[1] https://www.apache.org/foundation/marks/#whoweare


--
Sheng Wu
Apache SkyWalking, ShardingSphere, Zipkin
Twitter, wusheng1108







-- Original --
From:  "申远"mailto:shenyua...@gmail.com>>;
Date:  Mon, Feb 18, 2019 05:07 PM
To:  "general"mailto:general@incubator.apache.org>>;

Subject:  Re: Fwd: [DISCUSS] can we use weex.io  as
the short domain namefortheapache project



weex.apache.org  is fast too from my network
environment now.

We had received several complaint years ago from Chinese users that
weex.apache.org  is slow, so we launched
weex-project.io  with the same
content of weex.apache.org . If this is
against rules, I think we can make
it redirect to weex.apache.org , not sure
whether we would receive complaint
again.

Best Regards,
YorkShen

申远


吴晟 Sheng Wu mailto:wu.sh...@foxmail.com>>
于2019年2月18日周一 下午4:56写道：

 > Hi
 >
 >
 > I don't know why it is slow, I just tried, very quickly.
 >
 >
 >
 >
 > --
 > Sheng Wu
 > Apache SkyWalking, ShardingSphere, Zipkin
 > Twitter, wusheng1108
 >
 >
 >
 >
 >
 >
 >
 > -- Original --
 > From:  "申远"mailto:shenyua...@gmail.com>>;
 > Date:  Mon, Feb 18, 2019 04:33 PM
 > To:  "general"mailto:general@incubator.apache.org>>;
 >
 > Subject:  Re: Fwd: [DISCUSS] can we use weex.io 
as the short domain name
 > fortheapache project
 >
 >
 >
 > >
 > > 3. I don't think ASF websites are facing GFW issue.
 >
 > ASF website is quite slow when accessing from China, I am not
sure whether
 > this is a GFW issue or simply the server is on another continent
without a
 > CDN.
 >
 > We received complains about weex.apache.org
 from China mainland years ago,
 > so we deploy website to weex-project.io 
for fast access in China, as many
 > of our users are from China and there is CDN for weex-project.io
 .  If
 > there is a solution for this issue, please let me know.
 >
 > Best Regards,
 > YorkShen
 >
 > 申远
 >
 >
 > 吴晟 Sheng Wu mailto:wu.sh...@foxmail.com>> 于2019年2月18日周一 下午3:52写道：
 >
 > > Hi YorkShen
 > >
 > >
 > > From my understanding, weex project, including branding and
logo, should
 > > be donated to ASF(at least before Graduation).
 > > The basic policy is, weex.apache.org 
should be the only official website
 > > for the project.
 > > And project's website should 

Re: [Cava] Suitable name search

[Antoine Toulme]

First, a heartfelt thank you to all for participating in this discussion.

I am tempted to keep Cava _for now_ given this late feedback, and proceed to 
proposing the project.
To be more precise, I recommend we get the project into the incubator with this 
name. We can change the name of the project 3 to 6 months in.

We have so far received significant interest from the Apache community and 
others, and it looks like we can go from there.

John, good point on this website, kava.io. I note the company is named Kava 
Labs Inc. and their GitHub is Kava-Labs.
https://github.com/Kava-Labs
It also looks like their code is in the crypto domain, but more on the 
interchange/wallet side and written in Go and TypeScript.
I’ll add them to the list when performing the suitable name search item on Jira.

I am going to give everyone 48 hours to voice strong opinions against this 
approach.

Cheers,

Antoine

> On Feb 18, 2019, at 9:04 AM, John D. Ament  wrote:
> 
> If the project is already known as Cava and is looking to move to Apache, I
> would recommend starting off as Cava.  I can see that there's already a
> presence for it - https://github.com/ConsenSys/cava
> 
> However, I can see there's a pretty strong conflict on the name -
> https://kava.io/
> 
> John
> 
> On Mon, Feb 18, 2019 at 11:43 AM Serge Huber  wrote:
> 
>> I agree that it doesn't matter if it "meant" something, you can simply
>> forget the original meaning.
>> 
>> So it could mean "Cryptographic Java"
>> 
>> Here are other suggestions, because I like have the block and/or in the
>> name :)
>> 
>> - Blockava
>> - Blockva
>> - Chainava
>> 
>> Please note I didn't do any proper name search for the above :)
>> 
>> Regards,
>>  Serge...
>> 
>> On Mon, Feb 18, 2019 at 5:32 PM Jim Jagielski  wrote:
>>> 
>>> Consensus Java :)
>>> 
 On Feb 16, 2019, at 1:59 PM, Antoine Toulme 
>> wrote:
 
 I explained it in the proposal and the original thread, Cava stands
>> for “ConsenSys Java”, after Guava.
 
 It’s not a bad name per se, so let’s add it to the proposals.
 
> On Feb 16, 2019, at 9:58 AM, Henry Saputra 
>> wrote:
> 
> From last thread, I was not sure why Cava was not a suitable name?
> 
> If there is a concern about trademarked name, the community can
>> always go
> with Apache Cava name.
> 
> - Henry
> 
> On Fri, Feb 15, 2019, 5:21 PM Antoine Toulme > wrote:
> 
>> Thank you Anu.
>> 
>> I’ll add your proposal to mine and start a vote Monday if that’s
>> agreeable.
>> 
>> Cheers,
>> 
>> Antoine
>> 
>>> On Feb 13, 2019, at 12:03 PM, Anu Engineer <
>> aengin...@hortonworks.com>
>> wrote:
>>> 
>>> I would like to suggest “Jal”, in reference to Indra’s net (or Indra
>> jal) https://en.wikipedia.org/wiki/Indra%27s_net
>>> 
>>> From the link:
>>> "Imagine a multidimensional spider's web in the early morning
>> covered
>> with dew drops. And every dew drop contains the reflection of all
>> the other
>> dew drops.
>>> And, in each reflected dew drop, the reflections of all the other
>> dew
>> drops in that reflection. And so ad infinitum. That is the Buddhist
>> conception of the universe in an image." –Alan Watts[1]
>>> 
>>> And for what it is worth, it is the ultimate connected chain or
>> graph (
>>> 
>>> --Anu
>>> 
>>> 
>>> 
>>> 
>>> 
>>> On 2/13/19, 10:58 AM, "Antoine Toulme"  wrote:
>>> 
>>> Hello all,
>>> 
>>> As discussed previously, Cava is not a proper name for the proposal
>> discussed last week on this list and published to the wiki [0].
>>> 
>>> I humbly would like to ask the community for feedback and proposals
>> on a suitable name for this proposal, in line with the guidelines
>> [1].
>>> 
>>> In preparation for this search, I have put together a list of
>> names:
>>> 
>>> - Rainbow (after the name of my kid’s favorite toy, and in line
>> with
>> the crypto community unicorn punk theme [2].
>>> - Winch (a mechanical device used to wind up or wind out wires
>> (Wikipedia) , in the chain theme)
>>> - Sprocket (a profiled wheel with teeth, or cogs, that mesh with a
>> chain, track or other perforated or indented material. (Wikipedia),
>> in the
>> chain theme as well)
>>> 
>>> I have researched those names lightly and I have not seen them used
>> heavily by an open source project in crypto. I followed the
>> guidelines to
>> search across different open source communities.
>>> 
>>> Please provide your own proposal and let’s work together towards a
>> rough consensus. If one of the proposals above registers, please let
>> us
>> know as well.
>>> 
>>> Cheers,
>>> 
>>> Antoine
>>> 
>>> [0]: https://wiki.apache.org/incubator/CavaProposal
>>> [1]: https://incubator.apache.org/guides/names.html <
>> 

Re: [VOTE] Accept Training into the Apache Incubator

[Brahma Reddy Battula]

Sure,will bring this once after starting mailing list.

On Mon, Feb 18, 2019 at 8:44 PM Lars Francke  wrote:

> Would you mind bringing this up either in the DISCUSS thread or after we've
> started (it looks like we're good to go) on the mailing lists there. I
> touched on this in the proposal and received no comments during the
> discussion phase.
>
> On Fri, Feb 15, 2019 at 6:07 AM Brahma Reddy Battula 
> wrote:
>
> > +1 (non-Binding).
> >
> > Gone through discussion thread, it will greatly help in knowing the
> > ecosystem.
> > May we can extend to certification also..?
> >
> > On Fri, Feb 15, 2019 at 1:08 AM Kenneth Knowles  wrote:
> >
> > > +1 (binding)
> > >
> > > Looking forward to this.
> > >
> > > On Thu, Feb 14, 2019 at 11:11 AM Woonsan Ko 
> wrote:
> > >
> > > > +1 (binding)
> > > >
> > > > Cool!
> > > >
> > > > Woonsan
> > > >
> > > > On Wed, Feb 13, 2019 at 2:58 AM Lars Francke  >
> > > > wrote:
> > > > >
> > > > > Hi everyone,
> > > > >
> > > > > we've discussed the proposal for the Training project in [1] and
> [2].
> > > The
> > > > > proposal itself can be found on the wiki[3].
> > > > >
> > > > > According to the Incubator rules[4] I'd like to call a vote to
> accept
> > > the
> > > > > new "Training" project as a podling in the Apache Incubator.
> > > > >
> > > > > A vote for accepting a new Apache Incubator podling is a majority
> > vote.
> > > > > Everyone is welcome to vote, only Incubator PMC member votes are
> > > binding.
> > > > > It would be helpful (but not required) if you could add a comment
> > > stating
> > > > > whether your vote is binding or non-binding.
> > > > >
> > > > > This vote will run for at least 72 hours (but I expect to keep it
> > open
> > > > for
> > > > > longer). Please VOTE as follows:
> > > > >
> > > > > [ ] +1 Accept Training into the Apache Incubator
> > > > > [ ] +0 Abstain
> > > > > [ ] -1 Do not accept Training into the Apache Incubator because ...
> > > > >
> > > > > Thank you for everyone who decided to join in in the past
> > discussions!
> > > > > Lars
> > > > >
> > > > > [1] <
> > > > >
> > > >
> > >
> >
> https://lists.apache.org/thread.html/5c00016b769135cc302bb2ce4e5f6bbfeeda933a07e9c38b5017d651@%3Cgeneral.incubator.apache.org%3E
> > > > > >
> > > > >
> > > > > [2] <
> > > > >
> > > >
> > >
> >
> https://lists.apache.org/thread.html/9cb4d7eef73e0d526e0124944c3d37325aa892675351a1eed0a25de3@%3Cgeneral.incubator.apache.org%3E
> > > > > >
> > > > >
> > > > > [3] 
> > > > >
> > > > > [4] <
> > > > >
> > > >
> > >
> >
> https://incubator.apache.org/policy/incubation.html#approval_of_proposal_by_sponsor
> > > > > >
> > > >
> > > > -
> > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > > For additional commands, e-mail: general-h...@incubator.apache.org
> > > >
> > > >
> > >
> >
> >
> > --
> > --Brahma Reddy Battula
> >
>


-- 



--Brahma Reddy Battula

Re: [Cava] Suitable name search

[John D. Ament]

If the project is already known as Cava and is looking to move to Apache, I
would recommend starting off as Cava.  I can see that there's already a
presence for it - https://github.com/ConsenSys/cava

However, I can see there's a pretty strong conflict on the name -
https://kava.io/

John

On Mon, Feb 18, 2019 at 11:43 AM Serge Huber  wrote:

> I agree that it doesn't matter if it "meant" something, you can simply
> forget the original meaning.
>
> So it could mean "Cryptographic Java"
>
> Here are other suggestions, because I like have the block and/or in the
> name :)
>
> - Blockava
> - Blockva
> - Chainava
>
> Please note I didn't do any proper name search for the above :)
>
> Regards,
>   Serge...
>
> On Mon, Feb 18, 2019 at 5:32 PM Jim Jagielski  wrote:
> >
> > Consensus Java :)
> >
> > > On Feb 16, 2019, at 1:59 PM, Antoine Toulme 
> wrote:
> > >
> > > I explained it in the proposal and the original thread, Cava stands
> for “ConsenSys Java”, after Guava.
> > >
> > > It’s not a bad name per se, so let’s add it to the proposals.
> > >
> > >> On Feb 16, 2019, at 9:58 AM, Henry Saputra 
> wrote:
> > >>
> > >> From last thread, I was not sure why Cava was not a suitable name?
> > >>
> > >> If there is a concern about trademarked name, the community can
> always go
> > >> with Apache Cava name.
> > >>
> > >> - Henry
> > >>
> > >> On Fri, Feb 15, 2019, 5:21 PM Antoine Toulme  wrote:
> > >>
> > >>> Thank you Anu.
> > >>>
> > >>> I’ll add your proposal to mine and start a vote Monday if that’s
> agreeable.
> > >>>
> > >>> Cheers,
> > >>>
> > >>> Antoine
> > >>>
> >  On Feb 13, 2019, at 12:03 PM, Anu Engineer <
> aengin...@hortonworks.com>
> > >>> wrote:
> > 
> >  I would like to suggest “Jal”, in reference to Indra’s net (or Indra
> > >>> jal) https://en.wikipedia.org/wiki/Indra%27s_net
> > 
> >  From the link:
> >  "Imagine a multidimensional spider's web in the early morning
> covered
> > >>> with dew drops. And every dew drop contains the reflection of all
> the other
> > >>> dew drops.
> >  And, in each reflected dew drop, the reflections of all the other
> dew
> > >>> drops in that reflection. And so ad infinitum. That is the Buddhist
> > >>> conception of the universe in an image." –Alan Watts[1]
> > 
> >  And for what it is worth, it is the ultimate connected chain or
> graph (
> > 
> >  --Anu
> > 
> > 
> > 
> > 
> > 
> >  On 2/13/19, 10:58 AM, "Antoine Toulme"  wrote:
> > 
> >   Hello all,
> > 
> >   As discussed previously, Cava is not a proper name for the proposal
> > >>> discussed last week on this list and published to the wiki [0].
> > 
> >   I humbly would like to ask the community for feedback and proposals
> > >>> on a suitable name for this proposal, in line with the guidelines
> [1].
> > 
> >   In preparation for this search, I have put together a list of
> names:
> > 
> >   - Rainbow (after the name of my kid’s favorite toy, and in line
> with
> > >>> the crypto community unicorn punk theme [2].
> >   - Winch (a mechanical device used to wind up or wind out wires
> > >>> (Wikipedia) , in the chain theme)
> >   - Sprocket (a profiled wheel with teeth, or cogs, that mesh with a
> > >>> chain, track or other perforated or indented material. (Wikipedia),
> in the
> > >>> chain theme as well)
> > 
> >   I have researched those names lightly and I have not seen them used
> > >>> heavily by an open source project in crypto. I followed the
> guidelines to
> > >>> search across different open source communities.
> > 
> >   Please provide your own proposal and let’s work together towards a
> > >>> rough consensus. If one of the proposals above registers, please let
> us
> > >>> know as well.
> > 
> >   Cheers,
> > 
> >   Antoine
> > 
> >   [0]: https://wiki.apache.org/incubator/CavaProposal
> >   [1]: https://incubator.apache.org/guides/names.html <
> > >>> https://incubator.apache.org/guides/names.html>
> >   [2]:
> https://www.urbandictionary.com/define.php?term=unicorn%20punk
> > 
> > 
> > 
> -
> >  To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >  For additional commands, e-mail: general-h...@incubator.apache.org
> > >>>
> > >>>
> > >>> -
> > >>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > >>> For additional commands, e-mail: general-h...@incubator.apache.org
> > >>>
> > >>>
> > >
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> >
> >
> > -
> > To unsubscribe, e-mail: 

Re: [Cava] Suitable name search

[Serge Huber]

I agree that it doesn't matter if it "meant" something, you can simply
forget the original meaning.

So it could mean "Cryptographic Java"

Here are other suggestions, because I like have the block and/or in the name :)

- Blockava
- Blockva
- Chainava

Please note I didn't do any proper name search for the above :)

Regards,
  Serge...

On Mon, Feb 18, 2019 at 5:32 PM Jim Jagielski  wrote:
>
> Consensus Java :)
>
> > On Feb 16, 2019, at 1:59 PM, Antoine Toulme  wrote:
> >
> > I explained it in the proposal and the original thread, Cava stands for 
> > “ConsenSys Java”, after Guava.
> >
> > It’s not a bad name per se, so let’s add it to the proposals.
> >
> >> On Feb 16, 2019, at 9:58 AM, Henry Saputra  wrote:
> >>
> >> From last thread, I was not sure why Cava was not a suitable name?
> >>
> >> If there is a concern about trademarked name, the community can always go
> >> with Apache Cava name.
> >>
> >> - Henry
> >>
> >> On Fri, Feb 15, 2019, 5:21 PM Antoine Toulme  >>
> >>> Thank you Anu.
> >>>
> >>> I’ll add your proposal to mine and start a vote Monday if that’s 
> >>> agreeable.
> >>>
> >>> Cheers,
> >>>
> >>> Antoine
> >>>
>  On Feb 13, 2019, at 12:03 PM, Anu Engineer 
> >>> wrote:
> 
>  I would like to suggest “Jal”, in reference to Indra’s net (or Indra
> >>> jal) https://en.wikipedia.org/wiki/Indra%27s_net
> 
>  From the link:
>  "Imagine a multidimensional spider's web in the early morning covered
> >>> with dew drops. And every dew drop contains the reflection of all the 
> >>> other
> >>> dew drops.
>  And, in each reflected dew drop, the reflections of all the other dew
> >>> drops in that reflection. And so ad infinitum. That is the Buddhist
> >>> conception of the universe in an image." –Alan Watts[1]
> 
>  And for what it is worth, it is the ultimate connected chain or graph (
> 
>  --Anu
> 
> 
> 
> 
> 
>  On 2/13/19, 10:58 AM, "Antoine Toulme"  wrote:
> 
>   Hello all,
> 
>   As discussed previously, Cava is not a proper name for the proposal
> >>> discussed last week on this list and published to the wiki [0].
> 
>   I humbly would like to ask the community for feedback and proposals
> >>> on a suitable name for this proposal, in line with the guidelines [1].
> 
>   In preparation for this search, I have put together a list of names:
> 
>   - Rainbow (after the name of my kid’s favorite toy, and in line with
> >>> the crypto community unicorn punk theme [2].
>   - Winch (a mechanical device used to wind up or wind out wires
> >>> (Wikipedia) , in the chain theme)
>   - Sprocket (a profiled wheel with teeth, or cogs, that mesh with a
> >>> chain, track or other perforated or indented material. (Wikipedia), in the
> >>> chain theme as well)
> 
>   I have researched those names lightly and I have not seen them used
> >>> heavily by an open source project in crypto. I followed the guidelines to
> >>> search across different open source communities.
> 
>   Please provide your own proposal and let’s work together towards a
> >>> rough consensus. If one of the proposals above registers, please let us
> >>> know as well.
> 
>   Cheers,
> 
>   Antoine
> 
>   [0]: https://wiki.apache.org/incubator/CavaProposal
>   [1]: https://incubator.apache.org/guides/names.html <
> >>> https://incubator.apache.org/guides/names.html>
>   [2]: https://www.urbandictionary.com/define.php?term=unicorn%20punk
> 
> 
>  -
>  To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>  For additional commands, e-mail: general-h...@incubator.apache.org
> >>>
> >>>
> >>> -
> >>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >>> For additional commands, e-mail: general-h...@incubator.apache.org
> >>>
> >>>
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [PROPOSAL] New blockchain project: Cava

[John D. Ament]

On Tue, Feb 5, 2019 at 6:52 PM Michael Wall  wrote:

> Interesting proposal.  I would be interested in helping.  Seems like you
> don't need anymore mentors so I can volunteer in any capacity you need.
>
> I think you are going to have trouble with the name though as
> https://cava.com/ is a great restaurant.
>
>
Sorry for the late reply - but that's not how naming works.  I would
suggest that the proposed podling works with their champion to figure out
if the name needs to be changed before incubation.  This isn't typically
how we do it.

Typically, a name needs to be in a related field.  If there was something
called "Cava" that also dealt with Blockchain or databases or similar, then
the name "Cava" would be an issue.  Just because a restaurant chain is
named Cava doesn't mean it's not a suitable name.

John


> Mike
>
> On Tue, Feb 5, 2019 at 6:36 PM Dave Fisher  wrote:
>
> > Hi -
> >
> > I would also be happy to volunteer as a Mentor to this podling.
> >
> > Regards,
> > Dave
> >
> > > On Feb 5, 2019, at 3:28 PM, Kenneth Knowles  wrote:
> > >
> > > +1
> > >
> > > I would like to volunteer as an additional mentor.
> > >
> > > Kenn
> > >
> > > On Tue, Feb 5, 2019 at 2:57 PM Justin Mclean  >
> > > wrote:
> > >
> > >> Hi,
> > >>
> > >> Nice proposal. Just a couple of  comments.
> > >>
> > >>> The project is well established and counts 2 active committers. Some
> > >> contributions were made from the community.
> > >>
> > >> Being that small may be a concern, the ASF prefers project with a
> > >> community around them, but it’s not always a barrier to entry see for
> > >> example Apache PLC4X.
> > >>
> > >>> Blockchain protocol developers organize well in communities, and some
> > >> lively discussions take place over Twitter, Gitter, Telegram.
> > >>
> > >> At the ASF all decisions need to be made on the mailing list not on
> any
> > >> external platform mentioned above. Would the project be OK with moving
> > >> discussions to a mailing list and having them in an asynchronous
> manner?
> > >>
> > >>> We will remain in incubation for a period of no less than a year so
> we
> > >> can properly invest and build a community of users, contributors and
> > >> committers around our goals.
> > >>
> > >> Most projects take more than a year to graduate, two years is usual
> but
> > >> some projects do take longer. Is the project OK with that and will
> your
> > >> mentors stay around for that long?
> > >>
> > >>> '''Initial Committers'''
> > >>>
> > >>> Antoine Toulme (toulmean at apache dot org) *
> > >>
> > >> Seem odd to only list one initial committer, all initial committer s
> are
> > >> on the PPMC and you would need a minimum of 3 active people. The IPMC
> > >> generally likes to see 5.
> > >>
> > >> Thanks,
> > >> Justin
> > >> -
> > >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > >> For additional commands, e-mail: general-h...@incubator.apache.org
> > >>
> > >>
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: [Cava] Suitable name search

[Jim Jagielski]

Consensus Java :)

> On Feb 16, 2019, at 1:59 PM, Antoine Toulme  wrote:
> 
> I explained it in the proposal and the original thread, Cava stands for 
> “ConsenSys Java”, after Guava.
> 
> It’s not a bad name per se, so let’s add it to the proposals.
> 
>> On Feb 16, 2019, at 9:58 AM, Henry Saputra  wrote:
>> 
>> From last thread, I was not sure why Cava was not a suitable name?
>> 
>> If there is a concern about trademarked name, the community can always go
>> with Apache Cava name.
>> 
>> - Henry
>> 
>> On Fri, Feb 15, 2019, 5:21 PM Antoine Toulme > 
>>> Thank you Anu.
>>> 
>>> I’ll add your proposal to mine and start a vote Monday if that’s agreeable.
>>> 
>>> Cheers,
>>> 
>>> Antoine
>>> 
 On Feb 13, 2019, at 12:03 PM, Anu Engineer 
>>> wrote:
 
 I would like to suggest “Jal”, in reference to Indra’s net (or Indra
>>> jal) https://en.wikipedia.org/wiki/Indra%27s_net
 
 From the link:
 "Imagine a multidimensional spider's web in the early morning covered
>>> with dew drops. And every dew drop contains the reflection of all the other
>>> dew drops.
 And, in each reflected dew drop, the reflections of all the other dew
>>> drops in that reflection. And so ad infinitum. That is the Buddhist
>>> conception of the universe in an image." –Alan Watts[1]
 
 And for what it is worth, it is the ultimate connected chain or graph (
 
 --Anu
 
 
 
 
 
 On 2/13/19, 10:58 AM, "Antoine Toulme"  wrote:
 
  Hello all,
 
  As discussed previously, Cava is not a proper name for the proposal
>>> discussed last week on this list and published to the wiki [0].
 
  I humbly would like to ask the community for feedback and proposals
>>> on a suitable name for this proposal, in line with the guidelines [1].
 
  In preparation for this search, I have put together a list of names:
 
  - Rainbow (after the name of my kid’s favorite toy, and in line with
>>> the crypto community unicorn punk theme [2].
  - Winch (a mechanical device used to wind up or wind out wires
>>> (Wikipedia) , in the chain theme)
  - Sprocket (a profiled wheel with teeth, or cogs, that mesh with a
>>> chain, track or other perforated or indented material. (Wikipedia), in the
>>> chain theme as well)
 
  I have researched those names lightly and I have not seen them used
>>> heavily by an open source project in crypto. I followed the guidelines to
>>> search across different open source communities.
 
  Please provide your own proposal and let’s work together towards a
>>> rough consensus. If one of the proposals above registers, please let us
>>> know as well.
 
  Cheers,
 
  Antoine
 
  [0]: https://wiki.apache.org/incubator/CavaProposal
  [1]: https://incubator.apache.org/guides/names.html <
>>> https://incubator.apache.org/guides/names.html>
  [2]: https://www.urbandictionary.com/define.php?term=unicorn%20punk
 
 
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
>>> 
>>> 
>>> -
>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>> 
>>> 
> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Accept Training into the Apache Incubator

[Lars Francke]

Would you mind bringing this up either in the DISCUSS thread or after we've
started (it looks like we're good to go) on the mailing lists there. I
touched on this in the proposal and received no comments during the
discussion phase.

On Fri, Feb 15, 2019 at 6:07 AM Brahma Reddy Battula 
wrote:

> +1 (non-Binding).
>
> Gone through discussion thread, it will greatly help in knowing the
> ecosystem.
> May we can extend to certification also..?
>
> On Fri, Feb 15, 2019 at 1:08 AM Kenneth Knowles  wrote:
>
> > +1 (binding)
> >
> > Looking forward to this.
> >
> > On Thu, Feb 14, 2019 at 11:11 AM Woonsan Ko  wrote:
> >
> > > +1 (binding)
> > >
> > > Cool!
> > >
> > > Woonsan
> > >
> > > On Wed, Feb 13, 2019 at 2:58 AM Lars Francke 
> > > wrote:
> > > >
> > > > Hi everyone,
> > > >
> > > > we've discussed the proposal for the Training project in [1] and [2].
> > The
> > > > proposal itself can be found on the wiki[3].
> > > >
> > > > According to the Incubator rules[4] I'd like to call a vote to accept
> > the
> > > > new "Training" project as a podling in the Apache Incubator.
> > > >
> > > > A vote for accepting a new Apache Incubator podling is a majority
> vote.
> > > > Everyone is welcome to vote, only Incubator PMC member votes are
> > binding.
> > > > It would be helpful (but not required) if you could add a comment
> > stating
> > > > whether your vote is binding or non-binding.
> > > >
> > > > This vote will run for at least 72 hours (but I expect to keep it
> open
> > > for
> > > > longer). Please VOTE as follows:
> > > >
> > > > [ ] +1 Accept Training into the Apache Incubator
> > > > [ ] +0 Abstain
> > > > [ ] -1 Do not accept Training into the Apache Incubator because ...
> > > >
> > > > Thank you for everyone who decided to join in in the past
> discussions!
> > > > Lars
> > > >
> > > > [1] <
> > > >
> > >
> >
> https://lists.apache.org/thread.html/5c00016b769135cc302bb2ce4e5f6bbfeeda933a07e9c38b5017d651@%3Cgeneral.incubator.apache.org%3E
> > > > >
> > > >
> > > > [2] <
> > > >
> > >
> >
> https://lists.apache.org/thread.html/9cb4d7eef73e0d526e0124944c3d37325aa892675351a1eed0a25de3@%3Cgeneral.incubator.apache.org%3E
> > > > >
> > > >
> > > > [3] 
> > > >
> > > > [4] <
> > > >
> > >
> >
> https://incubator.apache.org/policy/incubation.html#approval_of_proposal_by_sponsor
> > > > >
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
> >
>
>
> --
> --Brahma Reddy Battula
>

Re: [VOTE] Accept Training into the Apache Incubator

[Lars Francke]

Hello everyone,

thank you for voting so far. We have already had more than the 72 hours but
I won't get around to do much until Wednesday this week so it doesn't hurt
to leave this open for two more days.

That said we already have more than enough vote for a successful outcome.

Thank you,
Lars

On Wed, Feb 13, 2019 at 8:57 AM Lars Francke  wrote:

> Hi everyone,
>
> we've discussed the proposal for the Training project in [1] and [2]. The
> proposal itself can be found on the wiki[3].
>
> According to the Incubator rules[4] I'd like to call a vote to accept the
> new "Training" project as a podling in the Apache Incubator.
>
> A vote for accepting a new Apache Incubator podling is a majority vote.
> Everyone is welcome to vote, only Incubator PMC member votes are binding.
> It would be helpful (but not required) if you could add a comment stating
> whether your vote is binding or non-binding.
>
> This vote will run for at least 72 hours (but I expect to keep it open
> for longer). Please VOTE as follows:
>
> [ ] +1 Accept Training into the Apache Incubator
> [ ] +0 Abstain
> [ ] -1 Do not accept Training into the Apache Incubator because ...
>
> Thank you for everyone who decided to join in in the past discussions!
> Lars
>
> [1] <
> https://lists.apache.org/thread.html/5c00016b769135cc302bb2ce4e5f6bbfeeda933a07e9c38b5017d651@%3Cgeneral.incubator.apache.org%3E
> >
>
> [2] <
> https://lists.apache.org/thread.html/9cb4d7eef73e0d526e0124944c3d37325aa892675351a1eed0a25de3@%3Cgeneral.incubator.apache.org%3E
> >
>
> [3] 
>
> [4] <
> https://incubator.apache.org/policy/incubation.html#approval_of_proposal_by_sponsor
> >
>

Re: Fwd: [DISCUSS] can we use weex.io as the short domainnamefortheapache project

[???? Sheng Wu]

Thanks for the feedback. Sadly, It looks like really get the network issue. 


In my mind, hosting `weex.io` site out ASF is not right.


--
Sheng Wu
Apache SkyWalking, ShardingSphere, Zipkin
Twitter, wusheng1108


 




-- Original --
From:  "";
Date:  Mon, Feb 18, 2019 09:02 PM
To:  "general";

Subject:  Re: Fwd: [DISCUSS] can we use weex.io as the short 
domainnamefortheapache project



Actually, with the tool provided by https://ping.chinaz.com/, there is huge 
difference of network speed between https://weex.apache.org/ and 
https://weex.io/ , though their content is totally the same.


The average speed for https://weex.io/ is 65ms from 142 different IP address, 
while it is 271ms for https://weex.apache.org/


But if using another domain is against the rule of Apache, I think I can live 
with it and redirect https://weex.io/ to https://weex.apache.org/


Best Regards,
YorkShen






 Sheng Wu  ??2019??2??18?? 5:16??

> weex.apache.org is fast too from my network environment now.
 
 
 The Chinese network status is strange, we all know. :) Right?
 
 > We had received several complaint years ago from Chinese users that
 weex.apache.org is slow, so we launched weex-project.io with the same
 content of weex.apache.org. If this is against rules, I think we can make
 it redirect to weex.apache.org, not sure whether we would receive complaint
 again.
 
 In my mind, redirect is better. You could try, and listen to the community. 
 
 
 If really need some another, I suggest you to talk with Brand Management 
Committee.[1]
 
 
 Maybe publish an website, but don't use `weex` in name and say clearly, this 
is not Apache Weex official documents, 
 just documents maintained by volunteers. This is not so cool, I know.
 
 
 [1] https://www.apache.org/foundation/marks/#whoweare
 
 
 --
 Sheng Wu
 Apache SkyWalking, ShardingSphere, Zipkin
 Twitter, wusheng1108
 
 
 
 
 
 
 
 -- Original --
 From:  "";
 Date:  Mon, Feb 18, 2019 05:07 PM
 To:  "general";
 
 Subject:  Re: Fwd: [DISCUSS] can we use weex.io as the short domain 
namefortheapache project
 
 
 
 weex.apache.org is fast too from my network environment now.
 
 We had received several complaint years ago from Chinese users that
 weex.apache.org is slow, so we launched weex-project.io with the same
 content of weex.apache.org. If this is against rules, I think we can make
 it redirect to weex.apache.org, not sure whether we would receive complaint
 again.
 
 Best Regards,
 YorkShen
 
 
 
 
  Sheng Wu  ??2019??2??18?? 4:56??
 
 > Hi
 >
 >
 > I don't know why it is slow, I just tried, very quickly.
 >
 >
 >
 >
 > --
 > Sheng Wu
 > Apache SkyWalking, ShardingSphere, Zipkin
 > Twitter, wusheng1108
 >
 >
 >
 >
 >
 >
 >
 > -- Original --
 > From:  "";
 > Date:  Mon, Feb 18, 2019 04:33 PM
 > To:  "general";
 >
 > Subject:  Re: Fwd: [DISCUSS] can we use weex.io as the short domain name
 > fortheapache project
 >
 >
 >
 > >
 > > 3. I don't think ASF websites are facing GFW issue.
 >
 > ASF website is quite slow when accessing from China, I am not sure whether
 > this is a GFW issue or simply the server is on another continent without a
 > CDN.
 >
 > We received complains about weex.apache.org from China mainland years ago,
 > so we deploy website to weex-project.io for fast access in China, as many
 > of our users are from China and there is CDN for weex-project.io .  If
 > there is a solution for this issue, please let me know.
 >
 > Best Regards,
 > YorkShen
 >
 > 
 >
 >
 >  Sheng Wu  ??2019??2??18?? 3:52??
 >
 > > Hi YorkShen
 > >
 > >
 > > From my understanding, weex project, including branding and logo, should
 > > be donated to ASF(at least before Graduation).
 > > The basic policy is, weex.apache.org should be the only official website
 > > for the project.
 > > And project's website should be hosted in Apache Infra.
 > >
 > >
 > > If you have others, let's say weex.io and weex-project.io, and run by
 > > your committers team, I suggest
 > > 1. Set redirect for `weex.io` to `weex.apache.org`, for the end user
 > > convenience.
 > > 2. For the Chinese documents, if your committers/contributors maintain
 > > this, put it in `http://weex.apache.org/cn/`makes
 > 
 > >  sense.
 > > 3. I don't think ASF websites are facing GFW issue.
 > >
 > >
 > > If you want to publish another domain/website for ecosystem, you should
 > > avoid using `weex-`, `weex.`, to avoid branding issues.
 > > And I suggest you don't do that, because the community will be split.
 > >
 > >
 > > The following are just suggestions from my experiences.
 > > Blog(cn/en) post are popular in many Apache project, which could be
 > easily
 > > supported by our CI hook in GitHub, also have post control and review.
 > > If you 

Re: [Proposal] Apache TVM

[Bertrand Delacretaz]

Hi,

On Mon, Feb 18, 2019 at 11:44 AM Justin Mclean  wrote:
> > If the Apache License works for those artifacts I think that's fine...
>
> It probably doesn’t, but it's complex and INAL, but I have touched on this 
> about this in IoT talks at previous ApacheCons...

FWIW the prior discussions that I mentioned are linked below - from
board@ so accessible for ASF Members of Officers only, but we can
distill them as needed if a concrete need appears with TVM.

We didn't go past the discussions stage at that time (2011) but if
there's another case of hardware at the ASF I'm willing to help
restart those discussions to move this forward. Either to define which
additions to the Apache License are required, or to clarify that it's
ok as is.

So unless there are specific objections about accepting a project
which includes hardware as a software artifact I'm in favor of
accepting TVM and sorting out these things during incubation.

-Bertrand

Prior board@ discussions at https://s.apache.org/hw2011_1 and
https://s.apache.org/hw2011_2

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: the case of the maven wrapper

[Myrle Krantz]

On Thu, Feb 14, 2019 at 7:05 AM Mick Semb Wever  wrote:

> One of the tings I've noticed is that the vetos on a podling's first
> release can be a bit harsh.
>


> On releases I would rather see such vetos replaced with comments that are
> feedback, while still obvious that they are an issue that is expected to be
> fixed by the next release (and before graduation). I think this would be
> warmer feedback, and permit a more incremental approach to getting to the
> standard of release required for graduation.


I have to disagree here. I’ve been watching Justin vote on releases for
*years* now. No one is more prolific (not even by half). And he always
gives detailed reasons for his vote. He’s also very clear about what issues
he sees as blockers and what issues aren’t blockers, but that he’d like to
see resolved before graduation. The overarching principle is clear: if it
could place users, contributors, or the ASF in jeopardy we veto. Justin is
very good at finding these.  This is the reason that, even though vetos
don’t technically block the release, when Justin states a -1, others will
often withdraw a +1.

And yes: that’s frustrating. No amount of warm verbiage added to the veto
will change the fact that it’s frustrating.  Would you rather we accept the
legal jeopardy?

Justin is not always right about a given detail.  No one is.  That may be
the case in this specific instance.  But what I'm responding to is a
general statement about the way our release vetting process.  I do not
believe we are too harsh.

I’d also note: we are all doing this on his own *unpaid* time. While our
communications should be clear and empathetic there are still limits as to
how much time we can spend on our emails (and how many words others will
read). At some point the reader will need to take responsibility for their
own reactions.

Best Regards,
Myrle

Re: [ANNOUNCE] Apache Dubbo OPS (incubating) 0.1 has been released

[Ian Luo]

Congratulations, at meantime it would be nice if you could share all of us
the plan of the next release.

-Ian.

On Fri, Feb 15, 2019 at 6:07 PM Minxuan Zhuang  wrote:

> Hi community,
>
> The Apache Dubbo(incubating) team is pleasured to announce that the
> Apache Dubbo OPS (Incubating) 0.1 has just been released.
>
> The source release[1] is available now, you can also find the detailed
> release notes here[2].
>
> If you have any usage questions, or have problems when upgrading or find
> any problems about enhancements included in this release, please don’t
> hesitate to let us know by sending feedback to this mailing list or filing
> an issue on GitHub[3].
>
> [1]
>
> https://www.apache.org/dyn/closer.cgi?path=incubator/dubbo/dubbo-ops/0.1/apache-dubbo-ops-incubating-0.1-source-release.zip
> [2] https://github.com/apache/incubator-dubbo-ops/releases
> [3] https://github.com/apache/incubator-dubbo-ops/issues
>
>
> Best Regards,
>
> The Apache Dubbo (Incubating) Team
>

Re: [Proposal] Apache TVM

[Bertrand Delacretaz]

Hi,

On Fri, Feb 15, 2019 at 7:42 PM Markus Weimer  wrote:
> ...(3) The project contains hardware as a software artifact. We are not
> aware of another ASF project like that and wonder if and how it
> affects its acceptance into the incubator...

If the Apache License works for those artifacts I think that's fine,
and personally I like it a lot if we're expanding into new fields.

If changes are needed in our processes or anything else I'm happy to
help - I suppose I'll be following this podling anyway, sounds
exciting.

-Bertrand

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Fwd: [DISCUSS] can we use weex.io as the short domain namefortheapache project

[吴晟 Sheng Wu]

> weex.apache.org is fast too from my network environment now.


The Chinese network status is strange, we all know. :) Right?

> We had received several complaint years ago from Chinese users that
weex.apache.org is slow, so we launched weex-project.io with the same
content of weex.apache.org. If this is against rules, I think we can make
it redirect to weex.apache.org, not sure whether we would receive complaint
again.

In my mind, redirect is better. You could try, and listen to the community. 


If really need some another, I suggest you to talk with Brand Management 
Committee.[1]


Maybe publish an website, but don't use `weex` in name and say clearly, this is 
not Apache Weex official documents, 
just documents maintained by volunteers. This is not so cool, I know.


[1] https://www.apache.org/foundation/marks/#whoweare


--
Sheng Wu
Apache SkyWalking, ShardingSphere, Zipkin
Twitter, wusheng1108


 




-- Original --
From:  "申远";
Date:  Mon, Feb 18, 2019 05:07 PM
To:  "general";

Subject:  Re: Fwd: [DISCUSS] can we use weex.io as the short domain 
namefortheapache project



weex.apache.org is fast too from my network environment now.

We had received several complaint years ago from Chinese users that
weex.apache.org is slow, so we launched weex-project.io with the same
content of weex.apache.org. If this is against rules, I think we can make
it redirect to weex.apache.org, not sure whether we would receive complaint
again.

Best Regards,
YorkShen

申远


吴晟 Sheng Wu  于2019年2月18日周一 下午4:56写道：

> Hi
>
>
> I don't know why it is slow, I just tried, very quickly.
>
>
>
>
> --
> Sheng Wu
> Apache SkyWalking, ShardingSphere, Zipkin
> Twitter, wusheng1108
>
>
>
>
>
>
>
> -- Original --
> From:  "申远";
> Date:  Mon, Feb 18, 2019 04:33 PM
> To:  "general";
>
> Subject:  Re: Fwd: [DISCUSS] can we use weex.io as the short domain name
> fortheapache project
>
>
>
> >
> > 3. I don't think ASF websites are facing GFW issue.
>
> ASF website is quite slow when accessing from China, I am not sure whether
> this is a GFW issue or simply the server is on another continent without a
> CDN.
>
> We received complains about weex.apache.org from China mainland years ago,
> so we deploy website to weex-project.io for fast access in China, as many
> of our users are from China and there is CDN for weex-project.io .  If
> there is a solution for this issue, please let me know.
>
> Best Regards,
> YorkShen
>
> 申远
>
>
> 吴晟 Sheng Wu  于2019年2月18日周一 下午3:52写道：
>
> > Hi YorkShen
> >
> >
> > From my understanding, weex project, including branding and logo, should
> > be donated to ASF(at least before Graduation).
> > The basic policy is, weex.apache.org should be the only official website
> > for the project.
> > And project's website should be hosted in Apache Infra.
> >
> >
> > If you have others, let's say weex.io and weex-project.io, and run by
> > your committers team, I suggest
> > 1. Set redirect for `weex.io` to `weex.apache.org`, for the end user
> > convenience.
> > 2. For the Chinese documents, if your committers/contributors maintain
> > this, put it in `http://weex.apache.org/cn/`makes
> 
> >  sense.
> > 3. I don't think ASF websites are facing GFW issue.
> >
> >
> > If you want to publish another domain/website for ecosystem, you should
> > avoid using `weex-`, `weex.`, to avoid branding issues.
> > And I suggest you don't do that, because the community will be split.
> >
> >
> > The following are just suggestions from my experiences.
> > Blog(cn/en) post are popular in many Apache project, which could be
> easily
> > supported by our CI hook in GitHub, also have post control and review.
> > If you want helps from this, ping me or `d...@skywalking.apache.org`, we
> > have done something.
> >
> >
> > For Q robots, if you are running that on GitHub issue, a Robot account
> > with project subscription should be good enough.
> > If you want to do that at Website, I think it will be more complex.
> >
> >
> > --
> > Sheng Wu
> > Apache SkyWalking, ShardingSphere, Zipkin
> > Twitter, wusheng1108
> >
> >
> >
> >
> >
> >
> >
> > -- Original --
> > From:  "申远";
> > Date:  Mon, Feb 18, 2019 03:07 PM
> > To:  "general";
> >
> > Subject:  Fwd: [DISCUSS] can we use weex.io as the short domain name for
> > theapache project
> >
> >
> >
> > Hi, there
> >
> > I am a PPMC member of incubator-weex, there is some confusion about
> > third-party domain and it seems like difficult to resolve in dev@
> mailing
> > list, maybe someone here could give a hand to solve the problem of
> domains.
> >
> > 1.I 'd like to know if there is a formal rule that projects should use
> > xxx.apache.org instead of xxx.io, which is shorter and easier to
> remember.
> > 2. we have another domain  weex-project.io for fast access of Çhinese
> > Developers 

Re: Fwd: [DISCUSS] can we use weex.io as the short domain name fortheapache project

[申远]

weex.apache.org is fast too from my network environment now.

We had received several complaint years ago from Chinese users that
weex.apache.org is slow, so we launched weex-project.io with the same
content of weex.apache.org. If this is against rules, I think we can make
it redirect to weex.apache.org, not sure whether we would receive complaint
again.

Best Regards,
YorkShen

申远


吴晟 Sheng Wu  于2019年2月18日周一 下午4:56写道：

> Hi
>
>
> I don't know why it is slow, I just tried, very quickly.
>
>
>
>
> --
> Sheng Wu
> Apache SkyWalking, ShardingSphere, Zipkin
> Twitter, wusheng1108
>
>
>
>
>
>
>
> -- Original --
> From:  "申远";
> Date:  Mon, Feb 18, 2019 04:33 PM
> To:  "general";
>
> Subject:  Re: Fwd: [DISCUSS] can we use weex.io as the short domain name
> fortheapache project
>
>
>
> >
> > 3. I don't think ASF websites are facing GFW issue.
>
> ASF website is quite slow when accessing from China, I am not sure whether
> this is a GFW issue or simply the server is on another continent without a
> CDN.
>
> We received complains about weex.apache.org from China mainland years ago,
> so we deploy website to weex-project.io for fast access in China, as many
> of our users are from China and there is CDN for weex-project.io .  If
> there is a solution for this issue, please let me know.
>
> Best Regards,
> YorkShen
>
> 申远
>
>
> 吴晟 Sheng Wu  于2019年2月18日周一 下午3:52写道：
>
> > Hi YorkShen
> >
> >
> > From my understanding, weex project, including branding and logo, should
> > be donated to ASF(at least before Graduation).
> > The basic policy is, weex.apache.org should be the only official website
> > for the project.
> > And project's website should be hosted in Apache Infra.
> >
> >
> > If you have others, let's say weex.io and weex-project.io, and run by
> > your committers team, I suggest
> > 1. Set redirect for `weex.io` to `weex.apache.org`, for the end user
> > convenience.
> > 2. For the Chinese documents, if your committers/contributors maintain
> > this, put it in `http://weex.apache.org/cn/`makes
> 
> >  sense.
> > 3. I don't think ASF websites are facing GFW issue.
> >
> >
> > If you want to publish another domain/website for ecosystem, you should
> > avoid using `weex-`, `weex.`, to avoid branding issues.
> > And I suggest you don't do that, because the community will be split.
> >
> >
> > The following are just suggestions from my experiences.
> > Blog(cn/en) post are popular in many Apache project, which could be
> easily
> > supported by our CI hook in GitHub, also have post control and review.
> > If you want helps from this, ping me or `d...@skywalking.apache.org`, we
> > have done something.
> >
> >
> > For Q robots, if you are running that on GitHub issue, a Robot account
> > with project subscription should be good enough.
> > If you want to do that at Website, I think it will be more complex.
> >
> >
> > --
> > Sheng Wu
> > Apache SkyWalking, ShardingSphere, Zipkin
> > Twitter, wusheng1108
> >
> >
> >
> >
> >
> >
> >
> > -- Original --
> > From:  "申远";
> > Date:  Mon, Feb 18, 2019 03:07 PM
> > To:  "general";
> >
> > Subject:  Fwd: [DISCUSS] can we use weex.io as the short domain name for
> > theapache project
> >
> >
> >
> > Hi, there
> >
> > I am a PPMC member of incubator-weex, there is some confusion about
> > third-party domain and it seems like difficult to resolve in dev@
> mailing
> > list, maybe someone here could give a hand to solve the problem of
> domains.
> >
> > 1.I 'd like to know if there is a formal rule that projects should use
> > xxx.apache.org instead of xxx.io, which is shorter and easier to
> remember.
> > 2. we have another domain  weex-project.io for fast access of Çhinese
> > Developers as GFW have some confluence on https://weex.apache.org/cn/.
> Is
> > this against rules for apache project.
> >
> > Best Regards,
> > YorkShen
> >
> > 申远
> >
> >
> > -- Forwarded message -
> > From: Dan 
> > Date: 2019年2月15日周五 下午2:39
> > Subject: [DISCUSS] can we use weex.io as the short domain name for the
> > apache project
> > To: 
> >
> >
> > Hi, Myrle/Willem,
> >
> > Currently, we have a domain name of weex.io and want to use it to
> replace
> > the previous weex-project.io domain name for the following reasons:
> >
> > 1. The domain name is shorter and easier to remember.
> > 2. Apache's website has slower access to the developer in China, so there
> > is a mirror website weex-project.io for Chinese developer.
> > 3. We expect to support https on this website and support some of our own
> > server functions, such as Q robots, article blog posts, etc.
> >
> > I would like to ask if apache has any restrictions on this third-party
> > domain name, and look forward to hearing from you.
> >
> > Thanks,
> > Dan

Re: Fwd: [DISCUSS] can we use weex.io as the short domain name fortheapache project

[吴晟 Sheng Wu]

Hi


I don't know why it is slow, I just tried, very quickly. 




--
Sheng Wu
Apache SkyWalking, ShardingSphere, Zipkin
Twitter, wusheng1108


 




-- Original --
From:  "申远";
Date:  Mon, Feb 18, 2019 04:33 PM
To:  "general";

Subject:  Re: Fwd: [DISCUSS] can we use weex.io as the short domain name 
fortheapache project



>
> 3. I don't think ASF websites are facing GFW issue.

ASF website is quite slow when accessing from China, I am not sure whether
this is a GFW issue or simply the server is on another continent without a
CDN.

We received complains about weex.apache.org from China mainland years ago,
so we deploy website to weex-project.io for fast access in China, as many
of our users are from China and there is CDN for weex-project.io .  If
there is a solution for this issue, please let me know.

Best Regards,
YorkShen

申远


吴晟 Sheng Wu  于2019年2月18日周一 下午3:52写道：

> Hi YorkShen
>
>
> From my understanding, weex project, including branding and logo, should
> be donated to ASF(at least before Graduation).
> The basic policy is, weex.apache.org should be the only official website
> for the project.
> And project's website should be hosted in Apache Infra.
>
>
> If you have others, let's say weex.io and weex-project.io, and run by
> your committers team, I suggest
> 1. Set redirect for `weex.io` to `weex.apache.org`, for the end user
> convenience.
> 2. For the Chinese documents, if your committers/contributors maintain
> this, put it in `http://weex.apache.org/cn/`makes
>  sense.
> 3. I don't think ASF websites are facing GFW issue.
>
>
> If you want to publish another domain/website for ecosystem, you should
> avoid using `weex-`, `weex.`, to avoid branding issues.
> And I suggest you don't do that, because the community will be split.
>
>
> The following are just suggestions from my experiences.
> Blog(cn/en) post are popular in many Apache project, which could be easily
> supported by our CI hook in GitHub, also have post control and review.
> If you want helps from this, ping me or `d...@skywalking.apache.org`, we
> have done something.
>
>
> For Q robots, if you are running that on GitHub issue, a Robot account
> with project subscription should be good enough.
> If you want to do that at Website, I think it will be more complex.
>
>
> --
> Sheng Wu
> Apache SkyWalking, ShardingSphere, Zipkin
> Twitter, wusheng1108
>
>
>
>
>
>
>
> -- Original --
> From:  "申远";
> Date:  Mon, Feb 18, 2019 03:07 PM
> To:  "general";
>
> Subject:  Fwd: [DISCUSS] can we use weex.io as the short domain name for
> theapache project
>
>
>
> Hi, there
>
> I am a PPMC member of incubator-weex, there is some confusion about
> third-party domain and it seems like difficult to resolve in dev@ mailing
> list, maybe someone here could give a hand to solve the problem of domains.
>
> 1.I 'd like to know if there is a formal rule that projects should use
> xxx.apache.org instead of xxx.io, which is shorter and easier to remember.
> 2. we have another domain  weex-project.io for fast access of Çhinese
> Developers as GFW have some confluence on https://weex.apache.org/cn/. Is
> this against rules for apache project.
>
> Best Regards,
> YorkShen
>
> 申远
>
>
> -- Forwarded message -
> From: Dan 
> Date: 2019年2月15日周五 下午2:39
> Subject: [DISCUSS] can we use weex.io as the short domain name for the
> apache project
> To: 
>
>
> Hi, Myrle/Willem,
>
> Currently, we have a domain name of weex.io and want to use it to replace
> the previous weex-project.io domain name for the following reasons:
>
> 1. The domain name is shorter and easier to remember.
> 2. Apache's website has slower access to the developer in China, so there
> is a mirror website weex-project.io for Chinese developer.
> 3. We expect to support https on this website and support some of our own
> server functions, such as Q robots, article blog posts, etc.
>
> I would like to ask if apache has any restrictions on this third-party
> domain name, and look forward to hearing from you.
>
> Thanks,
> Dan

Re: Fwd: [DISCUSS] can we use weex.io as the short domain name for theapache project

[申远]

>
> 3. I don't think ASF websites are facing GFW issue.

ASF website is quite slow when accessing from China, I am not sure whether
this is a GFW issue or simply the server is on another continent without a
CDN.

We received complains about weex.apache.org from China mainland years ago,
so we deploy website to weex-project.io for fast access in China, as many
of our users are from China and there is CDN for weex-project.io .  If
there is a solution for this issue, please let me know.

Best Regards,
YorkShen

申远


吴晟 Sheng Wu  于2019年2月18日周一 下午3:52写道：

> Hi YorkShen
>
>
> From my understanding, weex project, including branding and logo, should
> be donated to ASF(at least before Graduation).
> The basic policy is, weex.apache.org should be the only official website
> for the project.
> And project's website should be hosted in Apache Infra.
>
>
> If you have others, let's say weex.io and weex-project.io, and run by
> your committers team, I suggest
> 1. Set redirect for `weex.io` to `weex.apache.org`, for the end user
> convenience.
> 2. For the Chinese documents, if your committers/contributors maintain
> this, put it in `http://weex.apache.org/cn/`makes
>  sense.
> 3. I don't think ASF websites are facing GFW issue.
>
>
> If you want to publish another domain/website for ecosystem, you should
> avoid using `weex-`, `weex.`, to avoid branding issues.
> And I suggest you don't do that, because the community will be split.
>
>
> The following are just suggestions from my experiences.
> Blog(cn/en) post are popular in many Apache project, which could be easily
> supported by our CI hook in GitHub, also have post control and review.
> If you want helps from this, ping me or `d...@skywalking.apache.org`, we
> have done something.
>
>
> For Q robots, if you are running that on GitHub issue, a Robot account
> with project subscription should be good enough.
> If you want to do that at Website, I think it will be more complex.
>
>
> --
> Sheng Wu
> Apache SkyWalking, ShardingSphere, Zipkin
> Twitter, wusheng1108
>
>
>
>
>
>
>
> -- Original --
> From:  "申远";
> Date:  Mon, Feb 18, 2019 03:07 PM
> To:  "general";
>
> Subject:  Fwd: [DISCUSS] can we use weex.io as the short domain name for
> theapache project
>
>
>
> Hi, there
>
> I am a PPMC member of incubator-weex, there is some confusion about
> third-party domain and it seems like difficult to resolve in dev@ mailing
> list, maybe someone here could give a hand to solve the problem of domains.
>
> 1.I 'd like to know if there is a formal rule that projects should use
> xxx.apache.org instead of xxx.io, which is shorter and easier to remember.
> 2. we have another domain  weex-project.io for fast access of Çhinese
> Developers as GFW have some confluence on https://weex.apache.org/cn/. Is
> this against rules for apache project.
>
> Best Regards,
> YorkShen
>
> 申远
>
>
> -- Forwarded message -
> From: Dan 
> Date: 2019年2月15日周五 下午2:39
> Subject: [DISCUSS] can we use weex.io as the short domain name for the
> apache project
> To: 
>
>
> Hi, Myrle/Willem,
>
> Currently, we have a domain name of weex.io and want to use it to replace
> the previous weex-project.io domain name for the following reasons:
>
> 1. The domain name is shorter and easier to remember.
> 2. Apache's website has slower access to the developer in China, so there
> is a mirror website weex-project.io for Chinese developer.
> 3. We expect to support https on this website and support some of our own
> server functions, such as Q robots, article blog posts, etc.
>
> I would like to ask if apache has any restrictions on this third-party
> domain name, and look forward to hearing from you.
>
> Thanks,
> Dan

[ANNOUNCE] Apache Doris (incubating) 0.9.0 Release

[德 李]

Hi All,

We are pleased to announce the release of Apache Doris 0.9.0-incubating.

Apache Doris (incubating) is an MPP-based interactive SQL data warehousing
for reporting and analysis.

The release is available at:
http://doris.apache.org/downloads.html

Thanks to everyone who has contributed to this release, and the release note
can be found here:
https://github.com/apache/incubator-doris/releases

Best Regards,

On behalf of the Doris team,
Reed