To whom it may concern:=20
Enclosed please find a revised contribution proposal for the Ajax Toolkit w=
hich takes into account the principal feedback that we have received to dat=
e. We welcome a further dialog on the merits of this submission.=20
Thank you for your consideration.=20
Regards=20
Ross=20
--=20
Ross Dargahi=20
Co-founder, VP. Engineering=20
Zimbra=20
---------=20
AJAX Toolkit Proposal=20
0. Rationale=20
While the term AJAX (Asynchronous Javascript and XML) has only recently bee=
n coined, the underlying web standards and technologies (JavaScript a.k.a. =
ECMAScript, DOM, XML, SOAP, and so on) have been around for years. Although=
the term is used in a variety of ways, AJAX typically describes techniques=
towards developing interactive applications on the web client including as=
ynchronous messaging, use of XML grammar in client-side applications, incre=
mental page updates, and improved user interface controls. AJAX application=
s combine the rich UI experience of programmed clients with the low-cost li=
fecycle management of web-based applications.=20
AJAX has raised awareness of the high potential of web applications, it has=
encouraged companies to adopt rich web-based interfaces over traditional "=
fat" clients, and it has spawned development activity to create toolkits an=
d abstractions to make AJAX-style development easier and more powerful. Thi=
s is an important trend for open source. The client itself can be composed =
entirely of open-source parts, such as Mozilla's Firefox or KDE's Konqueror=
, and does not require any particular operating system, helping to make a m=
ore level playing field for all development. More importantly, AJAX is back=
-end agnostic as transactions are done over HTTP. Keeping the client open f=
orces vendors to keep the communication channel open as well, and this can =
only continue as long as the client technology keeps pace with proprietary =
alternatives. The open, standards based communications channel is what driv=
es many technologies inside Apache, so success of the open client is vital =
to Apache. The mission of this project is to encourage innovation around en=
terprise-strength client runtimes and tools and build a community which can=
select and nurture a select set which will be most beneficial to the web.=
=20
0.1 Criteria=20
Meritocracy:=20
Apache was chosen for an incubator primarily because of the guidance the co=
mmunity can provide.=20
Community:=20
The contributed work was inspired by open source development but needs a st=
rong and diverse community to validate its mission and carry it forward. A =
primary objective of the project is to build a vibrant community of users a=
nd active contributors.=20
Core Developers:=20
All of the initial committers are members of the Zimbra development team s =
. All developers have worked on open source projects before and have experi=
ence and understanding of open source principles.=20
Alignment:=20
The Zimbra AJAX Development Toolkit provides a rich client library, similar=
in style to traditional object-oriented widget libraries like Eclipse's SW=
T. This toolkit hides implementation details and browser quirks and makes w=
eb development more accessible to the enterprise developer. It provides=20
* User interface development=20
* Network communications (both synchronous and asynchronous)=20
* SOAP programming=20
* XML document creation and manipulation=20
* UI event handling and management=20
For further information, please see the Zimbra AjaxTK whitepaper:=20
http://www.zimbra.com/pdf/Zimbra%20AJAX%20TK%20Whitepaper.pdf=20
0.2 Warning signs=20
Orphaned products:=20
The initial committers are users of this toolkit and have a long-term inter=
est in use and maintenance of the code.=20
Inexperience with open source:=20
Several of the commiters are very experienced in Open Source environment. A=
ll efforts will be made to ensure that the work done and momentum will be i=
n strict adherence to open source guidelines.=20
Homogenous developers:=20
The current list of committers includes developers who are experienced with=
working in a distributed environment, and with resolving technical differe=
nces.=20
Reliance on salaried developers:=20
The initial set of committers are salaried developers. Through the incubati=
on process, more diversity will hopefully be achieved in many aspects, incl=
uding reliance on salaried developers.=20
No ties to other Apache products:=20
The initial codebase will be licensed under the Apache License 2.0. While t=
here are no direct build dependencies on other Apache projects, the develop=
ment of AJAX clients will often be driven by Apache middleware and will hav=
e a positive impact on the open source movement as described in the "Ration=
ale" section.=20
A fascination with the Apache brand:=20
The committers are intent on developing a strong open source community. We =
believe that the Apache Software Foundation's emphasis on community develop=
ment makes it the most suitable choice.=20
1. Scope of the subprojects=20
The Zimbra AjaxTK, as described in 0.1.=20
2. Identify the initial source from which the subprojects are to be=20
populated=20
The Zimbra AjaxTK is available today in open source, and can be downloaded =
at=20
http://www.zimbra.com/community/downloads.php (See Zimbra Ajax Toolkit Down=
load).=20
(A snapshot of the AJAX toolkit code is also available via http://www.apach=
e.org/~rubys/ajax/Ajax.tar.gz)=20
2.1 External Dependencies of the project=20
None.=20
3. Identify the ASF resources to be created=20
3.1 mailing list(s)=20
* ajaxtk-ppmc=20
* ajaxtk-dev=20
* ajaxtk-commits=20
* ajaxtk-user=20
3.2 Subversion repository=20
* [WWW] https://svn.apache.org/repos/asf/incubator/ajaxtk=20
3.3 Bugzilla=20
* AJAXTK (AJAXTK)=20
4. Identify the initial set of committers:=20
* Andrew Clark=20
* Conrad Damon=20
* Ross Dargahi=20
* Roland Schemers=20
* Parag Shah=20
* Greg Solovyev=20
5. Identify Apache sponsoring individual=20
We request that the Apache Incubator PMC sponsor the AJAX Toolkit Framework=
as an=20
incubating project, with the eventual goal of graduation as a TLP. The=20
initial contributors feel the scope of the project doesn't clearly=20
overlap with any existing TLP, and is broad enough to justify eventual=20
TLP status.=20
Champion: Sam Ruby=20
Mentors: Andy Clark=20
|