rename argonaut to FusionDirectory Communication Server or FusionDirectory CS in short
Descriptive title for this enhancement
Rename argonaut to FusionDirectory Communication Server or FusionDirectory CS in short
Actual behavior
all the tools got the name argonaut, but :
- Its not linked to FusionDirectory in anyway
- Its difficult to explain what it does
- Its potential is not exploited
Expected behavior
- Rename every file and tool as beign part of FusionDirectory Communication Server or FusionDirectory CS
Step by step description of new behaviour
- Rename every Argonaut to FusionDirectory Communication Server inside documentation included in files
- Rename each tool directory to fusiondirectory-cs-nameofthetool
- Rename if need inside the tools themselve if they use another tool internally
Benefits
- Easier to explain
- Easier to document inside the global FusionDirectory Documentation
- Easier to market as an FusionDirectory extension
- Add more Value to FusionDirectory itself
Possible Drawbacks
- work
- testing the whole set again