Help wanted about the license of the theme for building SkyWalking's website.

[peng-yongsheng]

Hello Incubator PMC’ers,

I purchased a WordPress theme from the site of https://themeforest.net, and
this theme's license is a regular license.

This license description is:
1. You are licensed to use the Item to create one single End Product for
yourself or for one client (a “single application”), and the End Product
can be distributed for Free.
2. You can create one End Product for a client, and you can transfer that
single End Product to your client for any fee. This license is then
transferred to your client.


And the ThemeForest say something can't do with the theme:
1. You can’t Sell the End Product, except to one client. (If you or your
client want to Sell the End Product, you will need the Extended License.)
2. You can’t re-distribute the Item as stock, in a tool or template, or
with source files. You can’t do this with an Item either on its own or
bundled with other items, and even if you modify the Item. You can’t
re-distribute or make available the Item as-is or with superficial
modifications. These things are not allowed even if the re-distribution is
for Free
3. You can’t use the Item in any application allowing an end user to
customise a digital or physical product to their specific needs, such as an
“on demand”, “made to order” or “build it yourself” application. You can
use the Item in this way only if you purchase a separate license for each
final product incorporating the Item that is created using the application.
4. Although you can modify the Item and therefore delete unwanted
components before creating your single End Product, you can’t extract and
use a single component of an Item on a stand-alone basis.

The detail of regular license:
https://themeforest.net/licenses/terms/regular/2.2%20(Copy)

*Can we use this theme for building SkyWalking's website?*


*The attachment is the authorization file of the theme.*

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

Re: Help wanted about the license of the theme for building SkyWalking's website.

[Shane Curcuru]

Can you provide a link to the specific theme?

On first look, I don't see how this can be appropriate for building any
major part of an Apache project's web presence.  The licenses there
would seem to prevent other people from forking any of the website,
which would not be appropriate.  For example, the License FAQ:

"8. You can’t re-distribute the Item as stock, in a tool or template, or
with source files. You can’t do this with an Item either on its own or
bundled with other items, and even if you modify the Item. You can’t
re-distribute or make available the Item as-is or with superficial
modifications. These things are not allowed even if the re-distribution
is for Free."

That seems to say that you couldn't put the theme files in a public SVN
repository, which means... other project committers couldn't build the
website.

Reminder: it's a good idea to get feedback here on general@, but if the
feedback you get doesn't have a definitive answer, then head over to the
Legal Affairs Committee to get a specific answer.


-- 

- Shane
  IPMC & Member
  The Apache Software Foundation

peng-yongsheng wrote on 7/25/18 10:34 AM:
> Hello Incubator PMC’ers,
> 
> I purchased a WordPress theme from the site of https://themeforest.net,
> and this theme's license is a regular license.  
> 
> This license description is: 
> 1. You are licensed to use the Item to create one single End Product for
> yourself or for one client (a “single application”), and the End Product
> can be distributed for Free.
> 2. You can create one End Product for a client, and you can transfer
> that single End Product to your client for any fee. This license is then
> transferred to your client.
> 
> 
> And the ThemeForest say something can't do with the theme: 
> 1. You can’t Sell the End Product, except to one client. (If you or your
> client want to Sell the End Product, you will need the Extended License.)
> 2. You can’t re-distribute the Item as stock, in a tool or template, or
> with source files. You can’t do this with an Item either on its own or
> bundled with other items, and even if you modify the Item. You can’t
> re-distribute or make available the Item as-is or with superficial
> modifications. These things are not allowed even if the re-distribution
> is for Free
> 3. You can’t use the Item in any application allowing an end user to
> customise a digital or physical product to their specific needs, such as
> an “on demand”, “made to order” or “build it yourself” application. You
> can use the Item in this way only if you purchase a separate license for
> each final product incorporating the Item that is created using the
> application.
> 4. Although you can modify the Item and therefore delete unwanted
> components before creating your single End Product, you can’t extract
> and use a single component of an Item on a stand-alone basis.
> 
> The detail of regular license:
> https://themeforest.net/licenses/terms/regular/2.2%20(Copy)
> 
> 
> *Can we use this theme for building SkyWalking's website?*
> *
> *
> *The attachment is the authorization file of the theme.
> *

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

[VOTE] Pulsar Release 2.1.0-incubating Candidate 5

[Sijie Guo]

This is the 5th release candidate for Apache Pulsar, version
2.1.0-incubating.

Link to the vote on dev@pulsar list:
https://lists.apache.org/thread.html/9f1ec1266c02dde859d19e11a61416b3747eb4920d8bd8868dbb2988@%3Cdev.pulsar.apache.org%3E

Pulsar is a highly scalable, low latency messaging platform running on
commodity hardware.
It provides simple pub-sub semantics over topics, guaranteed at-least-once
and effective-once delivery of messages, automatic cursor management for
subscribers, and geo-replication.

This is a feature release, introducing following new features:

- Pulsar I/O: a serverless connector framework built on top of Pulsar
Functions.
- TieredStorage: offloads bookkeeper ledgers to a cold storage (like S3).
- Stateful Function: Pulsar Functions supports storing state back to
bookkeeper.
- Go Client: a Go client wrapping over existing cpp client.
- Avro and Protobuf schema are supported.

Full list of changes and fixes are available:

https://github.com/apache/incubator-pulsar/milestone/13?closed=1

*** Please download, test and vote on this release. This vote will stay open
for at least 72 hours ***

Note that we are voting upon the source (tag), binaries are provided for
convenience.

Source and binary files:
https://dist.apache.org/repos/dist/dev/incubator/pulsar/pulsar-2.1.0-incubating-candidate-5/

SHA-1 checksums:

f0f6b6d7c48d119da36fc4fa1f934fd1f9ba8498
./apache-pulsar-2.1.0-incubating-bin.tar.gz

b6a968249a7c5d21be89ece27895b862efda9a92
./apache-pulsar-2.1.0-incubating-src.tar.gz

ddcf929eb18082ff2b9979507054453e8e803ed3
./apache-pulsar-io-connectors-2.1.0-incubating-bin.tar.gz


Maven staging repo:
https://repository.apache.org/content/repositories/orgapachepulsar-1025/

The tag to be voted upon:
v2.1.0-incubating-candidate-5 (75f79b77f55fbad351cb517e7f3b8ba4ab2dc177)
https://github.com/apache/incubator-pulsar/releases/tag/v2.1.0-incubating-candidate-5

Pulsar's KEYS file containing PGP keys we use to sign the release:
https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS

Please download the the source package, and follow the README to build
and run the Pulsar standalone service.

A few notes for voting 2.1.0 release:

- For compiling source distribution, use "mvn clean install
-Dmaven.gitcommitid.skip=true
[-DskipTests]".
- Starting from this release, Pulsar is shipping RPM & DEB packages for
pulsar non-java clients.
- Starting from this release, Pulsar is shipping a binary distribution
called `apache-pulsar-io-connectors`
  including all built-in connectors. Each connector is packaged with all
their dependencies and
  a META-INF/DEPEDENCIES file with licensing information for
all dependencies.
- Since there are a lot of features introduced in 2.1, You can use the
instructions documented in the link for
  validating the binary release candidate:
https://github.com/apache/incubator-pulsar/wiki/Release-Candidate-Validation

- Sijie

Re: [VOTE] Pulsar Release 2.1.0-incubating Candidate 5

[Dave Fisher]

Hi -

Repeating my +1 IPMC binding from the dev list VOTE

Regards,
Dave

> On Jul 25, 2018, at 11:17 AM, Sijie Guo  wrote:
> 
> This is the 5th release candidate for Apache Pulsar, version
> 2.1.0-incubating.
> 
> Link to the vote on dev@pulsar list:
> https://lists.apache.org/thread.html/9f1ec1266c02dde859d19e11a61416b3747eb4920d8bd8868dbb2988@%3Cdev.pulsar.apache.org%3E
> 
> Pulsar is a highly scalable, low latency messaging platform running on
> commodity hardware.
> It provides simple pub-sub semantics over topics, guaranteed at-least-once
> and effective-once delivery of messages, automatic cursor management for
> subscribers, and geo-replication.
> 
> This is a feature release, introducing following new features:
> 
> - Pulsar I/O: a serverless connector framework built on top of Pulsar
> Functions.
> - TieredStorage: offloads bookkeeper ledgers to a cold storage (like S3).
> - Stateful Function: Pulsar Functions supports storing state back to
> bookkeeper.
> - Go Client: a Go client wrapping over existing cpp client.
> - Avro and Protobuf schema are supported.
> 
> Full list of changes and fixes are available:
> 
> https://github.com/apache/incubator-pulsar/milestone/13?closed=1
> 
> *** Please download, test and vote on this release. This vote will stay open
> for at least 72 hours ***
> 
> Note that we are voting upon the source (tag), binaries are provided for
> convenience.
> 
> Source and binary files:
> https://dist.apache.org/repos/dist/dev/incubator/pulsar/pulsar-2.1.0-incubating-candidate-5/
> 
> SHA-1 checksums:
> 
> f0f6b6d7c48d119da36fc4fa1f934fd1f9ba8498
> ./apache-pulsar-2.1.0-incubating-bin.tar.gz
> 
> b6a968249a7c5d21be89ece27895b862efda9a92
> ./apache-pulsar-2.1.0-incubating-src.tar.gz
> 
> ddcf929eb18082ff2b9979507054453e8e803ed3
> ./apache-pulsar-io-connectors-2.1.0-incubating-bin.tar.gz
> 
> 
> Maven staging repo:
> https://repository.apache.org/content/repositories/orgapachepulsar-1025/
> 
> The tag to be voted upon:
> v2.1.0-incubating-candidate-5 (75f79b77f55fbad351cb517e7f3b8ba4ab2dc177)
> https://github.com/apache/incubator-pulsar/releases/tag/v2.1.0-incubating-candidate-5
> 
> Pulsar's KEYS file containing PGP keys we use to sign the release:
> https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS
> 
> Please download the the source package, and follow the README to build
> and run the Pulsar standalone service.
> 
> A few notes for voting 2.1.0 release:
> 
> - For compiling source distribution, use "mvn clean install
> -Dmaven.gitcommitid.skip=true
> [-DskipTests]".
> - Starting from this release, Pulsar is shipping RPM & DEB packages for
> pulsar non-java clients.
> - Starting from this release, Pulsar is shipping a binary distribution
> called `apache-pulsar-io-connectors`
>  including all built-in connectors. Each connector is packaged with all
> their dependencies and
>  a META-INF/DEPEDENCIES file with licensing information for
> all dependencies.
> - Since there are a lot of features introduced in 2.1, You can use the
> instructions documented in the link for
>  validating the binary release candidate:
> https://github.com/apache/incubator-pulsar/wiki/Release-Candidate-Validation
> 
> - Sijie



signature.asc
Description: Message signed with OpenPGP

Re: [VOTE] Release Apache NetBeans 9.0 (incubating) [vote candidate 3]

[Geertjan Wielenga]

Here's an article that is really well done and describes the context of
this vote thread, maybe helpful as background info here:

*https://adtmag.com/blogs/watersworks/2018/07/netbeans-9-almost-final.aspx
*

Thanks,

Gj




On Tue, Jul 24, 2018 at 11:27 AM, Geertjan Wielenga <
geertjan.wiele...@googlemail.com> wrote:

> Hi all,
>
> Not directly relevant since this is relevant to the functioning of the
> convenience binary, but it might be interesting from an informative point
> of view for all to know that the Apache NetBeans (incubating) community has
> done a Community Acceptance survey [1] for users of the upcoming Apache
> NetBeans (incubating) 9.0. I.e., the survey is about the usage and
> functionality of the convenience binary of the voting candidate under
> consideration in this thread and the results are documented below.
>
> [1] https://cwiki.apache.org/confluence/display/NETBEANS/
> Results+from+Apache+NetBeans+IDE+9.0+Community+Acceptance+survey
>
> Thanks,
>
> Gj
>
>
>
> On Tue, Jul 24, 2018 at 7:27 AM, Emilian Bold  invalid> wrote:
>
>> Hi all,
>>
>> The Apache NetBeans community has voted on and approved a proposal to
>> release Apache NetBeans 9.0 (incubating) [vc3].
>>
>> We now kindly request that the Incubator PMC members review and vote on
>> this incubator release candidate.
>>
>> Vote thread:
>>
>> https://lists.apache.org/thread.html/a644bb8e3ba2cbd06328bb0
>> 04f1b18b4171763cd3d78a9131615f687@%3Cdev.netbeans.apache.org%3E
>>
>> Vote result thread:
>>
>> https://lists.apache.org/thread.html/31f8a8fd70dc2ba635c6a67
>> 693c512ed9e5b30af99fbe79afe55293b@%3Cdev.netbeans.apache.org%3E
>>
>> In the above, note there are two IPMC binding votes from Ate Douma and
>> Bertrand Delacretaz, both Apache NetBeans (incubating) mentors, 11 PPMC
>> votes and 16 Apache NetBeans community votes.
>>
>> Apache NetBeans 9.0 (incubating) constitutes all the modules in the
>> Apache NetBeans Git repo, which together provide the NetBeans Platform
>> (i.e., the underlying application framework), as well as all the modules
>> that provide the Java SE-related features of Apache NetBeans.
>>
>> In short, Apache NetBeans 9.0 (incubating) is a full IDE for Java SE
>> development.
>>
>> Build artifacts available here:
>>
>> https://dist.apache.org/repos/dist/dev/incubator/netbeans/in
>> cubating-netbeans-java/incubating-9.0-vc3
>>
>> The specific artifact to be voted on:
>>
>> https://dist.apache.org/repos/dist/dev/incubator/netbeans/in
>> cubating-netbeans-java/incubating-9.0-vc3/incubating-netbean
>> s-java-9.0-source.zip
>>
>> Included in the above are the DEPENDENCIES, DISCLAIMER, LICENSE, and
>> NOTICE files, as well as a README file with build instructions, which are
>> the same as these:
>>
>> https://gitbox.apache.org/repos/asf?p=incubator-netbeans.
>> git;a=blob_plain;f=README.md;h=eccd3c6cc707ba9ca219bcfb7297
>> 9435d85f5f7a;hb=97904961e496383d6150aef9b78fa8dff8f3e1ce
>>
>> SHA1: ed2098c173460ec81f05635055066da06a7ea82b
>>
>> KEYS file:
>>
>> https://dist.apache.org/repos/dist/release/incubator/netbeans/KEYS
>>
>> Apache NetBeans Git Repo tag: 9.0-vc3 :
>>
>> https://gitbox.apache.org/repos/asf?p=incubator-netbeans.
>> git;a=tag;h=refs/tags/9.0-vc3
>>
>> Note: NetBeans license violation checks are managed via the
>> rat-exclusions.txt file:
>>
>> https://gitbox.apache.org/repos/asf?p=incubator-netbeans.
>> git;a=blob;f=nbbuild/rat-exclusions.txt;h=36cb8a3eae40b
>> d7fc41c63c6055bce42f7916859;hb=97904961e496383d6150aef9b78fa8dff8f3e1ce
>>
>> Rat report shows no unknown licenses, except for license files:
>>
>> https://builds.apache.org/job/incubator-netbeans-release/334
>> /artifact/rat-java-temp/nbbuild/build/rat-report.txt
>>
>> Included as a convenience binary, not relevant for the voting purposes
>> (unzip it, run it and you'll see Apache NetBeans):
>>
>> https://dist.apache.org/repos/dist/dev/incubator/netbeans/in
>> cubating-netbeans-java/incubating-9.0-vc3/incubating-netbean
>> s-java-9.0-bin.zip
>>
>> Also included as a convenience binary the NBMs:
>>
>> https://dist.apache.org/repos/dist/dev/incubator/netbeans/in
>> cubating-netbeans-java/incubating-9.0-vc3/nbms
>>
>> New & Noteworthy features of the 9.0 Release:
>>
>> https://cwiki.apache.org/confluence/display/NETBEANS/Apache+
>> NetBeans+9.0+New+and+Noteworthy
>>
>> Release specific wiki page:
>>
>> https://cwiki.apache.org/confluence/display/NETBEANS/Apache+
>> NetBeans+9.0+Final+Release
>>
>> How (and what) to try out the release:
>>
>> 1. Download the artifact to be voted on and unzip it.
>> 2. Verify the cryptographic signatures, the NOTICE and LICENSE file
>> 3. Build it using the README provided by the artifact.
>> 4. Look in nbbuild/netbeans for the NetBeans installation created by the
>> build process.
>> 5. Run the NetBeans executable and (if you're running on JDK 8) you'll be
>> prompted to install nb-javac, after agreeing to its licensing terms, and
>> (if you

Re: [DISCUSS] Graduate Apache HAWQ (incubating) as a TLP

[Roman Shaposhnik]

It seems that the concerned raised around commercialization of HAWQ by
Oushu Inc have been fully addressed and no additional concerns have
been raised.

With that in mind, I plan to start an official vote over the weekend.

Thanks,
Roman.

On Fri, Jul 13, 2018 at 2:01 AM, Willem Jiang  wrote:
> Hi Radar,
>
> OK, I think I got the answer.
>
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Fri, Jul 13, 2018 at 2:14 PM, Radar Lei  wrote:
>
>> Hi Willem,
>>
>> I did a check but didn't find the '12 PPMC member' is mentioned, would you
>> specify which report it is in? The only similar one I found is we mentioned
>> 'HAWQ New Committers (12)' in ASF Maturity Evaluation
>> > >.
>>
>> For the PMC size 45, we make the proposal because of the total committer
>> number 45 is pretty close with current PPMC member number 38, so we chose
>> to make the PMC=Committers as the graduation resolution.
>>
>> Hope this answers your question. Thanks.
>>
>>
>> Regards,
>> Radar
>>
>> On Thu, Jul 12, 2018 at 9:22 AM, Willem Jiang 
>> wrote:
>>
>> > Just a quick question for the PMC size 45.
>> > From the report, I can see there are 12 PPMC member, but the PMC size is
>> > same with the Committer size.
>> > I guess that could be a typo, am I right?
>> >
>> >
>> >
>> >
>> > Willem Jiang
>> >
>> > Twitter: willemjiang
>> > Weibo: 姜宁willem
>> >
>> > On Fri, Jul 6, 2018 at 9:54 AM, Roman Shaposhnik  wrote:
>> >
>> > > Hi!
>> > >
>> > > HAWQ community seems to be ready to graduate. What
>> > > do fellow IPMC members think?
>> > >
>> > > Details on the community are below and here's a link to
>> > > the DISCUSS thread:
>> > > https://lists.apache.org/thread.html/
>> 67a2d52ef29cbf9e93d8050ed0193c
>> > > c110a919962dd92f8436b343b7@%3Cdev.hawq.apache.org%3E
>> > >
>> > > Thanks,
>> > > Roman.
>> > >
>> > > -- Forwarded message --
>> > > From: Radar Lei 
>> > > Date: Tue, Jun 19, 2018 at 2:40 AM
>> > > Subject: [DISCUSS] Graduate Apache HAWQ (incubating) as a TLP
>> > > To: dev 
>> > >
>> > >
>> > > Hi All,
>> > >
>> > > With the 2.3.0.0-incubating release officially out, the Apache HAWQ
>> > > community and its mentors believe it is time to consider graduation to
>> > the
>> > > TLP:
>> > > https://lists.apache.org/thread.html/b4a0b5671ce377b3d51c9b7
>> > > ab00496a1eebfcbf1696ce8b67e078c64@%3Cdev.hawq.apache.org%3E
>> > >
>> > > Apache HAWQ entered incubation in September of 2015, since then, the
>> HAWQ
>> > > community learned a lot about how to do things in Apache ways. Now we
>> > have
>> > > a healthy and engaged community, ready to help with all questions from
>> > the
>> > > HAWQ community. We delivered four releases including two binary
>> releases,
>> > > now we can do self-driving releases in good cadence. The PPMC has
>> > > demonstrated a good understanding of growing the community by electing
>> 12
>> > > individuals as committers and PPMC members. The PPMC addressed the
>> > maturity
>> > > issues one by one followed by Apache Project Maturity Model, currently
>> > all
>> > > the License and IP issues are resolved. This demonstrated our
>> > understanding
>> > > of ASF's IP policies.
>> > >
>> > > All in all, I believe this project is qualified as a true TLP and we
>> > should
>> > > recognize this fact by formally awarding it such a status. This thread
>> > > means to open up the very same discussion that we had among the mentors
>> > and
>> > > HAWQ community to the rest of the IPMC. It is a DISCUSS thread so feel
>> > free
>> > > to ask questions.
>> > >
>> > > To get you all going, here are a few data points which may help:
>> > >
>> > > Project status:
>> > >  http://incubator.apache.org/projects/hawq.html
>> > >
>> > > Project website:
>> > >   http://hawq.incubator.apache.org/
>> > >
>> > > Project documentation:
>> > >http://hawq.incubator.apache.org/docs/userguide/2.3.0.0-inc
>> > > ubating/overview/HAWQOverview.html
>> > >http://hawq.apache.org/#download
>> > >
>> > > Maturity assessment:
>> > > https://cwiki.apache.org/confluence/display/HAWQ/ASF+
>> Maturity+Evaluation
>> > >
>> > > DRAFT of the board resolution is at the bottom of this email
>> > >
>> > > Proposed PMC size: 45 members
>> > >
>> > > Total number of committers: 45 members
>> > >
>> > > PMC affiliation (* indicated chair):
>> > >Pivotal (20)
>> > >  * Oushu (7)
>> > >Amazon (3)
>> > >Hashdata (2)
>> > >Autonomic (1)
>> > >Confluent (1)
>> > >Datometry (1)
>> > >Hortonworks (1)
>> > >Microsoft (1)
>> > >PETUUM (1)
>> > >Privacera (1)
>> > >Qubole (1)
>> > >Snowflake (1)
>> > >State Street (1)
>> > >Unifi (1)
>> > >Visa (1)
>> > >ZEDEDA (1)
>> > >
>> > > 1549 commits on develop
>> > > 1375 PR”s on GitHub
>> > > 63 contributors across all branches
>> > >
>> > > 1624 issues created
>> > > 1350 issues resolved
>> > >
>> > > dev list averaged ~53 msgs/month over last 

Re: Help wanted about the license of the theme for building SkyWalking's website.

[Yongsheng Peng]

> Can you provide a link to the specific theme?
Link: https://themeforest.net/item/softa-software-wordpress-theme/20868500

> That seems to say that you couldn't put the theme files in a public SVN
> repository, which means... other project committers couldn't build the
> website.
Yes, I have the same understanding.


On 2018/07/25 14:54:35, Shane Curcuru  wrote: 
> Can you provide a link to the specific theme?
> 
> On first look, I don't see how this can be appropriate for building any
> major part of an Apache project's web presence.  The licenses there
> would seem to prevent other people from forking any of the website,
> which would not be appropriate.  For example, the License FAQ:
> 
> "8. You can’t re-distribute the Item as stock, in a tool or template, or
> with source files. You can’t do this with an Item either on its own or
> bundled with other items, and even if you modify the Item. You can’t
> re-distribute or make available the Item as-is or with superficial
> modifications. These things are not allowed even if the re-distribution
> is for Free."
> 
> That seems to say that you couldn't put the theme files in a public SVN
> repository, which means... other project committers couldn't build the
> website.
> 
> Reminder: it's a good idea to get feedback here on general@, but if the
> feedback you get doesn't have a definitive answer, then head over to the
> Legal Affairs Committee to get a specific answer.
> 
> 
> -- 
> 
> - Shane
>   IPMC & Member
>   The Apache Software Foundation
> 
> peng-yongsheng wrote on 7/25/18 10:34 AM:
> > Hello Incubator PMC’ers,
> > 
> > I purchased a WordPress theme from the site of https://themeforest.net,
> > and this theme's license is a regular license.  
> > 
> > This license description is: 
> > 1. You are licensed to use the Item to create one single End Product for
> > yourself or for one client (a “single application”), and the End Product
> > can be distributed for Free.
> > 2. You can create one End Product for a client, and you can transfer
> > that single End Product to your client for any fee. This license is then
> > transferred to your client.
> > 
> > 
> > And the ThemeForest say something can't do with the theme: 
> > 1. You can’t Sell the End Product, except to one client. (If you or your
> > client want to Sell the End Product, you will need the Extended License.)
> > 2. You can’t re-distribute the Item as stock, in a tool or template, or
> > with source files. You can’t do this with an Item either on its own or
> > bundled with other items, and even if you modify the Item. You can’t
> > re-distribute or make available the Item as-is or with superficial
> > modifications. These things are not allowed even if the re-distribution
> > is for Free
> > 3. You can’t use the Item in any application allowing an end user to
> > customise a digital or physical product to their specific needs, such as
> > an “on demand”, “made to order” or “build it yourself” application. You
> > can use the Item in this way only if you purchase a separate license for
> > each final product incorporating the Item that is created using the
> > application.
> > 4. Although you can modify the Item and therefore delete unwanted
> > components before creating your single End Product, you can’t extract
> > and use a single component of an Item on a stand-alone basis.
> > 
> > The detail of regular license:
> > https://themeforest.net/licenses/terms/regular/2.2%20(Copy)
> > 
> > 
> > *Can we use this theme for building SkyWalking's website?*
> > *
> > *
> > *The attachment is the authorization file of the theme.
> > *
> 
> -
> 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