On Aug 16, 2006, at 8:42 AM, Kevin Williams wrote:

This is a nice succinct intro to the project.  I like it.


haleh mahbod wrote:

Hi,
I am following the chapter in this book (http://producingoss.com/) that explains how to create an effective website, pages 22-25. It suggests that a
good website provides the following information upfront

1) A clear mission statement
2) States whether this open source is free or not and what license it is
under
3) It's content is progressive. It allows the reader to learn more as he
reads more.

Based on this guideline I re-wrote the text on Tuscany website's main page as follows. It can still be improved. Would you review and comment please?
Thanks

--------------------------------------------------------------------- ----------Start
of website
text----------------------------------------------------------------- ---------------------------------------------------

Welcome to the Apache Tuscany free open source project that is licensed
under version 2 of the Apache
License<http://www.apache.org/licenses/LICENSE-2.0_>.
This project is currently in incubation within the Apache incubator.

The aim of the Apache Tuscany is to create, as a community, the
infrastructure that simplifies the development of business solutions based on Service Oriented Architecture (SOA). Users of Apache Tuscany can create SOA based solutions by combining new or existing services with little or no
programming. They can also alter the solutions easily when business
requirements change.
I think this is an improvement over what we have but have a couple of additional suggestions. Specifically, I don't think the statement "with little or no programming" is something we want to claim. It is not really accurate and the primary audience coming to the website I imagine to be developers who by nature don't believe those kind of statements. I would prefer the page to be oriented to developers, with the particular purpose of recruiting those interested in writing systems-level software, i.e. working on Tuscany. I find these types to be generally skeptical by nature and focused on "cool technologies."

Some good examples to use for comparison would be Microsoft (who I think has generally excellent developer marketing), Spring (Rod is also a really good marketer too) and ServiceMix:

http://msdn.microsoft.com/winfx/technologies/communication/default.aspx

http://www.springframework.org/

http://www.servicemix.org/site/home.html


Based on these, I would rephrase and highlight the message that developers can leverage Tuscany technologies to build out SOA-based systems (as opposed to "business solutions"):

The aim of the Apache Tuscany is to create infrastructure that simplifies the development of SOA-based systems. Tuscany technologies may be used independently or in conjunction with other technologies such as Spring, Axis, and Celtix to create and assemble composite applications, or "service assemblies". Specifically, Tuscany provides:

- SCA-based Java and C++ runtimes for hosting and assembling services which can be extended to support new communications transports, qualities of service, and programming models - An SDO implementation for representing and tracking data as it flows across service assemblies - A Data Access Service for declaratively accessing persistent data in a service-oriented manner






The Tuscany project does this by providing implementations for the Service Component Architecture (SCA) and Service Data Objects (SDO) specifications and by providing a Data Access Service that supports SDO. Specifications for SDO and SCA can be found on www.osoa.org. Tuscany integrates with well established Web Services and server technologies such as Apache Axis2,
Apache Tomcat and Geronimo.

A high level view of the Tuscany runtime is shown below. You can click on the diagram to learn more about specific technologies. Tuscany is supported
in Java and C++.



<Diagram goes here>




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to