On Feb 5, 2008 10:49 PM, Niclas Hedhman <[EMAIL PROTECTED]> wrote: > Gang, I want to invite everyone to clash their heads together and > start dreaming up what Pax should eventually become. What direction? > What other components? What focus? What is the holy grail of OSGi > interoperability? Call it a brain dump. I want ideas flowing, because > we need to step up the ambition by a few notches. We are slowly > becoming recognized for our framework independabilty (although we > favor Felix a little bit), so what's next? There are 80 people on this > list, so if everyone just pitch one idea, we get more than plenty. --
Direction and Focus: I would like to see finishing and polishing the product that we have before taking another project. If we do this for every existing project that we have in the pax. I would think that would be very good for short term and long term of ops4j. At least the ops4j users would see that we're committed and not just stall some components for months/years etcs. Just because there's something more interesting out there. I'm definitely guilty for this :(. Components: o pax-test framework. o pax-osgi-idea-plugin. o I want to see deployment admin, restart radman or abolish it and redo it as part of pax-runner. o pax-construct-spring profile work that Stuart did. o pax-cluster framework o pax-sso? much later: o pax-qi4j? o pax-flex? (Flex seems getting a lot of traction in infoq website. I'm really torn between flex and javascript nightmares, Not too sure which one I would prefer to deal with. At least with flex we don't have to deal with IE) How about other works: o Tutorials on OSGi with pax bundles to get non-osgi people to get started. o osgi-jug-malaysia or osgi-jug-other countries? Regards, Edward Yakop _______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
