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 "StanbolProposal" by BertrandDelacretaz
Date Thu, 04 Nov 2010 17:24:14 GMT
Dear Wiki user,

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

The "StanbolProposal" page has been changed by BertrandDelacretaz.
The comment on this change is: FOO -> Stanbol.
http://wiki.apache.org/incubator/StanbolProposal?action=diff&rev1=12&rev2=13

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

  ## page was renamed from FOOproposal
- = Apache FOO incubation proposal =
+ = Apache Stanbol incubation proposal =
  
  == Abstract ==
- Apache FOO is a modular software stack and reusable set of components for semantic content
management.
+ Apache Stanbol is a modular software stack and reusable set of components for semantic content
management.
  
- FOO is a temporary name, the project team is still working on a final name.
+ Stanbol is a temporary name, the project team is still working on a final name.
  
  == Proposal ==
- FOO components are meant to be accessed over RESTful interfaces to provide semantic services
for content management. The current code is written in Java and based on the OSGi modularization
framework, but other server-side languages might be used as well.
+ Stanbol components are meant to be accessed over RESTful interfaces to provide semantic
services for content management. The current code is written in Java and based on the OSGi
modularization framework, but other server-side languages might be used as well.
  
  Applications include extending existing content management systems with semantic features,
and creating new types of content management systems with semantics at their core.
  
@@ -20, +20 @@

   * Interaction: intelligent user interface management and generation 
  
  == Background ==
- FOO comes out of the IKS project (Interactive Knowledge Stack, http://iks-project.eu/),
a research project funded by the European Community (EC) which aims to create a semantic content
management software stack.
+ Stanbol comes out of the IKS project (Interactive Knowledge Stack, http://iks-project.eu/),
a research project funded by the European Community (EC) which aims to create a semantic content
management software stack.
  
  One of the goals of IKS is for its software to survive the 4-year funding period of the
EC, which ends in 2012.
  
- Developing its code in the open at the Apache Software Foundation, and growing a community
before IKS funding runs out, is the best way to ensure the sustainability of the FOO software.
+ Developing its code in the open at the Apache Software Foundation, and growing a community
before IKS funding runs out, is the best way to ensure the sustainability of the Stanbol software.
  
  For more background information, some articles and tutorials on FISE, which was the first
usable IKS module, can be found in the “FISE links” section of http://wiki.iks-project.eu/index.php/FISE
   
@@ -35, +35 @@

  
  Some big companies are using semantic technologies behind the scenes to provide powerful
services, but that technology is usually not accessible to smaller vendors.
  
- FOO aims to bridge these gaps by providing CMS vendors and developers with easy to integrate
semantic components that add value to their offerings.
+ Stanbol aims to bridge these gaps by providing CMS vendors and developers with easy to integrate
semantic components that add value to their offerings.
  
- At the same time, more experimental advanced semantic applications will be built on the
FOO stack, with the medium-term goal of enabling pure semantic-based content management applications.

+ At the same time, more experimental advanced semantic applications will be built on the
Stanbol stack, with the medium-term goal of enabling pure semantic-based content management
applications. 
  
  == Initial Goals ==
   * Import the existing IKS code.
   * Clean up as needed to take advantage of Apache infrastructure (Hudson continuous builds,
etc.)
   * Replace up any dependencies that do not fulfill Apache licensing criteria (we have identifed
just one at this time).
-  * Create the FOO website and migrate IKS website/wiki information to it as needed.
+  * Create the Stanbol website and migrate IKS website/wiki information to it as needed.
   * Make a first release and publicize it to start growing the community.  
  
  == Current Status ==
@@ -52, +52 @@

  
  However, due to the open source way of working adopted by the consortium, an informal meritocracy
has emerged within IKS.
  
- We estimate that adapting to the ASF’s meritocratic way of working will be easy for the
initial set of FOO committers, as the differences to the current way of working are not dramatic.
+ We estimate that adapting to the ASF’s meritocratic way of working will be easy for the
initial set of Stanbol committers, as the differences to the current way of working are not
dramatic.
  
  === Community ===
  The IKS project plan includes an important effort to build a community around the software
that it produces. Several community workshops have already taken place, attended by more than
40 European CMS developers and vendors.
@@ -76, +76 @@

  === Orphaned Products ===
  The IKS code as it stands now might be orphaned when the EC funding of IKS runs out at the
end of 2012.
  
- That’s why we want to move to Apache now, to have a bit more than two years to make FOO
independent of its EC funding.
+ That’s why we want to move to Apache now, to have a bit more than two years to make Stanbol
independent of its EC funding.
  
  === Inexperience with Open Source ===
  The IKS team includes a number of very experienced Open Source developers, along with people
doing their first open source contributions.
@@ -89, +89 @@

  === Reliance on Salaried Developers ===
  Until the end of 2012, the work of IKS consortium members is funded by the consortium, so
there is a “common boss” problem, and we can assume that most or all of that work is salaried.
  
- Moving software development to the ASF, and especially growing a community to include committers
from outside the IKS consortium, should help reduce or eliminate this risk. Even IKS partners
using the software in their products will help reduce the “common boss” problem, as both
the IKS and the partner company will have a need for FOO software.
+ Moving software development to the ASF, and especially growing a community to include committers
from outside the IKS consortium, should help reduce or eliminate this risk. Even IKS partners
using the software in their products will help reduce the “common boss” problem, as both
the IKS and the partner company will have a need for Stanbol software.
  
  === Relationships with Other Apache Products ===
  The IKS software is written as a set of OSGi components and runs on Apache Felix, using
the launcher from Apache Sling.
@@ -245, +245 @@

  
  === Mailing Lists ===
  
-  * FOO-private (moderated subscriptions)
+  * Stanbol-private (moderated subscriptions)
-  * FOO-dev
-  * FOO-commits
+  * Stanbol-dev
+  * Stanbol-commits
  
  === Subversion Directory ===
  
-  * [[http://svn.apache.org/repos/asf/incubator/FOO]]
+  * [[http://svn.apache.org/repos/asf/incubator/Stanbol]]
  
  === Issue Tracking ===
-  * JIRA (FOO) 
+  * JIRA (Stanbol) 
  
  === Other Resources ===
  We will probably request a wiki once the podling is setup, and access to a Hudson continuous
build server.

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


Mime
View raw message