Java Advanced Imaging Project Structure and Mailing Lists

Java Advanced Imaging and Image I/O Tools are hosted within the jai and jai-imageio projects on
Project Structure
The JAI and Image I/O Tools projects are organized in a tree fashion:
             jai                            jai-imageio
           /     \                        /             \
          /       \                      /               \
         /         \                    /                 \
     jai-core    jai-demos          jai-imageio-core    jai-imageio-demos

The only projects which contain source code are the ones at the bottom, i.e., the *-core and *-demos projects. The other projects are containers which are useful to collect related sub-projects under the same umbrella. At the moment the "imageio" project is rather hollow as it was created to be capable of containing non-JAI projects in Image I/O none of which exist as yet.

Mailing Lists
The extant mailing lists are as follows:
          jai jai-core jai-demos jai-imageio jai-imageio-core jai-imageio-demos

announce  X     -        -         X           -                -

cvs       X     X        X         X           X                X

interest  X     -        -         X           -                -

issues    X     X        X         X           X                X

Note that the announce and interest lists do not exist for the *-core and *-demos projects; those lists are subsumed by the respective mailing lists of the corresponding container projects.

Also note that the cvs and issues mailing lists of the container projects pertain generally to information posted on the web pages of those container projects and not to the sub-projects and specifically not to source code per se.

The 'announce' lists are low volume and obviously intended for significant announcements.

The 'interest' lists are the primary discussion medium and in general are the highest volume.

The 'issues' lists are the means by which filing and fixing issues may be monitored for a given project. Again, for issues related to actual source code only the 'issues' lists of the *-core and *-demos project are likely to be pertinent.

The 'cvs' lists are the means by which source code check in activity may be monitored. (This of course does not list all activity, only that which represents code which is considered to be of sufficient quality to check in.) Monitoring these lists provides the finest grained view into the state of the source base. Again, only the 'cvs' lists of the *-core and *-demos project pertain to actual source code.