This is an automated email from the ASF dual-hosted git repository.
zregvart pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel-website.git
The following commit(s) were added to refs/heads/master by this push:
new ef2a011 [CAMEL-12998] Add some community pages
ef2a011 is described below
commit ef2a01138e6fb626f579bb5d08c381a23a74ca6d
Author: Francois Papon <[email protected]>
AuthorDate: Sun Feb 17 10:25:27 2019 +0400
[CAMEL-12998] Add some community pages
---
config.toml | 2 +-
content/community/contributing.md | 1 -
content/community/irc-room.md | 21 +++++
content/community/mailing-list.md | 30 +++++++
content/community/sources.md | 35 ++++++++
content/community/support.md | 70 +++++++++++++++-
content/community/team.md | 168 +++++++++++++++++++++++++++++++++++++-
layouts/community/single.html | 6 +-
layouts/index.html | 16 ++--
9 files changed, 334 insertions(+), 15 deletions(-)
diff --git a/config.toml b/config.toml
index 5dfce93..995fc04 100644
--- a/config.toml
+++ b/config.toml
@@ -77,7 +77,7 @@ relativeURLs = true
parent = "community"
weight = 2
identifier = "community-contributing"
- url = "/community/contributing/"
+ url = "https://github.com/apache/camel/blob/master/CONTRIBUTING.md";
[[menu.main]]
name = "User stories"
diff --git a/content/community/contributing.md
b/content/community/contributing.md
deleted file mode 100644
index 919bf34..0000000
--- a/content/community/contributing.md
+++ /dev/null
@@ -1 +0,0 @@
-contributing!
diff --git a/content/community/irc-room.md b/content/community/irc-room.md
new file mode 100644
index 0000000..9009c60
--- /dev/null
+++ b/content/community/irc-room.md
@@ -0,0 +1,21 @@
+---
+title: "Support"
+---
+
+## IRC
+
+You can hang out on IRC in the #apache-camel room at freenode with other
Apache Camel developers and users.
+
+### Using an IRC client
+
+Here are the connection details.
+
+{{< bootstrap-table "table table-hover text-left" >}}
+| server | port | room |
+|---------|------|------|
+| irc.freenode.net | 6667 | #apache-camel
+{{< /bootstrap-table >}}
+
+### Gitter Room
+
+Apache Camel is also on Gitter in the
[apache/apache-camel](https://gitter.im/apache/apache-camel) room which you can
access from a web browser.
diff --git a/content/community/mailing-list.md
b/content/community/mailing-list.md
new file mode 100644
index 0000000..b6a9f09
--- /dev/null
+++ b/content/community/mailing-list.md
@@ -0,0 +1,30 @@
+---
+title: "Support"
+---
+
+## Mailing Lists
+
+*Use Camel User List*
+
+You should post and subscriber to the Camel User List for all your questions
on using Camel, or how to do X with Camel etc. If in doubt use this list.
+The other list Camel Developer List, is for the Camel team to discus
development of the actual Camel project; do not use this list for question on
using Camel.
+Again to re-iterate, use the Camel User List, for you Camel questions. This is
the correct mailing list, and have the most people there ready for helping you.
+
+*Post plain text mails*
+
+When posting to the mailing lists, use plain text mails. Do not use HTML
mails. HTML mails is more likely to be targeted as spam mails and will be
rejected; as well it's not easily readable by others.
+
+{{< bootstrap-table "table table-hover text-left" >}}
+| List Name | Address | Subscribe | Unsubscribe | Archive | Nabble (Online
Forums) | Comment |
+|------------|---------|-----------|-------------|---------|------------------------|---------|
+| Camel User List | [email protected] |
[subscribe]([email protected]) | [unsubscribe]([email protected]) |
[Archives](http://mail-archives.apache.org/mod_mbox/camel-users/) |
[Nabble](http://camel.465427.n5.nabble.com/Camel-Users-f465428.html) | Use this
list for your Camel questions. |
+| Camel Developer List | [email protected] |
[subscribe]([email protected]) | [unsubscribe]([email protected]) |
[Archives](http://mail-archives.apache.org/mod_mbox/camel-dev/) |
[Nabble](http://camel.465427.n5.nabble.com/Camel-Development-f479097.html) | |
+| Camel Commits List | [email protected] |
[subscribe]([email protected]) | [unsubscribe]([email protected])
| [Archives](http://mail-archives.apache.org/mod_mbox/camel-commits/) |
[Nabble](http://camel.465427.n5.nabble.com/Camel-Commits-f498405.html) | |
+| Camel Issues List | [email protected] |
[subscribe]([email protected]) | [unsubscribe]([email protected]) |
[Archives](http://mail-archives.apache.org/mod_mbox/camel-issues/) | | |
+{{< /bootstrap-table >}}
+
+There were various discussions before these mailing lists were setup on the
ActiveMQ Mailing Lists such as these
[threads](http://www.nabble.com/forum/Search.jtp?forum=2354&local=y&query=%5Bcamel%5D)
+
+## Discussion Forums
+
+If you prefer you could use our Discussion Forums which are sync'd with the
above mailing lists.
diff --git a/content/community/sources.md b/content/community/sources.md
new file mode 100644
index 0000000..36b8183
--- /dev/null
+++ b/content/community/sources.md
@@ -0,0 +1,35 @@
+---
+title: "Sources"
+---
+
+## Web Browsing of git
+
+To browse via the web:
+
+```
+https://gitbox.apache.org/repos/asf/camel.git
+```
+
+## Web Browing Using FishEye
+
+A hearty thanks to Atlassian for providing FishEye hosting for Camel. Below is
the URL to browse the Subversion repo via FishEye:
+
+```
+https://fisheye6.atlassian.com/browse/camel-git
+```
+
+## Checking out from git
+
+```
+git clone https://gitbox.apache.org/repos/asf/camel.git
+```
+
+Only project developers can commit to the git via this method. SSH must be
installed on your client machine. Enter your site password when prompted.
+
+## Using github
+
+The source code is mirrored to github, so you can also checkout the source
code from github, if you are familiar with using github. By using github you
can submit pull requests to the project using the standard github way.
+
+```
+https://github.com/apache/camel/
+```
diff --git a/content/community/support.md b/content/community/support.md
index 0ee8a07..b8776a7 100644
--- a/content/community/support.md
+++ b/content/community/support.md
@@ -1 +1,69 @@
-support!
+---
+title: "Support"
+---
+
+## Getting help
+
+If you are experiencing problems using Camel then please report your problem
to our mailing list. This allows the entire community to help with your
problem.
+If indeed a bug has been identified in the Camel software, then document the
problem in our [Issue Tracker](https://issues.apache.org/jira/browse/CAMEL).
+Please refrain from immediately opening a ticket in the issue tracker unless
you are certain it's a problem in the Camel software.
+
+If you are in doubt, we appreciate asking the [mailing
list](/community/mailing-list), [IRC chat](/community/irc-room), or
[Gitter](https://gitter.im/apache/apache-camel) chat first.
+
+Please read the section below (How to get help), and follow the bullets
advised there first:
+
+* [Issue tracker](https://issues.apache.org/jira/browse/CAMEL)
+* [FAQ](community/faq)
+
+### Reporting bugs - Please read this first
+
+We prefer people to get in touch first using the mailing list, IRC chat or
Gitter chat. Or take time to read FAQs, or search in the mailing list archives
to find answers.
+Unfortunately some people create a JIRA ticket as first thing. Please don't do
that! Only if you are sure it really is a bug etc. JIRA tickets create noise
+for the Camel team to react on issues that are not bugs. But already covered
in FAQs, in the mailing lists etc. Or in the existing documentation.
+Also on the mailing lists there is more people active to help you better.
+
+### Alternative discussion forums
+
+There's a number of sites outside Apache that offer discussion forums on
Camel. For example, [Stack Overflow](http://stackoverflow.com/) is a popular Q
& A site with a dedicated [Apache Camel
forum](http://stackoverflow.com/questions/tagged/apache-camel).
+You are also likely to find helpful discussions on technical blogs, on
[Google](https://www.google.com/search?q=apache+camel), or even on
[Twitter](https://twitter.com/#!/search/apache%20camel).
+
+### Using deprecated components
+
+Deprecated components are not supported and issues such as bugs may not be
fixed. We encourage users to migrate away from using any deprecated component.
+A list of deprecated components is listed on the github page at:
https://github.com/apache/camel/tree/master/components#components
+
+### How to get help
+
+Before you report a problem, you may wish to read the [FAQ](community/faq).
+When you report an issue, please be sure to include as much information as
possible. The more we know, the easier it is to reach an effective solution
quickly.
+
+*What version do you use*
+
+What version of Camel do you use! Remember to include this information.
+
+* what are the version numbers of involved software components? (this is very
important to detail)
+* what platform and JDK?
+* any particular container being used? and if so, what version?
+* stack traces generally really help! (Remember to post which version of
Camel you use, this is important to know when posting stacktraces) If in doubt,
include the whole thing; often exceptions get wrapped in other exceptions and
the exception right near the bottom explains the actual error, not the first
few lines at the top. It's very easy for us to skim-read past unnecessary parts
of a stack trace.
+* log output can be useful too; sometimes enabling DEBUG logging can help
+* your code & configuration files are often useful
+* did it work before? what have you changed to break it?
+* try upgrading to the latest release and see if it's fixed there
+* try the latest SNAPSHOT to see if it's fixed in the pre-release
+* search the user forum to see if has been discussed before
+* see the "known issues" section in the release notes
+* and check the issue tracker to see if the issue has already been reported
+* do not send private emails to Camel Team members to ask them to help you
faster, or in the private only. Help on Apache Camel is volunteer based and
must happen in the open on the public Mailing Lists. If you want to get help
faster or in private, then see further below.
+
+### How to get help faster
+
+We can help you much quicker if you try the following
+
+* provide us with a JUnit test case that demonstrates your issue. e.g. if you
think you've found a bug, can you create a test case to demonstrate the bug?
+* [submit a patch](/community/contributing) fixing the bug! (We also buy you
beer when we meet you if you submit bug fixes (smile) )
+* for memory leak or performance related issues, if you can run a profiler on
your test case and attach the output as a file (or zipped file if it's huge) to
the JIRA we can normally fix things much faster. e.g. you could run jmap/jhat,
JProfiler or YourKit on your code and send us the output. To find memory leaks
it's quicker to resolve if you can tell us what classes are taking up all of
the RAM; we can normally figure out what's wrong from that.
+
+## Commercial Support
+
+This is an open source project, so the amount of time we have available to
help resolve your issue is often limited as all help is provided on a volunteer
basis.
+If you want to get priority help, need to get up to speed quickly, require
some training or mentoring, or need full 24 x 7 production support you could
contact one of the following companies with [Commercial Camel
Offerings](/community/commercial-camel-offerings).
diff --git a/content/community/team.md b/content/community/team.md
index 0779112..2191219 100644
--- a/content/community/team.md
+++ b/content/community/team.md
@@ -1 +1,167 @@
-team!
+---
+title: "Team"
+---
+
+This page lists who we are. By all means add yourself to the list - lets sort
it in alphabetical order
+
+## Committers
+
+When posting to the mailing lists, use plain text mails. Do not use HTML
mails. HTML mails is more likely to be targeted as spam mails and will be
rejected; as well it's not easily readable by others.
+
+{{< bootstrap-table "table table-hover text-left" >}}
+| Name | ID | Organisation |
+|-------|----|--------------|
+| Aaron Mulder | ammulder | Chariot Solutions |
+| Akitoshi Yoshida | ay | SAP |
+| Andrea Cosentino | acosentino | Red Hat |
+| Antonin Stefanutti | astefanutti | Red Hat |
+| Babak Vahdat | bvahdat | Cyberlogic Consulting GmbH |
+| Ben O'Day | boday | Initek Consulting |
+| Bilgin Ibryam | bibryam | Red Hat |
+| Bruce Snyder | bsnyder | |
+| Charles Moulliard | cmoulliard | Red Hat
+| Christian Mueller | cmueller | Amazon Web Services |
+| Christian Posta | ceposta | Red Hat |
+| Christian Schneider | cschneider
+| Claus Ibsen | davsclaus | Red Hat |
+| Colm O hEigeartaigh | coheigea | Talend |
+| David Jencks | djencks | IBM |
+| Daniel Kulp | dkulp | Talend |
+| Franz Forsthofer | forsthofer | SAP |
+| Freeman Fang | ffang | Red Hat |
+| Gary Tully | gtully | Red Hat |
+| Gert Vanthienen | gertv | |
+| Gregor Zurowski | gzurowski | Sotheby's |
+| Guillaume Nodet | gnodet | Red Hat |
+| Hadrian Zbarcea | hadrian | |
+| Henryk Konsek | hekonsek | Red Hat |
+| Hiram Chirino | chirino | Red Hat |
+| Ioannis Canellos | iocanel | Red Hat |
+| Jacek Laskowski | jlaskowski | |
+| James Carman | jcarman | Savoir Technologies |
+| Jean-Baptiste Onofré | jbonofre | Talend |
+| Jeff Genender | jgenender | Savoir Technologies |
+| Johan Edstrom | joed | Savoir Technologies |
+| John Poth | | Red Hat |
+| Jonathan Anstey | janstey | Red Hat |
+| James Netherton | Red Hat | |
+| James Strachan | jstrachan | |
+| Luca Burgazzoli | lburgazzoli | Red Hat |
+| Martin Krasser | krasserm | |
+| Nicky Sandhu | nsandhu | |
+| Onder Sezgin | onders | |
+| Quinn Stevenson | quinn | |
+| Raul Kripalani | raulk | |
+| Rich Newcomb | rnewcomb | |
+| Richard Kettelerij | rickette | Avisi BV |
+| Rob Davies | rajdavies | |
+| Roman Kalukiewicz | romkal | |
+| Scott England-Sullivan | sully6768 | Red Hat |
+| Stan Lewis | slewis | Red Hat |
+| Tomohisa Igarashi | igarashitm | Red Hat |
+| Tracy Snell | tjsnell | Juice Labs |
+| Willem Jiang | ningjiang | Huawei |
+| William Tam | wtam | Progress Software |
+| Zoran Regvart | zregvart | Red Hat |
+{{< /bootstrap-table >}}
+
+## Contributors
+
+Adding your name to the list below.
+
+If you have been contributing to the Apache Camel project, and you want your
name added to the list below. Then you can get in touch with the Camel team
from the [Mailing Lists](community/mailing-list) and ask to be added.
+
+{{< bootstrap-table "table table-hover text-left" >}}
+| Name | Organisation |
+|-------|--------------|
+| Aaron Crickenberger | |
+| Al Maw | |
+| Aleksi Kallio | |
+| Andrew Deason | |
+| Andy Depue | |
+| Axel Hohaus | |
+| Arjan Moraal | |
+| Arno Noordover | het CAK |
+| Barry Kaplan | |
+| Brett Meyer| 3RiverDev, Savoir Technologies |
+| Brian Diesenhaus | |
+| Brian Guan | |
+| Brian Madigan | |
+| Bruno Barin | |
+| Bruno Borges | |
+| Bryan Schmidt | |
+| Chris Kingsbury | TradingScreen |
+| Christoph Emmersberger | |
+| Christopher G. Stach II | |
+| Charles Anthony | |
+| Christian Posta | Red Hat |
+| Claus Straube | |
+| Dan Checkoway | |
+| Dennis Byrne | Thoughtworks |
+| Erik Onnen | |
+| Fabrizio Spataro | Bizmate |
+| Fernando Ribeiro | |
+| Gert Vanthienen | |
+| Glen Klyuzner | Tullib |
+| Hakan Guleryuz | ASPone |
+| James Chamberlain | |
+| James Zhang | |
+| Jamie McCrindle | |
+| Jason Anderson | |
+| Jason Carreira | |
+| Jason Sherman | |
+| Jérôme Delagnes | |
+| Jeff Sparkes | |
+| Jeff Lansing | SYS Technologies |
+| Joe Fernandez | TTM |
+| John Heitmann | |
+| Jonathan Cook | BBC |
+| Juraj Tomasov | |
+| Kevin Ross | |
+| Kranti Parisa | |
+| Leo Pechersky | |
+| Li Ma | |
+| Lars Heinemann | Red Hat |
+| Lauri Lehmijoki | |
+| Lauri Kimmel | |
+| Marco Buss | product + concept |
+| Marco Luebcke | |
+| Mark Bucayan | |
+| Mark Timmings | |
+| Mario Siegenthaler | |
+| Mathieu Lalonde | |
+| Mats Henricson | |
+| Matt Hoffman | |
+| Matthew Vincent | |
+| Mathew Kuppe | 360 Treasury Systems |
+| Mike Perham | |
+| Mitko Kolev | InterComponentWare AG |
+| Neil Clayton | Royal Bank of Scotland |
+| Neil Thorne | |
+| Nick Reid | Evolution | |
+| Niklas Gustavsson | |
+| Ning Li | |
+| Noah Nordrum | |
+| Oliver Belikan | |
+| Ozgur Cetinturk | |
+| Paul Smith | |
+| Paul Wai | |
+| Pawel Tucholski | |
+| Peter Henning | |
+| Przemyslaw Budzik | |
+| Radek Sedmak | |
+| Reuben Garrett | |
+| Robert Liguori | Solentus |
+| Robin Roos | Dresdner Kleinwort Wasserstein |
+| Ross Mason | |
+| Sachin Handiekar | |
+| Sami Dalouche | |
+| Sanjiv Jivan | |
+| Steven Marcus | |
+| Taariq Levack | |
+| Taylor Gautier | |
+| Thomas Heller | |
+| Trevor Pounds | |
+| Viral Gohel | Red Hat |
+| Xueqiang Mi | |
+{{< /bootstrap-table >}}
diff --git a/layouts/community/single.html b/layouts/community/single.html
index ef3a636..485bf39 100644
--- a/layouts/community/single.html
+++ b/layouts/community/single.html
@@ -1,9 +1,9 @@
{{ partial "header.html" . }}
<div class="container pb-5">
- <div class="row">
- {{ .Content }}
- </div>
+ <h1>{{ .Title }}</h1>
+
+ {{ .Content }}
</div>
{{ partial "footer.html" . }}
diff --git a/layouts/index.html b/layouts/index.html
index ff27209..7d4a9bc 100644
--- a/layouts/index.html
+++ b/layouts/index.html
@@ -5,7 +5,7 @@
<div class="col-md-6">
<h1 class="title">Integration that you want!</h1>
<h2 class="subtitle text-muted mb-5">Camel empowers you to define
routing and mediation rules in a variety of domain-specific languages.</h2>
- <p class="mt-5"><a href="#" class="primary-btn">Get started</a>
+ <p class="mt-5"><a href="/docs/getting-started"
class="primary-btn">Get started</a>
</p>
</div>
<div class="col-md-6 pt-5">
@@ -85,13 +85,13 @@
<h3>Camel K</h3>
<p class="text-muted lead">Apache Camel K is a lightweight integration
framework built from Apache Camel that runs
natively on Kubernetes and is specifically designed for serverless
and microservice architectures.</p>
- <p class="pt-5 pb-5"><a href="#" class="primary-btn">Get
started</a></p>
+ <p class="pt-5 pb-5"><a href="/docs/getting-started"
class="primary-btn">Get started</a></p>
</div>
</section>
<section>
- <div class="container">
+ <div class="container pb-3">
<div class="row">
<div class="col-md-7">
<h3>Apache & OpenSource</h3>
@@ -100,12 +100,12 @@
<p class="text-muted">
Camel is an <a href="https://www.apache.org";>Apache
Software Foundation</a> project, available under the Apache v2 license.<br/>
It's a complete open community, always listening proposals
and comments.<br/>
- <a href="community.html">Sources</a>, <a
href="community.html">mailing lists</a>, <a href="community.html">issue
tracker</a>: it's fully open, you can access directly.<br/>
- We also love contributions : don't hesitate to <a
href="community.html">contribute</a>.
+ <a href="/community/sources">Sources</a>, <a
href="/community/mailing-list">mailing lists</a>, <a
href="/community/support">issue tracker</a>: it's fully open, you can access
directly.<br/>
+ We also love contributions : don't hesitate to <a
href="https://github.com/apache/camel/blob/master/CONTRIBUTING.md";>contribute</a>.
</p>
<p>
- <a href="community.html">Be Involved In The Community</a> |
- <a href="community.html">How To Contribute</a>
+ <a
href="https://github.com/apache/camel/blob/master/CONTRIBUTING.md";>Be Involved
In The Community</a> |
+ <a
href="https://github.com/apache/camel/blob/master/CONTRIBUTING.md";>How To
Contribute</a>
</p>
</div>
<div class="col-md-5 logo pt-5">
@@ -116,7 +116,7 @@
</section>
<section class="bg-orange">
- <div class="container text-white text-center">
+ <div class="container pt-3 text-white text-center">
<h1 class="title">Latest news</h1>
</div>
<div class="container pt-5 pb-5">
