|
Hello: below is a project proposal for incubation
consideration. The project welcomes your feedback as well as interest in involvement
(such as additional mentors etc.). This proposal is also located online at http://wiki.apache.org/incubator/XapProposal
. Best regards, ---Coach XAP - eXtensible Ajax Platform
An Ajax-based
Rich Internet Application framework April 2006,
Coach Wei (cwei at nexaweb dot com) PROJECT
PROPOSAL
XAP is to
provide an XML-based declarative framework for building, deploying and
maintaining rich, interactive, Ajax-powered web applications. A basic principal
of XAP is to leverage existing 0.
Rationale
With the recent
excitement around Although these
toolkits ease development of Ajax-powered web applications, there are still
significant development and maintenance challenges, mainly associated with
writing, debugging and maintaining _javascript_ code. In particular, some
developers would prefer not to use _javascript_. There are many
possible solutions to address these challenges and each approach can solve the
challenges to a different degree. On the one side, open source community has
responded with Building on
these vibrant community efforts already underway, the proposed project is to
create an extensible software framework for building and deploying Ajax-powered
rich internet applications declaratively. The project is "pluggable"
with client side This project
seeks to provide
The architecture
of this proposal embraces existing Key benefits:
0.1
Criteria
Meritocracy:
We plan to do
everything possible to encourage an environment that supports meritocracy. We
know that meritocracies don't just evolve from good intentions; they require
actively asking the community for help, listing/specifying the work that needs
to be done, and keeping track of and encouraging members of the community who
make any contributions. Community:
We are committed
to building a strong community around the proposed project. The committers will
supply example code and documentation to help bring new members up to speed as
to the current functionality of the code and how it is organized and
maintained. In addition, the committers plan to spend the time necessary to
answer user and developer questions. Along with our plans to encourage meritocracy
(mentioned above), we hope these efforts will eventually create a user and
development community that can live beyond the contribution of any one person
and beyond the goals of any contributor’s employer. Core
Developers:
More than half
of the initial committers are key members of Nexaweb's development, test, and
project management team. The rest are developers who have had significant
experience with the framework or the technologies it is built upon. Some of
these committers are contributing to this project on behalf of their employer,
some of them are self-employed consultants, and some of them are just
contributing as individuals. Alignment:
The project is a
pure client-side implementation. It should support any server side
infrastructure. The initial code base is targeted to support the following
environments:
For further
information, please see 0.2
Warning signs
Orphaned
products:
The initial code
contribution is being developed specifically for the developer community and is
not an orphaned product. The committers have long term interest to develop and
maintain the code. Inexperience
with open source:
Only a few of
the initial committers have contributed to open source projects; however, all
of the initial committers have been reading Apache process documents, the
incubator general mailing list, and the dev lists of current Apache projects.
We’ve also spent time with ASF members and at ApacheCon to prepare ourselves as much as
possible. Homogenous
developers:
The initial list
of developers consists primarily of paid employees of the donating company. The
donating company has reached out and will continue to reach out to build a
diverse and vibrant community. The remaining initial committers are
independent. They have had experience with the technology before and are
personally passionate about the technology. The committers
are geographically distributed. They are experienced with working in a
distributed environment. Reliance
on salaried developers:
Some of the
initial committers are salaried developers employed by No
ties to other Apache products:
This proposal is
related to many ongoing projects at Apache, such as Kabuki and MyFaces, and it fits into the overall
vision of that set of projects. There is an optional dependency on Kabuki. A
fascination with the Apache brand:
The committers
are intent on developing a strong open source community around the XAP
framework whether Apache is the right place or not; however, we believe that
the project's current use of Apache projects, the potential for future
synergies, and the Apache way of developing software make the ASF the ideal
host community. 1.
Scope
Provide
declarative syntax and framework for writing The initial
commit will contain:
For further
technical or background information, please see:
2.
Identify the initial source from which the subprojects are to be populated
The initial
source will be denoted by Nexaweb Technologies Inc..The donating company will
make code available after the proposal is accepted and necessary infrastructure
has been set up. For further background or technical infomation, please see 2.1
External Dependencies of the project
None. 3.
Identify the ASF resources to be created
3.1
mailing list(s)
3.2
Subversion repository
3.3
Bugzilla
4.
Identify the initial set of committers:
5.
Identify Apache sponsoring individual
Champion: Cliff
Schmidt Mentors: Cliff
Schmidt ... We request that
the Apache Incubator PMC sponsor XAP as an incubating project. There is not
currently another TLP that would be an obvious fit as sponsor for this project.
As the project approaches graduation, we would reevaluate possible TLP
destinations and work with others at Apache to consider whether a new TLP is
warranted to include XAP and possibly other related Apache projects. |
