Author: grobmeier
Date: Mon Sep 9 09:03:20 2013
New Revision: 1521001
URL: http://svn.apache.org/r1521001
Log:
initial text youatstruts, took some from the faq
Added:
struts/site/branches/next/content/markdown/youatstruts.md
- copied, changed from r1520971,
struts/site/branches/next/content/markdown/birdseye.md
Modified:
struts/site/branches/next/content/fml/helping.fml
Modified: struts/site/branches/next/content/fml/helping.fml
URL:
http://svn.apache.org/viewvc/struts/site/branches/next/content/fml/helping.fml?rev=1521001&r1=1521000&r2=1521001&view=diff
==============================================================================
--- struts/site/branches/next/content/fml/helping.fml (original)
+++ struts/site/branches/next/content/fml/helping.fml Mon Sep 9 09:03:20 2013
@@ -36,122 +36,6 @@ limitations under the License.
-->
<part id="general">
- <faq id="involved">
- <question>Getting Involved</question>
- <answer>
-
- <p>
- Every volunteer project obtains its strength
- from the people involved in it.
- We invite you to participate as much or as little as you
- choose.
- The roles and responsibilities that people can assume in
- the project
- are based on merit.
- Everybody's input matters!
- </p>
-
- <p>
- Here is one developer's advice how to get involved.
- It specifically talks about Tomcat,
- but the general idea can applied to any of the Apache
- Projects.
- </p>
-
- <ul>
- <li>
- <a
href="http://jakarta.apache.org/site/contributing.html";>
- Contributing</a>
- -- Craig R. McClanahan
- </li>
- </ul>
-
- <p>
- Here is another comment that was sent to the Jakarta
- Turbine Mailing
- List about the open source process and the contrast
- between how an
- open source product and a proprietary product improve
- through the user
- community.
- </p>
-
- <ul>
- <li>
- <a
href="http://jakarta.apache.org/site/understandingopensource.html";>
- Understanding Opensource</a>
- -- Cameron Riley
- </li>
- </ul>
-
- <p>
- While written for ASF developers,
- the Rules for Revolutionaries provides insight into how
- the
- collaborative process works,
- and how our process differs from working on a hierarchical
- team.
- </p>
-
- <ul>
- <li>
- <a
href="http://incubator.apache.org/learn/rules-for-revolutionaries.html";>
- Rules for Revolutionaries</a>
- -- James Duncan Davidson
- </li>
- </ul>
-
- <p>
- Just using the products is a very important role.
- We need people who will report issues, contribute patches,
- suggest features, and so forth.
- Your feedback helps the technology to evolve.
- </p>
-
- </answer>
- </faq>
-
- <faq id="mail">
- <question>Joining the Mailing Lists</question>
- <answer>
-
- <p>
- There are a variety of ways to participate.
- Regardless of how you choose to participate,
- we suggest you join our mailing lists.
- </p>
-
- <p>
- Before joining any ASF mailing list, please be sure to
- read the
- <a href="mail.html#Guidelines">Mailing List Guidelines.</a>
- If you have read and understood these guidelines, you are
- welcome to
- <a href="mail.html#Subscribing">join the Struts mailing
- lists.</a>
- </p>
-
- <p>
- Before posting a new question, be sure to consult one of
- the
- <a href="mail.html#Archives">
- <strong>Mailing List Archives</strong>
- </a>
- and the very excellent
- <a
href="http://www.catb.org/~esr/faqs/smart-questions.html";>
- How To Ask Questions The Smart Way</a>
- by Eric Raymond.
- </p>
-
- <p>
- Please do be sure to
- <a href="http://expita.com/nomime.html";>turn off
- HTML</a>
- in your email client before posting.
- </p>
- </answer>
- </faq>
-
<faq id="corp">
<question>What can my company do to help support Apache
Struts?</question>
Copied: struts/site/branches/next/content/markdown/youatstruts.md (from
r1520971, struts/site/branches/next/content/markdown/birdseye.md)
URL:
http://svn.apache.org/viewvc/struts/site/branches/next/content/markdown/youatstruts.md?p2=struts/site/branches/next/content/markdown/youatstruts.md&p1=struts/site/branches/next/content/markdown/birdseye.md&r1=1520971&r2=1521001&rev=1521001&view=diff
==============================================================================
--- struts/site/branches/next/content/markdown/birdseye.md (original)
+++ struts/site/branches/next/content/markdown/youatstruts.md Mon Sep 9
09:03:20 2013
@@ -1,88 +1,58 @@
-<head><title>From a birds eye</title></head>
+<head><title>You at Struts</title></head>
-# From a birds eye
+# You at Apache Struts
-## The Apache Struts web framework
-
-The Apache Struts web framework is a free open-source solution for
-creating Java web applications.
-
-Web applications differ from conventional websites in that web applications
-can create a dynamic response. Many websites deliver only static pages.
-A web application can interact with databases and business logic engines
-to customize a response.
-
-Web applications based on JavaServer Pages sometimes commingle database
-code, page design code, and control flow code. In practice, we find that
-unless these concerns are separated, larger applications become
-difficult to maintain.
-
-One way to separate concerns in a software application is to use a
-Model-View-Controller (MVC) architecture. The Model represents the business or
-database code, the View represents the page design code, and the Controller
-represents the navigational code. The Struts framework is designed to help
-developers create web applications that utilize a MVC architecture.
-
-The framework provides three key components:
-
-A "request" handler provided by the application developer that is mapped to a
standard URI.
-A "response" handler that transfers control to another resource which
completes the response.
-A tag library that helps developers create interactive form-based applications
with server pages.
-The framework's architecture and tags are buzzword compliant. Struts works
-well with conventional REST applications and with technologies like SOAP and
AJAX.
-
-## The Apache Struts Project
-
-The Apache Struts Project is the open source community that creates and
maintains
-the Apache Struts framework. The project consists of a diverse group of
volunteers
-who share common values regarding collaborative, community-based open source
development.
-The Apache Struts Project is proud to share these values with our parent
organization:
-The Apache Software Foundation.
-
-The project is called "Struts" because the framework is meant to furnish the
-"invisible underpinnings" that support professional application development.
-Struts provides the glue that joins the various elements of the standard Java
platform
-into a coherent whole. Our goal is to leverage existing standards by producing
the missing
-pieces we need to create enterprise-grade applications that are easy to
maintain over time.
-
-Long time the Apache Struts Project offered two major versions of the Struts
framework.
-Meanwhile we maintaining only Struts 2. It is recommended to upgrade all
Struts 1.x
-application to Struts 2. Please do not start any more applications on top of
Struts 1.x,
-as you will not receive security patches any more.
-
-Struts 2 was originally known as WebWork 2. After working independently for
several years,
-the WebWork and Struts communities joined forces to create Struts 2. The 2.x
framework
-is the best choice for teams who value elegant solutions to difficult problems.
-
-## Why should you use Apache Struts?
-
-Apache Struts is a modern, maintained and full-featured web framework. It has
been there
-for years and give the huge user base it is unlikely it will go away anytime
soon
-in the future. Not only that we have dedicated users and developers on the
project.
-Apache Struts is licensed to the Apache License 2.0 and this will not change.
We maintain
-a clean IP and you are "safe" to use the project. Sometimes you are not "safe"
to use
-a project when a company controls the SCM. Access to Source Code doesn't mean
it is free.
-With Apache Struts, you are not only free to "do what you want with it", you
can even
-contribute (which is not always the case). And best of it: you can become a
part of the
-core team too.
-
-It is usually very easy to integrate other technologies with Apache Struts. If
you are
-using an ORM like Apache Cayenne, Hibernate or JDBC you will not have any
restrictions.
-Apache Struts is not even tied too much to a frontend technology. In old days
it was
-JSP, then came Velocity and Freemarker. Nowadays you might build your web
application
-with just static HTML and AngularJS. Or you want to use Sitemesh or Tiles.
This all
-is no problem due to Struts elegant and easy to use extension mechanisms.
-
-Unlike other, component oriented frameworks, we do not aim to hide the
stateless nature
-of the web. We think it is perfectly acceptable to build upon a
Request/Response cycle.
-We also think the MVC pattern is not so bad, just because it is old. In fact,
we believe
-the Apache Struts architecture is clean and easy to understand.
-
-Of course, if you wish to build components on the server side which render on
the front end
-side, you are most likely wrong with Struts. This is a different approach
which promises
-to reduce the amount of HTML/JavaScript knowledge needed and to create
reusable components for
-the view layer. Projects like <a href="http://wicket.apache.org";>Wicket</a> and
-<a href="http://tapestry.apache.org";>Tapestry</a> serve this purpose very
well. As with every
-framework you need to decide if it makes sense for you to build components or
if
-you are better with the Struts-approach.
+We are happy you are considering to contribute to Apache Struts and
+we are definitely looking forward to your work.
+We all are a happy group of volunteers and much often work on Struts
+in our free time. We are not getting any money for our work from the
+Apache Software Foundation (nor does any other project receive money)
+and most of us are not paid by a company for working on Struts.
+
+Still we are happy to contribute, meet up from time to time and
+provide user support. That's because we have formed a community
+where we know, trust, and learn from each other.
+
+Considering that we are a grown set of people, you must understand
+that you need to grow into the project as well if you want to join.
+While we are happy to accept your patches if they fit or discuss
+technical changes on them with you, we cannot provide SCM access
+on request. But if we start to believe you have grown into the project
+and would make a great addition to our committer community we'll
+held a private discussion and eventually invite you to join officially.
+
+You can read more about this on the page ["How the ASF
works"](http://www.apache.org/foundation/how-it-works.html).
+
+Now as you have understood that you don't need to ask for anything to start,
+you can simply start. It is always a good idea to first subscribe to the
+[Developers Mailinglist](dev-mail.html). We are discussing everything
+around Struts in public (except a few things, like discussions on persons).
+With reading the developers list you'll get a good idea what we are planning
+and maybe even how you can help.
+
+Another way is to simply look through the [Issue
Tracker](https://issues.apache.org/jira/browse/WW)
+and work on a patch. It's recommended to first try to understand and then
discuss
+what you plan on the mailing list. This way we will find out if we are on
+the same page and of course will learn about you.
+
+Please note, not only code contributions are welcome. We also invite people
+to join us because they have written extraordinary examples, documentation
+or help a lot on the user mailing lists. For us, "Community is over Code".
+And a good community does not reduce itself to people who write code.
+
+If you like, you can read Craig R. McClanahans article on
+[Contributing](http://jakarta.apache.org/site/contributing.html).
+
+Here is another comment that was sent to the Jakarta Turbine Mailing
+List about the open source process and the contrastbetween how an
+open source product and a proprietary product improve through the user
+community: [Understanding
Opensource](http://jakarta.apache.org/site/understandingopensource.html).
+
+While written for ASF developers, the Rules for Revolutionaries provides
insight into how
+the collaborative process works, and how our process differs from working on a
hierarchical
+team: [Rules for
Revolutionaries](http://incubator.apache.org/learn/rules-for-revolutionaries.html)
+
+Feel free to ping us on the [Developers Mailinglist](dev-mail.html) if you have
+any questions. Also make sure you read the [FAQ](helping.html) which provides
+more information how you can help us.
