You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@edgent.apache.org by wc...@apache.org on 2016/07/27 21:46:04 UTC
[50/51] [abbrv] [partial] incubator-quarks-website git commit:
[QUARKS-233] Rename Quarks to Edgent * text references * image references *
placeholder logos * Javadoc
http://git-wip-us.apache.org/repos/asf/incubator-quarks-website/blob/05ad5e88/README.md
----------------------------------------------------------------------
diff --git a/README.md b/README.md
index b60e09b..beacb10 100644
--- a/README.md
+++ b/README.md
@@ -17,7 +17,7 @@ limitations under the License.
{% endcomment %}
-->
-# Quarks web site
+# Edgent website
## Location
@@ -45,7 +45,7 @@ If you would like to make a change to the site:
If you are a committer, do the following:
1. Update the master branch with your (or a Pull Request's) change
-2. Push updated master to the [asf remote master](https://git-wip-us.apache.org/repos/asf/incubator-quarks-site.git)
+2. Push updated master to the [ASF remote master](https://git-wip-us.apache.org/repos/asf/incubator-quarks-site.git)
3. Run `build.sh` from the master branch directory (requires Jekyll). This checks out and updates the `asf-site` branch with a new commit of the build from the current branch.
4. At this point, you should be on the `asf-site` branch. Simply push this branch to the asf remote with `git push origin asf-site` and the site will automatically be updated within seconds.
http://git-wip-us.apache.org/repos/asf/incubator-quarks-website/blob/05ad5e88/site/_config.yml
----------------------------------------------------------------------
diff --git a/site/_config.yml b/site/_config.yml
index 298347c..c7820ff 100755
--- a/site/_config.yml
+++ b/site/_config.yml
@@ -26,17 +26,17 @@ platform: all
version: all
output: web
destination: ../_site
-topnav_title: Apache Quarks Documentation
-homepage_title: Apache Quarks Documentation
-site_title: Apache Quarks Documentation
+topnav_title: Apache Edgent Documentation
+homepage_title: Apache Edgent Documentation
+site_title: Apache Edgent Documentation
project_folder: docs
-company_name: Apache Quarks
+company_name: Apache Edgent
footer_image_location: ../../common_images/company_logo.png
github_editme_path: apache/incubator-quarks-website/blob/master/site
disqus_shortname: idrbwjekyll
# variables
-sidebar_tagline: Quarks
+sidebar_tagline: Edgent
sidebar_version: Version 0.3.0
theme_file: theme-blue.css
@@ -91,8 +91,8 @@ defaults:
url: http://quarks.incubator.apache.org
baseurl:
-title: Apache Quarks
-description: Quarks is an open source community for accelerating analytics at the edge.
+title: Apache Edgent
+description: Edgent is an open source community for accelerating analytics at the edge.
# ----------------------- #
# Jekyll & Plugins #
@@ -116,7 +116,7 @@ social:
- title: github
url: https://github.com/quarks-edge/quarks/
- title: stack-overflow
- url: http://stackoverflow.com/questions/ask?tags=quarks
+ url: http://stackoverflow.com/questions/ask?tags=edgent
detach: false
port: 4000
http://git-wip-us.apache.org/repos/asf/incubator-quarks-website/blob/05ad5e88/site/_data/mydoc/mydoc_sidebar.yml
----------------------------------------------------------------------
diff --git a/site/_data/mydoc/mydoc_sidebar.yml b/site/_data/mydoc/mydoc_sidebar.yml
index f43d78a..1b93e81 100644
--- a/site/_data/mydoc/mydoc_sidebar.yml
+++ b/site/_data/mydoc/mydoc_sidebar.yml
@@ -37,7 +37,7 @@ entries:
output: web, pdf
items:
- title: Introduction
- url: /docs/quarks_index.html
+ url: /docs/edgent_index.html
audience: writers, designers
platform: all
product: all
@@ -59,7 +59,7 @@ entries:
output: web, pdf
items:
- title: Getting started guide
- url: /docs/quarks-getting-started.html
+ url: /docs/edgent-getting-started.html
audience: writers, designers
platform: all
product: all
@@ -67,22 +67,22 @@ entries:
output: web, pdf
- title: Common operations
- url: /docs/common-quarks-operations.html
+ url: /docs/common-edgent-operations.html
audience: writers, designers
platform: all
product: all
version: all
output: web, pdf
- - title: Quarks Cookbook
+ - title: Edgent Cookbook
audience: writers, designers
platform: all
product: all
version: all
output: web, pdf
items:
- - title: Hello Quarks!
- url: /recipes/recipe_hello_quarks.html
+ - title: Hello Edgent!
+ url: /recipes/recipe_hello_edgent.html
audience: writers, designers
platform: all
product: all
http://git-wip-us.apache.org/repos/asf/incubator-quarks-website/blob/05ad5e88/site/_data/mydoc/mydoc_topnav.yml
----------------------------------------------------------------------
diff --git a/site/_data/mydoc/mydoc_topnav.yml b/site/_data/mydoc/mydoc_topnav.yml
index 8b752c4..00edad9 100644
--- a/site/_data/mydoc/mydoc_topnav.yml
+++ b/site/_data/mydoc/mydoc_topnav.yml
@@ -39,7 +39,7 @@ topnav:
- title: Topnav
subcategories:
- title: Javadoc
- external_url: http://quarks.incubator.apache.org/javadoc/lastest/index.html
+ external_url: http://quarks.incubator.apache.org/javadoc/latest/index.html
audience: writers, designers
platform: all
product: all
@@ -50,7 +50,7 @@ topnav:
topnav_dropdowns:
- title: Topnav dropdowns
subcategories:
- - title: Quarks Resources
+ - title: Edgent Resources
audience: writers, designers
platform: all
product: all
http://git-wip-us.apache.org/repos/asf/incubator-quarks-website/blob/05ad5e88/site/_data/project.yml
----------------------------------------------------------------------
diff --git a/site/_data/project.yml b/site/_data/project.yml
index dc4b69a..5925d7b 100644
--- a/site/_data/project.yml
+++ b/site/_data/project.yml
@@ -13,14 +13,14 @@
# See the License for the specific language governing permissions and
# limitations under the License.
#
-# Quarks Project configurations
+# Edgent Project configurations
#
-name: Apache Quarks
-short_name: Quarks
+name: Apache Edgent
+short_name: Edgent
unix_name: quarks
incubator_name: incubator-quarks
incubator_slash_name: incubator/quarks
-description: Quarks is a community for accelerating analytics in edge devices.
+description: Edgent is a community for accelerating analytics in edge devices.
download: https://github.com/apache/incubator-quarks
http://git-wip-us.apache.org/repos/asf/incubator-quarks-website/blob/05ad5e88/site/_includes/feedback.html
----------------------------------------------------------------------
diff --git a/site/_includes/feedback.html b/site/_includes/feedback.html
index 30cf13e..1e1e2c2 100644
--- a/site/_includes/feedback.html
+++ b/site/_includes/feedback.html
@@ -13,4 +13,4 @@ window.location.href = uri;
}
</script>
-<li><a href="mailto:dev@quarks.incubator.apache.org" target="_blank"><i class="fa fa-envelope-o"></i> Feedback</a></li>
+<li><a href="mailto:{{ site.data.project.dev_list }}" target="_blank"><i class="fa fa-envelope-o"></i> Feedback</a></li>
http://git-wip-us.apache.org/repos/asf/incubator-quarks-website/blob/05ad5e88/site/_includes/footer.html
----------------------------------------------------------------------
diff --git a/site/_includes/footer.html b/site/_includes/footer.html
index a67708a..b5a0af8 100755
--- a/site/_includes/footer.html
+++ b/site/_includes/footer.html
@@ -10,7 +10,7 @@
<br/>
<div class="row">
<div class="col-md-12">
- <p class="small">Apache Quarks is an effort undergoing Incubation at The Apache Software
+ <p class="small">Apache Edgent is an effort undergoing Incubation at The Apache Software
Foundation (ASF), sponsored by the Incubator. Incubation is required of all newly accepted projects
until a further review indicates that the infrastructure, communications, and decision making process
have stabilized in a manner consistent with other successful ASF projects. While incubation status is
http://git-wip-us.apache.org/repos/asf/incubator-quarks-website/blob/05ad5e88/site/_includes/footer_orig.html
----------------------------------------------------------------------
diff --git a/site/_includes/footer_orig.html b/site/_includes/footer_orig.html
index 185abbc..9aa420e 100644
--- a/site/_includes/footer_orig.html
+++ b/site/_includes/footer_orig.html
@@ -21,13 +21,13 @@ limitations under the License.
<div class="container">
<div class="row">
<div class="col-md-6 col-lg-offset-3">
- <img class="img-responsive center-block" src="img/quarks_incubation.png" alt="">
+ <img class="img-responsive center-block" src="img/edgent_incubation.png" alt="">
</div>
</div>
</br>
<div class="row">
<div class="col-md-12">
- <p class="text-muted small">Apache Quarks is an effort undergoing Incubation at The Apache Software Foundation (ASF), sponsored by the Incubator. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF.</p>
+ <p class="text-muted small">Apache Edgent is an effort undergoing Incubation at The Apache Software Foundation (ASF), sponsored by the Incubator. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF.</p>
</div>
</div>
http://git-wip-us.apache.org/repos/asf/incubator-quarks-website/blob/05ad5e88/site/_includes/header.html
----------------------------------------------------------------------
diff --git a/site/_includes/header.html b/site/_includes/header.html
index 8a86e49..0a5a779 100755
--- a/site/_includes/header.html
+++ b/site/_includes/header.html
@@ -65,29 +65,29 @@ limitations under the License.
<span class="icon-bar"></span>
<span class="icon-bar"></span>
</button>
- <a class="navbar-brand page-scroll" href="http://quarks.incubator.apache.org/#home">Home</a>
+ <a class="navbar-brand page-scroll" href="http://{{ site.data.project.unix_name }}.incubator.apache.org/#home">Home</a>
</div>
<!-- Collect the nav links, forms, and other content for toggling -->
<div class="collapse navbar-collapse" id="bs-example-navbar-collapse-1">
<ul class="nav navbar-nav">
- <li class="dropdown"><a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-haspopup="true" aria-expanded="false">About Quarks</a>
+ <li class="dropdown"><a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-haspopup="true" aria-expanded="false">About Edgent</a>
<ul class="dropdown-menu">
- <li><a href="/docs/overview">About Quarks</a></li>
+ <li><a href="/docs/overview">About Edgent</a></li>
<li><a href="{{ site.sourceurl }}/blob/master/LICENSE">License</a></li>
</ul>
</li>
<li class="dropdown"><a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-haspopup="true" aria-expanded="false">Community</a>
<ul class="dropdown-menu">
<li><a href="docs/community">Get Involved</a></li>
- <li><a href="https://issues.apache.org/jira/browse/QUARKS">Issue Tracker</a></li>
+ <li><a href="https://issues.apache.org/jira/browse/{{ site.data.project.jira }}">Issue Tracker</a></li>
<li><a href="{{ site.sourceurl }}/">Source Code</a></li>
<li><a href="docs/committers">Committers</a></li>
- <li><a href="https://cwiki.apache.org/confluence/display/QUARKS/Apache+Quarks+Wiki+Home">Wiki</a></li>
+ <li><a href="https://cwiki.apache.org/confluence/display/{{ site.data.project.unix_name }}/Apache+{{ site.data.project.unix_name }}+Wiki+Home">Wiki</a></li>
</ul>
</li>
<li class="dropdown"><a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-haspopup="true" aria-expanded="false">Getting Started</a>
<ul class="dropdown-menu">
- <li><a href="docs/quarks-getting-started">Getting Started Guide</a></li>
+ <li><a href="docs/edgent-getting-started">Getting Started Guide</a></li>
<li><a href="{{ site.sourceurl }}">Download Source</a></li>
<li><a href="docs/samples">Sample Programs</a></li>
<li><a href="docs/faq">FAQ</a></li>
@@ -98,7 +98,7 @@ limitations under the License.
<a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-haspopup="true" aria-expanded="false">Documentation</a>
<ul class="dropdown-menu">
<li><a href="docs/home">Documentation Home</a></li>
- <li><a href="{{ site.docsurl }}/lastest/index.html">Javadoc</a></li>
+ <li><a href="{{ site.docsurl }}/latest/index.html">Javadoc</a></li>
</ul>
</li>
<li class="dropdown">
http://git-wip-us.apache.org/repos/asf/incubator-quarks-website/blob/05ad5e88/site/_includes/open_ecosystem.html
----------------------------------------------------------------------
diff --git a/site/_includes/open_ecosystem.html b/site/_includes/open_ecosystem.html
index 6d43b3d..775b2ef 100755
--- a/site/_includes/open_ecosystem.html
+++ b/site/_includes/open_ecosystem.html
@@ -26,7 +26,7 @@ limitations under the License.
<hr class="section-heading-spacer">
<div class="clearfix"></div>
<h2 class="section-heading">An Open IoT Ecosystem</h2>
- <div class="lead">Apache Quarks is API driven and modular and can be used in conjunction with vendor and open source data and analytics solutions such as Apache Kafka, Apache Spark and Apache Storm.
+ <div class="lead">Apache Edgent is API driven and modular and can be used in conjunction with vendor and open source data and analytics solutions such as Apache Kafka, Apache Spark and Apache Storm.
</div>
</div>
<div class="col-lg-7 col-sm-6">
http://git-wip-us.apache.org/repos/asf/incubator-quarks-website/blob/05ad5e88/site/_includes/webcast.html
----------------------------------------------------------------------
diff --git a/site/_includes/webcast.html b/site/_includes/webcast.html
index f6641af..e37eadb 100644
--- a/site/_includes/webcast.html
+++ b/site/_includes/webcast.html
@@ -24,10 +24,10 @@ limitations under the License.
<div class="row">
<div class="col-lg-5 col-sm-6 col-sm-push-7">
- <h2 ><a href="https://plus.google.com/events/c9i8t4j2mqq7g0d6ftad84c5bd8">Hangout: Apache Quarks on Raspberry Pi</a></h2>
+ <h2 ><a href="https://plus.google.com/events/c9i8t4j2mqq7g0d6ftad84c5bd8">Hangout: Apache Edgent on Raspberry Pi</a></h2>
<h4 >Thursday, May 12 10am-11am PDT</h3>
- <div class="lead">In this <a href="https://plus.google.com/events/c9i8t4j2mqq7g0d6ftad84c5bd8">Google+ Hangout</a>, we showed you how you can use Quarks to work with real sensor data on a Raspberry Pi. We also demonstrated an application where we implemented a smart sprinkler system using Apache Quarks, Raspberry Pi, Watson IoT Platform and the Streaming Analytics service.</div>
+ <div class="lead">In this <a href="https://plus.google.com/events/c9i8t4j2mqq7g0d6ftad84c5bd8">Google+ Hangout</a>, we showed you how you can use Edgent to work with real sensor data on a Raspberry Pi. We also demonstrated an application where we implemented a smart sprinkler system using Apache Edgent, Raspberry Pi, Watson IoT Platform and the Streaming Analytics service.</div>
</div>
<div class="col-lg-7 col-sm-pull-5 col-sm-6">
<div class="embed-responsive embed-responsive-16by9">
@@ -49,10 +49,10 @@ limitations under the License.
<div class="row">
<div class="col-lg-5 col-sm-6 col-sm-push-7">
- <h2 ><a href="https://plus.google.com/events/c4v0hjbefda5vcfceffllgncv2k">Hangout: Intro to Apache Quarks</a></h2>
+ <h2 ><a href="https://plus.google.com/events/c4v0hjbefda5vcfceffllgncv2k">Hangout: Intro to Apache Edgent</a></h2>
<h4 >Wednesday, April 13 10am-12pm PDT</h3>
- <div class="lead">In this <a href="https://plus.google.com/events/c4v0hjbefda5vcfceffllgncv2k">Google+ Hangout</a>, the committers presented a high-level overview of the Apache Quarks project and demonstrated how you can write, monitor and debug your Quarks application. They also showed you how you can get involved and contribute to the Quarks community. </div>
+ <div class="lead">In this <a href="https://plus.google.com/events/c4v0hjbefda5vcfceffllgncv2k">Google+ Hangout</a>, the committers presented a high-level overview of the Apache Edgent project and demonstrated how you can write, monitor and debug your Edgent application. They also showed you how you can get involved and contribute to the Edgent community. </div>
</div>
<div class="col-lg-7 col-sm-pull-5 col-sm-6">
<div class="embed-responsive embed-responsive-16by9">
http://git-wip-us.apache.org/repos/asf/incubator-quarks-website/blob/05ad5e88/site/_includes/why_edgent.html
----------------------------------------------------------------------
diff --git a/site/_includes/why_edgent.html b/site/_includes/why_edgent.html
new file mode 100755
index 0000000..c0c9174
--- /dev/null
+++ b/site/_includes/why_edgent.html
@@ -0,0 +1,59 @@
+<!--
+{% comment %}
+Licensed to the Apache Software Foundation (ASF) under one or more
+contributor license agreements. See the NOTICE file distributed with
+this work for additional information regarding copyright ownership.
+The ASF licenses this file to you under the Apache License, Version 2.0
+(the "License"); you may not use this file except in compliance with
+the License. You may obtain a copy of the License at
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
+{% endcomment %}
+-->
+ <section id="services">
+ <div class="content-section-b">
+
+ <div class="container">
+
+ <div class="row">
+ <div class="col-lg-5 col-sm-6">
+ <hr class="section-heading-spacer">
+ <div class="clearfix"></div>
+ <h2 class="section-heading">Why Apache Edgent?</h2>
+ </div>
+ </div>
+
+ <div class="row">
+ <div class="col-lg-4 col-sm-6 box">
+ <div class="text-box">
+ <h4 class="section-heading text-center">Reduced Communication Costs</h4>
+ <div class="clearfix"></div>
+ <div class="lead">Edgent performs real-time analytics on the edge device, separating the interesting from the mundane, so you don\u2019t have to send every sensor reading over a network. If 99% of readings are normal, Edgent detects the 1% anomalies and just transmits those for further processing.
+ </div>
+ </div>
+ </div>
+ <div class="col-lg-4 col-sm-6 box">
+ <div class="text-box">
+ <h4 class="section-heading text-center">Local and Faster Time to Action</h4>
+ <div class="clearfix"></div>
+ <div class="lead">Edgent makes devices more intelligent, enabling them to take immediate action. For example, a connected vehicle running Edgent can adjust traction control based on the weight of the cargo/passengers.</div>
+ </div>
+ </div>
+ <div class="col-lg-4 col-sm-6 box">
+ <div class="text-box">
+ <h4 class="section-heading text-center">Learning From Related Devices</h4>
+ <div class="clearfix"></div>
+ <div class="lead">Edgent enables connected devices to learn from related devices. For example, a truck maneuvering roads in Oregon can adjust based on the data received from trucks operating under similar loads and conditions in Colorado; data such as altitude, cargo, weather and traffic conditions.
+</div>
+ </div>
+ </div>
+ </div>
+
+ </div>
+</section>
http://git-wip-us.apache.org/repos/asf/incubator-quarks-website/blob/05ad5e88/site/_includes/why_quarks.html
----------------------------------------------------------------------
diff --git a/site/_includes/why_quarks.html b/site/_includes/why_quarks.html
deleted file mode 100755
index d8bbce2..0000000
--- a/site/_includes/why_quarks.html
+++ /dev/null
@@ -1,59 +0,0 @@
-<!--
-{% comment %}
-Licensed to the Apache Software Foundation (ASF) under one or more
-contributor license agreements. See the NOTICE file distributed with
-this work for additional information regarding copyright ownership.
-The ASF licenses this file to you under the Apache License, Version 2.0
-(the "License"); you may not use this file except in compliance with
-the License. You may obtain a copy of the License at
-
-http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing, software
-distributed under the License is distributed on an "AS IS" BASIS,
-WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-See the License for the specific language governing permissions and
-limitations under the License.
-{% endcomment %}
--->
- <section id="services">
- <div class="content-section-b">
-
- <div class="container">
-
- <div class="row">
- <div class="col-lg-5 col-sm-6">
- <hr class="section-heading-spacer">
- <div class="clearfix"></div>
- <h2 class="section-heading">Why Apache Quarks?</h2>
- </div>
- </div>
-
- <div class="row">
- <div class="col-lg-4 col-sm-6 box">
- <div class="text-box">
- <h4 class="section-heading text-center">Reduced Communication Costs</h4>
- <div class="clearfix"></div>
- <div class="lead">Quarks performs real-time analytics on the edge device, separating the interesting from the mundane, so you don\u2019t have to send every sensor reading over a network. If 99% of readings are normal, Quarks detects the 1% anomalies and just transmits those for further processing.
- </div>
- </div>
- </div>
- <div class="col-lg-4 col-sm-6 box">
- <div class="text-box">
- <h4 class="section-heading text-center">Local and Faster Time to Action</h4>
- <div class="clearfix"></div>
- <div class="lead">Quarks makes devices more intelligent, enabling them to take immediate action. For example, a connected vehicle running Quarks can adjust traction control based on the weight of the cargo/passengers.</div>
- </div>
- </div>
- <div class="col-lg-4 col-sm-6 box">
- <div class="text-box">
- <h4 class="section-heading text-center">Learning From Related Devices</h4>
- <div class="clearfix"></div>
- <div class="lead">Quarks enables connected devices to learn from related devices. For example, a truck maneuvering roads in Oregon can adjust based on the data received from trucks operating under similar loads and conditions in Colorado; data such as altitude, cargo, weather and traffic conditions.
-</div>
- </div>
- </div>
- </div>
-
- </div>
-</section>
http://git-wip-us.apache.org/repos/asf/incubator-quarks-website/blob/05ad5e88/site/_layouts/default_orig.html
----------------------------------------------------------------------
diff --git a/site/_layouts/default_orig.html b/site/_layouts/default_orig.html
index 63831bc..c692a5b 100644
--- a/site/_layouts/default_orig.html
+++ b/site/_layouts/default_orig.html
@@ -27,7 +27,7 @@ limitations under the License.
{% include incubation.html %}
{% include webcast.html %}
{% include open_ecosystem.html %}
- {% include why_quarks.html %}
+ {% include why_edgent.html %}
{% include footer_orig.html %}
{% include js.html %}
</body>
http://git-wip-us.apache.org/repos/asf/incubator-quarks-website/blob/05ad5e88/site/doap_Edgent.rdf
----------------------------------------------------------------------
diff --git a/site/doap_Edgent.rdf b/site/doap_Edgent.rdf
new file mode 100644
index 0000000..c7f833b
--- /dev/null
+++ b/site/doap_Edgent.rdf
@@ -0,0 +1,53 @@
+<?xml version="1.0"?>
+<?xml-stylesheet type="text/xsl"?>
+<rdf:RDF xml:lang="en"
+ xmlns="http://usefulinc.com/ns/doap#"
+ xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+ xmlns:asfext="http://projects.apache.org/ns/asfext#"
+ xmlns:foaf="http://xmlns.com/foaf/0.1/">
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+ <Project rdf:about="http://edgent.incubator.apache.org/">
+ <created>2016-04-30</created>
+ <license rdf:resource="http://spdx.org/licenses/Apache-2.0" />
+ <name>Apache Edgent</name>
+ <homepage rdf:resource="http://edgent.incubator.apache.org/" />
+ <asfext:pmc rdf:resource="http://incubator.apache.org" />
+ <shortdesc>Edgent is a stream processing programming model and lightweight runtime to execute analytics at devices on the edge or at the gateway.</shortdesc>
+ <description>Apache Edgent is a programming model and micro-kernel style runtime that can be embedded in gateways and small footprint edge devices enabling local, real-time, analytics on the continuous streams of data coming from equipment, vehicles, systems, appliances, devices and sensors of all kinds (for example, Raspberry Pis or smart phones). Working in conjunction with centralized analytic systems, Apache Edgent provides efficient and timely analytics across the whole IoT ecosystem: from the center to the edge.</description>
+ <bug-database rdf:resource="https://issues.apache.org/jira/browse/EDGENT" />
+ <mailing-list rdf:resource="http://edgent.incubator.apache.org/docs/community#mailing-list" />
+ <programming-language>Java</programming-language>
+ <programming-language>JavaScript</programming-language>
+ <category rdf:resource="http://projects.apache.org/category/big-data" />
+ <category rdf:resource="http://projects.apache.org/category/library" />
+ <category rdf:resource="http://projects.apache.org/category/mobile" />
+ <category rdf:resource="http://projects.apache.org/category/network-client" />
+ <repository>
+ <GitRepository>
+ <location rdf:resource="https://git-wip-us.apache.org/repos/asf/incubator-edgent.git"/>
+ <browse rdf:resource="https://git-wip-us.apache.org/repos/asf?p=incubator-edgent.git"/>
+ </GitRepository>
+ </repository>
+ <maintainer>
+ <foaf:Person>
+ <foaf:name>Cazen Lee</foaf:name>
+ <foaf:mbox rdf:resource="mailto:cazen@apache.org"/>
+ </foaf:Person>
+ </maintainer>
+ </Project>
+</rdf:RDF>
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/incubator-quarks-website/blob/05ad5e88/site/doap_Quarks.rdf
----------------------------------------------------------------------
diff --git a/site/doap_Quarks.rdf b/site/doap_Quarks.rdf
deleted file mode 100644
index c444715..0000000
--- a/site/doap_Quarks.rdf
+++ /dev/null
@@ -1,53 +0,0 @@
-<?xml version="1.0"?>
-<?xml-stylesheet type="text/xsl"?>
-<rdf:RDF xml:lang="en"
- xmlns="http://usefulinc.com/ns/doap#"
- xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
- xmlns:asfext="http://projects.apache.org/ns/asfext#"
- xmlns:foaf="http://xmlns.com/foaf/0.1/">
-<!--
- Licensed to the Apache Software Foundation (ASF) under one or more
- contributor license agreements. See the NOTICE file distributed with
- this work for additional information regarding copyright ownership.
- The ASF licenses this file to You under the Apache License, Version 2.0
- (the "License"); you may not use this file except in compliance with
- the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing, software
- distributed under the License is distributed on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- See the License for the specific language governing permissions and
- limitations under the License.
--->
- <Project rdf:about="http://quarks.incubator.apache.org/">
- <created>2016-04-30</created>
- <license rdf:resource="http://spdx.org/licenses/Apache-2.0" />
- <name>Apache Quarks</name>
- <homepage rdf:resource="http://quarks.incubator.apache.org/" />
- <asfext:pmc rdf:resource="http://incubator.apache.org" />
- <shortdesc>Quarks is a stream processing programming model and lightweight runtime to execute analytics at devices on the edge or at the gateway.</shortdesc>
- <description>Apache Quarks is a programming model and micro-kernel style runtime that can be embedded in gateways and small footprint edge devices enabling local, real-time, analytics on the continuous streams of data coming from equipment, vehicles, systems, appliances, devices and sensors of all kinds (for example, Raspberry Pis or smart phones). Working in conjunction with centralized analytic systems, Apache Quarks provides efficient and timely analytics across the whole IoT ecosystem: from the center to the edge.</description>
- <bug-database rdf:resource="https://issues.apache.org/jira/browse/QUARKS" />
- <mailing-list rdf:resource="http://quarks.incubator.apache.org/docs/community#mailing-list" />
- <programming-language>Java</programming-language>
- <programming-language>JavaScript</programming-language>
- <category rdf:resource="http://projects.apache.org/category/big-data" />
- <category rdf:resource="http://projects.apache.org/category/library" />
- <category rdf:resource="http://projects.apache.org/category/mobile" />
- <category rdf:resource="http://projects.apache.org/category/network-client" />
- <repository>
- <GitRepository>
- <location rdf:resource="https://git-wip-us.apache.org/repos/asf/incubator-quarks.git"/>
- <browse rdf:resource="https://git-wip-us.apache.org/repos/asf?p=incubator-quarks.git"/>
- </GitRepository>
- </repository>
- <maintainer>
- <foaf:Person>
- <foaf:name>Cazen Lee</foaf:name>
- <foaf:mbox rdf:resource="mailto:cazen@apache.org"/>
- </foaf:Person>
- </maintainer>
- </Project>
-</rdf:RDF>
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/incubator-quarks-website/blob/05ad5e88/site/docs/committers.md
----------------------------------------------------------------------
diff --git a/site/docs/committers.md b/site/docs/committers.md
index 0d7cf17..c9be1ff 100644
--- a/site/docs/committers.md
+++ b/site/docs/committers.md
@@ -4,14 +4,14 @@ title: Committers
## Commit activity
-To see commit activity for Apache Quarks, click [here](https://github.com/apache/incubator-quarks/pulse).
+To see commit activity for Apache Edgent, click [here]({{ site.data.project.source_repository_mirror }}/pulse).
## How to become a committer
-You can become a committer by contributing to Apache Quarks. Qualifications for a new committer include:
+You can become a committer by contributing to Apache Edgent. Qualifications for a new committer include:
-* **Sustained Contributions**: Potential committers should have a history of contributions to Quarks. They will create pull requests over a period of time.
+* **Sustained Contributions**: Potential committers should have a history of contributions to Edgent. They will create pull requests over a period of time.
-* **Quality of Contributions**: Potential committers should submit code that adds value to Quarks, including tests and documentation as needed. They should comment in a positive way on issues and pull requests, providing guidance and input to improve Quarks.
+* **Quality of Contributions**: Potential committers should submit code that adds value to Edgent, including tests and documentation as needed. They should comment in a positive way on issues and pull requests, providing guidance and input to improve Edgent.
-* **Community Involvement**: Committers should participate in discussions in a positive way, triage and fix bugs, and interact with users who submit questions. They will remain courteous, and helpful, and encourage new members to join the Quarks community.
+* **Community Involvement**: Committers should participate in discussions in a positive way, triage and fix bugs, and interact with users who submit questions. They will remain courteous, and helpful, and encourage new members to join the Edgent community.
http://git-wip-us.apache.org/repos/asf/incubator-quarks-website/blob/05ad5e88/site/docs/common-edgent-operations.md
----------------------------------------------------------------------
diff --git a/site/docs/common-edgent-operations.md b/site/docs/common-edgent-operations.md
new file mode 100644
index 0000000..705db07
--- /dev/null
+++ b/site/docs/common-edgent-operations.md
@@ -0,0 +1,62 @@
+---
+title: Common Edgent operations
+---
+
+In the [Getting started guide](edgent-getting-started), we covered an Edgent application where we read from a device's simulated temperature sensor. Yet Edgent supports more operations than simple filtering. Data analysis and streaming require a suite of functionality, the most important components of which will be outlined below.
+
+## TStream.map()
+
+`TStream.map()` is arguably the most used method in the Edgent API. Its two main purposes are to perform stateful or stateless operations on a stream's tuples, and to produce a `TStream` with tuples of a different type from that of the calling stream.
+
+### Changing a TStream's tuple type
+
+In addition to filtering tuples, `TStream`s support operations that *transform* tuples from one Java type to another by invoking the `TStream.map()` method.
+
+<img src="images/Map_Type_Change.jpg" alt="Image of a type change" style="width:750px; height:150px;">
+
+This is useful in cases such as calculating the floating point average of a list of `Integer`s, or tokenizing a Java String into a list of `String`s. To demonstrate this, let's say we have a `TStream` which contains a few lines, each of which contains multiple words:
+
+```java
+TStream<String> lines = topology.strings(
+ "this is a line",
+ "this is another line",
+ "there are three lines now",
+ "and now four"
+);
+```
+
+We then want to print the third word in each line. The best way to do this is to convert each line to a list of `String`s by tokenizing them. We can do this in one line of code with the `TStream.map()` method:
+
+```java
+TStream<List<String> > wordsInLine = lines.map(tuple -> Arrays.asList(tuple.split(" ")));
+```
+
+Since each tuple is now a list of strings, the `wordsInLine` stream is of type `List<String>`. As you can see, the `map()` method has the ability to change the type of the `TStream`. Finally, we can use the `wordsInLine` stream to print the third word in each line.
+
+```java
+wordsInLine.sink(list -> System.out.println(list.get(2)));
+```
+
+As mentioned in the [Getting started guide](edgent-getting-started), a `TStream` can be parameterized to any serializable Java type, including ones created by the user.
+
+### Performing stateful operations
+
+In all previous examples, the operations performed on a `TStream` have been stateless; keeping track of information over multiple invocations of the same operation has not been necessary. What if we want to keep track of the number of Strings sent over a stream? To do this, we need our `TStream.map()` method to contain a counter as state.
+
+<img src="images/Map_Stateful.jpg" alt="Image of a stateful operation" style="width:750px; height:150px;">
+
+This can be achieved by creating an anonymous `Function` class, and giving it the required fields.
+
+```java
+TStream<String> streamOfStrings = ...;
+TStream<Integer> counts = streamOfStrings.map(new Function<String, Integer>() {
+ int count = 0;
+ @Override
+ public Integer apply(String arg0) {
+ count = count + 1;
+ return count;
+ }
+});
+```
+
+The `count` field will now contain the number of `String`s which were sent over `streamOfStrings`. Although this is a simple example, the anonymous `Function` passed to `TStream.map()` can contain any kind of state! This could be a `HashMap<K,V>`, a running list of tuples, or any serializable Java type. The state will be maintained throughout the entire runtime of your application.
http://git-wip-us.apache.org/repos/asf/incubator-quarks-website/blob/05ad5e88/site/docs/common-quarks-operations.md
----------------------------------------------------------------------
diff --git a/site/docs/common-quarks-operations.md b/site/docs/common-quarks-operations.md
deleted file mode 100644
index d65a8ec..0000000
--- a/site/docs/common-quarks-operations.md
+++ /dev/null
@@ -1,62 +0,0 @@
----
-title: Common Quarks operations
----
-
-In the [Getting started guide](quarks-getting-started), we covered a Quarks application where we read from a device's simulated temperature sensor. Yet Quarks supports more operations than simple filtering. Data analysis and streaming require a suite of functionality, the most important components of which will be outlined below.
-
-## TStream.map()
-
-`TStream.map()` is arguably the most used method in the Quarks API. Its two main purposes are to perform stateful or stateless operations on a stream's tuples, and to produce a `TStream` with tuples of a different type from that of the calling stream.
-
-### Changing a TStream's tuple type
-
-In addition to filtering tuples, `TStream`s support operations that *transform* tuples from one Java type to another by invoking the `TStream.map()` method.
-
-<img src="images/Map_Type_Change.jpg" alt="Image of a type change" style="width:750px; height:150px;">
-
-This is useful in cases such as calculating the floating point average of a list of `Integer`s, or tokenizing a Java String into a list of `String`s. To demonstrate this, let's say we have a `TStream` which contains a few lines, each of which contains multiple words:
-
-```java
-TStream<String> lines = topology.strings(
- "this is a line",
- "this is another line",
- "there are three lines now",
- "and now four"
-);
-```
-
-We then want to print the third word in each line. The best way to do this is to convert each line to a list of `String`s by tokenizing them. We can do this in one line of code with the `TStream.map()` method:
-
-```java
-TStream<List<String> > wordsInLine = lines.map(tuple -> Arrays.asList(tuple.split(" ")));
-```
-
-Since each tuple is now a list of strings, the `wordsInLine` stream is of type `List<String>`. As you can see, the `map()` method has the ability to change the type of the `TStream`. Finally, we can use the `wordsInLine` stream to print the third word in each line.
-
-```java
-wordsInLine.sink(list -> System.out.println(list.get(2)));
-```
-
-As mentioned in the [Getting started guide](quarks-getting-started), a `TStream` can be parameterized to any serializable Java type, including ones created by the user.
-
-### Performing stateful operations
-
-In all previous examples, the operations performed on a `TStream` have been stateless; keeping track of information over multiple invocations of the same operation has not been necessary. What if we want to keep track of the number of Strings sent over a stream? To do this, we need our `TStream.map()` method to contain a counter as state.
-
-<img src="images/Map_Stateful.jpg" alt="Image of a stateful operation" style="width:750px; height:150px;">
-
-This can be achieved by creating an anonymous `Function` class, and giving it the required fields.
-
-```java
-TStream<String> streamOfStrings = ...;
-TStream<Integer> counts = streamOfStrings.map(new Function<String, Integer>() {
- int count = 0;
- @Override
- public Integer apply(String arg0) {
- count = count + 1;
- return count;
- }
-});
-```
-
-The `count` field will now contain the number of `String`s which were sent over `streamOfStrings`. Although this is a simple example, the anonymous `Function` passed to `TStream.map()` can contain any kind of state! This could be a `HashMap<K,V>`, a running list of tuples, or any serializable Java type. The state will be maintained throughout the entire runtime of your application.
http://git-wip-us.apache.org/repos/asf/incubator-quarks-website/blob/05ad5e88/site/docs/community.md
----------------------------------------------------------------------
diff --git a/site/docs/community.md b/site/docs/community.md
index 439d2c1..48161bf 100644
--- a/site/docs/community.md
+++ b/site/docs/community.md
@@ -1,5 +1,5 @@
---
-title: Apache Quarks community
+title: Apache Edgent community
---
<!--
{% comment %}
@@ -43,11 +43,11 @@ Get help using {{ site.data.project.short_name }} or contribute to the project o
## Issue tracker
-We use Jira here: [https://issues.apache.org/jira/browse/{{ site.data.project.jira }}](https://issues.apache.org/jira/browse/{{ site.data.project.jira }})
+We use JIRA here: [https://issues.apache.org/jira/browse/{{ site.data.project.jira }}](https://issues.apache.org/jira/browse/{{ site.data.project.jira }})
### Bug reports
-Found bug? Create an issue in [Jira](https://issues.apache.org/jira/browse/{{ site.data.project.jira }}).
+Found a bug? Create an issue in [JIRA](https://issues.apache.org/jira/browse/{{ site.data.project.jira }}).
Before submitting an issue, please:
@@ -57,24 +57,24 @@ Before submitting an issue, please:
### Feature requests
-Enhancement requests for new features are also welcome. The more concrete the request is and the better rationale you provide, the greater the chance it will incorporated into future releases. To make a request, create an issue in [Jira](https://issues.apache.org/jira/browse/{{ site.data.project.jira }}).
+Enhancement requests for new features are also welcome. The more concrete the request is and the better rationale you provide, the greater the chance it will incorporated into future releases. To make a request, create an issue in [JIRA](https://issues.apache.org/jira/browse/{{ site.data.project.jira }}).
## Source code
The project sources are accessible via the [source code repository]({{ site.data.project.source_repository }}) which is also mirrored in [GitHub]({{ site.data.project.source_repository_mirror }}).
-When you are considering a code contribution, make sure there is an [Jira issue](https://issues.apache.org/jira/browse/{{ site.data.project.jira }}) that describes your work or the bug you are fixing. For significant contributions, please discuss your proposed changes in the issue so that others can comment on your plans. Someone else may be working on the same functionality, so it's good to communicate early and often. A committer is more likely to accept your change if there is clear information in the issue.
+When you are considering a code contribution, make sure there is a [JIRA issue](https://issues.apache.org/jira/browse/{{ site.data.project.jira }}) that describes your work or the bug you are fixing. For significant contributions, please discuss your proposed changes in the issue so that others can comment on your plans. Someone else may be working on the same functionality, so it's good to communicate early and often. A committer is more likely to accept your change if there is clear information in the issue.
-To contribute, [fork](https://help.github.com/articles/fork-a-repo/) the [mirror]({{ site.data.project.source_repository_mirror }}) and issue a [pull request](https://help.github.com/articles/using-pull-requests/). Put the Jira issue number, e.g. {{ site.data.project.jira }}-100 in the pull request title. The tag [WIP] can also be used in the title of pull requests to indicate that you are not ready to merge but want feedback. Remove [WIP] when you are ready for merge. Make sure you document your code and contribute tests along with the code.
+To contribute, [fork](https://help.github.com/articles/fork-a-repo/) the [mirror]({{ site.data.project.source_repository_mirror }}) and issue a [pull request](https://help.github.com/articles/using-pull-requests/). Put the JIRA issue number, e.g. {{ site.data.project.jira }}-100 in the pull request title. The tag [WIP] can also be used in the title of pull requests to indicate that you are not ready to merge but want feedback. Remove [WIP] when you are ready for merge. Make sure you document your code and contribute tests along with the code.
-Read [DEVELOPMENT.md](https://github.com/apache/incubator-quarks/blob/master/DEVELOPMENT.md) at the top of the code tree for details on setting up your development environment.
+Read [DEVELOPMENT.md]({{ site.data.project.source_repository_mirror }}/blob/master/DEVELOPMENT.md) at the top of the code tree for details on setting up your development environment.
-## Web site and documentation source code
+## Website and documentation source code
-The project website and documentation sources are accessible via the [website source code repository]({{ site.data.project.website_repository }}) which is also mirrored in [GitHub]({{ site.data.project.website_repository_mirror }}). Contributing changes to the web site and documentation is similar to contributing code. Follow the instructions in the *Source Code* section above, but fork and issue a pull request against the [web site mirror]({{ site.data.project.website_repository_mirror }}). Follow the instructions in the top-level [README.md]({{ site.data.project.website_repository_mirror }}/blob/master/README.md) for details on contributing to the web site and documentation.
+The project website and documentation sources are accessible via the [website source code repository]({{ site.data.project.website_repository }}) which is also mirrored in [GitHub]({{ site.data.project.website_repository_mirror }}). Contributing changes to the website and documentation is similar to contributing code. Follow the instructions in the *Source Code* section above, but fork and issue a pull request against the [website mirror]({{ site.data.project.website_repository_mirror }}). Follow the instructions in the top-level [README.md]({{ site.data.project.website_repository_mirror }}/blob/master/README.md) for details on contributing to the website and documentation.
You will need to use [Markdown](https://daringfireball.net/projects/markdown/) and [Jekyll](http://jekyllrb.com) to develop pages. See:
* [Markdown Cheat Sheet](https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet)
-* [Jekyll on linux and Mac](https://jekyllrb.com/)
+* [Jekyll on Linux and Mac](https://jekyllrb.com/)
* [Jekyll on Windows](https://jekyllrb.com/docs/windows/) is not officially supported but people have gotten it to work
http://git-wip-us.apache.org/repos/asf/incubator-quarks-website/blob/05ad5e88/site/docs/console.md
----------------------------------------------------------------------
diff --git a/site/docs/console.md b/site/docs/console.md
index 97177b8..86eba52 100644
--- a/site/docs/console.md
+++ b/site/docs/console.md
@@ -4,21 +4,21 @@ title: Application console
## Visualizing and monitoring your application
-The Quarks application console is a web application that enables you to visualize your application topology and monitor the tuples flowing through your application. The kind of oplets used in the topology, as well as the stream tags included in the topology, are also visible in the console.
+The Edgent application console is a web application that enables you to visualize your application topology and monitor the tuples flowing through your application. The kind of oplets used in the topology, as well as the stream tags included in the topology, are also visible in the console.
## Adding the console web app to your application
-To use the console, you must use the Quarks classes that provide the service to access the console web application or directly call the `HttpServer` class itself, start the server and then obtain the console URL.
+To use the console, you must use the Edgent classes that provide the service to access the console web application or directly call the `HttpServer` class itself, start the server and then obtain the console URL.
The easiest way to include the console in your application is to use the the `DevelopmentProvider` class. `DevelopmentProvider` is a subclass of `DirectProvider` and adds services such as access to the console web application and counter oplets used to determine tuple counts. You can get the URL for the console from the `DevelopmentProvider` using the `getService` method as shown in a hypothetical application shown below:
```java
import java.util.concurrent.TimeUnit;
-import quarks.console.server.HttpServer;
-import quarks.providers.development.DevelopmentProvider;
-import quarks.topology.TStream;
-import quarks.topology.Topology;
+import org.apache.edgent.console.server.HttpServer;
+import org.apache.edgent.providers.development.DevelopmentProvider;
+import org.apache.edgent.topology.TStream;
+import org.apache.edgent.topology.Topology;
public class TempSensorApplication {
public static void main(String[] args) throws Exception {
@@ -50,7 +50,7 @@ try {
dp.submit(topology);
```
-The other way to embed the console in your application is shown in the `HttpServerSample.java` example (on [GitHub](https://github.com/apache/incubator-quarks/blob/master/samples/console/src/main/java/quarks/samples/console/HttpServerSample.java)). It gets the `HttpServer` instance, starts it, and prints out the console URL. Note that it does not submit a job, so when the console is displayed in the browser, there are no running jobs and therefore no topology graph. The example is meant to show how to get the `HttpServer` instance, start the console web app and get the URL of the console.
+The other way to embed the console in your application is shown in the `HttpServerSample.java` example (on [GitHub]({{ site.data.project.source_repository_mirror }}/blob/master/samples/console/src/main/java/{{ site.data.project.unix_name }}/samples/console/HttpServerSample.java)). It gets the `HttpServer` instance, starts it, and prints out the console URL. Note that it does not submit a job, so when the console is displayed in the browser, there are no running jobs and therefore no topology graph. The example is meant to show how to get the `HttpServer` instance, start the console web app and get the URL of the console.
## Accessing the console
@@ -64,17 +64,17 @@ If you cannot access the console at this URL, ensure there is a `console.war` fi
## ConsoleWaterDetector sample
-To see the features of the console in action and as a way to demonstrate how to monitor a topology in the console, let's look at the `ConsoleWaterDetector` sample (on [GitHub](https://github.com/apache/incubator-quarks/blob/master/samples/console/src/main/java/quarks/samples/console/ConsoleWaterDetector.java)).
+To see the features of the console in action and as a way to demonstrate how to monitor a topology in the console, let's look at the `ConsoleWaterDetector` sample (on [GitHub]({{ site.data.project.source_repository_mirror }}/blob/master/samples/console/src/main/java/{{ site.data.project.unix_name }}/samples/console/ConsoleWaterDetector.java)).
-Prior to running any console applications, the `console.war` file must be built as mentioned above. If you are building quarks from a Git repository, go to the top level Quarks directory and run `ant`.
+Prior to running any console applications, the `console.war` file must be built as mentioned above. If you are building Edgent from a Git repository, go to the top level Edgent directory and run `ant`.
Here is an example in my environment:
```
-Susans-MacBook-Pro-247:quarks susancline$ pwd
-/Users/susancline/git/quarks
-Susans-MacBook-Pro-247:quarks susancline$ ant
-Buildfile: /Users/susancline/git/quarks/build.xml
+Susans-MacBook-Pro-247:edgent susancline$ pwd
+/Users/susancline/git/edgent
+Susans-MacBook-Pro-247:edgent susancline$ ant
+Buildfile: /Users/susancline/git/edgent/build.xml
setcommitversion:
@@ -91,10 +91,10 @@ compile:
[javadoc] Constructing Javadoc information...
[javadoc] Standard Doclet version 1.8.0_71
[javadoc] Building tree for all the packages and classes...
-[javadoc] Generating /Users/susancline/git/quarks/target/docs/javadoc/quarks/analytics/sensors/package-summary.html...
-[javadoc] Copying file /Users/susancline/git/quarks/analytics/sensors/src/main/java/quarks/analytics/sensors/doc-files/deadband.png to directory /Users/susancline/git/quarks/target/docs/javadoc/quarks/analytics/sensors/doc-files...
-[javadoc] Generating /Users/susancline/git/quarks/target/docs/javadoc/quarks/topology/package-summary.html...
-[javadoc] Copying file /Users/susancline/git/quarks/api/topology/src/main/java/quarks/topology/doc-files/sources.html to directory /Users/susancline/git/quarks/target/docs/javadoc/quarks/topology/doc-files...
+[javadoc] Generating /Users/susancline/git/edgent/target/docs/javadoc/edgent/analytics/sensors/package-summary.html...
+[javadoc] Copying file /Users/susancline/git/edgent/analytics/sensors/src/main/java/edgent/analytics/sensors/doc-files/deadband.png to directory /Users/susancline/git/edgent/target/docs/javadoc/edgent/analytics/sensors/doc-files...
+[javadoc] Generating /Users/susancline/git/edgent/target/docs/javadoc/edgent/topology/package-summary.html...
+[javadoc] Copying file /Users/susancline/git/edgent/api/topology/src/main/java/edgent/topology/doc-files/sources.html to directory /Users/susancline/git/edgent/target/docs/javadoc/edgent/topology/doc-files...
[javadoc] Building index for all the packages and classes...
[javadoc] Building index for all classes...
@@ -107,22 +107,22 @@ Total time: 3 seconds
This command will let you know that `console.war` was built and is in the correct place, under the `webapps` directory.
```
-Susans-MacBook-Pro-247:quarks susancline$ find . -name console.war -print
+Susans-MacBook-Pro-247:edgent susancline$ find . -name console.war -print
./target/java8/console/webapps/console.war
```
Now we know we have built `console.war`, so we're good to go. To run this sample from the command line:
```
-Susans-MacBook-Pro-247:quarks susancline$ pwd
-/Users/susancline/git/quarks
-Susans-MacBook-Pro-247:quarks susancline$ java -cp target/java8/samples/lib/quarks.samples.console.jar:. quarks.samples.console.ConsoleWaterDetector
+Susans-MacBook-Pro-247:edgent susancline$ pwd
+/Users/susancline/git/edgent
+Susans-MacBook-Pro-247:edgent susancline$ java -cp target/java8/samples/lib/edgent.samples.console.jar:. edgent.samples.console.ConsoleWaterDetector
```
If everything is successful, you'll start seeing output. You may have to scroll back up to get the URL of the console:
```
-Susans-MacBook-Pro-247:quarks susancline$ java -cp target/java8/samples/lib/quarks.samples.console.jar:. quarks.samples.console.ConsoleWaterDetector
+Susans-MacBook-Pro-247:edgent susancline$ java -cp target/java8/samples/lib/edgent.samples.console.jar:. edgent.samples.console.ConsoleWaterDetector
Mar 07, 2016 12:04:52 PM org.eclipse.jetty.util.log.Log initialized
INFO: Logging initialized @176ms
Mar 07, 2016 12:04:53 PM org.eclipse.jetty.server.Server doStart
@@ -277,15 +277,15 @@ while (true) {
What this does is get all the counters in the `MetricRegistry` class and print out the name of the counter oplet they are monitoring along with the tuple count if it is zero. Here is some sample output:
```
-Counter Op:TupleCounter.quarks.oplet.JOB_0.OP_44 has a tuple count of zero!
-Counter Op:TupleCounter.quarks.oplet.JOB_0.OP_45 has a tuple count of zero!
-Counter Op:TupleCounter.quarks.oplet.JOB_0.OP_46 has a tuple count of zero!
-Counter Op:TupleCounter.quarks.oplet.JOB_0.OP_47 has a tuple count of zero!
-Counter Op:TupleCounter.quarks.oplet.JOB_0.OP_89 has a tuple count of zero!
-Counter Op:TupleCounter.quarks.oplet.JOB_0.OP_95 has a tuple count of zero!
-Counter Op:TupleCounter.quarks.oplet.JOB_0.OP_96 has a tuple count of zero!
-Counter Op:TupleCounter.quarks.oplet.JOB_0.OP_97 has a tuple count of zero!
-Counter Op:TupleCounter.quarks.oplet.JOB_0.OP_98 has a tuple count of zero!
+Counter Op:TupleCounter.edgent.oplet.JOB_0.OP_44 has a tuple count of zero!
+Counter Op:TupleCounter.edgent.oplet.JOB_0.OP_45 has a tuple count of zero!
+Counter Op:TupleCounter.edgent.oplet.JOB_0.OP_46 has a tuple count of zero!
+Counter Op:TupleCounter.edgent.oplet.JOB_0.OP_47 has a tuple count of zero!
+Counter Op:TupleCounter.edgent.oplet.JOB_0.OP_89 has a tuple count of zero!
+Counter Op:TupleCounter.edgent.oplet.JOB_0.OP_95 has a tuple count of zero!
+Counter Op:TupleCounter.edgent.oplet.JOB_0.OP_96 has a tuple count of zero!
+Counter Op:TupleCounter.edgent.oplet.JOB_0.OP_97 has a tuple count of zero!
+Counter Op:TupleCounter.edgent.oplet.JOB_0.OP_98 has a tuple count of zero!
```
To summarize what the application is doing:
@@ -327,7 +327,7 @@ The screen shot below shows the output from clicking on the 'View all oplet prop
<img src='images/console_oplet_properties.jpg' alt='Displays a table showing the relationship between the oplets and vertices' width='100%'/>
-Looking at the sixth line in the table, where the Name is 'OP_5', we can see that the Oplet kind is a `Map`, a `quarks.oplet.functional.Map`, the Tuple count is 0 (this is because the view is in Static flow mode - the graph does not show the number of tuples flowing in it), the source oplet is 'OP_55', the target oplet is 'OP_60', and there are no stream tags coming from the source or target streams. Relationships for all oplets can be viewed in this manner.
+Looking at the sixth line in the table, where the Name is 'OP_5', we can see that the Oplet kind is a `Map`, a `edgent.oplet.functional.Map`, the Tuple count is 0 (this is because the view is in Static flow mode - the graph does not show the number of tuples flowing in it), the source oplet is 'OP_55', the target oplet is 'OP_60', and there are no stream tags coming from the source or target streams. Relationships for all oplets can be viewed in this manner.
Now, looking at the graph, if we want to see the relationships for a single oplet, we can hover over it. The image below shows the hover when we are over 'OP_5'.
@@ -398,11 +398,11 @@ The topology graph oplets can sometimes sit on top of each other. If this is the
If you scroll the browser window down, you can see a Metrics section. This section appears when the application contains the following:
* A `DevelopmentProvider` is used; this automatically inserts counters on the streams of the topology
-* A `quarks.metrics.Metric.Counter` or `quarks.metrics.Metric.RateMeter` is added to an individual stream
+* A `edgent.metrics.Metric.Counter` or `edgent.metrics.Metric.RateMeter` is added to an individual stream
## Counters
-In the `ConsoleWaterDetector` application we used a `DevelopmentProvider`. Therefore, counters were added to most streams (edges) with the following exceptions (from the [Javadoc]({{ site.docsurl }}/lastest/quarks/metrics/Metrics.html#counter-quarks.topology.TStream-) for `quarks.metrics.Metrics`):
+In the `ConsoleWaterDetector` application we used a `DevelopmentProvider`. Therefore, counters were added to most streams (edges) with the following exceptions (from the [Javadoc]({{ site.docsurl }}/latest/{{ site.data.project.unix_name }}/metrics/Metrics.html#counter-{{ site.data.project.unix_name }}.topology.TStream-) for `edgent.metrics.Metrics`):
*Oplets are only inserted upstream from a FanOut oplet.*
@@ -480,7 +480,7 @@ If a single rate meter is placed on a stream, in addition to plotting a bar char
The intent of the information on this page is to help you understand the following:
-* How to add the console application to a Quarks application
+* How to add the console application to an Edgent application
* How to run the `ConsoleWaterDetector` sample
* The design/architecture in the `ConsoleWaterDetector` application
* The controls for the Topology graph are and what they do, including the different views of the graph
@@ -490,6 +490,6 @@ The intent of the information on this page is to help you understand the followi
* How to use the metrics section to understand tuple counters and rate meters
* How to correlate values from the metrics section with the topology graph
-The Quarks console will continue to evolve and improve. Please open an issue if you see a problem with the existing console, but more importantly add an issue if you have an idea of how to make the console better.
+The Edgent console will continue to evolve and improve. Please open an issue if you see a problem with the existing console, but more importantly add an issue if you have an idea of how to make the console better.
-The more folks write Quarks applications and view them in the console, the more information we can gather from the community about what is needed in the console. Please consider making a contribution if there is a feature in the console that would really help you and others!
+The more folks write Edgent applications and view them in the console, the more information we can gather from the community about what is needed in the console. Please consider making a contribution if there is a feature in the console that would really help you and others!
http://git-wip-us.apache.org/repos/asf/incubator-quarks-website/blob/05ad5e88/site/docs/edgent-getting-started.md
----------------------------------------------------------------------
diff --git a/site/docs/edgent-getting-started.md b/site/docs/edgent-getting-started.md
new file mode 100644
index 0000000..6a433cd
--- /dev/null
+++ b/site/docs/edgent-getting-started.md
@@ -0,0 +1,197 @@
+---
+title: Getting started with Apache Edgent
+---
+
+## What is Apache Edgent?
+
+Edgent is an open source programming model and runtime for edge devices that enables you to analyze streaming data on your edge devices. When you analyze on the edge, you can:
+
+* Reduce the amount of data that you transmit to your analytics server
+* Reduce the amount of data that you store
+
+For more information, see the [Edgent overview](home).
+
+### Apache Edgent and streaming analytics
+
+The fundamental building block of an Edgent application is a **stream**: a continuous sequence of tuples (messages, events, sensor readings, and so on).
+
+The Edgent API provides the ability to process or analyze each tuple as it appears on a stream, resulting in a derived stream.
+
+Source streams are streams that originate data for analysis, such as readings from a device's temperature sensor.
+
+Streams are terminated using sink functions that can perform local device control or send information to centralized analytic systems through a message hub.
+
+Edgent's primary API is functional where streams are sourced, transformed, analyzed or sinked though functions, typically represented as lambda expressions, such as `reading -> reading < 50 || reading > 80` to filter temperature readings in Fahrenheit.
+
+### Downloading Apache Edgent
+
+To use Edgent, access the source code and build it. You can read more about building Edgent [here]({{ site.data.project.source_repository_mirror }}/blob/master/DEVELOPMENT.md).
+
+After you build the Edgent package, you can set up your environment.
+
+### Setting up your environment
+
+Ensure that you are running a supported environment. For more information, see the [Edgent overview](home). This guide assumes you're running Java 8.
+
+The Edgent Java 8 JAR files are located in the `edgent/java8/lib` directory.
+
+1. Create a new Java project in Eclipse, and specify Java 8 as the execution environment JRE:
+
+ <img src="images/New_Java_Project.JPG" style="width:448px;height:589px;">
+
+
+2. Modify the Java build path to include all of the JAR files in the `edgent\java8\lib` directory:
+
+ <img src="images/Build_Path_Jars.JPG" style="width:660px;height:469px;">
+
+Your environment is set up! You can start writing your first Edgent application.
+
+## Creating a simple application
+
+If you're new to Edgent or to writing streaming applications, the best way to get started is to write a simple program.
+
+Edgent is a framework that pushes data analytics and machine learning to *edge devices*. (Edge devices include things like routers, gateways, machines, equipment, sensors, appliances, or vehicles that are connected to a network.) Edgent enables you to process data locally—such as, in a car engine, on an Android phone, or Raspberry Pi—before you send data over a network.
+
+For example, if your device takes temperature readings from a sensor 1,000 times per second, it is more efficient to process the data locally and send only interesting or unexpected results over the network. To simulate this, let's define a (simulated) TempSensor class:
+
+```java
+import java.util.Random;
+
+import org.apache.edgent.function.Supplier;
+
+/**
+ * Every time get() is called, TempSensor generates a temperature reading.
+ */
+public class TempSensor implements Supplier<Double> {
+ double currentTemp = 65.0;
+ Random rand;
+
+ TempSensor(){
+ rand = new Random();
+ }
+
+ @Override
+ public Double get() {
+ // Change the current temperature some random amount
+ double newTemp = rand.nextGaussian() + currentTemp;
+ currentTemp = newTemp;
+ return currentTemp;
+ }
+}
+```
+
+Every time you call `TempSensor.get()`, it returns a new temperature reading. The continuous temperature readings are a stream of data that an Edgent application can process.
+
+Our sample Edgent application processes this stream by filtering the data and printing the results. Let's define a TempSensorApplication class for the application:
+
+```java
+import java.util.concurrent.TimeUnit;
+
+import org.apache.edgent.providers.direct.DirectProvider;
+import org.apache.edgent.topology.TStream;
+import org.apache.edgent.topology.Topology;
+
+public class TempSensorApplication {
+ public static void main(String[] args) throws Exception {
+ TempSensor sensor = new TempSensor();
+ DirectProvider dp = new DirectProvider();
+ Topology topology = dp.newTopology();
+ TStream<Double> tempReadings = topology.poll(sensor, 1, TimeUnit.MILLISECONDS);
+ TStream<Double> filteredReadings = tempReadings.filter(reading -> reading < 50 || reading > 80);
+
+ filteredReadings.print();
+ dp.submit(topology);
+ }
+}
+```
+
+To understand how the application processes the stream, let's review each line.
+
+### Specifying a provider
+
+Your first step when you write an Edgent application is to create a [`DirectProvider`]({{ site.docsurl }}/latest/index.html?edgent/providers/direct/DirectProvider.html):
+
+```java
+DirectProvider dp = new DirectProvider();
+```
+
+A `Provider` is an object that contains information on how and where your Edgent application will run. A `DirectProvider` is a type of Provider that runs your application directly within the current virtual machine when its `submit()` method is called.
+
+### Creating a topology
+
+Additionally a Provider is used to create a [`Topology`]({{ site.docsurl }}/latest/index.html?edgent/topology/Topology.html) instance:
+
+```java
+Topology topology = dp.newTopology();
+```
+
+In Edgent, `Topology` is a container that describes the structure of your application:
+
+* Where the streams in the application come from
+* How the data in the stream is modified
+
+In the TempSensor application above, we have exactly one data source: the `TempSensor` object. We define the source stream by calling `topology.poll()`, which takes both a `Supplier` function and a time parameter to indicate how frequently readings should be taken. In our case, we read from the sensor every millisecond:
+
+```java
+TStream<Double> tempReadings = topology.poll(sensor, 1, TimeUnit.MILLISECONDS);
+```
+
+### Defining the `TStream` object
+
+Calling `topology.poll()` to define a source stream creates a `TStream<Double>` instance, which represents the series of readings taken from the temperature sensor.
+
+A streaming application can run indefinitely, so the `TStream` might see an arbitrarily large number of readings pass through it. Because a `TStream` represents the flow of your data, it supports a number of operations which allow you to modify your data.
+
+### Filtering a `TStream`
+
+In our example, we want to filter the stream of temperature readings, and remove any "uninteresting" or expected readings—specifically readings which are above 50 degrees and below 80 degrees. To do this, we call the `TStream`'s `filter` method and pass in a function that returns *true* if the data is interesting and *false* if the data is uninteresting:
+
+```java
+TStream<Double> filteredReadings = tempReadings.filter(reading -> reading < 50 || reading > 80);
+```
+
+As you can see, the function that is passed to `filter` operates on each tuple individually. Unlike data streaming frameworks like [Apache Spark](https://spark.apache.org/), which operate on a collection of data in batch mode, Edgent achieves low latency processing by manipulating each piece of data as soon as it becomes available. Filtering a `TStream` produces another `TStream` that contains only the filtered tuples; for example, the `filteredReadings` stream.
+
+### Printing to output
+
+When our application detects interesting data (data outside of the expected parameters), we want to print results. You can do this by calling the `TStream.print()` method, which prints using `.toString()` on each tuple that passes through the stream:
+
+```java
+filteredReadings.print();
+```
+
+Unlike `TStream.filter()`, `TStream.print()` does not produce another `TStream`. This is because `TStream.print()` is a **sink**, which represents the terminus of a stream.
+
+In addition to `TStream.print()` there are other sink operations that send tuples to an MQTT server, JDBC connection, file, or Kafka cluster. Additionally, you can define your own sink by invoking `TStream.sink()` and passing in your own function.
+
+### Submitting your application
+
+Now that your application has been completely declared, the final step is to run your application.
+
+`DirectProvider` contains a `submit()` method, which runs your application directly within the current virtual machine:
+
+```java
+dp.submit(topology);
+```
+
+After you run your program, you should see output containing only "interesting" data coming from your sensor:
+
+```
+49.904032311772596
+47.97837504039084
+46.59272336309031
+46.681544551652934
+47.400819234155236
+...
+```
+
+As you can see, all temperatures are outside the 50-80 degree range. In terms of a real-world application, this would prevent a device from sending superfluous data over a network, thereby reducing communication costs.
+
+## Further examples
+
+This example demonstrates a small piece of Edgent's functionality. Edgent supports more complicated topologies, such as topologies that require merging and splitting data streams, or perform operations which aggregate the last *N* seconds of data (for example, calculating a moving average).
+
+For more complex examples, see:
+
+* [Edgent sample programs](samples)
+* [Common Edgent operations](common-edgent-operations)
http://git-wip-us.apache.org/repos/asf/incubator-quarks-website/blob/05ad5e88/site/docs/edgent_index.md
----------------------------------------------------------------------
diff --git a/site/docs/edgent_index.md b/site/docs/edgent_index.md
new file mode 100644
index 0000000..8264647
--- /dev/null
+++ b/site/docs/edgent_index.md
@@ -0,0 +1,29 @@
+---
+title: Apache Edgent documentation
+audience: field engineers, clients
+---
+
+## New documentation
+
+Apache Edgent is evolving, and so is the documentation. If the existing documentation hasn't answered your questions, you can request new or updated documentation by opening a [JIRA](https://issues.apache.org/jira/browse/{{ site.data.project.jira }}) issue.
+
+## Providing feedback
+
+To provide feedback on our documentation:
+
+1. Navigate to the documentation page for which you are providing feedback
+1. Click on the **Feedback** button in the top right corner
+
+This will open an issue for the page that you are currently visiting.
+
+## Contributing documentation
+
+If you have ideas on how we can better document or explain some of the concepts, we would love to have your contribution! This site uses GitHub's flavor of Markdown and Jekyll markdown for our documentation.
+
+Refer to this documentation on GitHub's flavor of Markdown: [Writing on GitHub](https://help.github.com/categories/writing-on-github).
+
+Refer to this documentation to get started: [Using Jekyll with Pages](https://help.github.com/articles/using-jekyll-with-pages/).
+
+To contribute, clone this project locally, make your changes, and create a [pull request]({{ site.data.project.website_repository_mirror }}/pulls).
+
+To learn more, visit [Get Involved](community).
http://git-wip-us.apache.org/repos/asf/incubator-quarks-website/blob/05ad5e88/site/docs/faq.md
----------------------------------------------------------------------
diff --git a/site/docs/faq.md b/site/docs/faq.md
index 566784f..f646f45 100644
--- a/site/docs/faq.md
+++ b/site/docs/faq.md
@@ -2,53 +2,53 @@
title: FAQ
---
-## What is Apache Quarks?
+## What is Apache Edgent?
-Quarks provides APIs and a lightweight runtime to analyze streaming data at the edge.
+Edgent provides APIs and a lightweight runtime to analyze streaming data at the edge.
## What do you mean by the edge?
The edge includes devices, gateways, equipment, vehicles, systems, appliances and sensors of all kinds as part of the Internet of Things.
-## How is Apache Quarks used?
+## How is Apache Edgent used?
-Quarks can be used at the edge of the Internet of Things, for example, to analyze data on devices, engines, connected cars, etc. Quarks could be on the device itself, or a gateway device collecting data from local devices. You can write an edge application on Quarks and connect it to a Cloud service, such as the IBM Watson IoT Platform. It can also be used for enterprise data collection and analysis; for example log collectors, application data, and data center analytics.
+Edgent can be used at the edge of the Internet of Things, for example, to analyze data on devices, engines, connected cars, etc. Edgent could be on the device itself, or a gateway device collecting data from local devices. You can write an edge application on Edgent and connect it to a Cloud service, such as the IBM Watson IoT Platform. It can also be used for enterprise data collection and analysis; for example log collectors, application data, and data center analytics.
## How are applications developed?
Applications are developed using a functional flow API to define operations on data streams that are executed as a graph of "oplets" in a lightweight embeddable runtime. The SDK provides capabilities like windowing, aggregation and connectors with an extensible model for the community to expand its capabilities.
-## What APIs does Apache Quarks support?
+## What APIs does Apache Edgent support?
-Currently, Quarks supports APIs for Java and Android. Support for additional languages, such as Python, is likely as more developers get involved. Please consider joining the Quarks open source development community to accelerate the contributions of additional APIs.
+Currently, Edgent supports APIs for Java and Android. Support for additional languages, such as Python, is likely as more developers get involved. Please consider joining the Edgent open source development community to accelerate the contributions of additional APIs.
-## What type of analytics can be done with Apache Quarks?
+## What type of analytics can be done with Apache Edgent?
-Quarks provides windowing, aggregation and simple filtering. It uses Apache Common Math to provide simple analytics aimed at device sensors. Quarks is also extensible, so you can call existing libraries from within your Quarks application. In the future, Quarks will include more analytics, either exposing more functionality from Apache Common Math, other libraries or hand-coded analytics.
+Edgent provides windowing, aggregation and simple filtering. It uses Apache Common Math to provide simple analytics aimed at device sensors. Edgent is also extensible, so you can call existing libraries from within your Edgent application. In the future, Edgent will include more analytics, either exposing more functionality from Apache Common Math, other libraries or hand-coded analytics.
-## What connectors does Apache Quarks support?
+## What connectors does Apache Edgent support?
-Quarks supports connectors for MQTT, HTTP, JDBC, File, Apache Kafka and IBM Watson IoT Platform. Quarks is extensible; you can add the connector of your choice.
+Edgent supports connectors for MQTT, HTTP, JDBC, File, Apache Kafka and IBM Watson IoT Platform. Edgent is extensible; you can add the connector of your choice.
-## What centralized streaming analytic systems does Apache Quarks support?
+## What centralized streaming analytic systems does Apache Edgent support?
-Quarks supports open source technology (such as Apache Spark, Apache Storm, Flink and samza), IBM Streams (on-premises or IBM Streaming Analytics on Bluemix), or any custom application of your choice.
+Edgent supports open source technology (such as Apache Spark, Apache Storm, Flink and samza), IBM Streams (on-premises or IBM Streaming Analytics on Bluemix), or any custom application of your choice.
-## Why do I need Apache Quarks on the edge, rather than my streaming analytic system?
+## Why do I need Apache Edgent on the edge, rather than my streaming analytic system?
-Quarks is designed for the edge, rather than a more centralized system. It has a small footprint, suitable for running on devices. Quarks provides simple analytics, allowing a device to analyze data locally and to only send to the centralized system if there is a need, reducing communication costs.
+Edgent is designed for the edge, rather than a more centralized system. It has a small footprint, suitable for running on devices. Edgent provides simple analytics, allowing a device to analyze data locally and to only send to the centralized system if there is a need, reducing communication costs.
-## Why do I need Apache Quarks, rather than coding the complete application myself?
+## Why do I need Apache Edgent, rather than coding the complete application myself?
-Quarks is a tool for edge analytics that allows you to be more productive. Quarks provides a consistent data model (streams and windows) and provides useful functionality, such as aggregations, joins, etc. Using Quarks lets you to take advantage of this functionality, allowing you to focus on your application needs.
+Edgent is a tool for edge analytics that allows you to be more productive. Edgent provides a consistent data model (streams and windows) and provides useful functionality, such as aggregations, joins, etc. Using Edgent lets you to take advantage of this functionality, allowing you to focus on your application needs.
-## Where can I download Apache Quarks to try it out?
+## Where can I download Apache Edgent to try it out?
-Quarks is migrating from github quarks-edge to Apache. You can download the source from Apache and build it yourself [here](https://github.com/apache/incubator-quarks). You can also find already built pre-Apache releases of Quarks for download [here](https://github.com/quarks-edge/quarks/releases/latest). These releases are not associated with Apache.
+Edgent is migrating from GitHub quarks-edge to Apache. You can download the source from Apache and build it yourself [here]({{ site.data.project.source_repository_mirror }}). You can also find already built pre-Apache releases of Edgent for download [here](https://github.com/quarks-edge/quarks/releases/latest). These releases are not associated with Apache.
## How do I get started?
-Getting started is simple. Once you have downloaded Quarks, everything you need to know to get up and running, you will find [here](quarks-getting-started). We suggest you also run the [Quarks sample programs](samples) to familiarize yourselves with the code base.
+Getting started is simple. Once you have downloaded Edgent, everything you need to know to get up and running, you will find [here](edgent-getting-started). We suggest you also run the [Edgent sample programs](samples) to familiarize yourselves with the code base.
## How can I get involved?
@@ -56,32 +56,36 @@ We would love to have your help! Visit [Get Involved](community) to learn more a
## How can I contribute code?
-Just submit a [pull request](https://github.com/apache/incubator-quarks) and wait for a committer to review. For more information, visit our [committer page](committers) and read [DEVELOPMENT.md](https://github.com/apache/incubator-quarks/blob/master/DEVELOPMENT.md) at the top of the code tree.
+Just submit a [pull request]({{ site.data.project.source_repository_mirror }}/pulls) and wait for a committer to review. For more information, visit our [committer page](committers) and read [DEVELOPMENT.md]({{ site.data.project.source_repository_mirror }}/blob/master/DEVELOPMENT.md) at the top of the code tree.
## Can I become a committer?
-Read about Quarks committers and how to become a committer [here](committers).
+Read about Edgent committers and how to become a committer [here](committers).
## Where can I get the code?
-The source code is available [here](https://github.com/apache/incubator-quarks).
+The source code is available [here]({{ site.data.project.source_repository_mirror }}).
## Can I take a copy of the code and fork it for my own use?
-Yes. Quarks is available under the Apache 2.0 license which allows you to fork the code. We hope you will contribute your changes back to the Quarks community.
+Yes. Edgent is available under the Apache 2.0 license which allows you to fork the code. We hope you will contribute your changes back to the Edgent community.
## How do I suggest new features?
-Click [Issues](https://issues.apache.org/jira/browse/QUARKS) to submit requests for new features. You may browse or query the Issues database to see what other members of the Quarks community have already requested.
+Click [Issues](https://issues.apache.org/jira/browse/{{ site.data.project.jira }}) to submit requests for new features. You may browse or query the Issues database to see what other members of the Edgent community have already requested.
## How do I submit bug reports?
-Click [Issues](https://issues.apache.org/jira/browse/QUARKS) to submit a bug report.
+Click [Issues](https://issues.apache.org/jira/browse/{{ site.data.project.jira }}) to submit a bug report.
-## How do I ask questions about Apache Quarks?
+## How do I ask questions about Apache Edgent?
-Use [site.data.project.user_list](mailto:{{ site.data.project.user_list }}) to submit questions to the Quarks community.
+Use the [dev list](mailto:{{ site.data.project.dev_list }}) to submit questions to the Edgent community.
-## Why is Apache Quarks open source?
+## Why is Apache Edgent open source?
-With the growth of the Internet of Things there is a need to execute analytics at the edge. Quarks was developed to address requirements for analytics at the edge for IoT use cases that were not addressed by central analytic solutions. These capabilities will be useful to many organizations and that the diverse nature of edge devices and use cases is best addressed by an open community. Our goal is to develop a vibrant community of developers and users to expand the capabilities and real-world use of Quarks by companies and individuals to enable edge analytics and further innovation for the IoT space.
+With the growth of the Internet of Things there is a need to execute analytics at the edge. Edgent was developed to address requirements for analytics at the edge for IoT use cases that were not addressed by central analytic solutions. These capabilities will be useful to many organizations and that the diverse nature of edge devices and use cases is best addressed by an open community. Our goal is to develop a vibrant community of developers and users to expand the capabilities and real-world use of Edgent by companies and individuals to enable edge analytics and further innovation for the IoT space.
+
+## I see references to "Quarks." How does it relate to Apache Edgent?
+
+Up until July 2016, Edgent was known as Quarks. Quarks was renamed due to the name not being unique enough. The suitable name search for Edgent is currently in progress at The Apache Software Foundation.