This page stores all info on the documentation updates to improve website, and establishes perspective for further activities. We will try to keep up-to-date a list of documents that are planned for updates or creation.
Certain pages do require help of technical experts, so, please, do not ignore the information below.
Doxygen API Reference Documentation
Doxygen materials provide reference information on public interfaces of DRLVM and its components. This API reference is created semi-automatically from the source code. We are using several metrics to evaluate and track improvement of the quality of the reference materials:
DRLVM_Documentation_Quality describes some rating of DRLVM code comments evaluation quality.
DRLVM_Documentation_Quality_Doxygen_Warning_Rating describes additional rating that shows the amount of warnings during the Doxygen files generation.
To produce adequate and uniform results, we recommend following some simple markup rules when documenting a header.
Many headers using in Doxygen reference generation lack ample and well-formatted comments. To get easily readable, complete and useful info for DRLVM interface reference and Java class library reference, the following JIRAs were opened:
HARMONY-3262 Covers VM_Common interface header files
HARMONY-3263 Covers VM_JIT and VM_EM interface header files
HARMONY-3264 Covers VM_Interpreter interface header files
HARMONY-3273 Covers VM_GC interface and VM_Thread interface header files
HARMONY-3274 Covers JNI and JVMTI interface header files
HARMONY-3275 Covers Execution manager external interface headers
HARMONY-3277 Covers Thread manager external interface headers
HARMONY-3278 Covers Garbage collector and Execution engine external interface headers
HARMONY-3284 Covers OS portability layer external interface
You are welcome to contribute to any of the JIRAs listed above or to create new ones that improve quality of markup.
If you want to make an impact in development and improvement DRLVM Doxygen documentation, feel free to contribute to JIRAs filed against doc component.
Besides the open bugs, we have several enhancements in mind and some ongoing work that cannot easily map to one finite JIRA. The current list of activities includes the following items:
Create Porting Guide to document what needs to be done to port Apache Harmony to other OSs, such as FreeBSD, Solaris, QNX, etc. For that task, the following materials can be useful:
Update Developer's Guide: sections 4.1 and 4.8 about Initialization and Shutdown are out of date
Improve Bytecode verifier description to improve wording, structure and style
- Publish BTI (Build Test Infrastructure) launching and usage instructions
Update Thread Manager description after new threading features are implemented
- Create localized pages of popular pages, such as in Russian and Chinese
Website_Improvement - suggestions on website improvement and the trial site version
Doxygen_Docs_Look&Feel_Improvements - suggestions on how to improve the look and feel of generated Doxygen documentation
Folks, here is the place for your creation
Feel free to leave your ideas/suggestions/comments on documentation, either negative or positive, right here.
Do not hesitate to ask questions. I’ll try to do my best to satisfy your tiptoe curiosity
Thank you for Getting Started For Contributors document :)
It really helps me to build Class Library and DRLVM