This is an umbrella project for applications ready to run in Loom. The Applications project is separate from Loom itself and all applications gathered here are separate from each other and may have different development teams. Internal applications are maintained here and external once elsewhere.
Internal applications
Name |
Purpose |
Maturity level |
Owner |
Team |
Link |
|---|
External applications
Name |
Purpose |
Maturity level |
Link |
|---|---|---|---|
Jervlet |
Connect Servlets and Components |
pre-alpha |
|
pl-j |
Java Stored Procedure Server for PostgreSQL |
beta |
|
XFire |
Export blocks as SOAP services |
functional |
|
Instructions for developers
Starting a new project
Talk to Loom's development team to get your project accepted and to get access set up. Before granting any kind of access we usually expect people to take part in the community for some time and get known.
To take part in the community, read Loom's documentation and subscribe to the mailing lists. Mailing lists are official communication channels. IRC discussions are also possible and usually very time effective.
Access rights
There might not be separate access rights set up for the project(s) you work on. This means access to the repository is largely based on trust. Make changes to the project(s) you are assiged to only. To get involved in a project, talk to its owner or team members. They should know what to do.
Build tools
There are no predefined or mandatory build tools. Use Maven, Ant or any other that suits the project.
Code style
Loom's coding conventions are preferable, but not mandatory. Each project is independent and can mostly define its own rules.
Directories
Each project has its cvs home under loom-apps. The name of the project is the directory name. This name is also used for a possible Confluence home page under Loom Applications and/or a static site under public_html\applications.
Release distributions.
To be defined