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 "February2010" by AteDouma
Date Sat, 13 Feb 2010 14:00:46 GMT
Dear Wiki user,

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

The "February2010" page has been changed by AteDouma.
http://wiki.apache.org/incubator/February2010?action=diff&rev1=30&rev2=31

--------------------------------------------------

  
  Next steps:
  
-     * integration with Tika 
+  * integration with Tika
  
  Top 2/3 Issues before graduation:
  
-     * Get our website online, currently it's just a placeholder
+  * Get our website online, currently it's just a placeholder
-     * Prepare some easy-to-run demos to get people interested in Clerezza
+  * Prepare some easy-to-run demos to get people interested in Clerezza
-     * Prepare for a first release 
+  * Prepare for a first release
  
  Signed off by mentor:
  
@@ -58, +58 @@

   * the community is trying to organize a community day to fix current tickets
  
  Issues before graduation :
+ 
   * Do a release
   * Grow community
-  * IP clearance 
+  * IP clearance
  
  Signed off by mentor:
  
@@ -79, +80 @@

  Signed off by mentor:
  
  = Lucene Connector Framework =
- 
  * A brief description of your project, which assumes no knowledge of the project
+ 
-  or necessarily of its field
+  . or necessarily of its field
  
  The Lucene Connectors Framework (LCF) is an effort to build and support an open source framework
for connecting to content repositories like Microsoft Sharepoint and EMC Documentum, amongst
others via a single API.
  
- * A list of the three most important issues to address in the move towards 
+ * A list of the three most important issues to address in the move towards
+ 
-  graduation.
+  . graduation.
  
+ 1. Process initial code grant and incorporate into SVN 2. Do a release 3. Build out a diverse
community.  We have a diverse set of committers already.
- 1. Process initial code grant and incorporate into SVN
- 2. Do a release
- 3. Build out a diverse community.  We have a diverse set of committers already.
  
  * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of
  
@@ -98, +98 @@

  
  * How has the community developed since the last report
  
- N/A: First report.  
+ N/A: First report.
  
  * How has the project developed since the last report.
  
  N/A: First report.
  
  Signed off by mentor: gsingers
- 
- 
  
  = OODT =
  === Description ===
@@ -149, +147 @@

  Signed off by: lresende
  
  = Stonehenge =
- Stonehenge has been incubating since December 2008. Stonehenge is a set of example applications
for Service Oriented Architecture that spans languages and platforms and demonstrates best
practices and interoperability by using currently defined W3C OASIS standard protocols. 
+ Stonehenge has been incubating since December 2008. Stonehenge is a set of example applications
for Service Oriented Architecture that spans languages and platforms and demonstrates best
practices and interoperability by using currently defined W3C OASIS standard protocols.
  
  Since the last report in December 2009, the Stonehenge project has intensified its efforts
around interop testing between the M2 implementation of the claims-based security model extension
to the Stock Trader implementations. Testing between .NET, Axis2/Java and Metro/Glassfish
implementations have uncovered various bugs and were subsequently corrected in the web services
library and the application code. An example of which is an OpenSSO problem in the Metro/Glassfish
implementation that was corrected in the original code base.
  
- '''M2''' 
+ '''M2'''
  
  With testing winding down, the community is preparing to vote and release its M2.  M2 constituted
of expanding the Stocktrader application to use claims-based authentication using an active
and a passive STS for each implementation. We also upgraded the usage of the WS-* specs from
the submitted versions to the ratified one. Extensive documentation work was done in parallel
to describe the new feature set and simplify the installation and configuration process.
  
- '''M3''' 
+ '''M3'''
  
+ The focus remains on creating "micro samples" for many common WS-* scenarios, with the goal
being around creating implementations with low barriers to entry. Discussions are in  progress
about testing frameworks and scenarios of interest. A proposed spec should be presented soon
to the community to seed the discussion around defining M3
- The focus remains on creating "micro samples" for many common WS-* scenarios, with the goal
being around creating implementations with low barriers to entry. Discussions are in 
- progress about testing frameworks and scenarios of interest. A proposed spec should be presented
soon to the community to seed the discussion around defining M3
  
  '''Graduation Map'''
  
@@ -232, +229 @@

  
  '''Notable activities:'''
  
-  * Wookie is now one of 3 products with 100% conformance to the W3C Widgets specification:
see [[http://dev.w3.org/2006/waf/widgets/imp-report/]]
+  * Wookie is now one of 3 products with 100% conformance to the W3C Widgets specification:
see http://dev.w3.org/2006/waf/widgets/imp-report/
-  * Work progressing on conformance to W3C Widgets Interface specification: see [[http://dev.w3.org/2006/waf/widgets-api/imp-report/]]
+  * Work progressing on conformance to W3C Widgets Interface specification: see http://dev.w3.org/2006/waf/widgets-api/imp-report/
   * Wookie Plugins for Elgg and Moodle have migrated to their respective project communities
   * JIRA Activity is increasing as is frequency of patches received from external contributors
   * External contributors engaged in more significant design work such as oAuth/OpenID integration
architecture and inter-widget communication models
@@ -241, +238 @@

  
  '''Items to be resolved before graduation:'''
  
+ Create a release Develop community
- Create a release
- Develop community 
  
- Signed off by mentor: !GavinMcDonald
+ Signed off by mentor: !GavinMcDonald, ate
  
  = Wink =
  Apache Wink is a project that enables development and consumption of REST style web services.
The core server runtime is based on the JAX-RS (JSR 311) standard. The project also introduces
a client runtime which can leverage certain components of the server-side runtime. Apache
Wink will deliver component technology that can be easily integrated into a variety of environments.
@@ -258, +254 @@

   * Added some experimental Google Guice support.
  
   * A few IBM developerWorks articles have recently been written regarding Apache Wink.
-     *  http://www.ibm.com/developerworks/web/library/wa-useapachewink/index.html
+   * http://www.ibm.com/developerworks/web/library/wa-useapachewink/index.html
-     *  http://www.ibm.com/developerworks/web/library/wa-apachewink1/index.html
+   * http://www.ibm.com/developerworks/web/library/wa-apachewink1/index.html
  
  Planned Activity:
  
@@ -269, +265 @@

  
   * Build community
  
- 
  Signed off by mentor: Kevan
  
  = WSRP4J =
- 
  The WSRP4J Project is an implementation of WSRP 1.0 Producer. WSRP is an OASIS specification
that describes a protocol which allows portlets to be accessed remotely using Web Services.
  
  The WSRP4J Project has been adopted by the Portals PMC, while still in the Apache Incubator,
since August 2003, with the intent to graduate as a sub-project of Apache Portals.

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


Mime
View raw message