Author: paulmerlin
Date: Sun Jun 14 20:22:57 2015
New Revision: 1685460
URL: http://svn.apache.org/r1685460
Log:
zest: update codebase page
Modified:
zest/site/content/atom.xml
zest/site/content/community/codebase.html
zest/site/src/community/codebase.html
Modified: zest/site/content/atom.xml
URL:
http://svn.apache.org/viewvc/zest/site/content/atom.xml?rev=1685460&r1=1685459&r2=1685460&view=diff
==============================================================================
--- zest/site/content/atom.xml (original)
+++ zest/site/content/atom.xml Sun Jun 14 20:22:57 2015
@@ -4,7 +4,7 @@
<title></title>
<link href="http://zest.apache.org/atom.xml"; rel="self"/>
<link href="http://zest.apache.org"/>
- <updated>2015-06-14T21:36:16+02:00</updated>
+ <updated>2015-06-14T22:22:29+02:00</updated>
<id>http://zest.apache.org</id>
<author>
<name></name>
Modified: zest/site/content/community/codebase.html
URL:
http://svn.apache.org/viewvc/zest/site/content/community/codebase.html?rev=1685460&r1=1685459&r2=1685460&view=diff
==============================================================================
--- zest/site/content/community/codebase.html (original)
+++ zest/site/content/community/codebase.html Sun Jun 14 20:22:57 2015
@@ -106,17 +106,22 @@
<div class="span8">
<div class="row-fluid">
<div class="span6">
- <script type="text/javascript"
src="http://www.ohloh.net/p/13150/widgets/project_basic_stats.js";></script>
+ <script type="text/javascript"
src="//www.ohloh.net/p/13150/widgets/project_basic_stats.js"></script>
</div>
<div class="span6">
- <script type="text/javascript"
src="http://www.ohloh.net/p/13150/widgets/project_factoids.js";></script>
+ <script type="text/javascript"
src="//www.ohloh.net/p/13150/widgets/project_factoids.js"></script>
</div>
</div>
<p>
- After the first 3 years of depending on the OPS4J project, the
Qi4j community finally moved to GitHub on
- the 1 November 2010. This should simplify the learning, as not
only does developers have plenty of
- experience with GitHub external link and the tools it provides,
but also there are endless amount of
- documentation and user forums to support each individual,
off-loading some of that burden from us.
+ After the first 3 years of depending on the
+ <a href="http://team.ops4j.org"; title="Open Participation for
Java">OPS4J</a> project, then 5 years on
+ <a href="https://github.com/qi4j";>Github</a>, the Qi4j community
finally moved to the
+ <a href="https://www.apache.org/";>Apache Software Foundation</a>
(ASF) on March 2015.
+ The codebase history is kept in <a
href="https://git-scm.com/";>Git</a> repositories, mirrored to the
+ <a href="https://github.com/apache?query=zest";>ASF Github
organization</a>.
+ This should simplify the learning, as not only does developers
have plenty of experience with Git, and
+ tools around it, but also there are endless amount of
documentation and user forums to support each
+ individual, off-loading some of that burden from us.
This page only contain rudimentary information.
</p>
<h2>Public Access Repository</h2>
@@ -137,30 +142,30 @@
</ul>
<p>
Qi4j used to have many repositories to accommodate for the
authorization issue above, but eventually
- settled with a single GitHub repository, and now only have 2
repositories;
+ settled with a single Git repository, and now only have 2
repositories;
</p>
<ul>
- <li><code>qi4j-sdk</code></li>
- <li><code>qi4j-sandbox</code></li>
+ <li><code>zest-qi4j</code></li>
+ <li><code>zest-sandbox</code></li>
</ul>
<p>
The sandbox is where experimental code goes, and modules that are
not ready to be shipped, or can not be
shipped due to licensing restrictions (e.g. Oracle doesn't provide
Coherence as automatic download for our
- testing, so can't really ship the coherence extension). The
sandbox is a normal GitHub repository available
- to clone as; <code>git clone
git://github.com/Qi4j/qi4j-sandbox.git</code>
+ testing, so can't really ship the coherence extension). The
sandbox is a normal Git repository available
+ to clone as; <code>git clone
https://git-wip-us.apache.org/repos/asf/zest-sandbox.git</code>
</p>
<p>
The Qi4j SDK is the main development codebase, and to start
working with it you simply clone it;
- <code>git clone git://github.com/Qi4j/qi4j-sdk.git</code>
+ <code>git clone
https://git-wip-us.apache.org/repos/asf/zest-qi4j.git</code>
</p>
<h2>Web Access</h2>
<p>
- The two repositories can be browsed here;
+ The two repositories can be browsed on the mirrors on the ASF
Github organization;
</p>
<ul>
- <li><a
href="http://github.com/Qi4j/qi4j-sdk";>http://github.com/Qi4j/qi4j-sdk</a></li>
- <li><a
href="http://github.com/Qi4j/qi4j-sandbox";>http://github.com/Qi4j/qi4j-sandbox</a></li>
+ <li><a
href="https://github.com/apache/zest-qi4j";>https://github.com/apache/zest-qi4j</a></li>
+ <li><a
href="https://github.com/apache/zest-sandbox";>https://github.com/apache/zest-sandbox</a></li>
</ul>
<h2>Committer Access</h2>
@@ -214,9 +219,9 @@
<h3>How to Join?</h3>
<p>
- To become a Community Developer, just subscribe to the qi4j-dev at
Google Group and request it together
- with your GitHub user id. For Community Developer, the bar is
really, really low and nothing more than a
- desire to help is required.
+ To become a Community Developer, just subscribe to the
+ <a
href="mailto:[email protected]";>[email protected]</a> mailing
list and participate,
+ nothing more than a desire to help is required.
</p>
<p>
Community Developers who are active and keep contributing
feedback, patches and/or documentation are likely
@@ -225,32 +230,24 @@
time.
</p>
- <h3>How to get Access to the writable central repositories?</h3>
- <p>
- Once you have commit access to a repository, you will access it
differently. This is the clone command
- needed, and after that you will need to do the same as above for
pubic access;
- </p>
- <pre><code>git clone [email protected]:Qi4j/qi4j-sdk.git
-cd qi4j-sdk</code></pre>
-
<h2>Commit Policy</h2>
<p class="lead">
Qi4j generally uses a Commit-Then-Review policy on most changes.
This allows a reasonable high velocity of
development.
</p>
<p>
- Commits are visible at GitHub and active contributors should
review all incoming commits to ensure quality
- of contributions and avoidance of mistakes.
+ Commits are visible in Git history and at GitHub. Active
contributors should review all incoming commits to
+ ensure quality of contributions and avoidance of mistakes.
</p>
<p>
- For any given commit, any member of the community may raise
concern(s) on the qi4j-dev forum at Google
- Groups. We encourage as many people as possible to review the
changes that are occurring. "With enough
+ For any given commit, any member of the community may raise
concern(s) on the <code>dev@</code> mailing
+ list. We encourage as many people as possible to review the
changes that are occurring. "With enough
eyeballs every bug is shallow." wrote Eric S. Raymond in "The
Cathedral and The Bazaar" about open source.
</p>
<p>
Special rules applies to changes in the Core Test suite. Adding
new tests are CTR, but modifying existing
tests, either to accommodate for code changes in Core or to
tighten the constraints of them, MUST be
- discussed on the qi4j-dev forum at Google Groups, prior to
committing them to the 'develop' branch. We
+ discussed on the <code>dev@</code> mailing list, prior to
committing them to the 'develop' branch. We
recommend that a different branch is used for these changes,
unless simply codesnippets are pasted to mail.
This exists to ensure that we have a stable evolution of Qi4j
Runtime, and no surprises will occur in
existing applications with new versions.
Modified: zest/site/src/community/codebase.html
URL:
http://svn.apache.org/viewvc/zest/site/src/community/codebase.html?rev=1685460&r1=1685459&r2=1685460&view=diff
==============================================================================
--- zest/site/src/community/codebase.html (original)
+++ zest/site/src/community/codebase.html Sun Jun 14 20:22:57 2015
@@ -11,17 +11,22 @@ layout: default
<div class="span8">
<div class="row-fluid">
<div class="span6">
- <script type="text/javascript"
src="http://www.ohloh.net/p/13150/widgets/project_basic_stats.js";></script>
+ <script type="text/javascript"
src="//www.ohloh.net/p/13150/widgets/project_basic_stats.js"></script>
</div>
<div class="span6">
- <script type="text/javascript"
src="http://www.ohloh.net/p/13150/widgets/project_factoids.js";></script>
+ <script type="text/javascript"
src="//www.ohloh.net/p/13150/widgets/project_factoids.js"></script>
</div>
</div>
<p>
- After the first 3 years of depending on the OPS4J project, the
Qi4j community finally moved to GitHub on
- the 1 November 2010. This should simplify the learning, as not
only does developers have plenty of
- experience with GitHub external link and the tools it provides,
but also there are endless amount of
- documentation and user forums to support each individual,
off-loading some of that burden from us.
+ After the first 3 years of depending on the
+ <a href="http://team.ops4j.org"; title="Open Participation for
Java">OPS4J</a> project, then 5 years on
+ <a href="https://github.com/qi4j";>Github</a>, the Qi4j community
finally moved to the
+ <a href="https://www.apache.org/";>Apache Software Foundation</a>
(ASF) on March 2015.
+ The codebase history is kept in <a
href="https://git-scm.com/";>Git</a> repositories, mirrored to the
+ <a href="https://github.com/apache?query=zest";>ASF Github
organization</a>.
+ This should simplify the learning, as not only does developers
have plenty of experience with Git, and
+ tools around it, but also there are endless amount of
documentation and user forums to support each
+ individual, off-loading some of that burden from us.
This page only contain rudimentary information.
</p>
<h2>Public Access Repository</h2>
@@ -42,30 +47,30 @@ layout: default
</ul>
<p>
Qi4j used to have many repositories to accommodate for the
authorization issue above, but eventually
- settled with a single GitHub repository, and now only have 2
repositories;
+ settled with a single Git repository, and now only have 2
repositories;
</p>
<ul>
- <li><code>qi4j-sdk</code></li>
- <li><code>qi4j-sandbox</code></li>
+ <li><code>zest-qi4j</code></li>
+ <li><code>zest-sandbox</code></li>
</ul>
<p>
The sandbox is where experimental code goes, and modules that are
not ready to be shipped, or can not be
shipped due to licensing restrictions (e.g. Oracle doesn't provide
Coherence as automatic download for our
- testing, so can't really ship the coherence extension). The
sandbox is a normal GitHub repository available
- to clone as; <code>git clone
git://github.com/Qi4j/qi4j-sandbox.git</code>
+ testing, so can't really ship the coherence extension). The
sandbox is a normal Git repository available
+ to clone as; <code>git clone
https://git-wip-us.apache.org/repos/asf/zest-sandbox.git</code>
</p>
<p>
The Qi4j SDK is the main development codebase, and to start
working with it you simply clone it;
- <code>git clone git://github.com/Qi4j/qi4j-sdk.git</code>
+ <code>git clone
https://git-wip-us.apache.org/repos/asf/zest-qi4j.git</code>
</p>
<h2>Web Access</h2>
<p>
- The two repositories can be browsed here;
+ The two repositories can be browsed on the mirrors on the ASF
Github organization;
</p>
<ul>
- <li><a
href="http://github.com/Qi4j/qi4j-sdk";>http://github.com/Qi4j/qi4j-sdk</a></li>
- <li><a
href="http://github.com/Qi4j/qi4j-sandbox";>http://github.com/Qi4j/qi4j-sandbox</a></li>
+ <li><a
href="https://github.com/apache/zest-qi4j";>https://github.com/apache/zest-qi4j</a></li>
+ <li><a
href="https://github.com/apache/zest-sandbox";>https://github.com/apache/zest-sandbox</a></li>
</ul>
<h2>Committer Access</h2>
@@ -119,9 +124,9 @@ layout: default
<h3>How to Join?</h3>
<p>
- To become a Community Developer, just subscribe to the qi4j-dev at
Google Group and request it together
- with your GitHub user id. For Community Developer, the bar is
really, really low and nothing more than a
- desire to help is required.
+ To become a Community Developer, just subscribe to the
+ <a
href="mailto:[email protected]";>[email protected]</a> mailing
list and participate,
+ nothing more than a desire to help is required.
</p>
<p>
Community Developers who are active and keep contributing
feedback, patches and/or documentation are likely
@@ -130,32 +135,24 @@ layout: default
time.
</p>
- <h3>How to get Access to the writable central repositories?</h3>
- <p>
- Once you have commit access to a repository, you will access it
differently. This is the clone command
- needed, and after that you will need to do the same as above for
pubic access;
- </p>
- <pre><code>git clone [email protected]:Qi4j/qi4j-sdk.git
-cd qi4j-sdk</code></pre>
-
<h2>Commit Policy</h2>
<p class="lead">
Qi4j generally uses a Commit-Then-Review policy on most changes.
This allows a reasonable high velocity of
development.
</p>
<p>
- Commits are visible at GitHub and active contributors should
review all incoming commits to ensure quality
- of contributions and avoidance of mistakes.
+ Commits are visible in Git history and at GitHub. Active
contributors should review all incoming commits to
+ ensure quality of contributions and avoidance of mistakes.
</p>
<p>
- For any given commit, any member of the community may raise
concern(s) on the qi4j-dev forum at Google
- Groups. We encourage as many people as possible to review the
changes that are occurring. "With enough
+ For any given commit, any member of the community may raise
concern(s) on the <code>dev@</code> mailing
+ list. We encourage as many people as possible to review the
changes that are occurring. "With enough
eyeballs every bug is shallow." wrote Eric S. Raymond in "The
Cathedral and The Bazaar" about open source.
</p>
<p>
Special rules applies to changes in the Core Test suite. Adding
new tests are CTR, but modifying existing
tests, either to accommodate for code changes in Core or to
tighten the constraints of them, MUST be
- discussed on the qi4j-dev forum at Google Groups, prior to
committing them to the 'develop' branch. We
+ discussed on the <code>dev@</code> mailing list, prior to
committing them to the 'develop' branch. We
recommend that a different branch is used for these changes,
unless simply codesnippets are pasted to mail.
This exists to ensure that we have a stable evolution of Qi4j
Runtime, and no surprises will occur in
existing applications with new versions.
