Geir, The below is good. Under project goals, I would add that we want Harmony to run commercially relevant workloads.
I would also add rationale for modularizing the JVM. The text for this topic would be something like: - increased project efficiency. Open Source volunteers can make contributions to a single module without having to learn details of the entire JVM. - ability to swap in/out different implementations of each module (e.g. JIT, GC, Threading Module) - On 6/24/05, Geir Magnusson Jr. <[EMAIL PROTECTED]> wrote: > So I have to do the Harmony J1 talk next week. This is about our > project, so I'm looking for community input. > > What are the major themes we want to emphasize, and what do we want > to cover? Please comment/add/subtract to the outline below. > > - project goals > - community developed architecture > - implementation of a complete, compatible stack > > - why we think an open/free java implementation is important > > - current state of the open/free java universe > - projects we want to mention > > - current thoughts on modularization of VM and classlibrary > - what do implementations do now > - where we want to be > - modularization possibilities (OSGi, JSR-277, ?) > > - challenges we are facing > - technical issues > - legal issues > > - plans for project structure > - legal framework for committers > - technical framework for testing > - technical framework for surveillance > > - projects we can start on now > - in our "standard" repository > > - our roadmap going forward > > -- > Geir Magnusson Jr +1-203-665-6437 > [EMAIL PROTECTED] > > >
