Frequently Asked Questions
This page lists answers to frequently asked questions. Questions are grouped with other related questions.
- OpenCLAWS Development and Testing
- RIT's CLAWS / Migration
- Why are you forking CLAWS?
- Are you legally allowed to release the CLAWS source code?
- Can I download the original CLAWS source code?
- CLAWS component X is missing from OpenCLAWS. What's the deal?
- How are CLAWS components migrated?
- Can CLAWS components interoperate with OpenCLAWS components?
- Are there any plans to contribute updates to RIT?
OpenCLAWS Development and Testing
What is the absolute minimum environment needed to run OpenCLAWS?
Currently, you need a machine running Apache Tomcat and an Oracle database to successfully start the OpenCLAWS Central Server (CAT). You'll also, at very least, want to run modHistory and modIdentity, both of which run in any POSIX-compliant environment.
Other modules (as they are migrated over) will have additional requirements which you can read about in the handbook.
RIT's CLAWS / Migration
Why are you forking CLAWS?
We believe that IT organizations could benefit from CLAWS, and so we are continuing development (independent of RIT). You can read about the project and its mission for more information.
Are you legally allowed to release the CLAWS source code?
Yes. While it's true that CLAWS is no longer open source, it was originally released under the GPL. This means that anyone is free to modify and release derivative products based on CLAWS.
OpenCLAWS is free, open source, and released under the GPL. RIT still owns the copyright to any of the original source code, and we own the changes we've made.
Can I download the original CLAWS source code?
No -- at least not from us. We feel that the CLAWS sources may contain proprietary information about RIT, and that it would be inappropriate for us to release that information to the public.
CLAWS component X is missing from OpenCLAWS. What's the deal?
We are gradually migrating components from the CLAWS to OpenCLAWS. Some components are being directly ported, most are being refactored, and a few are being abandoned. Keep an eye on the roadmap to see when components are scheduled for migration.
How are CLAWS components migrated?
The migration path for CLAWS components has three parts. The first is a series a patches (the original PAWS project) that significantly alter parts of the CLAWS sources. After the patches are applied, the target component is copied into an OpenCLAWS working directory where it is manually updated until it compiles or works with existing components. After the initial port is committed to the repository, the component may be refactored until it meets project coding and style standards.
Can CLAWS components interoperate with OpenCLAWS components?
Maybe. Take a look at the CLAWS Compatibility document for more information.
Are there any plans to contribute updates to RIT?
Not specifically. Since OpenCLAWS is open source, updates are available to anyone. If we encountered a critical bug that affects CLAWS, then we'd be happy to back-port a patch.
