blob: c59b54a44eaa2e78bb560deea0394b5bba64c99d [file] [log] [blame]
Alex Karasulu59d49122005-07-26 16:50:17 +00001Project Oscar
2====================
3
4Motivation
5----------
6
7Unlike .NET, which requires that applications are packaged as assemblies
8with explicit dependencies among them, the Java platform does not offer
9sufficient support for modularity. This lack of support complicates not
10only Java application development, but also subsequent deployment and
11administration. Many of the complications result from the fact that
12every project that requires some form of modularity ends up inventing
13their own ClassLoader-based approach for solving their needs. This
14phenomenon is evident in application servers, integrated development
15environments, and any component- or plugin-oriented systems. The OSGi
16framework defined by the OSGi Alliance has a long history of addressing
17these types of issues and the imminent release of version R4 of the OSGi
18specification is set to move the OSGi framework even further along
19this path.
20
21The recent adoption of OSGi technology as the modularity layer of the
22Eclipse Rich Client Platform (RCP) underscores the inroads that OSGi
23technology has made. Further, the announcement of JSR 277 verifies that
24demand for modularity in Java has reached a critical point.
25
26This project can serve the greater Java open source community by
27providing immediate modularity support for Java applications today
28through the OSGi framework, creating a unifying community around open
29source OSGi technology, and tracking and participating in the progression
30of JSR 277.
31
32
33Proposal
34--------
35
36We propose the creation of a new Apache project, Oscar, that will achieve
37the following goals :
38
391) create a compliant, independent implementation of the OSGi R4 core
40 framework with framework-dependent services under the Apache License,
41 Version 2.0.
42
432) unify resources from the OSGi community to implement, document, maintain,
44 and support standard OSGi R4 services.
45
463) provide a focal point for the OSGi community to develop interfaces, APIs,
47 and other common needs not fully specified by the OSGi R4 specification,
48 such as store interfaces, aspects of the runtime container's packaging
49 and configuration, and the design and behavior of bundle repositories.
50
514) provide a focal point for the open-source OSGi community to develop next
52 generation enhancements to the core framework and act as a conduit for
53 the open-source community to the OSGi Alliance.
54
555) evangelize the OSGi Service Platform within Apache and provide documentation
56 and support for successful container migrations.
57
58
59Starting Participants
60---------------------
61
62We propose that the following people are considered the starting participants.
63We hope to start with a diverse cross-section of the community and preserve
64this as we grow. The information in parenthesis indicates other community
65participation or relevant experiences of that individual.
66
67These individuals have expressed an interest in participating in the
68architecture and design work and in participating as committers for the
69Apache-licensed implementation :
70
71 Richard Hall (OSGi Alliance (Invited Researcher) and Founder of the Oscar project)
72 Alex Karasulu (Apache)
73 Enrique Rodriguez (Apache)
74 Trustin Lee (Apache)
75
76These individuals will participate as Incubator Mentors :
77
78 Alex Karasulu (Apache)
79
80The following Apache Members will be the sponsoring members :
81
82 Alex Karasulu (Apache)
83 Noel Bergman (Apache)
84 Carsten Ziegeler (Apache)
85 Berin Loritsch (Apache)
86 Sylvain Wallez (Apache)
87 Bertrand Delacretaz (Apache)
88 Upayavira (Apache)
Michael E. Rodriguezea211be2005-08-04 01:06:01 +000089 Brett Porter (Apache)
Alex Karasulu59d49122005-07-26 16:50:17 +000090
91The following community members support this effort :
92
93 Daniel Fagerstrom (Apache)
94 Niclas Hedhman (Apache)
95 Reinhard Poetz (Apache)
96 Stefano Mazzocchi (Apache)
97 Andreas Oberhack (Apache)
98 Timothy Bennett (Apache and Metro Government of Nashville/Davidson County)
99 Peter Kriens (OSGi Alliance (Director of Technology) and Managing Director, aQute)
100 Humberto Cervantes (Service Binder author and Professor/Researcher, UAM Iztapalapa)
101 Marcel Offermans (+2 others, Luminis)
102 Rob Walker (Ascert)
103 Gerald Friedland (Researcher, Freie Universität Berlin, E-Chalk Project)
104 Juan Alonso (Independent)
105 Stéphane Frénot (Associate Professor, INSA-Lyon/INRIA)
106 Frédéric Le Mouël (Associate Professor, INSA-Lyon/INRIA)
107 Emil Ivov (PhD Candidate, Louis Pasteur University, Strasboug, France)
108 Tom Enderes (CTO, Gatewide LLC)
109 Eric Swindell (Software Craftsman, Caribbean Blue)
110 Jesus Bermejo (Independent)
111 David Ence (Lockheed Martin)
112 Ed Anuff (DriveFire)
113 Rick Litton (Kyocera)
114 Peter Neubauer (OPS4J)
115 Francesco Furfari (Domoware, Domotics Lab, ISTI-CNR)
116 Stefano Lenzi (Domoware, Domotics Lab, ISTI-CNR)
117 Matteo Demuru (Domoware, Domotics Lab, ISTI-CNR)
118 Karl Pauls (Raccoon/Eureka/Sopa, Researcher (DFG), Fu-Berlin)
119 Heejune Ahn (Independent)
120 Yalcin Akdogan (Zeroadmin Software)
121 Juan C. Dueñas (ITEA/Eureka researcher and Associate Professor, DIT-UPM)
122 José L. Ruiz (PhD Candidate, DIT-UPM)
123 Manuel Santillan (PhD Candidate, DIT-UPM)
124 David Leangen (Bioscene Informatics, Japan)
125 Miles Sabin (Technical Director, Codefarm Software Ltd.)
126 Roger Ni (ASPire Technologies)
Michael E. Rodriguezcca2e352005-08-01 12:30:34 +0000127 Mikael Desertot (University of Grenoble)
128 Clement Escoffier (University of Grenoble)
129 Didier Donsez (University of Grenoble)
Michael E. Rodrigueza53a5f82005-08-03 20:11:53 +0000130 Stéphane Chomat (University of Grenoble)
131 Cristina Marin (University of Grenoble)
132 Antonin Chazalet (University of Grenoble)
Alex Karasulu59d49122005-07-26 16:50:17 +0000133
134
135Operating Considerations
136------------------------
137
138We have established a list for discussions. Unless your comment is directed
139to the general Incubator community or the Incubator PMC, please post
140everything to :
141
142 oscar-dev@incubator.apache.org
143
144You can subscribe by sending an email to
145
146 oscar-dev-subscribe@incubator.apache.org
147
148Until this proposal has been accepted by the Apache Incubator PMC, these lists
149are provisional.
150
151
152--
153Alex Karasulu +1-904-982-6992
154akarasulu@apache.org