incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Incubator Wiki] Update of "ESMEProposal" by DarrenHague
Date Mon, 03 Nov 2008 22:55:15 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Incubator Wiki" for change notification.

The following page has been changed by DarrenHague:
http://wiki.apache.org/incubator/ESMEProposal

The comment on the change is:
Edited language for clarity

------------------------------------------------------------------------------
  
  The use of  Adobe Flex/AIR on the client assures that business users are given a user interface
that meets their needs regarding functionality without clutter. ESME's open architecture enables
the possibility of other client technologies such as Symbian S60 mobile, SAP Web Dynpro, RIM
Black-Berry and Apple iPhone as examples.
  
- \The alpha version of ESME is currently "live" at http://www.esme.us/esme/index and the
AIR client is also available to download from the same address. This version was presented
in front of around 5,000 developers at the Demo Jam events during SAP's Tech-Ed conferences
in Las Vegas and Berlin.
+ The alpha version of ESME is currently "live" at http://www.esme.us/esme/index and the AIR
client is also available to download from the same address. This version was presented in
front of around 5,000 developers at the Demo Jam events during SAP's Tech-Ed conferences in
Las Vegas and Berlin.
    
  ESME focuses primarily on usage in enterprise settings where the use of open-source software
is often controversial. Our decision to move to Apache will help further the use of open-source
software in corporate settings especially as it has already been architected for inclusion
in SAP environments. 
  
  = Rationale =
- 
  ESME has attracted a great deal of media and end-user attention based on its unique feature-set
and the underlying technology (see http://blog.esme.us/2008/09/25/esme-in-the-news/).  We
believe that ESME's vision is unique in the area of microsharing.
   
  The ESME project team is interested in joining the Apache Software Foundation for several
reasons: 
@@ -33, +32 @@

  = Current Status =
  
  == Meritocracy ==
- 
- Since the project's inception, its development has been coordinated through collaborative
decision-making on the mailing list, daily scrum calls, Twitter and open discussion on ESME
itself. The ESME community encourages suggestions and contributions from any potential users
and developers. The ESME team has no leader, merely a set of core contributors and others
who help the project in any way they can. All of the core developers are committers to the
current repository; new committers are granted access once they have demonstrated an understanding
of ESME and have at least a proof-of-concept of their patch working.
+ Since the project's inception, its development has been coordinated through collaborative
decision-making on the mailing list, through daily scrum calls, via Twitter and using open
discussion on ESME itself. The ESME community encourages suggestions and contributions from
any potential users and developers. The ESME team has no leader: it operates by consensus
among a set of core contributors aided by a larger group of allies who help the project in
any way they can. All of the core developers are committers to the current repository; new
committers are granted access once they have demonstrated an understanding of ESME and have
at least a proof-of-concept of their patch working.
  
  == Community ==
- Many of the team are SAP Mentors: "SAP Mentors are role models who differentiate themselves
through the high quality and frequency of their community contributions, their perspectives,
attitudes, and interaction styles. They are subject-matter experts who are passionate about
SAP and share their opinions and insights with the community" (Source: https://wiki.sdn.sap.com/wiki/display/SAPMentors/SAP+Mentor+Initiative+FAQs).
In addition, team member David Pollak also runs the Lift project, and is an active member
of the Lift and Scala communities.
+ Many members of the team are SAP Mentors, i.e. professionals who "are role models who differentiate
themselves through the high quality and frequency of their community contributions, their
perspectives, attitudes, and interaction styles. They are subject-matter experts who are passionate
about SAP and share their opinions and insights with the community" (Source: https://wiki.sdn.sap.com/wiki/display/SAPMentors/SAP+Mentor+Initiative+FAQs).
In addition, team member David Pollak runs the Lift project, and is an active member of the
Lift and Scala communities.
  
- The important role that the community plays is also evident in the number of ESME clients
that are now available (ABAP, VBA, Java, Javascript, etc.) that were contributed by the community
and which are either available in the Google Code repository (http://code.google.com/p/esmeproject/)
or on the ESME blog (http://blog.esme.us/).
+ The important role that the community plays is also evident in the number of available ESME
clients (ABAP, VBA, Java, Javascript, etc.) that were contributed by the community and which
are either available in the Google Code repository (http://code.google.com/p/esmeproject/)
or on the ESME blog (http://blog.esme.us/).
-   
- The community has been active in guiding the features that were developed and which are
currently being planned for future releases. 
  
  == Core Developers ==
  David Pollak (most of the Scala code)
@@ -54, +50 @@

  Anne Kathrine Petterøe (some HTML)
  
  == Alignment ==
- ESME aligns well with ASF projects utilizing J2EE infrastructure such as Tomcat. Of particular
relevance are projects such as Lucene (which is used for searches in messages) and Apache
Maven. Key libraries used include Lift and Compass, both Apache-licensed projects. ESME does
not use any GPL code.
+ ESME aligns well with ASF projects utilizing J2EE infrastructure such as Tomcat. Of particular
relevance are projects such as Lucene and Maven. Key libraries used include Lift and Compass,
both of them Apache-licensed projects. ESME does not use any GPL code.
  
- Although ESME has come from the SAP community and has SAP-specific extensions, the core
server code will always be designed to run on any J2EE-compliant server. SAP- (or other vendor-)
specific extensions will always be implemented as modular plug-ins, so as not to create a
dependency on SAP or any other vendor.
+ Although ESME orginated within the SAP community and has SAP-specific extensions, the core
server code is and will continue to be designed to run on any J2EE-compliant server. SAP-
(or other vendor-) specific extensions will be implemented as modular plug-ins, so as not
to create a dependency on SAP or any other vendor.
  
  == License ==
  The ESME codebase is Apache 2.0 licensed, and currently hosted at Google Code.
@@ -64, +60 @@

  = Known Risks / Avoiding the Warning Signs =
  
  == Orphaned Products ==
- Most of the active developers would like to become "Committers" and have a long term interest
to develop and maintain the code. 
+ Most of the active developers aim to become Apache committers and have a long term interest
in developing and maintaining the code. 
  
- Most of the Scala and Lift knowledge for the ESME server resides with David Pollak at the
present time, although Darren Hague, Vassil Dichev, Mrinal Wadhwa and others have all spent
time working with the server code. If David were to leave the project, this would significantly
affect the pace of server-side development. One of the reasons for coming to the Apache Software
Foundation is to help bring in more developers who interested in using ESME to learn or polish
their Scala & Lift skills, and this would in time mitigate the dependence on David's knowledge.
Another mitigation is that the Scala and Lift communities have active and helpful mailing
lists for any queries that the ESME team may have.
+ Most of the Scala and Lift knowledge for the ESME server currently resides with David Pollak.
If David were to leave the project, this would significantly affect the pace of server-side
development. However, Darren Hague, Vassil Dichev, Mrinal Wadhwa and others have all spent
time working with the server code and could continue the work in David's absence, albeit more
slowly. In addition, we hope that joining the Apache Software Foundation will help bring in
more developers who may be interested in using ESME to learn or polish their Scala & Lift
skills. In time, this would mitigate the project's dependence on David's knowledge. Another
mitigating factor is that the Scala and Lift communities have active and helpful mailing lists
for any queries that the ESME team may have.
  
  == Inexperience with Open Source ==
+ As a lead developer, David Pollak has significant experience with open-source projects including
Lift, Social Fabric, and others. His guidance has been extremely useful in ensuring we use
libraries with Apache-compatible licenses. Although many members of the team have no prior
open source committer experience, they have become familiar with the open source approach
through their involvement with ESME, which was community-based from the start, and moved source
control and issue tracking into the open on Google Code in September. Moving to the Apache
Software Foundation would enable the team to learn  more about open source project governance
and to correct bad habits such as a tendency to use our private Google group for discussion
and a tendency not to record minutes during our team conference calls.
- 
- As a lead developer, David Pollak has long experience in open-source projects including
Lift, social fabric, etc. His guidance has been extremely useful so far in keeping us to Apache-compatible
licenses for any libraries we use. For many of the team, however, this is their first open-source
project as a committer. In mitigation, the project has been community-based from the start,
and moved source control and issue tracking into the open on Google Code in September. One
of the benefits of moving to the Apache Software Foundation is to learn  more about open source
project governance and to correct some of our bad habits (e.g. a tendency to use our private
Google group for discussion and a tendency not to record minutes during our team conference
calls).
  
  == Homogenous Developers ==
+ The ESME project team consists of more than just developers. As a result of our focus on
the enterprise, the individuals involved range from process experts, UI designers, bloggers
and marketing gurus to Java developers, Scala developers and ABAP developers who are joined
by a common desire to bring microsharing to the enterprise. 
- 
- ESME is a project that is made up of much more than just developers. Our team reflects our
focus on the enterprise; thus, we have a diverse group of individuals involved ranging from
process experts, UI designers, bloggers, marketing gurus, Java developers, Scala developers,
ABAP developers, etc. We are joined by a common desire to bring microsharing to the enterprise.

    
- The current list of committers includes developers from several different companies plus
many independent volunteers. The committers are geographically distributed across the U.S.,
Europe, and Asia, and they are all experienced with working in a distributed environment.
+ The current list of committers includes developers from several different companies plus
many independent volunteers. The committers are geographically distributed across the U.S.,
Europe, and Asia, and they are all adept at working in a distributed environment.
   
  == Reliance on Salaried Developers ==
+ Some of the initial committers are salaried developers employed by SAP. Like everyone involved
in the project, however, they work on ESME in their own time, and SAP does not own any of
the ESME code. The remaining developers are individual volunteers who are passionate about
technology and the ESME vision.  
- 
- Some of the initial committers are salaried developers employed by SAP, although like everyone
involved in the project they work on ESME in their own time, and SAP does not own any of the
ESME code. The remaining developers are individual volunteers who are passionate about the
technology / vision. The involved companies have reached out and will continue to reach out
in their efforts to build a diverse community. 
  
  == Relationships with Other Apache Products ==
+ ESME uses Maven for its builds, and the current stable release is deployed on Tomcat at
http://esme.us; when running in developer/test mode, it uses Derby as the database; Lucene
is used for the search engine, wrapped by the Apache-licensed Compass library. A closer association
between ESME and Apache OFBiz may also be of interest, since ESME has already proven its ability
to integrate well with SAP and other ERP systems. A tighter integration in this area could
prove beneficial to both projects.
  
- ESME uses Maven for its builds, and the current stable release is deployed on Tomcat at
http://esme.us. When run by developers during testing (mvn jetty:run), Derby is used as the
database. Lucene is used for the search engine, wrapped by the Apache-licensed Compass library.
Of interest might be a closer association between ESME and Apache OFBiz since ESME has already
proven its ability to integrate well with SAP and other ERP systems. A tighter integration
in this area would prove beneficial to both parties.
- 
- == A Excessive Fascination with the Apache Brand ==
+ == An Excessive Fascination with the Apache Brand ==
+ The ESME team will strive to avoid inadvertent abuse of the Apache brand and will work with
the Incubator to ensure the brand policies are respected. Although the impact of the Apache
brand cannot be ignored, it is more a valuable by-product of joining the Apache Software Foundation
than an aim in itself: our primary motivation is to enable ESME to benefit from the Apache
Incubator's experience with the diverse projects with which it has been involved. This would
provide us with direction and help identify ways to improve our processes. 
- 
- One can’t ignore the impact the Apache brand has on a project, but what this project needs
isn’t branding -- it is benefiting from experience accumulated at the Incubator based on
the diverse number / characteristics of those projects with which it has been involved. This
resulting experience would provide us direction and improve our processes. We will be sensitive
to inadvertent abuse of the Apache brand and will work with the Incubator to ensure the brand
policies are respected.
  
  == Maturity of the Lift Framework ==
- The Lift framework, used heavily by the ESME server, is not yet at version 1.0 and has been
subject to breaking changes in the API; in order to get support from the Lift developer community,
ESME must be built against the nightly builds of Lift. In mitigation, the 1.0 release candidate
is expected to be ready at the end of 2008, and stability of the API is expected as a result.
+ The Lift framework, used heavily by the ESME server, has not yet reached version 1.0 and
has been subject to breaking changes in the API; in order to get support from the Lift developer
community, ESME needs to be built using the nightly builds of Lift. However, we expect that
the API will become stable at the end of 2008 when the Lift 1.0 release candidate becomes
available. 
  
  == Documentation ==
   * [http://code.google.com/p/esmeproject/downloads/list]
@@ -104, +95 @@

  
  http://code.google.com/p/esmeproject/source/checkout 
  
- All dependencies have Apache compatible licenses 
+ All dependencies have Apache compatible licenses. 
  
  == Source and Intellectual Property Submission Plan ==
- ESME is based on the Apache 2.0 license. 
+ ESME has already been released under the Apache 2.0 license. 
  
  == External Dependencies ==
- Since ESME is based on the scala-based lift framework, many of the dependecies are to be
taken care of with this framework.  
+ The dependencies all have Apache compatible licenses. These include BSD, CDDL, CPL, MPL
and MIT licensed dependencies. .  
  
  == Required Resources ==
  
@@ -126, +117 @@

  JIRA ESME 
  
  == Initial Committers ==
- 
   * David Pollak   feeder.of.the.bears at gmail.com  
   * Darren Hague   d.hague at sap.com  
   * Vassil Dichev  vdichev at gmail.com  
@@ -134, +124 @@

   
  
  == Affiliations ==
-  
   * Darren Hague  (SAP)
   * Thomas Jung  (SAP)
   * Dick Hirsch  (Siemens SIS) 

---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@incubator.apache.org
For additional commands, e-mail: cvs-help@incubator.apache.org


Mime
View raw message