[luxor-xul-develop] Developer Activity

[Daniel K. <dk...@kc...>]

I am very interested in getting involved in the work with this project. 
In a way it frustrates me...I think that for once I spawn an original
idea just to learn that someone else is already exploring it. :)  

What I am looking to put together is a general application framework
that is fully configurable via XML.  This general application can then
load plug-in modules (each customized via XML and scripting) to add the
business functionality.  I would like this framework to support
customizable rendering and scripting engines, component services, etc.

In a sense, I would like to bring a component-hosting environment to the
desktop similar to how J2EE has brought a component-hosting environment
to the server.

I have tracked down many news threads regarding this project and have
some concerns regarding it.  The first concern is that their is only one
developer listed on the sourceforge site.  I don't believe that this is
a one-man show; however, it concerns me that I can only view the source
on-line...i.e. I cannot access the source, run builds against it, view
test suites, etc.  If others are developing this framework, where is
this code submitted to and why is the source for these new submissions
--    

    Modul-mania. New modules include: Apollo, Caramel, Houston, Rachel,
    and Salsa
              o Apollo - Test Skeleton for Web Start/JNLP
              o Caramel - Java Extensions (non-GUI only)
              o Houston - Yet Another Status and Logging Toolkit
              o Rachel - Resource Loading (includes HTTP web service)
              o Salsa - Swing GUI Add-Ons
    
not viewable or accessible except in binary format (JAR files)?

I would like to become a contributor, however this project "smells" like
a proprietary project under the guise of "OpenSource".  If I am wrong I
sincerely apologies -- I am not out to flame anyone -- I just want to be
given a fair chance to contribute my piece...without fear of having it
taken away by someone "dual" licensing my contributions; thus barring my
opportunity to build a proprietary application upon this framework.