You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@ignite.apache.org by dm...@apache.org on 2020/03/27 17:08:37 UTC
svn commit: r1875787 [1/12] - in /ignite/site/trunk: ./ arch/ community/
css/ features/ images/ images/benchmarks/ images/png-diagrams/
images/svg-diagrams/ images/svg-sprites/ images/svg/ includes/ js/
releases/2.6.0/dotnetdoc/ releases/2.7.0/dotnetdo...
Author: dmagda
Date: Fri Mar 27 17:08:35 2020
New Revision: 1875787
URL: http://svn.apache.org/viewvc?rev=1875787&view=rev
Log:
Ignite new website merged
Added:
ignite/site/trunk/arch/multi-tier-storage.html
- copied unchanged from r1875784, ignite/site/branches/ignite-redisign/arch/multi-tier-storage.html
ignite/site/trunk/css/ignite-redesign.css
- copied unchanged from r1875784, ignite/site/branches/ignite-redisign/css/ignite-redesign.css
ignite/site/trunk/docs-and-apis.html
- copied unchanged from r1875784, ignite/site/branches/ignite-redisign/docs-and-apis.html
ignite/site/trunk/features/manageandmonitor.html
- copied unchanged from r1875784, ignite/site/branches/ignite-redisign/features/manageandmonitor.html
ignite/site/trunk/gulpfile.js
- copied unchanged from r1875784, ignite/site/branches/ignite-redisign/gulpfile.js
ignite/site/trunk/images/gg-iso-70x80.png
- copied unchanged from r1875784, ignite/site/branches/ignite-redisign/images/gg-iso-70x80.png
ignite/site/trunk/images/ggwc-dashboard.png
- copied unchanged from r1875784, ignite/site/branches/ignite-redisign/images/ggwc-dashboard.png
ignite/site/trunk/images/ico-csv.png
- copied unchanged from r1875784, ignite/site/branches/ignite-redisign/images/ico-csv.png
ignite/site/trunk/images/ico-json.png
- copied unchanged from r1875784, ignite/site/branches/ignite-redisign/images/ico-json.png
ignite/site/trunk/images/ico-pdf.png
- copied unchanged from r1875784, ignite/site/branches/ignite-redisign/images/ico-pdf.png
ignite/site/trunk/images/ico-xls.png
- copied unchanged from r1875784, ignite/site/branches/ignite-redisign/images/ico-xls.png
ignite/site/trunk/images/ico-xml.png
- copied unchanged from r1875784, ignite/site/branches/ignite-redisign/images/ico-xml.png
ignite/site/trunk/images/png-diagrams/
- copied from r1875784, ignite/site/branches/ignite-redisign/images/png-diagrams/
ignite/site/trunk/images/svg/
- copied from r1875784, ignite/site/branches/ignite-redisign/images/svg/
ignite/site/trunk/images/svg-diagrams/
- copied from r1875784, ignite/site/branches/ignite-redisign/images/svg-diagrams/
ignite/site/trunk/images/svg-sprites/
- copied from r1875784, ignite/site/branches/ignite-redisign/images/svg-sprites/
ignite/site/trunk/in-memory-computing.html
- copied unchanged from r1875784, ignite/site/branches/ignite-redisign/in-memory-computing.html
ignite/site/trunk/js/bootstrap.min.js
- copied unchanged from r1875784, ignite/site/branches/ignite-redisign/js/bootstrap.min.js
ignite/site/trunk/js/bootstrap.min.js.map
- copied unchanged from r1875784, ignite/site/branches/ignite-redisign/js/bootstrap.min.js.map
ignite/site/trunk/package-lock.json
- copied unchanged from r1875784, ignite/site/branches/ignite-redisign/package-lock.json
ignite/site/trunk/package.json
- copied unchanged from r1875784, ignite/site/branches/ignite-redisign/package.json
ignite/site/trunk/scss/ignite-redesign.scss
- copied unchanged from r1875784, ignite/site/branches/ignite-redisign/scss/ignite-redesign.scss
ignite/site/trunk/use-cases/datagrid.html
- copied unchanged from r1875784, ignite/site/branches/ignite-redisign/use-cases/datagrid.html
ignite/site/trunk/use-cases/digital-integration-hub.html
- copied unchanged from r1875784, ignite/site/branches/ignite-redisign/use-cases/digital-integration-hub.html
ignite/site/trunk/use-cases/hadoop-acceleration.html
- copied unchanged from r1875784, ignite/site/branches/ignite-redisign/use-cases/hadoop-acceleration.html
ignite/site/trunk/use-cases/hpc.html
- copied unchanged from r1875784, ignite/site/branches/ignite-redisign/use-cases/hpc.html
ignite/site/trunk/use-cases/in-memory-cache.html
- copied unchanged from r1875784, ignite/site/branches/ignite-redisign/use-cases/in-memory-cache.html
ignite/site/trunk/use-cases/in-memory-database.html
- copied unchanged from r1875784, ignite/site/branches/ignite-redisign/use-cases/in-memory-database.html
ignite/site/trunk/use-cases/key-value-store.html
- copied unchanged from r1875784, ignite/site/branches/ignite-redisign/use-cases/key-value-store.html
ignite/site/trunk/use-cases/provenusecases.html
- copied unchanged from r1875784, ignite/site/branches/ignite-redisign/use-cases/provenusecases.html
ignite/site/trunk/use-cases/spark-acceleration.html
- copied unchanged from r1875784, ignite/site/branches/ignite-redisign/use-cases/spark-acceleration.html
Removed:
ignite/site/trunk/addons.html
ignite/site/trunk/arch/durablememory.html
ignite/site/trunk/arch/memorycentric.html
ignite/site/trunk/blogs.html
ignite/site/trunk/css/all.css
ignite/site/trunk/features/computegrid.html
ignite/site/trunk/features/datagrid-2.html
ignite/site/trunk/features/datagrid.html
ignite/site/trunk/features/datavisualization.html
ignite/site/trunk/features/igfs.html
ignite/site/trunk/features/igniterdd.html
ignite/site/trunk/features/mapreduce.html
ignite/site/trunk/features/multilanguage-2.html
ignite/site/trunk/features/runseverywhere.html
ignite/site/trunk/features/sql-2.html
ignite/site/trunk/features/transactions-2.html
ignite/site/trunk/images/1.png
ignite/site/trunk/images/Artboard-1.png
ignite/site/trunk/images/Artboard-2.png
ignite/site/trunk/images/Bg-red-grey-black.png
ignite/site/trunk/images/Diagram.png
ignite/site/trunk/images/DiagramBig.png
ignite/site/trunk/images/GAGrid_Logo.png
ignite/site/trunk/images/GAGrid_Logo_Beta.png
ignite/site/trunk/images/GAGrid_Overview.png
ignite/site/trunk/images/IMDG.png
ignite/site/trunk/images/Machine-Learning-Diagram_v4.png
ignite/site/trunk/images/Main-Ignite-Diagram-Memory-And-Disk-Trimmed_mod1_final.png
ignite/site/trunk/images/Main-Ignite-Diagram-Memory-And-Disk-Trimmed_mod2_final.png
ignite/site/trunk/images/Main-Ignite-Diagram-Memory-And-Disk-Trimmed_mod_final.png
ignite/site/trunk/images/Main-Ignite-diagram_v2.png
ignite/site/trunk/images/achaudhri.png
ignite/site/trunk/images/acid_transactions_icon.svg
ignite/site/trunk/images/acid_transactions_red_icon.svg
ignite/site/trunk/images/advanced-clustering.png
ignite/site/trunk/images/aiex-logo.png
ignite/site/trunk/images/aiex.png
ignite/site/trunk/images/ansi-99.png
ignite/site/trunk/images/apache-ignite-cluster.png
ignite/site/trunk/images/apache-ignite.png
ignite/site/trunk/images/apache_poweredby.png
ignite/site/trunk/images/ashitow.png
ignite/site/trunk/images/bannernodots-optimized-75.jpg
ignite/site/trunk/images/bannernodots.jpg
ignite/site/trunk/images/bannernodots.png
ignite/site/trunk/images/bannernodots_hr.png
ignite/site/trunk/images/bannerwithdots.png
ignite/site/trunk/images/bannerwithdots_hr.png
ignite/site/trunk/images/benchmarks/
ignite/site/trunk/images/bg-1-small.png
ignite/site/trunk/images/bg-1.png
ignite/site/trunk/images/bg-black-white.png
ignite/site/trunk/images/bg-carousel.jpg
ignite/site/trunk/images/bg-dark-blue.png
ignite/site/trunk/images/bg-red-black.png
ignite/site/trunk/images/cache-op-video.png
ignite/site/trunk/images/check_pointing-2.png
ignite/site/trunk/images/check_pointing.png
ignite/site/trunk/images/cluster_and_cylinders.png
ignite/site/trunk/images/clustering-video.png
ignite/site/trunk/images/collocated_processing.png
ignite/site/trunk/images/collocated_processing_icon.svg
ignite/site/trunk/images/collocated_processing_red_icon.svg
ignite/site/trunk/images/collocated_sql_queries.png
ignite/site/trunk/images/compute_grid.png
ignite/site/trunk/images/configure-cluster.png
ignite/site/trunk/images/cpp.png
ignite/site/trunk/images/data-streamers.png
ignite/site/trunk/images/data_grid.png
ignite/site/trunk/images/distributed_sql_icon.svg
ignite/site/trunk/images/distributed_sql_red_icon.svg
ignite/site/trunk/images/dmagda.png
ignite/site/trunk/images/dsetrakyan.png
ignite/site/trunk/images/dtraphagen.png
ignite/site/trunk/images/durable-memory.png
ignite/site/trunk/images/durable_memory.png
ignite/site/trunk/images/durable_memory_icon.svg
ignite/site/trunk/images/durable_memory_red_icon.svg
ignite/site/trunk/images/egg-logo1.png
ignite/site/trunk/images/fabric.jpg
ignite/site/trunk/images/forkmegithub.png
ignite/site/trunk/images/gitter-small.png
ignite/site/trunk/images/glucero.png
ignite/site/trunk/images/gridgain-logo.png
ignite/site/trunk/images/hadoop-mapreduce.png
ignite/site/trunk/images/hadoop_sequence-1.png
ignite/site/trunk/images/hadoop_sequence.png
ignite/site/trunk/images/hibernate-L2-cache.jpg
ignite/site/trunk/images/hibernate-L2-cache.png
ignite/site/trunk/images/ico-hadoop.png
ignite/site/trunk/images/ico-java.png
ignite/site/trunk/images/ico-net.png
ignite/site/trunk/images/ico-trust.png
ignite/site/trunk/images/ico-verisign.png
ignite/site/trunk/images/ignite-db-cache-2.png
ignite/site/trunk/images/ignite-db-cache.png
ignite/site/trunk/images/ignite-deploy-2.png
ignite/site/trunk/images/ignite-deploy_service_grid_v2.png
ignite/site/trunk/images/ignite-distributed-database.png
ignite/site/trunk/images/ignite_architecture.png
ignite/site/trunk/images/ignite_cluster.png
ignite/site/trunk/images/ignite_filesystem.png
ignite/site/trunk/images/ignite_service.png
ignite/site/trunk/images/ignite_used_by.svg
ignite/site/trunk/images/ignite_used_by_red.svg
ignite/site/trunk/images/img1.png
ignite/site/trunk/images/in-memory-data-grid.jpg
ignite/site/trunk/images/in_memory_compute.png
ignite/site/trunk/images/in_memory_data.png
ignite/site/trunk/images/in_memory_streaming.png
ignite/site/trunk/images/isapego.png
ignite/site/trunk/images/java.png
ignite/site/trunk/images/job_stealing_white.gif
ignite/site/trunk/images/keep_your_database.svg
ignite/site/trunk/images/keep_your_database_red.svg
ignite/site/trunk/images/key_value_icon.svg
ignite/site/trunk/images/key_value_red_icon.svg
ignite/site/trunk/images/logo.png
ignite/site/trunk/images/logo2.png
ignite/site/trunk/images/logo3.png
ignite/site/trunk/images/machine_learning.png
ignite/site/trunk/images/machine_learning_icon.svg
ignite/site/trunk/images/machine_learning_red_icon.svg
ignite/site/trunk/images/main-ignite-diagram-cluster.png
ignite/site/trunk/images/main-ignite-diagram-memory-disk-trimmed.png
ignite/site/trunk/images/main-ignite-diagram-memory-disk.png
ignite/site/trunk/images/memory-centric-storage.png
ignite/site/trunk/images/memory-centric.png
ignite/site/trunk/images/monitoring.png
ignite/site/trunk/images/native_persistence.png
ignite/site/trunk/images/native_persistence_key_value.png
ignite/site/trunk/images/nivanov.png
ignite/site/trunk/images/non_collocated_sql_queries.png
ignite/site/trunk/images/partitioned_cache.png
ignite/site/trunk/images/pgarg.png
ignite/site/trunk/images/ptupitsyn.png
ignite/site/trunk/images/replicated_cache.png
ignite/site/trunk/images/rshtykh.png
ignite/site/trunk/images/runs-everywhere.png
ignite/site/trunk/images/sbhuiyan.png
ignite/site/trunk/images/service_grid.png
ignite/site/trunk/images/shutterstock_676051051.jpg
ignite/site/trunk/images/sliding-event-window.png
ignite/site/trunk/images/smaitra.png
ignite/site/trunk/images/spark-igfs.png
ignite/site/trunk/images/spark-ignite-rdd.png
ignite/site/trunk/images/spark_integration.png
ignite/site/trunk/images/spring-small.png
ignite/site/trunk/images/sprite.png
ignite/site/trunk/images/sql-grid-2.png
ignite/site/trunk/images/sql-grid-banner.png
ignite/site/trunk/images/sql-queries-video.png
ignite/site/trunk/images/sql_at_nosql_scale.svg
ignite/site/trunk/images/sql_at_nosql_scale_red.svg
ignite/site/trunk/images/sql_database.png
ignite/site/trunk/images/streaming.png
ignite/site/trunk/images/support-apache.png
ignite/site/trunk/images/svengoly.png
ignite/site/trunk/images/tableau_logo-2.png
ignite/site/trunk/images/tableau_visualizing_data.png
ignite/site/trunk/images/tcampbell.png
ignite/site/trunk/images/user-default.png
ignite/site/trunk/images/video-screen-2-opt.jpg
ignite/site/trunk/images/video-screen-2.png
ignite/site/trunk/images/video-screen.png
ignite/site/trunk/images/web_sessions_3.png
ignite/site/trunk/images/webconsole-rdbms-1.png
ignite/site/trunk/images/webconsole-rdbms-2.png
ignite/site/trunk/images/webconsole-rdbms-3.png
ignite/site/trunk/images/yardstick-logo.png
ignite/site/trunk/images/zeppelin-integration-bargraph.png
ignite/site/trunk/images/zeppelin_logo.png
ignite/site/trunk/managedservices.html
ignite/site/trunk/provenusecases.html
ignite/site/trunk/scss/all.scss
ignite/site/trunk/scss/bootstrap/
ignite/site/trunk/scss/ignite.scss
ignite/site/trunk/test.php
ignite/site/trunk/use-cases/caching/database-caching.html
ignite/site/trunk/use-cases/comparison/
ignite/site/trunk/use-cases/database/
ignite/site/trunk/use-cases/hadoop/
ignite/site/trunk/use-cases/platforms/
ignite/site/trunk/use-cases/spark/
ignite/site/trunk/usecases.html
ignite/site/trunk/whatisignite-bk.html
Modified:
ignite/site/trunk/ (props changed)
ignite/site/trunk/.htaccess
ignite/site/trunk/arch/clustering.html
ignite/site/trunk/arch/persistence.html
ignite/site/trunk/community/contribute.html
ignite/site/trunk/community/resources.html
ignite/site/trunk/css/shCore.css
ignite/site/trunk/css/shCoreDefault.css
ignite/site/trunk/css/shCoreDjango.css
ignite/site/trunk/css/shCoreEclipse.css
ignite/site/trunk/css/shCoreEmacs.css
ignite/site/trunk/css/shCoreFadeToGrey.css
ignite/site/trunk/css/shCoreMDUltra.css
ignite/site/trunk/css/shCoreMidnight.css
ignite/site/trunk/css/shCoreRDark.css
ignite/site/trunk/css/shThemeDefault.css
ignite/site/trunk/css/shThemeDjango.css
ignite/site/trunk/css/shThemeEclipse.css
ignite/site/trunk/css/shThemeEmacs.css
ignite/site/trunk/css/shThemeFadeToGrey.css
ignite/site/trunk/css/shThemeMDUltra.css
ignite/site/trunk/css/shThemeMidnight.css
ignite/site/trunk/css/shThemeRDark.css
ignite/site/trunk/css/syntaxhighlighter.css
ignite/site/trunk/download.html
ignite/site/trunk/events.html
ignite/site/trunk/features.html
ignite/site/trunk/features/collocatedprocessing.html
ignite/site/trunk/features/datastructures.html
ignite/site/trunk/features/machinelearning.html
ignite/site/trunk/features/messaging.html
ignite/site/trunk/features/multilanguage.html
ignite/site/trunk/features/rdbmsintegration.html
ignite/site/trunk/features/servicegrid.html
ignite/site/trunk/features/sql.html
ignite/site/trunk/features/streaming.html
ignite/site/trunk/features/tensorflow.html
ignite/site/trunk/features/transactions.html
ignite/site/trunk/includes/footer.html
ignite/site/trunk/includes/header.html
ignite/site/trunk/includes/scripts.html
ignite/site/trunk/includes/styles.html
ignite/site/trunk/index.html
ignite/site/trunk/meetup-groups.html
ignite/site/trunk/releases/2.6.0/dotnetdoc/index.html
ignite/site/trunk/releases/2.7.0/dotnetdoc/index.html
ignite/site/trunk/releases/2.7.5/dotnetdoc/index.html
ignite/site/trunk/releases/2.7.6/dotnetdoc/index.html
ignite/site/trunk/releases/2.8.0/dotnetdoc/index.html
ignite/site/trunk/screencasts.html
ignite/site/trunk/sitemap.xml
ignite/site/trunk/use-cases/caching/hibernate-l2-cache.html
ignite/site/trunk/use-cases/caching/jcache-provider.html
ignite/site/trunk/use-cases/caching/web-session-clustering.html
ignite/site/trunk/whatisignite.html
Propchange: ignite/site/trunk/
------------------------------------------------------------------------------
Merged /ignite/site/branches/ignite-redisign:r1872006-1875784
Modified: ignite/site/trunk/.htaccess
URL: http://svn.apache.org/viewvc/ignite/site/trunk/.htaccess?rev=1875787&r1=1875786&r2=1875787&view=diff
==============================================================================
--- ignite/site/trunk/.htaccess (original)
+++ ignite/site/trunk/.htaccess Fri Mar 27 17:08:35 2020
@@ -6,16 +6,42 @@ Redirect 301 /features/java.html /featur
Redirect 301 /features/dotnet.html /features/multilanguage.html
Redirect 301 /features/cpp.html /features/multilanguage.html
Redirect 301 /features/clientprotos.html /features/multilanguage.html
-Redirect 301 collocatedprocessing.html /features/collocatedprocessing.html
-Redirect 301 /features/durablememory.html /arch/durablememory.html
-Redirect 301 /memorycentric.html /arch/memorycentric.html
+Redirect 301 /collocatedprocessing.html /features/collocatedprocessing.html
+Redirect 301 /features/durablememory.html /arch/multi-tier-storage.html
+Redirect 301 /arch/durablememory.html /arch/multi-tier-storage.html
+Redirect 301 /memorycentric.html /arch/multi-tier-storage.html
+Redirect 301 /arch/memorycentric.html /arch/multi-tier-storage.html
Redirect 301 /features/persistence.html /arch/persistence.html
Redirect 301 /features/deploy.html /arch/clustering.html
Redirect 301 /features/igniterdd.html /use-cases/spark/shared-memory-layer.html
+Redirect 301 /use-cases/spark/shared-memory-layer.html /use-cases/spark-acceleration.html
+Redirect 301 /use-cases/spark/sql-queries.html /use-cases/spark-acceleration.html
+Redirect 301 /use-cases/caching/database-caching.html /use-cases/in-memory-cache.html
+Redirect 301 /use-cases/database/in-memory-database.html /use-cases/in-memory-database.html
+Redirect 301 /use-cases/database/distributed-database.html /use-cases/in-memory-database.html
+Redirect 301 /use-cases/database/sql-database.html /use-cases/in-memory-database.html
+Redirect 301 /use-cases/hadoop/mapreduce.html /use-cases/hadoop-acceleration.html
+Redirect 301 /use-cases/hadoop/hdfs-cache.html /use-cases/hadoop-acceleration.html
+Redirect 301 /features/igfs.html /use-cases/hadoop-acceleration.html
+Redirect 301 /features/mapreduce.html /use-cases/hadoop-acceleration.html
+Redirect 301 /use-cases/database/key-value-store.html /use-cases/key-value-store.html
+Redirect 301 /usecases.html /
+Redirect 301 /use-cases/comparison/ignite-for-rdbms.html /
+Redirect 301 /use-cases/comparison/ignite-for-nosql.html /
+Redirect 301 /features/datagrid.html /use-cases/datagrid.html
+Redirect 301 /use-cases/platforms/dotnet.html /features/multilanguage.html
+Redirect 301 /provenusecases.html /use-cases/provenusecases.html
+Redirect 301 /features/datavisualization.html /features/manageandmonitor.html
+Redirect 301 /addons.html /features.html
+Redirect 301 /arch/durablememory.html /arch/multi-tier-storage.html
+Redirect 301 /features/runseverywhere.html /features/multilanguage.html
+Redirect 301 /features/igniterdd.html /use-cases/spark-acceleration.html
+Redirect 301 /blogs.html /
+Redirect 301 /features/computegrid.html /features/collocatedprocessing.html
-RewriteEngine On
+RewriteEngine On
-RewriteCond %{SERVER_PORT} 80
+RewriteCond %{SERVER_PORT} 80
RewriteRule ^(.*)$ https://%{SERVER_NAME}/$1 [R=301,L]
RewriteRule ^releases/latest/(.*)$ /releases/2.8.0/$1 [L]
Modified: ignite/site/trunk/arch/clustering.html
URL: http://svn.apache.org/viewvc/ignite/site/trunk/arch/clustering.html?rev=1875787&r1=1875786&r2=1875787&view=diff
==============================================================================
--- ignite/site/trunk/arch/clustering.html (original)
+++ ignite/site/trunk/arch/clustering.html Fri Mar 27 17:08:35 2020
@@ -39,246 +39,98 @@ under the License.
<meta http-equiv="Cache-Control" content="no-cache, no-store, must-revalidate" />
<meta http-equiv="Pragma" content="no-cache" />
<meta http-equiv="Expires" content="0" />
+
<title>Deploy Anywhere - Apache Ignite</title>
+
+ <meta name="description"
+ content="Apache Ignite implements the shared-nothing architecture when all the cluster nodes are equal
+ and there is no single point of failure or bottleneck. You can run Apache Ignite on bare metal, virtual
+ machines, Docker, Kubernetes, and cloud environments."/>
+
<!--#include virtual="/includes/styles.html" -->
<!--#include virtual="/includes/sh.html" -->
</head>
<body>
-<div id="wrapper">
- <!--#include virtual="/includes/header.html" -->
- <main id="main" role="main" class="container">
- <section id="deployment-options" class="page-section">
- <h1 class="first">Deploy Anywhere</h1>
- <div class="col-sm-12 col-md-12 col-xs-12" style="padding-left:0; padding-right:0;">
- <div class="col-sm-6 col-md-6 col-xs-12" style="padding-left:0; padding-right:0;">
- <p>
- Apache Ignite cluster is based on the shared-nothing architecture which implies that all the
- cluster nodes are equal, independent and self-sufficient, and there is no single point of failure
- across the cluster.
- </p>
- <p>
- Ignite nodes can automatically discover each other relying on flexible Discovery SPI component.
- This helps to scale the cluster out or down when needed and easily.
- </p>
- <p>
- Apache Ignite can run stand-alone, in a cluster, within Kubernetes and Docker containers, as well
- as on Apache Mesos and Hadoop Yarn. It can also run on physical servers as well as within
- virtual environments or clouds. Technically there are no limitations on where the cluster
- can be deployed.
- </p>
+ <!--#include virtual="/includes/header.html" -->
+<article>
+ <header>
+ <div class="container">
+ <h1>Apache Ignite <strong>Deployment Options</strong></h1>
+ </div>
+ </header>
+ <div class="container">
+
+
+ <p>
+ Apache Ignite® implements the shared-nothing architecture where all cluster nodes are equal
+ and there is no single point of failure or bottleneck.
+ Ignite does NOT have a component such as a master node or name node that is present in most
+ distributed systems.
+ </p>
+ <img class="img-responsive diagram-right" src="/images/svg-diagrams/ignite_cluster.svg" alt="Apache Ignite cluster diagram" />
+ <p>
+ Ignite nodes discover each other automatically in your environment, and the cluster can be
+ scaled out or in easily.
+ </p>
+ <p>
+ Apache Ignite can run on bare metal, virtual machines, Docker, Kubernetes, and cloud
+ environments. Technically there are no limitations in regards to deployment environments --
+ since Ignite nodes can auto-discover each other via the TCP/IP interface, you can launch a
+ cluster anywhere.
+ </p>
+
+
+ <h2>Servers, Clients and Protocols</h2>
+ <p>
+ Ignite defines two types of nodes â servers and clients.
+
+ A server node is the base computational and data storage unit. Typically, you start a single server
+ node per machine or container and it will scale vertically by utilizing all of the CPU, RAM, and other
+ resources available unless specified differently. These resources are pooled and become available to
+ Ignite applications once the server node joins the cluster of other server nodes.
+ </p>
+ <p>
+ A cluster is a group of server nodes interconnected together in order to provide shared resources
+ like RAM and CPU to your applications.
+ </p>
+ <p>
+ Client nodes (aka. thick clients) are your connection endpoints and gateways from the application layer
+ to the cluster of server nodes. You always embed a client into your application code and execute the
+ required APIs. The clients shield all the complexity of Igniteâs distributed nature from application
+ developers who will see the cluster as a single unit. Itâs as simple as connecting to an RDBMS via a
+ JDBC driver or Spring Data framework.
+ </p>
+ <p>
+ In addition to the thick clients, you can access the cluster with Ignite thin clients,
+ JDBC and ODBC drivers, or the REST API.
+ </p>
+
+ <div class="jumbotron jumbotron-fluid">
+ <div class="container">
+ <div class="title display-6">Learn More</div>
+ <hr class="my-4">
+ <div class="row">
+ <div class="col-sm-6">
+ <ul>
+ <li><a href="https://apacheignite.readme.io/docs/clustering" target="docs">Ignite Clustering <i class="fa fa-angle-double-right"></i></a></li>
+ <li><a href="https://apacheignite.readme.io/docs/tcpip-discovery" target="docs">Discovery SPI Configuration <i class="fa fa-angle-double-right"></i></a></li>
+ </ul>
</div>
- <div class="col-sm-6 col-md-6 col-xs-12" style="padding-right:0;">
- <img class="img-responsive" src="/images/ignite-deploy.png" width="540px" style="float:right;"/>
+ <div class="col-sm-6">
+ <ul>
+ <li><a href="https://apacheignite.readme.io/docs/network-config" target="docs">Communication SPI Configuration <i class="fa fa-angle-double-right"></i></a></li>
+ <li><a href="/features/multilanguage.html">Multi-Language Support <i class="fa fa-angle-double-right"></i></a></li>
+ </ul>
</div>
- </div>
-
- <div class="page-heading">Servers, Clients and Protocols</div>
- <p>
- There are two types of nodes defined in Ignite - client and server nodes. The nodes server a
- different purpose.
- </p>
- <p>
- The server nodes act as containers for data and computations. Once interconnected, the server nodes will
- represent a distributed database (or data grid) that stores the data, participates in queries processing,
- compute execution, stream processing, etc.
- </p>
- <p>
- The client nodes, on their turn, provide an ability to connect to the distributed database (a group of server nodes)
- remotely. Ignite native clients allow using the whole set of Ignite APIs, including SQL, transactions,
- compute, streaming, services, etc. from the client side.
- </p>
- <p>
- In addition to the client nodes, you can access the cluster by means of Ignite binary client protocol,
- JDBC and ODBC drivers, or REST API.
- </p>
-
- <div class="page-heading">Cloud Native Database</div>
- <p>
- Cloud native technologies allow us to build and run scalable applications in public, private and
- hybrid environments. Ignite is a <a href="https://landscape.cncf.io/landscape=database-and-data-warehouse" target="_blank" rel="noopener">
- cloud native database</a> designed specifically for a cloud
- computing architecture.
- </p>
- <p>
- Ignite has native integration with <code class="text-nowrap">Amazon AWS</code>
- and <code class="text-nowrap">Google Compute Engine</code>. For all other cloud environments, Ignite
- integrates with <code class="text-nowrap">Apache JClouds</code> that has support for most of the
- <a href="https://jclouds.apache.org/reference/providers/" target="_blank" rel="noopener" class="text-nowrap">existing
- cloud providers</a>.
- </p>
- <div class="page-heading">Containers</div>
- <p>
- Ignite can freely run within container environments. Ignite's integration with <code>Docker</code>
- allows to automatically build and deploy user code into Ignite prior to server startup.
- </p>
- <p>
- Apache Ignite cluster can also be deployed in <code>Kubernetes</code> that allows automatic deployment and management of
- containerized applications.
- </p>
-
- <div class="page-heading">Resource Managers</div>
- <p>
- Ignite provides native integration for <code class="text-nowrap">Hadoop Yarn</code>,<code>Kubernetes</code>,
- and <code class="text-nowrap">Apache Mesos</code> making it very easy to seamlessly deploy Ignite
- into specific environments and manage it there.
- </p>
-
- <div class="page-heading">More on Clustering and Deployment</div>
- <table class="formatted" name="Deployment Options Features">
- <thead>
- <tr>
- <th width="35%" class="left">Feature</th>
- <th>Description</th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td class="left">Clients and Servers</td>
- <td>
- <p>
- There are two types of nodes defined in Ignite - client and server nodes. The nodes server a
- different purpose:
- </p>
- <div class="page-links">
- <a href="https://apacheignite.readme.io/docs/clients-vs-servers" target="docs">Docs for this feature <i class="fa fa-angle-double-right"></i></a>
- </div>
- </td>
- </tr>
- <tr>
- <td class="left">Self-Healing Cluster</td>
- <td>
- <p>
- Ignite cluster can self-heal, where clients automatically reconnect in case of failures,
- slow clients are automatically kicked out, and data from failed nodes
- is automatically propagated to other nodes in the grid:
- </p>
- <div class="page-links">
- <a href="http://apacheignite.readme.io/docs/clients-vs-servers" target="docs">Docs for this Feature <i class="fa fa-angle-double-right"></i></a>
- </div>
- </td>
- </tr>
- <tr>
- <td class="left">Cross-platform Support</td>
- <td>
- <p>
- Applications can access the cluster from numerous programming languages as well as JDBC/ODBC
- drivers, and additional protocols:
- </p>
- <div class="page-links">
- <a href="/features/multilanguage.html" target="docs">Docs for this feature <i class="fa fa-angle-double-right"></i></a>
- </div>
- </td>
- </tr>
- <tr>
- <td class="left">Zero Deployment</td>
- <td>
- <p>
- Ignite nodes automatically become aware of custom classes, eliminating the need to explicitly deploy them:
- </p>
- <div class="page-links">
- <a href="https://apacheignite.readme.io/docs/zero-deployment" target="docs">Docs for this feature <i class="fa fa-angle-double-right"></i></a>
- </div>
- </td>
- </tr>
- <tr>
- <td class="left">Dynamic Schema Changes</td>
- <td>
- <p>
- Ignite stores objects in binary format eliminating the need to deploy classes on server nodes:
- </p>
- <div class="page-links">
- <a href="https://apacheignite.readme.io/docs/binary-marshaller" target="docs">Docs for this feature <i class="fa fa-angle-double-right"></i></a>
- </div>
- </td>
- </tr>
- <tr>
- <td class="left">Stand-Alone Clusters</td>
- <td>
- <p>
- Ignite nodes can automatically discover each other. This helps to scale the cluster
- when needed, without having to restart the whole cluster - simply start up new additional
- nodes and they will automatically join the existing work loads:
- </p>
- <div class="page-links">
- <a href="http://apacheignite.readme.io/docs/cluster" target="docs">Docs for this Feature <i class="fa fa-angle-double-right"></i></a>
- </div>
- </td>
- </tr>
- <tr>
- <td class="left">Docker Container</td>
- <td>
- <p>
- <code>Docker</code> allows to package Ignite deployment with all the dependencies into a
- standard container. Docker automates downloading the Ignite release, deploying users'
- code into Ignite, and configuring nodes. It also automatically starts up the fully
- configured Ignite node:
- </p>
- <div class="page-links">
- <a href="http://apacheignite.readme.io/docs/docker-deployment" target="docs">Docs for this Feature <i class="fa fa-angle-double-right"></i></a>
- </div>
- </td>
- </tr>
- <tr>
- <td class="left">Kubernetes</td>
- <td>
- <p>
- Apache Ignite cluster can be easily deployed in and maintained by <code>Kubernetes</code> which is an
- open-source system for automating deployment, scaling, and management of containerized applications:
- </p>
- <div class="page-links">
- <a href="https://apacheignite.readme.io/docs/kubernetes-deployment" target="docs">Docs for this Feature <i class="fa fa-angle-double-right"></i></a>
- </div>
- </td>
- </tr>
- <tr>
- <td class="left">Public Clouds</td>
- <td>
- <p>
- For public cloud environments, Ignite has native integration with <code class="text-nowrap">Amazon AWS</code>
- and <code class="text-nowrap">Google Compute Engine</code>. For all other cloud environments, Ignite
- integrates with <code class="text-nowrap">Apache JClouds</code> which has support for most of the
- <a href="https://jclouds.apache.org/reference/providers/" target="_blank" rel="noopener" class="text-nowrap">existing cloud providers</a>.
- </p>
- <div class="page-links" style="line-height: 1.3;">
- <a href="https://apacheignite-mix.readme.io/docs/amazon-aws" target="docs">Amazon AWS Integration <i class="fa fa-angle-double-right"></i></a><br/>
- <a href="https://apacheignite-mix.readme.io/docs/google-compute-engine" target="docs">Google Cloud Integration <i class="fa fa-angle-double-right"></i></a><br/>
- <a href="https://apacheignite-mix.readme.io/docs/jclouds" target="docs">Apache JClouds Integration <i class="fa fa-angle-double-right"></i></a>
- </div>
- </td>
- </tr>
- <tr>
- <td class="left">Apache Mesos</td>
- <td>
- <p>
- Ignite provides native integration for <code>Apache Mesos</code> making it very easy
- to deploy into Mesos data centers, such as, for example, Hadoop and Spark environments:
- </p>
- <div class="page-links">
- <a href="http://apacheignite.readme.io/docs/mesos-deployment" target="docs">Docs for this Feature <i class="fa fa-angle-double-right"></i></a>
- </div>
- </td>
- </tr>
- <tr>
- <td class="left">Hadoop Yarn</td>
- <td>
- <p>
- Ignite provides native integration for <code>Hadoop Yarn</code> making it very easy
- to deploy into Hadoop and Spark environments:
- </p>
- <div class="page-links">
- <a href="http://apacheignite.readme.io/docs/yarn-deployment" target="docs">Docs for this Feature <i class="fa fa-angle-double-right"></i></a>
- </div>
- </td>
- </tr>
- </tbody>
- </table>
- </section>
- </main>
-
- <!--#include virtual="/includes/footer.html" -->
+ </div>
+ </div>
+ </div>
</div>
+</article>
+ <!--#include virtual="/includes/footer.html" -->
+
<!--#include virtual="/includes/scripts.html" -->
</body>
</html>
Modified: ignite/site/trunk/arch/persistence.html
URL: http://svn.apache.org/viewvc/ignite/site/trunk/arch/persistence.html?rev=1875787&r1=1875786&r2=1875787&view=diff
==============================================================================
--- ignite/site/trunk/arch/persistence.html (original)
+++ ignite/site/trunk/arch/persistence.html Fri Mar 27 17:08:35 2020
@@ -33,147 +33,131 @@ under the License.
<!DOCTYPE html>
<html lang="en">
<head>
- <link rel="canonical" href="https://ignite.apache.org/arch/persistence.html" />
+ <link rel="canonical" href="https://ignite.apache.org/arch/persistence.html"/>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
- <meta http-equiv="Cache-Control" content="no-cache, no-store, must-revalidate" />
- <meta http-equiv="Pragma" content="no-cache" />
- <meta http-equiv="Expires" content="0" />
- <title>Distributed Peristence - Apache Ignite</title>
- <meta name="description" content="Apache Ignite can be used as a memory-centric distributed SQL database that allows executing SQL queries over the data that is both in memory and on disk"/>
+ <meta http-equiv="Cache-Control" content="no-cache, no-store, must-revalidate"/>
+ <meta http-equiv="Pragma" content="no-cache"/>
+ <meta http-equiv="Expires" content="0"/>
+
+ <title>Distributed Persistence - Apache Ignite</title>
+
+ <meta name="description"
+ content="The native persistence integrates into the Ignite multi-tier storage as a disk tier that can
+ be turned on to let Ignite store more data on disk than it can cache in memory and to enable fast cluster restarts."/>
+
<!--#include virtual="/includes/styles.html" -->
<!--#include virtual="/includes/sh.html" -->
</head>
<body>
-<div id="wrapper">
<!--#include virtual="/includes/header.html" -->
-
- <main id="main" role="main" class="container">
- <section id="native-persistence" class="page-section">
- <h1 class="first">Distributed Persistence</h1>
- <div class="col-sm-12 col-md-12 col-xs-12" style="padding-left:0; padding-right:0;">
- <div class="col-sm-6 col-md-6 col-xs-12" style="padding-left:0; padding-right:0;">
- <p>
- Ignite is widely used as a caching layer above an existing 3rd
- party database, such as RDBMS, Apache Cassandra or MongoDB, to
- accelerate them. At the same time, Ignite comes with its own persistence that is considered as an alternate
- and preferable persistence layer for an Ignite cluster.
- </p>
- <p>
- Ignite native persistence is a distributed, ACID, and <nobr>SQL-compliant</nobr> disk store
- that transparently integrates with Ignite memory-centric storage. Ignite persistence is optional
- and can be turned on and off. When turned off Ignite becomes a pure in-memory store.
- </p>
-
- </div>
- <div class="col-sm-6 col-md-6 col-xs-12" style="padding-right:0; top: -10px;">
- <a href="/images/native_persistence.png"><img class="img-responsive" src="/images/native_persistence.png" width="450px" style="float:right;" alt="Apache Ignite Native Persistence - Distributed SQL Database"/></a>
- </div>
+ <article>
+ <header>
+ <div class="container">
+ <h1>Apache Ignite <strong>Native Persistence</strong></h1>
+ </div>
+ </header>
+ <div class="container">
+
+ <p>
+ Even though Apache Ignite® is broadly used as a caching layer on top of external databases, it
+ comes with its native persistence - a distributed, ACID, and SQL-compliant disk-based
+ store. The native persistence integrates into the Ignite multi-tier storage as a disk tier that
+ can be turned on to let Ignite store more data on disk than it can cache in memory and to enable
+ fast cluster restarts.
+ </p>
+ <img class="img-responsive diagram-right" src="/images/svg-diagrams/native_persistence.svg" alt="Apache Ignite Native Persistence"/></a>
+ <p>
+ When the native persistence enabled, Ignite stores a superset of data on disk and caches as
+ much as it can in memory. For example, if your application needs to store 200 records in an
+ Ignite cluster and the memory capacity allows caching only 150 records, then all 200 will be
+ stored on disk, out of which 150 will be served from memory while the rest 50 from disk whenever
+ the application requests them.
+ </p>
+
+ <h2>Ignite Persistence vs. External Databases</h2>
+ <p>
+ The native persistence has the following advantages over external databases:
+ </p>
+ <ul>
+ <li>
+ The ability to cache a subset of the data - Ignite stores 100% of data on disk and lets you cache as
+ much as required in memory.
+ </li>
+ <li>
+ The ability to query data from disk - if any record is missing in memory, then Ignite reads it from
+ disk. This is supported for all the APIs including SQL.
+ </li>
+ <li>
+ Instantaneous cluster restarts - Ignite becomes fully operational from disk upon a cluster
+ startup or restarts without requiring to preload or warm up the memory tier.
+ </li>
+ </ul>
+
+ <h2>Write-Ahead Logging and Checkpointing</h2>
+ <p>
+ If Ignite native persistence is selected as a disk tier, then every time a record is updated in memory,
+ the change is added to the write-ahead log (WAL). The purpose of the WAL is to propagate updates to disk
+ in the fastest way possible and provide a consistent recovery mechanism that supports full cluster
+ failures.
+
+ As the WAL grows, it periodically gets checkpointed to the main storage. Checkpointing is the process of
+ copying dirty pages from the memory tier to the partition files on disk. A dirty page is a page that was
+ updated in memory, was appended to the WAL, but was not written to the respective partition file on disk yet.
+ </p>
+
+ <h2>Durability</h2>
+ <p>
+ Ignite native persistence provides the following ACID guarantees across the cluster:
+ </p>
+
+ <ul>
+ <li>
+ Committed transactions always survive failures.
+ </li>
+ <li>
+ The cluster can always be recovered to the latest successfully committed transaction.
+ </li>
+ </ul>
+
+ <div class="jumbotron jumbotron-fluid">
+ <div class="container">
+ <div class="display-6 title">Learn More</div>
+ <hr class="my-4">
+ <div class="row">
+ <div class="col-sm-6">
+ <ul>
+ <li>
+ <p><a href="/arch/multi-tier-storage.html">Multi-Tier Storage <i class="fa fa-angle-double-right"></i></a></p>
+ </li>
+ <li>
+ <p><a href="https://apacheignite.readme.io/docs/distributed-persistent-store" target="docs">Native Persistence Usage and Configuration <i class="fa fa-angle-double-right"></i></a></p>
+ </li>
+ <li>
+ <p><a href="https://cwiki.apache.org/confluence/display/IGNITE/Ignite+Persistent+Store+-+under+the+hood" target="docs">Native Persistence Implementation Details <i class="fa fa-angle-double-right"></i></a></p>
+ </li>
+ </ul>
</div>
- <p>
- With native persistence enabled, Ignite always stores a superset of data on disk,
- and as much as possible in RAM. For example, if there are
- 100 entries and RAM has the capacity to store only 20, then all 100 will be stored on disk
- and only 20 will be cached in RAM for better performance.
- </p>
- <p>
- Ignite native persistence has the following important characteristics:
- </p>
- <ul class="page-list" style="margin-bottom: 20px;">
- <li>
- SQL queries over the full data set that spans both, memory and disk. This means that Apache
- Ignite can be used as a memory-centric distributed SQL database.
- </li>
- <li>
- No need to have all the data in memory. Ignite persistence allows storing a superset
- of data on disk and only most frequently used subsets in memory.
- </li>
- <li>
- Instantaneous cluster restarts. Ignite becomes fully operational from disk immediately
- upon cluster startup or restart. There is no need to preload or warm up the in-memory caches.
- The data will be loaded in-memory lazily, as it gets accessed.
- </li>
- <li>
- Data and indexes are stored in a similar format both in memory and on disk, which helps avoid
- expensive transformations when moving data between memory and disk.
- </li>
- <li>
- Ability to create full and incremental cluster snapshots by plugging-in 3rd party solutions.
- </li>
- </ul>
-
- <div class="page-heading">Write-Ahead Log</div>
- <p>
- Every time the data is updated in memory, the update will be appended to the tail of
- the write-ahead log (WAL). The purpose of the WAL is to propagate updates to disk in
- the fastest way possible and provide a consistent recovery mechanism that supports full cluster failures.
- </p>
- <p>
- The whole WAL is split into several files, called segments, that are filled out sequentially.
- Once a segment is full, its content will be copied to the <i>WAL archive</i> where it will be preserved
- for a configurable amount of time. While the segment is being copied, another segment
- will be treated as an active WAL file.
- </p>
- <p>
- The cluster can always be recovered up to the latest successfully committed transaction.
- </p>
-
- <div class="page-heading">Checkpointing</div>
- <p>
- As WAL grows, it periodically gets <i>checkpointed</i> to the main storage.
- Checkpointing is the process of copying <i>dirty pages</i> from memory to the partition files on disk.
- A dirty page is a page that was updated in memory, was appended to WAL, but was not written to a respective partition
- file on disk yet.
- </p>
- <div class="page-heading">Durability</div>
- <p>
- Ignite native persistence provides ACID durability guarantees to the data:
-
- <ul class="page-list" style="margin-bottom: 20px;">
- <li>Committed transactions will always survive any failures.</li>
- <li>
- The cluster can always be recovered to the latest successfully committed transaction.
- </li>
- <li>
- The cluster restarts are very fast.
- </li>
- </ul>
- </p>
- <div class="page-heading">Configuration</div>
- <p>
- To enable Ignite persistence, add the following configuration parameter to the cluster's
- node configuration:
- </p>
- <div class="tab-content">
- <div class="tab-pane active" id="configuration">
- <pre class="brush:xml">
- <bean class="org.apache.ignite.configuration.IgniteConfiguration">
- <!-- Enabling Apache Ignite native persistence. -->
- <property name="dataStorageConfiguration">
- <bean class="org.apache.ignite.configuration.DataStorageConfiguration">
- <property name="defaultDataRegionConfiguration">
- <bean class="org.apache.ignite.configuration.DataRegionConfiguration">
- <property name="persistenceEnabled" value="true"/>
- </bean>
- </property>
- </bean>
- </property>
-
- <!-- Additional setting. -->
-
- </bean>
- </pre>
- </div>
+ <div class="col-sm-6">
+ <ul>
+ <li>
+ <p><a href="/features/sql.html">Distributed SQL <i class="fa fa-angle-double-right"></i></a></p>
+ </li>
+ <li>
+ <p><a href="/features/collocatedprocessing.html">Co-located Processing <i class="fa fa-angle-double-right"></i></a></p>
+ </li>
+ <li>
+ <p><a href="/features/transactions.html">ACID Transactions <i class="fa fa-angle-double-right"></i></a></p>
+ </li>
+ </ul>
</div>
-
- <p><a href="https://apacheignite.readme.io/docs/distributed-persistent-store" target="_blank" rel="noopener">Read more</a></p>
- </section>
-
- </main>
-
- <!--#include virtual="/includes/footer.html" -->
-</div>
+ </div>
+ </div>
+ </div>
+ </div><!-- end .container -->
+</article>
+<!--#include virtual="/includes/footer.html" -->
<!--#include virtual="/includes/scripts.html" -->
</body>
</html>
Modified: ignite/site/trunk/community/contribute.html
URL: http://svn.apache.org/viewvc/ignite/site/trunk/community/contribute.html?rev=1875787&r1=1875786&r2=1875787&view=diff
==============================================================================
--- ignite/site/trunk/community/contribute.html (original)
+++ ignite/site/trunk/community/contribute.html Fri Mar 27 17:08:35 2020
@@ -45,50 +45,135 @@ under the License.
<!--#include virtual="/includes/sh.html" -->
</head>
<body>
-<div id="wrapper">
<!--#include virtual="/includes/header.html" -->
-
- <main id="main" role="main" class="container">
- <section id="contribute" class="page-section">
- <h1 class="first">Contribute to Apache Ignite</h1>
- <p>
- Before you get involved in Apache Ignite development, please sign up to the
- <a href="mailto:dev@ignite.apache.org">dev mailing list</a> and say "Hello" to everyone in
- the community. Tell us as much as you can about your areas of expertise mentioning how
- exactly you would like to contribute. We are a friendly and inclusive community and will try to
- simplify your "onboarding" considering your strengths or areas of interest.
+<article>
+ <header>
+ <div class="container">
+ <h1 >Contribute to <strong>Apache Ignite</strong></h1>
+ </div>
+ </header>
+ <div class="container">
+
+ <p>
+ This guide discusses various types of contribution to Apache Ignite extending generic ideas
+ of the <a href="https://community.apache.org/gettingStarted/101.html" target="_blank">ASF Getting
+ Started</a>. Contributing to Ignite doesnât just mean writing code. Helping new users on the mailing
+ list and improving documentation are also important. In fact, proposing significant code changes
+ usually requires first gaining experience and credibility within the community by helping in other ways.
+ </p>
+ <p>
+ The guide organizes contributions in an order that should be considered by new contributors
+ who intend to get involved long-term. Build some track record of helping others, become more
+ experienced with Ignite rather than solely focusing on code pull-requests.
+ </p>
+ <p>
+ Also, our communication and collaboration are based on
+ <a href="http://www.apache.org/theapacheway/index.html" target="_blank">The Apache Way</a> that helps
+ us, as a group of professionals, drive the project forward in a respectful and inclusive way.
+ </p>
+
+ <h2>Getting Started</h2>
+ <p>
+ The first thing to do is to join our <a href="mailto:dev@ignite.apache.org">dev mailing
+ list</a> and say "Hello" to everyone in the community. Tell us something about your areas of
+ expertise mentioning how exactly you would like to contribute. We are a friendly and inclusive
+ community and will try to simplify your "onboarding" considering your strengths and areas of interest.
Also, make sure to share your JIRA ID in the same email
(<a href="https://issues.apache.org/jira/projects/IGNITE"target="_blank">create a new one</a>
if you don't have an ASF JIRA account yet). One of our community members will add you to
- the contributors' list and you will be able to go ahead and book Ignite tasks you'd like to work on.
- </li>
+ the contributors' list.
</p>
<p>
- Again, a small formality, you need to subscribe to the dev list before sending emails to it. To
- subscribe, send an empty email to <a
- href="mailto:dev-subscribe@ignite.apache.org?subject=Subscribe"><nobr>dev-subscribe@ignite.apache.org</nobr></a>
- and follow simple instructions in the reply.
+ Next, check the <a href="https://cwiki.apache.org/confluence/display/IGNITE/How+to+Collaborate" target="_blank">
+ How to Collaborate</a> page for more details on various communication channels used by the community
+ members. Even though most of the discussions take place on the dev list, we hang out on Slack.
</p>
+
+ <h2>Contribute by Helping Others</h2>
+
<p>
- Finally, check <a href="https://cwiki.apache.org/confluence/display/IGNITE/How+to+Collaborate" target="_blank">
- How to Collaborate</a> page for more details on various communication channels used by the community
- members. Even though most of the discussions take place on the dev list, we hang out in Slack.
+ A great way to contribute to Ignite and get more practical experience is by helping answer
+ user questions on the user@ignite.apache.org mailing list or on StackOverflow. Ignite users ask dozens
+ of questions daily; taking a few minutes to help answer a question or troubleshoot an issue is a very
+ valuable contribution to the project and community success.
+ </p>
+ <p>
+ Subscribe to the <a href="/community/resources.html">user list and set up StackOverflow notifications</a>
+ to stay up to date on whatâs happening in Ignite. Answering questions is an excellent and visible way
+ to help the community, which also demonstrates your expertise.
+ </p>
+
+ <h2>Contribute Documentation Changes</h2>
+ <p>
+ Contributing to technical documentation and API references such as JavaDocs are as valuable as contributing to bug
+ fixes or features. Ignite documentation is an integral part of the project, which educates Ignite users
+ about Ignite capabilities, configuration techniques, optimization aspects and many other areas they need
+ to understand to deploy Ignite successfully in production. Documentation and APIs are the faces of the
+ project and the community puts a lot of effort in maintaining them properly and professionally.
+ </p>
+ <p>
+ Code changes contribution is not the only way to become an Ignite committer. Help the community to
+ produce and maintain the documentation pages or API references, edit and correct existing content, stay
+ active on the user and dev mailing lists, and you'll become a committer in due course.
</p>
- <div class="page-heading">Contribution Process</div>
+
+ <ul class="page-list">
+ <li>
+ Came across a misprint or unclear documentation section? Use "Suggest Edits" feature of
+ our <a href="https://apacheignite.readme.io/docs" target="_blank"> main documentation portal</a> to
+ propose a change.
+ </li>
+ <li>
+ Select any <a href="https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20resolution%20%3D%20Unresolved%20AND%20status%20not%20in%20(closed%2C%20resolved)%20and%20component%20%3D%20documentation%20%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC" target="_blank">
+ open documentation ticket</a> and start working on it. Use "Suggest Edits" to submit improvements.
+ </li>
+ <li>
+ To propose a change to <a href="/docs-and-apis.html#apis">API references</a> such as JavaDocs,
+ follow the process similar to the code contribution described below -- update the docs and send a
+ pull-request.
+ </li>
+ </ul>
+
+
+ <h2>Code Contributions</h2>
<p>
- Before you start contributing, spend some time to get to know our
+ Before you start with code contributions, get to know our
<a href="https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute" target="_blank">Contribution and
- Development</a> process. In short, our communication and collaboration are based on
- <a href="http://www.apache.org/theapacheway/index.html" target="_blank">The Apache Way</a> that helps
- us, as a group of professionals, drive the project forward in a respectful and inclusive way.
+ Development</a> process.
</p>
- <div class="page-heading">Pick a Ticket</div>
+ <div class="page-heading">Extensions and Integrations Contribution</div>
+ <p>
+ Ignite is used together with a huge selection of libraries and
+ frameworks, and some of them are officially supported by the community. While some of the
+ existing integrations such as with Spark, Spring Data, or Hibernate still reside in the primary Ignite
+ repository, they all will eventually be moved to the Ignite Extensions repository. New integrations are
+ accepted to the Extensions repository only.
+ </p>
+ <p>
+ Feel free to contribute a new extension to Ignite or select an open ticket to help improve existing
+ integrations:
+ </p>
+ <ul>
+ <li>
+ <a href="https://issues.apache.org/jira/browse/IGNITE-8382?jql=project%20%3D%20Ignite%20and%20summary%20~%20%22spring%22%20and%20status%20not%20in%20(Resolved%2C%20Closed)" target="_blank">
+ Spring Framework</a> integrations.
+ </li>
+ <li>
+ <a href="https://issues.apache.org/jira/browse/IGNITE-12054?jql=project%20%3D%20Ignite%20and%20summary%20~%20%22spark%22%20and%20status%20not%20in%20(Resolved%2C%20Closed)" target="_blank">
+ Apache Spark</a> integration.
+ </li>
+ <li>
+ <a href="https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20component%20in%20(Integrations)%20and%20status%20%3D%20OPEN"
+ target="_blank">All other</a> integrations.
+ </li>
+ </ul>
+
+ <h2>Contribute to Ignite core</h2>
<p>
- Select a task of your interest and finish the first contributions! Start paving a path to the role of an
- Apache Ignite committer! To simplify your first choice, we prepared a list of tickets of easy and
- moderate complexity:
+ If you want to contribute to the core components of Ignite, then consider one of the tickets
+ below. These tickets are of easy and moderate complexity, which can simplify your start:
</p>
<ul class="page-list">
<li>
@@ -106,33 +191,29 @@ under the License.
SQL tasks</a> to start with.
</li>
<li>
- If you are more interested in .NET, Python, Node.JS or other programming languages different from
- Java then use <a
+ If you are more interested in .NET, Python, Node.JS, or other programming languages different from
+ Java, then use <a
href="https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20labels%20in%20(newbie)%20and%20component%20in%20(platforms)%20and%20status%20%3D%20OPEN" target="_blank">
- this filter</a> for the selection of the first tasks.
- </li>
- <li>
- Are you willing to integrate Ignite with other frameworks and technologies? Check one of
- <a href="https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20component%20in%20(Integrations)%20and%20status%20%3D%20OPEN"
- target="_blank">these tickets </a> or propose your integration.
+ this filter</a> to select your first task.
</li>
<li>
Curious in distributed data structures?
<a
href="https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20component%20in%20(%22data%20structures%22)%20and%20status%20%3D%20OPEN" target="_blank">
- Help to improve</a> existing ones or contribute a brand new.
+ Help to improve</a> the existing ones or contribute a brand new.
</li>
</ul>
<p>
Still haven't found anything gripping? Search through all the tickets in
<a href="https://issues.apache.org/jira/browse/IGNITE/">Ignite Jira</a>, check the latest Ignite
- discussions on the dev list or simply email us.
+ discussions on the dev list, or simply email us.
</p>
-
- <div class="page-heading">Become a Committer and PMC Member</div>
+
+
+ <h2>Become a Committer and PMC Member</h2>
<p>
We love contributions and gladly promote active contributors to committers and PMC members! If you
- are new to Apache Software Foundation then Ignite will be an excellent
+ are new to Apache Software Foundation then Ignite will be an excellent choice to start your journey.
</p>
<p>
The most important point of becoming a committer for Apache projects is active participation
@@ -141,7 +222,7 @@ under the License.
meritocratic principles of community management.
</p>
<p>
- Of course, code contributions are also important. Once you make a few code contributions,
+ Of course, code and documentation contributions are also important. Once you make a few of them,
you will become eligible to join Ignite committers, and possibly Ignite PMC.
Candidates for new committers or PMC members are suggested by the current committers, mentors, or
PMC members, and then must be approved by the PMC voting process.
@@ -149,26 +230,25 @@ under the License.
This page</a> explains how and when Ignite community members decide to propose contributors to
the roles of committers or PMC members.
</p>
- </section>
-
- <section id="ignite-dev" class="page-section">
+
+
<h2>Start Coding</h2>
<p>
Apache Ignite uses GIT for its VCS system. The "master" branch contains the last released version.
The "ignite-{version}" branch contains the latest code for the latest or upcoming release.
Refer to the <a href="https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute" target="_blank">Contribution and
- Development</a> page that explains the process in detail including reviews, pull-requests, etc. --
- everything you need to know and to do before a contribution can be accepted.
- While below you can find quick instructions if you can't wait and want to checkout the Ignite repo,
- explore its code and do some changes:
+ Development</a> page which explains the process in detail including reviews, pull-requests, etc. --
+ everything you need to know and do before a contribution can be accepted.
+ While below you can find more detailed instructions, here is how you can checkout the Ignite repo and explore
+ its code:
</p>
- <div class="page-heading">GIT checkout</div>
+ <h5>GIT checkout</h5>
<pre class="brush:bash">
# Master branch.
$ git clone https://github.com/apache/ignite.git
</pre>
- <div class="page-heading">Build Project</div>
+ <h5>Build Project</h5>
<pre class="brush:bash">
# Build project.
$ mvn clean install -Pall-java,all-scala,licenses -DskipTests
@@ -177,11 +257,11 @@ under the License.
See more detailed build instructions in the
<a href="https://github.com/apache/ignite/blob/master/DEVNOTES.txt" target="_blank" rel="noopener">DEVNOTES.txt</a> file.
</p>
- </section>
- </main>
- <!--#include virtual="/includes/footer.html" -->
-</main>
+
</div>
+</article>
+<!--#include virtual="/includes/footer.html" -->
+
<!--#include virtual="/includes/scripts.html" -->
</body>
</html>
Modified: ignite/site/trunk/community/resources.html
URL: http://svn.apache.org/viewvc/ignite/site/trunk/community/resources.html?rev=1875787&r1=1875786&r2=1875787&view=diff
==============================================================================
--- ignite/site/trunk/community/resources.html (original)
+++ ignite/site/trunk/community/resources.html Fri Mar 27 17:08:35 2020
@@ -45,120 +45,105 @@ under the License.
<!--#include virtual="/includes/sh.html" -->
</head>
<body>
-<div id="wrapper">
- <!--#include virtual="/includes/header.html" -->
-
- <main id="main" role="main" class="container">
- <section id="ask" class="page-section">
- <h1 class="first">Community Resources</h1>
- <p>
- There are many ways you can get help from Apache Ignite community. The <a href="#mail-lists">mailing lists</a>
- are the easiest way to get answers or to get involved with the project. Specifically, if you have any questions
- on how to use Ignite, you should subscribe to the user mailing list:
- <ul class="page-list">
- <li>
- <a href="http://apache-ignite-users.70518.x6.nabble.com/">user@ignite.apache.org</a>
- (<a href="mailto:user-subscribe@ignite.apache.org?subject=Subscribe&body=Please%20subscribe%20me.">subscribe</a>,
- <a href="mailto:user-unsubscribe@ignite.apache.org?subject=Unsubscribe&body=Please%20unsubscribe%20me.">unsubscribe</a>,
- <a href="http://apache-ignite-users.70518.x6.nabble.com/">forum</a>,
- <a href="http://mail-archives.apache.org/mod_mbox/ignite-user/">archives</a>)
- </li>
- </ul>
- </p>
- </section>
-
- <section id="stackoverflow" class="page-section">
- <h2>Stack Overflow</h2>
- <p>
- Many Ignite community members watch <a href="http://stackoverflow.com/questions/tagged/ignite">Stack Overflow</a>
- for the tag <b>"ignite"</b> or <b>"apacheignite"</b>, so you can post your questions there as well.
- </p>
- </section>
-
- <section id="mail-lists" class="page-section">
- <h2>Mailing Lists</h2>
- <ul class="page-list">
- <li>
- <a href="https://lists.apache.org/list.html?user@ignite.apache.org">user@ignite.apache.org</a> for general questions about Ignite
- (<a href="mailto:user-subscribe@ignite.apache.org?subject=Subscribe&body=Please%20subscribe%20me.">subscribe</a>,
- <a href="mailto:user-unsubscribe@ignite.apache.org?subject=Unsubscribe&body=Please%20unsubscribe%20me.">unsubscribe</a>,
- <a href="http://apache-ignite-users.70518.x6.nabble.com/">forum</a>,
- <a href="https://lists.apache.org/list.html?user@ignite.apache.org">archives</a>)
- </li>
- <li>
- <a href="https://lists.apache.org/list.html?dev@ignite.apache.org">dev@ignite.apache.org</a> for contributor discussions
- (<a href="mailto:dev-subscribe@ignite.apache.org?subject=Subscribe&body=Please%20subscribe%20me.">subscribe</a>,
- <a href="mailto:dev-unsubscribe@ignite.apache.org?subject=Unsubscribe&body=Please%20unsubscribe%20me.">unsubscribe</a>,
- <a href="http://apache-ignite-developers.2346864.n4.nabble.com/">nabble</a>,
- <a href="https://lists.apache.org/list.html?dev@ignite.apache.org">archives</a>)
- </li>
- <li>
- <a href="https://lists.apache.org/list.html?issues@ignite.apache.org">issues@ignite.apache.org</a> for JIRA notifications
- (<a href="mailto:issues-subscribe@ignite.apache.org?subject=Subscribe&body=Please%20subscribe%20me.">subscribe</a>,
- <a href="mailto:issues-unsubscribe@ignite.apache.org?subject=Unsubscribe&body=Please%20unsubscribe%20me.">unsubscribe</a>,
- <a href="http://apache-ignite-issues.70530.x6.nabble.com/">nabble</a>,
- <a href="https://lists.apache.org/list.html?issues@ignite.apache.org">archives</a>)
- </li>
- <li>
- <a href="https://lists.apache.org/list.html?notifications@ignite.apache.org">notifications@ignite.apache.org</a> for GitHub notifications
- (<a href="mailto:notifications-subscribe@ignite.apache.org?subject=Subscribe&body=Please%20subscribe%20me.">subscribe</a>,
- <a href="mailto:notifications-unsubscribe@ignite.apache.org?subject=Unsubscribe&body=Please%20unsubscribe%20me.">unsubscribe</a>,
- <a href="http://apache-ignite-commits.70531.x6.nabble.com/">nabble</a>,
- <a href="https://lists.apache.org/list.html?commits@ignite.apache.org">archives</a>)
- </li>
- <li>
- <a href="https://lists.apache.org/list.html?commits@ignite.apache.org">commits@ignite.apache.org</a> for GIT commits
- (<a href="mailto:commits-subscribe@ignite.apache.org?subject=Subscribe&body=Please%20subscribe%20me.">subscribe</a>,
- <a href="mailto:commits-unsubscribe@ignite.apache.org?subject=Unsubscribe&body=Please%20unsubscribe%20me.">unsubscribe</a>,
- <a href="http://apache-ignite-commits.70531.x6.nabble.com/">nabble</a>,
- <a href="https://lists.apache.org/list.html?commits@ignite.apache.org">archives</a>)
- </li>
- </ul>
- </section>
-
- <!--<section id="chatroom" class="page-section">-->
- <!--<h2>Chatroom</h2>-->
- <!--<p>-->
- <!--The official chatroom for Apache Ignite is hosted at Gitter: <a href="https://gitter.im/apacheignite/ignite">apacheignite/ignite</a>. Join us there!-->
- <!--<a id="gitter-badge" href="https://gitter.im/apacheignite/ignite">-->
- <!--<img src="https://badges.gitter.im/Join%20Chat.svg" alt="Join the chat at https://gitter.im/apacheignite/ignite" />-->
- <!--</a>-->
- <!--</p>-->
- <!--<p>-->
- <!--You will need a Github account.-->
- <!--</p>-->
- <!--</section>-->
-
- <section id="git" class="page-section">
- <h2>Git Repositories</h2>
- <ul class="page-list">
- <li>Ignite Git: <a href="https://gitbox.apache.org/repos/asf/ignite.git">https://gitbox.apache.org/repos/asf/ignite.git</a></li>
- <li>GitHub Mirror: <a href="https://github.com/apache/ignite">https://github.com/apache/ignite</a></li>
- </ul>
- </section>
-
- <section id="jira" class="page-section">
- <h2>Issue Tracking</h2>
- <p>
- Visit <a href="https://issues.apache.org/jira/browse/IGNITE" target="_blank" rel="noopener">Ignite Jira</a>
- if you would like to file a new issue or view existing issues. If you would like to
- assign an issue to yourself and start contributing, please send an email to the
- <a href="mailto:dev@ignite.apache.org">dev mailing list</a>, so you
- can be granted proper Jira permissions.
- </p>
- </section>
-
- <section id="wiki" class="page-section">
- <h2>Wiki</h2>
- <p>
- Visit <a href="https://cwiki.apache.org/confluence/display/IGNITE/" target="_blank" rel="noopener">Ignite Wiki</a>
- to learn about coding guidelines, release structure, and various design decisions behind Ignite features.
- </p>
- </section>
-
- <section id="people" class="page-section">
- <div class="col-sm-12 col-md-12 col-xs-12" style="padding:0 0 20px 0;">
- <!--<div class="col-sm-6 col-md-8 col-xs-12" style="padding-left:0; padding-right:20px;">-->
+ <!--#include virtual="/includes/header.html" -->
+ <article>
+ <header>
+ <div class="container">
+ <h1 >Community <strong>Resources</strong></h1>
+ </div>
+ </header>
+ <div class="container">
+ <p>
+ There are many ways you can get help from Apache Ignite community. The <a href="#mail-lists">mailing lists</a> are the easiest way to get answers or to get involved with the project. Specifically, if you have any questions on how to use Ignite, you should subscribe to the user mailing list:
+ </p>
+ <ul class="page-list">
+ <li>
+ <a href="http://apache-ignite-users.70518.x6.nabble.com/">user@ignite.apache.org</a>
+ (<a href="mailto:user-subscribe@ignite.apache.org?subject=Subscribe&body=Please%20subscribe%20me.">subscribe</a>,
+ <a href="mailto:user-unsubscribe@ignite.apache.org?subject=Unsubscribe&body=Please%20unsubscribe%20me.">unsubscribe</a>,
+ <a href="http://apache-ignite-users.70518.x6.nabble.com/">forum</a>,
+ <a href="http://mail-archives.apache.org/mod_mbox/ignite-user/">archives</a>)
+ </li>
+ </ul>
+
+
+
+ <section id="stackoverflow" class="page-section">
+ <h2>Stack Overflow</h2>
+ <p>
+ Many Ignite community members watch <a href="http://stackoverflow.com/questions/tagged/ignite">Stack Overflow</a> for the tag <b>"ignite"</b> or <b>"apacheignite"</b>, so you can post your questions there as well.
+ </p>
+ </section>
+
+
+ <section id="mail-lists" class="page-section">
+ <h2>Mailing Lists</h2>
+ <ul class="page-list">
+ <li>
+ <a href="https://lists.apache.org/list.html?user@ignite.apache.org">user@ignite.apache.org</a> for general questions about Ignite
+ <a href="mailto:user-subscribe@ignite.apache.org?subject=Subscribe&body=Please%20subscribe%20me.">subscribe</a>,
+ <a href="mailto:user-unsubscribe@ignite.apache.org?subject=Unsubscribe&body=Please%20unsubscribe%20me.">unsubscribe</a>,
+ <a href="http://apache-ignite-users.70518.x6.nabble.com/">forum</a>,
+ <a href="https://lists.apache.org/list.html?user@ignite.apache.org">archives</a>)
+ </li>
+ <li>
+ <a href="https://lists.apache.org/list.html?dev@ignite.apache.org">dev@ignite.apache.org</a> for contributor discussions
+ (<a href="mailto:dev-subscribe@ignite.apache.org?subject=Subscribe&body=Please%20subscribe%20me.">subscribe</a>,
+ <a href="mailto:dev-unsubscribe@ignite.apache.org?subject=Unsubscribe&body=Please%20unsubscribe%20me.">unsubscribe</a>,
+ <a href="http://apache-ignite-developers.2346864.n4.nabble.com/">nabble</a>,
+ <a href="https://lists.apache.org/list.html?dev@ignite.apache.org">archives</a>)
+ </li>
+ <li>
+ <a href="https://lists.apache.org/list.html?issues@ignite.apache.org">issues@ignite.apache.org</a> for JIRA notifications
+ (<a href="mailto:issues-subscribe@ignite.apache.org?subject=Subscribe&body=Please%20subscribe%20me.">subscribe</a>,
+ <a href="mailto:issues-unsubscribe@ignite.apache.org?subject=Unsubscribe&body=Please%20unsubscribe%20me.">unsubscribe</a>,
+ <a href="http://apache-ignite-issues.70530.x6.nabble.com/">nabble</a>,
+ <a href="https://lists.apache.org/list.html?issues@ignite.apache.org">archives</a>)
+ </li>
+ <li>
+ <a href="https://lists.apache.org/list.html?notifications@ignite.apache.org">notifications@ignite.apache.org</a> for GitHub notifications
+ (<a href="mailto:notifications-subscribe@ignite.apache.org?subject=Subscribe&body=Please%20subscribe%20me.">subscribe</a>,
+ <a href="mailto:notifications-unsubscribe@ignite.apache.org?subject=Unsubscribe&body=Please%20unsubscribe%20me.">unsubscribe</a>,
+ <a href="http://apache-ignite-commits.70531.x6.nabble.com/">nabble</a>,
+ <a href="https://lists.apache.org/list.html?commits@ignite.apache.org">archives</a>)
+ </li>
+ <li>
+ <a href="https://lists.apache.org/list.html?commits@ignite.apache.org">commits@ignite.apache.org</a> for GIT commits
+ (<a href="mailto:commits-subscribe@ignite.apache.org?subject=Subscribe&body=Please%20subscribe%20me.">subscribe</a>,
+ <a href="mailto:commits-unsubscribe@ignite.apache.org?subject=Unsubscribe&body=Please%20unsubscribe%20me.">unsubscribe</a>,
+ <a href="http://apache-ignite-commits.70531.x6.nabble.com/">nabble</a>,
+ <a href="https://lists.apache.org/list.html?commits@ignite.apache.org">archives</a>)
+ </li>
+ </ul>
+ </section>
+
+ <section id="git" class="page-section">
+ <h2>Git Repositories</h2>
+ <ul class="page-list">
+ <li>Ignite Git: <a href="https://gitbox.apache.org/repos/asf/ignite.git">https://gitbox.apache.org/repos/asf/ignite.git</a></li>
+ <li>GitHub Mirror: <a href="https://github.com/apache/ignite">https://github.com/apache/ignite</a></li>
+ </ul>
+ </section>
+
+ <section id="jira" class="page-section">
+ <h2>Issue Tracking</h2>
+ <p>
+ Visit <a href="https://issues.apache.org/jira/browse/IGNITE" target="_blank" rel="noopener">Ignite Jira</a>
+ if you would like to file a new issue or view existing issues. If you would like to
+ assign an issue to yourself and start contributing, please send an email to the
+ <a href="mailto:dev@ignite.apache.org">dev mailing list</a>, so you
+ can be granted proper Jira permissions.
+ </p>
+ </section>
+
+
+ <section id="wiki" class="page-section">
+ <h2>Wiki</h2>
+ <p> Visit <a href="https://cwiki.apache.org/confluence/display/IGNITE/" target="_blank" rel="noopener">Ignite Wiki</a> to learn about coding guidelines, release structure, and various design decisions behind Ignite features.</p>
+ </section>
+
+
+ <section id="people" class="page-section">
<h2>Contributers and Committers</h2>
<p>
Visit the <a href="https://github.com/apache/ignite/graphs/contributors">Apache Ignite Contributors page</a>
@@ -167,7 +152,7 @@ under the License.
<p>
The table below summarizes <a href="http://people.apache.org/phonebook.html?pmc=ignite" >committers and PMC members</a> of Apache Ignite:
</p>
- <table class="formatted committers" name="Apache Ignite Community Committers">
+ <table class="table table-bordered table-striped" name="Apache Ignite Community Committers">
<thead>
<tr><th>Name</th><th>Organization</th></tr>
</thead>
@@ -228,11 +213,12 @@ under the License.
* - PMC member<br/>
** - PMC chair
</p>
- </div>
- </section>
- </main>
+ </section>
+
+ </div>
+</article>
<!--#include virtual="/includes/footer.html" -->
-</div>
+
<!--#include virtual="/includes/scripts.html" -->
</body>
</html>