Re: [Vote] accept UIMA as a podling - #2

[Yonik Seeley]

On 9/26/06, Ian Holsman <[EMAIL PROTECTED]> wrote:

[X] +1 Accept UIMA as an Incubator podling
[ ]   0 Don't care
[ ] -1 Reject this proposal for the following reason:


+1  (non binding)

-Yonik

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Vote] accept UIMA as a podling - #2

[Otis Gospodnetic]

[X] +1 Accept UIMA as an Incubator podling
[ ]   0 Don't care
[ ] -1 Reject this proposal for the following reason:

Otis

- Original Message 
From: Ian Holsman <[EMAIL PROTECTED]>
To: general@incubator.apache.org
Sent: Tuesday, September 26, 2006 7:17:37 PM
Subject: [Vote] accept UIMA as a podling  - #2



issues addressed in this release:
1. updated proposal included
2. The first paragraph explains it to a layperson
3. OASIS issue addressed


[ ] +1 Accept UIMA as an Incubator podling
[ ]   0 Don't care
[ ] -1 Reject this proposal for the following reason:


8<---Proposal--8<--


Hello everyone -

We are submitting this proposal to the community for a
new project in the incubator, and look forward to starting to work with
this community.

This is a slightly modified and extended version of the proposal that  
has
already been posted to [EMAIL PROTECTED]  The whole mail  
thread
can be found [http://www.nabble.com/Proposal-for-a-new-incubation- 
project%3A-Unstructured-Information-Management-Architecture---UIMA- 
tf2154324.html here].

If you don't feel like reading the whole thread, the main question  
that came up was:
this is all very well, but what does it really '''do'''?  Attempts to  
answer that question
where made [http://www.nabble.com/Re%3A-Proposal-for-a-new-incubation- 
project%3A-Unstructured-Information-Management-Architecture---UIMA- 
p5986403.html here] and [http://www.nabble.com/Re%3A-Proposal-for-a- 
new-incubation-project%3A-Unstructured-Information-Management- 
Architecture---UIMA-p5987788.html here].  We have since worked some  
of these into the proposal itself.



= Proposal for Incubation Project: Unstructured Information  
Management Architecture - UIMA =

== Abstract ==

UIMA is a component framework for the analysis of unstructured  
content such as text, audio and video.  It comprises an SDK and  
tooling for composing and running analytic components written in Java  
and C++.


== Proposal:  Unstructured Information Management Architecture  
framework ==

Unstructured Information Management applications are software systems  
that analyze large volumes of unstructured information in order to  
discover knowledge that is relevant to an end user.  We propose UIMA,  
a framework and SDK for developing such applications.  An example UIM  
application might ingest plain text and identify entities, such as  
persons, places, organizations; or relations, such as works-for or  
located-at.  UIMA enables such an application to be decomposed into  
components, for example ''"language identification"'' -> ''"language  
specific segmentation"'' -> ''"sentence boundary detection"'' ->  
''"entity detection (person/place names etc.)"''.  Each component  
must implement interfaces defined by the framework and must provide  
self-describing metadata via XML descriptor files.  The framework  
manages these components and the data flow between them.  Components  
are written in Java or C++; the data that flows between components is  
designed for efficient mapping between these languages.  UIMA  
additionally provides capabilities to wrap components as network  
services, and can scale to very large volumes by replicating  
processing pipelines over a cluster of networked nodes.

This framework has already attracted a following among government,  
commercial, and academic institutions who previously developed  
analysis algorithms, but were unable to easily build on each other's  
works, and who want to be able to evolve their applications by  
independently upgrading parts, as better technology becomes  
available.  Applications built with this framework are being used  
with plain text, audio streams, and image/video streams, identifying  
entities and relations, converting speech to text, translating into  
different languages, and determining properties of images.

The UIMA framework runs components in a flow, passing a common data  
object containing unstructured information (free text, audio, video,  
etc.) through the components.  Each component examines the  
unstructured information and data added by other components, and adds  
data of its own.  The framework mandates a standardized form of the  
data being passed, and a standardized form of the interfaces to the  
components.

We propose a project to develop, implement, support and enhance this  
framework (and, over time, other implementations) that comply with  
the UIMA standard (which has been submitted for standardization work  
within [http://www.oasis-open.org OASIS].  Members of this community  
are encouraged to participate in that effort, as well; OASIS has an  
open approach to granting Technical Committee voting rights to  
members of OASIS, described here: http://www.oasis-open.org/ 
committees/process.php#2.4.

The proposal includes both the framework, as well as tools to  
develop, describe, compose and deploy UIMA-based components and  
applications. The initial work will be based on the U

[VOTE] Publish the Woden Milestone 6 release

[John Kaputin (gmail)]

The Woden developer community has voted on and approved a proposal to
release Woden 1.0.0 M6 (Milestone 6). The proposal recieved six +1 votes,
including three from WS PMC members. There were no -1 or 0 votes. The
proposal can be seen at [1].

The six +1 votes were from:
Eran Chinthaka (WS PMC)
Arthur Ryman
Jeremy Hughes (WS PMC)
Oshani Seneviratne
Davanum Srinivas (WS PMC)
John Kaputin

We would now like to request the permission of the Incubator PMC to publish
the Woden M6 archives on the Woden Download page at [2].

Please vote by 1pm EST, Friday September 29th 2006.

[1] Proposal,  
http://mail-archives.apache.org/mod_mbox/ws-woden-dev/200609.mbox/[EMAIL 
PROTECTED]


[2] Download, 
http://people.apache.org/dist/ws/woden/milestones/1.0.0M6-incubating/


Thanks,
John Kaputin

[Vote] accept UIMA as a podling - #2

[Ian Holsman]

issues addressed in this release:
1. updated proposal included
2. The first paragraph explains it to a layperson
3. OASIS issue addressed


[ ] +1 Accept UIMA as an Incubator podling
[ ]   0 Don't care
[ ] -1 Reject this proposal for the following reason:


8<---Proposal--8<--


Hello everyone -

We are submitting this proposal to the community for a
new project in the incubator, and look forward to starting to work with
this community.

This is a slightly modified and extended version of the proposal that  
has
already been posted to [EMAIL PROTECTED]  The whole mail  
thread
can be found [http://www.nabble.com/Proposal-for-a-new-incubation- 
project%3A-Unstructured-Information-Management-Architecture---UIMA- 
tf2154324.html here].


If you don't feel like reading the whole thread, the main question  
that came up was:
this is all very well, but what does it really '''do'''?  Attempts to  
answer that question
where made [http://www.nabble.com/Re%3A-Proposal-for-a-new-incubation- 
project%3A-Unstructured-Information-Management-Architecture---UIMA- 
p5986403.html here] and [http://www.nabble.com/Re%3A-Proposal-for-a- 
new-incubation-project%3A-Unstructured-Information-Management- 
Architecture---UIMA-p5987788.html here].  We have since worked some  
of these into the proposal itself.




= Proposal for Incubation Project: Unstructured Information  
Management Architecture - UIMA =


== Abstract ==

UIMA is a component framework for the analysis of unstructured  
content such as text, audio and video.  It comprises an SDK and  
tooling for composing and running analytic components written in Java  
and C++.



== Proposal:  Unstructured Information Management Architecture  
framework ==


Unstructured Information Management applications are software systems  
that analyze large volumes of unstructured information in order to  
discover knowledge that is relevant to an end user.  We propose UIMA,  
a framework and SDK for developing such applications.  An example UIM  
application might ingest plain text and identify entities, such as  
persons, places, organizations; or relations, such as works-for or  
located-at.  UIMA enables such an application to be decomposed into  
components, for example ''"language identification"'' -> ''"language  
specific segmentation"'' -> ''"sentence boundary detection"'' ->  
''"entity detection (person/place names etc.)"''.  Each component  
must implement interfaces defined by the framework and must provide  
self-describing metadata via XML descriptor files.  The framework  
manages these components and the data flow between them.  Components  
are written in Java or C++; the data that flows between components is  
designed for efficient mapping between these languages.  UIMA  
additionally provides capabilities to wrap components as network  
services, and can scale to very large volumes by replicating  
processing pipelines over a cluster of networked nodes.


This framework has already attracted a following among government,  
commercial, and academic institutions who previously developed  
analysis algorithms, but were unable to easily build on each other's  
works, and who want to be able to evolve their applications by  
independently upgrading parts, as better technology becomes  
available.  Applications built with this framework are being used  
with plain text, audio streams, and image/video streams, identifying  
entities and relations, converting speech to text, translating into  
different languages, and determining properties of images.


The UIMA framework runs components in a flow, passing a common data  
object containing unstructured information (free text, audio, video,  
etc.) through the components.  Each component examines the  
unstructured information and data added by other components, and adds  
data of its own.  The framework mandates a standardized form of the  
data being passed, and a standardized form of the interfaces to the  
components.


We propose a project to develop, implement, support and enhance this  
framework (and, over time, other implementations) that comply with  
the UIMA standard (which has been submitted for standardization work  
within [http://www.oasis-open.org OASIS].  Members of this community  
are encouraged to participate in that effort, as well; OASIS has an  
open approach to granting Technical Committee voting rights to  
members of OASIS, described here: http://www.oasis-open.org/ 
committees/process.php#2.4.


The proposal includes both the framework, as well as tools to  
develop, describe, compose and deploy UIMA-based components and  
applications. The initial work will be based on the UIMA Version 2  
framework code developed by IBM; snapshots of each release of this  
code are currently made available on [http://sourceforge.net/projects/ 
uima-framework SourceForge]. The Source``Forge versions would be  
stabilized in maintenance mode, if we are successful in moving to  
Apache.
The f

Re: [VOTE] OFBiz Test Snapshot Release: 4.0.0 TS3

[robert burrell donkin]

On 9/25/06, David E Jones <[EMAIL PROTECTED]> wrote:


The OFBiz podling (PPMC and community) has reached a consensus
internally approving the 4.0.0 TS3 test snapshot release. We are now
requesting a vote for review and approval from the general Incubator
group and the Incubator PMC.


gpg looks good to me (KEYS imports ok, key is available from public
key servers, signature ok) and sum checks

RAT turned up the following:

***IMPORTANT***
http://svn.apache.org/repos/asf/incubator/ofbiz/trunk/framework/service/src/org/ofbiz/service/rmi/socket/zip/CompressionClientSocketFa,
ctory.java, 
http://svn.apache.org/repos/asf/incubator/ofbiz/trunk/framework/service/src/org/ofbiz/service/rmi/socket/zip/CompressionInputStream.java
, 
http://svn.apache.org/repos/asf/incubator/ofbiz/trunk/framework/service/src/org/ofbiz/service/rmi/socket/zip/CompressionOutputStream.java,
framework/service/src/org/ofbiz/service/rmi/socket/zip/CompressionServerSocketFactory.java,
framework/service/src/org/ofbiz/service/rmi/socket/zip/CompressionSocket.java,
http://svn.apache.org/repos/asf/incubator/ofbiz/trunk/framework/service/src/org/ofbiz/service/rmi/socket/zip/CompressionServerSocket.java
and 
http://svn.apache.org/repos/asf/incubator/ofbiz/trunk/framework/service/src/org/ofbiz/service/rmi/socket/zip/CompressionConstants.java
do not appear to be licensed under an OSI compliant license. IMO the
terms are badly drafted and discriminate against the profession or
vocation of comedian (no laughing matter ;-) basically anyone using
the software must agree not to use the software to make fun of sun.
but IANAL and this needs to be raised on legal-discuss.


http://svn.apache.org/repos/asf/incubator/ofbiz/trunk/applications/content/webapp/content/WEB-INF/pagedefs/cms/CMSSiteFind.xml
is a bit of a mystery and seems to be lacking source

no license headers (check whether they are apache source)
http://svn.apache.org/repos/asf/incubator/ofbiz/trunk/applications/content/webapp/content/images/agincutil.js
http://svn.apache.org/repos/asf/incubator/ofbiz/trunk/applications/content/webapp/content/images/composite.js
http://svn.apache.org/repos/asf/incubator/ofbiz/trunk/applications/content/webapp/content/images/contentForum.css
http://svn.apache.org/repos/asf/incubator/ofbiz/trunk/applications/product/webapp/facility/facility/batchPrintMarkAsAccepted.ftl
http://svn.apache.org/repos/asf/incubator/ofbiz/trunk/framework/common/data/GeoData_ES.xml
http://svn.apache.org/repos/asf/incubator/ofbiz/trunk/framework/images/webapp/images/ecommain.css
http://svn.apache.org/repos/asf/incubator/ofbiz/trunk/framework/images/webapp/images/maincss.css
http://svn.apache.org/repos/asf/incubator/ofbiz/trunk/framework/images/webapp/images/tabstyles.css
http://svn.apache.org/repos/asf/incubator/ofbiz/trunk/framework/webtools/webapp/webtools/UomReport.xml
http://svn.apache.org/repos/asf/incubator/ofbiz/trunk/framework/webtools/webapp/webtools/includes/datepicker.js

i'm worried about
http://svn.apache.org/repos/asf/incubator/ofbiz/trunk/applications/pos/dtd/jcl.dtd.
DTD are a a PITA but it's a document and we need permission to
distribute.

http://svn.apache.org/repos/asf/incubator/ofbiz/trunk/applications/product/config/ProductEntityLabels_fr.properties
is licensed under Eclipse Public License v1.0. the draft third part
licensing policy allows this in only binary form due to a reciprocity
clause in the license. i'm a little worried by the fact that this is
the only localisation file which is not ASL'd.


http://svn.apache.org/repos/asf/incubator/ofbiz/trunk/framework/appserver/templates/weblogic81/startOFBizServer.cmd
and
http://svn.apache.org/repos/asf/incubator/ofbiz/trunk/framework/appserver/templates/weblogic81/startOFBizServer.sh
lack license files and appear to be similar to standard weblogic
startup scripts. this could be perfectly innocent (there are only a
few ways to start the server) and hopefully not an unfortunate
unlicensed derivative work...

ofbiz/framework/data/derby/ in the distribution contains some logs and
other bits and bats which aren't in subversion and i suspect didn't
really want to get released. same goes for ofbiz/framework/logs/

http://svn.apache.org/repos/asf/incubator/ofbiz/trunk/framework/images/webapp/images/calendar.html
and
http://svn.apache.org/repos/asf/incubator/ofbiz/trunk/framework/images/webapp/images/calendar1.js
terms probably needs to be noted in LICENSE

http://svn.apache.org/repos/asf/incubator/ofbiz/trunk/framework/images/webapp/images/calendarTable.css,
http://svn.apache.org/repos/asf/incubator/ofbiz/trunk/framework/images/webapp/images/combobox.js,
http://svn.apache.org/repos/asf/incubator/ofbiz/trunk/framework/images/webapp/images/fieldlookup.js
and 
http://svn.apache.org/repos/asf/incubator/ofbiz/trunk/framework/images/webapp/images/calendarstyles.css
appear to be associated with above but lack license headers. need to
check the right license.

http://svn.apache.org/repos/asf/incubator/ofbiz/trunk/framework/workflow/dt

Re: [VOTE] OFBiz Test Snapshot Release: 4.0.0 TS3

[robert burrell donkin]

On 9/25/06, robert burrell donkin <[EMAIL PROTECTED]> wrote:

On 9/25/06, Justin Erenkrantz <[EMAIL PROTECTED]> wrote:



> http://svn.apache.org/repos/asf/httpd/httpd/trunk/NOTICE


i was going to use the notice as an example of good practice until i
noted that it lacked the header which is now recommended. if it gains
one soon, let me know so i can use it as an example.

- robert

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Release request] Trinidad podling maven2 plugins

[robert burrell donkin]

On 9/26/06, Matthias Wessendorf <[EMAIL PROTECTED]> wrote:

The Trinidad community voted on and approved to release the the maven2
plugins as a milestone1 release. These plugins are required for the maven2
build of the "core" code of the Trinidad Podling. To fulfill the incubator
guides, we like to ask you guys, the Incubator PMC, for a permission to release
those maven plugins.

The vote has been tracked at [1], see it for the results.
(three binding +1 and one non-binding +1)

The plugins are documented at [2] and our release notes inculde
the bugs that have been addressed ([3]).

The plugins are available as source and bin inside the incubator
m2 repo (see [4]).


+1

BTW strongly consider adding detached signatures. it helps to prevent
tampering. there's an easy script in committers which does this.

- robert

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] OFBiz Test Snapshot Release: 4.0.0 TS3

[robert burrell donkin]

On 9/26/06, David E Jones <[EMAIL PROTECTED]> wrote:


On Sep 25, 2006, at 10:56 PM, robert burrell donkin wrote:

> (FYI a source distribution is required but i'm assume that you know
> how to svn export)

Do you mean a separate source distribution is needed?


many would argue that for open source, the source distribution is the
release: binaries are just for convenience :-)

here are a couple of pragmatic (as well as the philosophical) reasons
to issue source distributions:

1 downstream repackagers prefer to work from a pure source
distribution. typically, they will take the source distribution and
apply patches then build according to their system and then package.
helping downstream distributors helps acceptance of the project.

2 source distributions encourage developers. new developers are needed
to keep apache projects healthy.


In the past, as with this test snapshot, we have just included the
source and binary in the same archive. This has suited us well as
probably 70-80% of ofbiz is not compiled, ie script, configuration,
etc files.


s binary distribution is any distribution that is not just a source
export. it's not uncommon for binary distributions from apache to
contain source. so, that sounds fine for your binary distribution.

- robert

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: podcast on Jini

[david reid]

Jim Hurley wrote:
> Don't know if this is acceptable to send to this list -- so my
> apologies if I'm stepping in it here :-obut I know some people
> on the list may not be that familiar with Jini and so I thought
> I'd recommend a recent series of podcasts that the JavaPosse
> is doing on Jini (and the computecycles.dev.java.net project -
> which utilitzes Jini). Van has a nice way of explaining things,
> and so if you like podcasts, this may be of interest to you:
> 
> "Interview with Van Simmons about Jini and ComputeCycles"
> 
>   * Part 1  (Sep 17):
>  
>   * Part 2  (Sep  24):
> 
>   * Part 3  (coming...)
> 
> He also touches on our Jini Apache incubator Proposal, but is
> not intimate with the details of where we are in the process...
> so primarily just comments on how it's a "good thing"  :-)

Probably worth just pointing out that Rich Bowen and I do feathercast -
podcasts about the ASF and it's projects!

We've done one about Harmony already (and in fact hoping to catch up
with Geir to get a progress update in Autin) and incubator projects are
certainly fair game.

All you need do is contact us. Best address is
[EMAIL PROTECTED] We interview over Skype if distance is
an issue or face to face when we can.

-- 
david

http://feathercast.org/

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release ServiceMix 3.0-incubating

[Davanum Srinivas]

+1 (binding).

-- dims

On 9/26/06, Guillaume Nodet <[EMAIL PROTECTED]> wrote:

Would it be possible for an incubator PMC member to vote on this release ?
We still miss one +1,

Thanks,
Guillaume Nodet

Guillaume Nodet wrote:
> The ServiceMix community voted on and approved to release
> the 3.0-incubating version [1].  Pursuant to the Releases section of
> the Incubation Policy and we would now like to request the
> permission of the Incubator PMC to publish this release.
> The release / download page is available at [2]:
>
> [1]
> 
http://www.nabble.com/-VOTE--ServiceMix-3.0-M2-incubating-%28second-try%29-tf2251652.html
> [2] http://servicemix.goopen.org/site/servicemix-30.html
>
>
> Cheers,
> Guillaume Nodet
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Tomcat's servlet code in Felix (WAS: Re: Podling Release Requirement)

[Richard S. Hall]

Justin Erenkrantz wrote:
  

It also seems that Felix has forked Tomcat's servlet code - which is okay:

http://svn.apache.org/repos/asf/incubator/felix/trunk/javax.servlet/src/main/java/javax/servlet/GenericServlet.java

However, the copyright years have been altered from the original file
- removing 2004 and adding 2005 - which isn't okay:

http://svn.apache.org/repos/asf/tomcat/servletapi/branches/servlet2.3-jsp1.2-tc4.x/src/share/javax/servlet/GenericServlet.java


(Ideally, Felix should resync with Tomcat once they update their
license block to remove the copyright years; but Tomcat may not be
updating Servlet 2.3.  I'm unsure if an ASF project can relicense
forked code from another project - I'll ask on [EMAIL PROTECTED])



I am a little confused as to the exact solution to Felix' use of 
Tomcat's javax.servlet code.


The reason why the copyright was changed is because the subproject is a 
derivative work based on Tomcat's javax.servlet 2.4 code. The subproject 
downgraded javax.servlet 2.4 to 2.1, which is the version used by the 
OSGi HTTP Service. BJ Hargrave did the downgrade and said he used the 
servlet 2.4 code because it was licensed under Apache license v2, where 
servlet 2.3 and older was under Apache license v1.


Because servlet 2.1 is required, I doubt there will ever be a re-syncing 
of code with Tomcat.


So, what is the appropriate thing to do here? Leave the header unchanged 
or to change it? If we are not supposed to change it, then we can easily 
revert to the old header, but it seems misleading since we modified it. 
If we are supposed to change it, then I imagine we should change it to 
reflect the header at http://www.apache.org/legal/src-headers.html.


Clarification is desired.

-> richard

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Tomcat's servlet code in Felix (WAS: Re: Podling Release Requirement)

[Upayavira]

Richard S. Hall wrote:
> 
>> Justin Erenkrantz wrote:
>>  
>>> It also seems that Felix has forked Tomcat's servlet code - which is
>>> okay:
>>>
>>> http://svn.apache.org/repos/asf/incubator/felix/trunk/javax.servlet/src/main/java/javax/servlet/GenericServlet.java
>>>
>>>
>>> However, the copyright years have been altered from the original file
>>> - removing 2004 and adding 2005 - which isn't okay:
>>>
>>> http://svn.apache.org/repos/asf/tomcat/servletapi/branches/servlet2.3-jsp1.2-tc4.x/src/share/javax/servlet/GenericServlet.java
>>>
>>>
>>>
>>> (Ideally, Felix should resync with Tomcat once they update their
>>> license block to remove the copyright years; but Tomcat may not be
>>> updating Servlet 2.3.  I'm unsure if an ASF project can relicense
>>> forked code from another project - I'll ask on [EMAIL PROTECTED])
>>> 
> 
> I am a little confused as to the exact solution to Felix' use of
> Tomcat's javax.servlet code.
> 
> The reason why the copyright was changed is because the subproject is a
> derivative work based on Tomcat's javax.servlet 2.4 code. The subproject
> downgraded javax.servlet 2.4 to 2.1, which is the version used by the
> OSGi HTTP Service. BJ Hargrave did the downgrade and said he used the
> servlet 2.4 code because it was licensed under Apache license v2, where
> servlet 2.3 and older was under Apache license v1.
> 
> Because servlet 2.1 is required, I doubt there will ever be a re-syncing
> of code with Tomcat.
> 
> So, what is the appropriate thing to do here? Leave the header unchanged
> or to change it? If we are not supposed to change it, then we can easily
> revert to the old header, but it seems misleading since we modified it.
> If we are supposed to change it, then I imagine we should change it to
> reflect the header at http://www.apache.org/legal/src-headers.html.
> 
> Clarification is desired.

Or, should we dig an ASL 1 licensed tomcat servlet spec from SVN/CVS and
relicense it as AL2.0?

Upayavira

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

podcast on Jini

[Jim Hurley]

Don't know if this is acceptable to send to this list -- so my
apologies if I'm stepping in it here :-obut I know some people
on the list may not be that familiar with Jini and so I thought
I'd recommend a recent series of podcasts that the JavaPosse
is doing on Jini (and the computecycles.dev.java.net project -
which utilitzes Jini). Van has a nice way of explaining things,
and so if you like podcasts, this may be of interest to you:

"Interview with Van Simmons about Jini and ComputeCycles"

  * Part 1  (Sep 17):
 
  * Part 2  (Sep  24):

  * Part 3  (coming...)

He also touches on our Jini Apache incubator Proposal, but is
not intimate with the details of where we are in the process...
so primarily just comments on how it's a "good thing"  :-)

-Jim

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [JiniProposal] Choosing a new name...

[Jim Hurley]

Thanks Geir.

It's certainly a viable alternative plan, but we're trying to match  
up with

the history and culture we've created in the Jini Community of open
involvement, so it seems like goodness to engage more broadly and
give people a say.

We've had a number of good names submitted -- but I'm guessing the
winner is still out there... so please consider submitting a name.  
Thanks.


Many of the names submitted so far have played off the "Jini" name or
space (e.g., the "Eden example below). An alternate direction is to just
propose something different and fun (which might just be a cool name
and not tied at all to the technology).

We'll welcome all ideas through today and then start the vetting  
process.


Thanks again -Jim



On Sep 24, 2006, at 7:48 PM, Geir Magnusson Jr wrote:

While we all appreciate you inviting the community to help, I also
encourage the proposers to  consider choosing a name among yourselves.

There's nothing wrong with that, and as it's the project you are
proposing, it's natural that you can choose the name.

geir




Jim Hurley wrote:

Hi all-

I apologize for the gap in communication on our Proposal.  Following
my summary post:



and list discussion, I believe choosing a new name for the project  
and

then updating our Proposal are the last bits before we can ask for an
incubator vote.

We've been fairly consumed by our "Jini Community Meeting" event
last week in Brussels (see the Jini.org front page for links to  
info from
the event), so again, I'm sorry for not getting this closed sooner  
so we

can move on and (hopefully) get going.

As we're all too familiar with :-o  -- picking a name (that  
everyone likes)
is hard. In order to get as many creative ideas as possible, and  
have a
defined process (so that it doesn't drag out) for making a  
decision...

we'd like to:

* Gather Name Ideas --  through Tuesday, Sept 26
Ask both the Apache incubator and Jini Community for name
ideas. In order to not consume the lists with name mail,  
if you

could send me, [EMAIL PROTECTED] your name ideas, and
optionally your reasoning/meaning behind the name. I'd really
appreciate it. For example:
 name: "Eden"   -- reminds me of Barbara Eden from "I  
Dream of

 Genie"!   ;-)

   * Choose the New Name (voting) -- Thursday, Sept 28  through
  Monday, Oct 2
   We'll take the list of ideas, make sure they pass TM, etc and
   select a "top ten choices" that we'll put up for an open  
vote. Whatever
   name is supported the most by the vote is the one we'll  
choose for

   the project.

If these dates feel too tight we can be a little pliable, but we  
are hoping
to update our Proposal and have the voting (start) before the  
upcoming

ApacheCon if possible.

There's obviously an endless amount of ways to go about picking a  
name...
this might not be the best, but we wanted to engage the Apache  
incubator

and our existing Community in contributing. We're betting that with
everyone's creative juices flowing - we're going to collectively  
come up
with a cool name that represents the project well and that most  
people like.

I hope you'll give us your support.

thanks -Jim

Re: [VOTE] OFBiz Test Snapshot Release: 4.0.0 TS3

[David E Jones]

On Sep 25, 2006, at 10:56 PM, robert burrell donkin wrote:


(FYI a source distribution is required but i'm assume that you know
how to svn export)


Do you mean a separate source distribution is needed?

In the past, as with this test snapshot, we have just included the  
source and binary in the same archive. This has suited us well as  
probably 70-80% of ofbiz is not compiled, ie script, configuration,  
etc files.


-David


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release ServiceMix 3.0-incubating

[Guillaume Nodet]

Would it be possible for an incubator PMC member to vote on this release ?
We still miss one +1,

Thanks,
Guillaume Nodet

Guillaume Nodet wrote:
> The ServiceMix community voted on and approved to release
> the 3.0-incubating version [1].  Pursuant to the Releases section of 
> the Incubation Policy and we would now like to request the
> permission of the Incubator PMC to publish this release.
> The release / download page is available at [2]:
>
> [1]
> http://www.nabble.com/-VOTE--ServiceMix-3.0-M2-incubating-%28second-try%29-tf2251652.html
> [2] http://servicemix.goopen.org/site/servicemix-30.html
>
>
> Cheers,
> Guillaume Nodet
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>   

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[Release request] Trinidad podling maven2 plugins

[Matthias Wessendorf]

The Trinidad community voted on and approved to release the the maven2
plugins as a milestone1 release. These plugins are required for the maven2
build of the "core" code of the Trinidad Podling. To fulfill the incubator
guides, we like to ask you guys, the Incubator PMC, for a permission to release
those maven plugins.

The vote has been tracked at [1], see it for the results.
(three binding +1 and one non-binding +1)

The plugins are documented at [2] and our release notes inculde
the bugs that have been addressed ([3]).

The plugins are available as source and bin inside the incubator
m2 repo (see [4]).


Thanks
Matthias


[1] 
http://mail-archives.apache.org/mod_mbox/incubator-adffaces-dev/200608.mbox/ajax/[EMAIL
 PROTECTED]
[2] http://incubator.apache.org/adffaces/plugins/index.html
[3] http://wiki.apache.org/myfaces/ADF_Faces/plugins_release_candidate_m1
[4] 
http://people.apache.org/repo/m2-incubating-repository/org/apache/myfaces/trinidadbuild/



--
Matthias Wessendorf
http://tinyurl.com/fmywh

further stuff:
blog: http://jroller.com/page/mwessendorf
mail: mwessendorf-at-gmail-dot-com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]