blob: e59ba6823374fea9828bc7ace08811c760f5d41a [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)
89
90The following community members support this effort :
91
92 Daniel Fagerstrom (Apache)
93 Niclas Hedhman (Apache)
94 Reinhard Poetz (Apache)
95 Stefano Mazzocchi (Apache)
96 Andreas Oberhack (Apache)
97 Timothy Bennett (Apache and Metro Government of Nashville/Davidson County)
98 Peter Kriens (OSGi Alliance (Director of Technology) and Managing Director, aQute)
99 Humberto Cervantes (Service Binder author and Professor/Researcher, UAM Iztapalapa)
100 Marcel Offermans (+2 others, Luminis)
101 Rob Walker (Ascert)
102 Gerald Friedland (Researcher, Freie Universität Berlin, E-Chalk Project)
103 Juan Alonso (Independent)
104 Stéphane Frénot (Associate Professor, INSA-Lyon/INRIA)
105 Frédéric Le Mouël (Associate Professor, INSA-Lyon/INRIA)
106 Emil Ivov (PhD Candidate, Louis Pasteur University, Strasboug, France)
107 Tom Enderes (CTO, Gatewide LLC)
108 Eric Swindell (Software Craftsman, Caribbean Blue)
109 Jesus Bermejo (Independent)
110 David Ence (Lockheed Martin)
111 Ed Anuff (DriveFire)
112 Rick Litton (Kyocera)
113 Peter Neubauer (OPS4J)
114 Francesco Furfari (Domoware, Domotics Lab, ISTI-CNR)
115 Stefano Lenzi (Domoware, Domotics Lab, ISTI-CNR)
116 Matteo Demuru (Domoware, Domotics Lab, ISTI-CNR)
117 Karl Pauls (Raccoon/Eureka/Sopa, Researcher (DFG), Fu-Berlin)
118 Heejune Ahn (Independent)
119 Yalcin Akdogan (Zeroadmin Software)
120 Juan C. Dueñas (ITEA/Eureka researcher and Associate Professor, DIT-UPM)
121 José L. Ruiz (PhD Candidate, DIT-UPM)
122 Manuel Santillan (PhD Candidate, DIT-UPM)
123 David Leangen (Bioscene Informatics, Japan)
124 Miles Sabin (Technical Director, Codefarm Software Ltd.)
125 Roger Ni (ASPire Technologies)
126
127
128Operating Considerations
129------------------------
130
131We have established a list for discussions. Unless your comment is directed
132to the general Incubator community or the Incubator PMC, please post
133everything to :
134
135 oscar-dev@incubator.apache.org
136
137You can subscribe by sending an email to
138
139 oscar-dev-subscribe@incubator.apache.org
140
141Until this proposal has been accepted by the Apache Incubator PMC, these lists
142are provisional.
143
144
145--
146Alex Karasulu +1-904-982-6992
147akarasulu@apache.org