Get Involved Section (TUSCANY) edited by Simon Nash
Page:
http://cwiki.apache.org/confluence/display/TUSCANY/Get+Involved+Section
Changes:
http://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=55916&originalVersion=12&revisedVersion=13
Content:
---------------------------------------------------------------------
h3. Getting Involved
h4. Apache Tuscany
A successful project requires many people to play many roles, for example write
code, documentation, test, provide suggestions or feedback. These are all
important.
{section:border=false}
{column:width=60%}
*Here are some suggestions for getting started and welcome to the project.*
* Tuscany consists of several [subprojects|Tuscany Subprojects]. Identify what
areas you are interested in. Take a look at samples for that area.
* Subscribe to the [mailing list|Mailing Lists]. If you are interested to get
involved at the user level, subscribe to user mailing list. If you are
interested to get involved in the development of Tuscany, subscribe to the
developer list. Rememer that you can always unsubscribe later.
* Would like to contribute new ideas? Start with the mailing list and share
your thoughts.
* Answer questions posted to the [mailing list|Mailing Lists].
* Identify JIRAs in the area that you are interested in and provide patches.
* Contribute to the user or developer documentation or website. Create the Wiki
page on the [Tuscany Wiki|http://cwiki.apache.org/TUSCANYWIKI], create a JIRA
and attach the link.
* Identify [known issues|Issue Tracking] that you'd like to fix and provide a
patch.
* Contribute to feature developement. Just let the community know what you'd
like to work on. It is as easy as that.
* If in doubt about where to start, send a note to the mailing list and mention
your area of interest. Any questions is welcomed. We'd like you to be involved!
* *Provide feedback*: What is working well? What is missing? What can help you
with your deployment. This helps us create software that addresses real pain
points in SOA.
*communication*
Please note that a single mailing list is used for all the subprojects.
The Tuscany community also gets together on IRC. The IRC server is
irc.freenode.net and the channel is #tuscany.
Internet Relay Chat (IRC) Help is a good source of information on understanding
IRC chats.
The following are some IRC chat clients:
* mIRC http://www.mirc.com/
* Trillian http://www.ceruleanstudios.com/
* Pidgin http://www.pidgin.im/
If you are not familiar with Apache, you can read more about how Apache works
at [this link|http://www.apache.org/foundation/how-it-works.html].
{column}
{column:width=40%}
{include:Getting Involved - Projects Panel}
{column}
{section}
h4. Open CSA (SCA standards)
The SCA specifications which are implemented by Tuscany have moved to OASIS for
formal
standardization. This is being done as a series of OASIS technical
committees, each dealing with one or more of aspects of the SCA specifications.
The OASIS activities are carried out in public. You can either observe the
activities in the various technical committees, or join one or more of the
committees to contribute to.
There are 6 SCA technical committees and by clicking on the links below you can
find information about how to join as an observer or contributor. You will also
have access to the minutes of meetings of the meetings on the same page.
* [*OASIS SCA Assembly TC*|
http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=sca-assembly]:
Defining core SCA composition model to simplify SOA application development
* [*OASIS SCAPolicy TC*|
http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=sca-policy]:Defining
an SCA policy framework to simplify SOA application development
* [*OASIS SCA Bindings
TC*|http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=sca-bindings]:Standardizing
bindings for SCA services and references to communication protocols,
technologies and frameworks
* [*OASIS SCA-Java
TC*|http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=sca-j]:
Standardizing Java (tm) use within an SCA domain for SOA
* [*OASIS SCA-C & C++
TC*|http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=sca-c-cpp]:
Standardizing C and C++ use within an SCA domain for SOA
* [*OASIS SCA BPEL
TC*|http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=sca-bpel]:Specifying
how SCA component implementations for SOA can be written using BPEL
Each OASIS SCA TC mailing list archives can be found here:
* [OASIS SCA TC mail archive|http://www.oasis-open.org/archives/sca-assembly/]
* [OASIS SCA Policy TC mail
archive|http://www.oasis-open.org/archives/sca-policy/]
* [OASIS SCA Binding TC mail
archive|http://www.oasis-open.org/archives/sca-bindings/]
* [OASIS SCA-Java TC mail archive|http://www.oasis-open.org/archives/sca-j/]
* [OASIS SCA-C & C++ TC mail
archive|http://www.oasis-open.org/archives/sca-c-cpp/]
* [OASIS SCA BEPL TC mail archive|http://www.oasis-open.org/archives/sca-bpel/]
---------------------------------------------------------------------
CONFLUENCE INFORMATION
This message is automatically generated by Confluence
Unsubscribe or edit your notifications preferences
http://cwiki.apache.org/confluence/users/viewnotifications.action
If you think it was sent incorrectly contact one of the administrators
http://cwiki.apache.org/confluence/administrators.action
If you want more information on Confluence, or have a bug to report see
http://www.atlassian.com/software/confluence
