You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by Marshall Schor <ms...@schor.com> on 2007/01/22 22:27:40 UTC

Writing something about the Sandbox

Michael - could you write something about the Sandbox on Apache?  
Purpose, what's in it.  Something short - to be included in the docbook 
docs.

-Marshall

Re: Writing something about the Sandbox

Posted by Thilo Goetz <tw...@gmx.de>.
Marshall Schor wrote:
> Thilo Goetz wrote:
>> Here's what the Lucene folks say about their sandbox:
>>
>> "Lucene project also contains a workspace, Lucene Sandbox, that is 
>> open to all Lucene committers, as well as a few other developers. The 
>> purpose of the Sandbox is to host various third party contributions, 
>> and to serve as a place to try out new ideas and prepare them for 
>> inclusion into the core Lucene distribution.
>> Users are free to experiment with the components developed in the 
>> Sandbox, but Sandbox components will not necessarily be maintained, 
>> particularly in their current state."
>>
>> The Lucene sandbox is part of every Lucene release, it just comes with 
>> this disclaimer.  Since we've been modeling our sandbox on theirs, 
>> this is what we're aiming for.  I don't think we should add the 
>> sandbox to the first release, but after that, why not.  <snip>
>>
> 
> I would rather have a place for things we agree should be part of the 
> release (let call that something other than Sandbox), and *also* have a 
> Sandbox.
> 
> Things going into the release would have to get some consensus that they 
> should be in the release, and then also pass any other
> "release" requirements (if any).
> Things in the sandbox would have a lower bar on consensus, etc.
> 
> An example:  if there were two different, overlapping approaches to 
> something (a tool, an annotator, etc.) where one was clearly preferred 
> for whatever reasons by the current committers / (P)PMC, and the other 
> might have some questionable "clouds" hanging over it, still waiting 
> some kind of resolution, I would prefer to have these separate.
> 
> This allows us to take in things into the Sandbox and have them evolve 
> over time into things we feel good about releasing, which is a good 
> thing in my opinion :-)
> 
> -Marshall

I still don't quite understand what it is that you want.  Correct me if 
I'm wrong, but here's what I think you're saying.

* you don't want a Lucene style sandbox that's both low bar for entry 
and goes in the distribution

* you want some place with a low bar for entry, and the stuff doesn't go 
in the distribution

* once thing's from that other place (I'm not calling it a sandbox, 
that's a term I reserve for the Lucene variety) are good enough, you 
want to include them in the regular distribution, with no distinction

Did I get that right?

The Lucene model has the advantage that less sophisticated users can use 
the stuff from the sandbox without having to compile it.  That's what we 
want, as people should try the things from the sandbox and give us 
feedback.  If we don't include that sandbox stuff in distributions, we 
are encouraging a parallel universe where each tiny component has its 
own build instructions, its own release cycle and whatnot.  We're not 
such a big development community that there is any danger of anything 
totally wild coming in, not even through the sandbox.  Again, look at 
Lucene.   They're much bigger than we are, and managing quite well.  If 
that kind of thing ever becomes a problem, we can still change the policy.

--Thilo


Re: Writing something about the Sandbox

Posted by Marshall Schor <ms...@schor.com>.
Thilo Goetz wrote:
> Here's what the Lucene folks say about their sandbox:
>
> "Lucene project also contains a workspace, Lucene Sandbox, that is 
> open to all Lucene committers, as well as a few other developers. The 
> purpose of the Sandbox is to host various third party contributions, 
> and to serve as a place to try out new ideas and prepare them for 
> inclusion into the core Lucene distribution.
> Users are free to experiment with the components developed in the 
> Sandbox, but Sandbox components will not necessarily be maintained, 
> particularly in their current state."
>
> The Lucene sandbox is part of every Lucene release, it just comes with 
> this disclaimer.  Since we've been modeling our sandbox on theirs, 
> this is what we're aiming for.  I don't think we should add the 
> sandbox to the first release, but after that, why not.  <snip>
>

I would rather have a place for things we agree should be part of the 
release (let call that something other than Sandbox), and *also* have a 
Sandbox.

Things going into the release would have to get some consensus that they 
should be in the release, and then also pass any other
"release" requirements (if any). 

Things in the sandbox would have a lower bar on consensus, etc.

An example:  if there were two different, overlapping approaches to 
something (a tool, an annotator, etc.) where one was clearly preferred 
for whatever reasons by the current committers / (P)PMC, and the other 
might have some questionable "clouds" hanging over it, still waiting 
some kind of resolution, I would prefer to have these separate.

This allows us to take in things into the Sandbox and have them evolve 
over time into things we feel good about releasing, which is a good 
thing in my opinion :-)

-Marshall

RE: Writing something about the Sandbox

Posted by Pascal Coupet <pa...@temis.com>.
Hi Guys,

I'm following since a while the mailing list and I'm impressed by your
pace of work! This is my first contribution. Just some thoughts... 

It seems to me that the project can contains 3 levels of codes. The
framework itself, of course, which is the main part, some directly
related subprojects which are important but not mandatory to use the
framework and small contributions in the spirit of a sandbox.

One of the key requirements for a framework in my opinion is to provide
a great compatibility across releases. A good way to enforce this is to
avoid packing with it all needed tools because compatibility problems
may show up late in the development cycle or not show up at all.  

Subprojects are strongly related to the framework but can evolve at a
different pace and be handled by different people. They are not
mandatory to use the framework. Apache HTTP has by example a lot of
modules for this. 
We can imagine a lot of subprojects like tools (CPE GUI), tutorials,
sources, annotators, consumers, Connector for non Java objects (Perl
annotators or sources ...)...  

The sandbox is where I can upload some interesting code without a
quality level and support. It's a nice place to get a starting point for
some developments that may at some point end into the product or branch
into another project. 

Now if I take my user hat, I really dislike having to download several
files and do some configuration to test an open source project! So it
makes a lot of sense to have a binary distribution including the
framework and at least a reasonable set of sub-projects providing me the
capability to start interesting stuff out of the box. This split should
be clear in the files organization so it's easy by example to repackage
just the framework. I don't feel that the sandbox part should be part of
the default distribution. 

Pascal

-----Original Message-----
From: lally.adam@gmail.com [mailto:lally.adam@gmail.com] On Behalf Of
Adam Lally
Sent: Thursday, February 01, 2007 1:42 PM
To: uima-dev@incubator.apache.org
Subject: Re: Writing something about the Sandbox

On 2/1/07, Thilo Goetz <tw...@gmx.de> wrote:
> Here's what the Lucene folks say about their sandbox:
>
> "Lucene project also contains a workspace, Lucene Sandbox, that is
open
> to all Lucene committers, as well as a few other developers. The
purpose
> of the Sandbox is to host various third party contributions, and to
> serve as a place to try out new ideas and prepare them for inclusion
> into the core Lucene distribution.
> Users are free to experiment with the components developed in the
> Sandbox, but Sandbox components will not necessarily be maintained,
> particularly in their current state."
>
> The Lucene sandbox is part of every Lucene release, it just comes with
> this disclaimer.  Since we've been modeling our sandbox on theirs,
this
> is what we're aiming for.  I don't think we should add the sandbox to
> the first release, but after that, why not.
>


I did grab the lucene distribution and I do see you are right, there
is a contrib folder with the sandbox components.  (The quote you
posted, to me, doesn't imply that, but I see it's the case.)

However, does this always contain ALL sandbox compoments?  I see that
there are some folders in their sandbox SVN that are not in the
contrib directory of the Lucene 2.0.0 release (e.g., db, gdata-server,
javascript).

So perhaps there is after all a case-by-case decision made on each
sandbox component deciding when it is ready to be released?

-Adam

Re: Writing something about the Sandbox

Posted by Adam Lally <al...@alum.rpi.edu>.
On 2/1/07, Thilo Goetz <tw...@gmx.de> wrote:
> Here's what the Lucene folks say about their sandbox:
>
> "Lucene project also contains a workspace, Lucene Sandbox, that is open
> to all Lucene committers, as well as a few other developers. The purpose
> of the Sandbox is to host various third party contributions, and to
> serve as a place to try out new ideas and prepare them for inclusion
> into the core Lucene distribution.
> Users are free to experiment with the components developed in the
> Sandbox, but Sandbox components will not necessarily be maintained,
> particularly in their current state."
>
> The Lucene sandbox is part of every Lucene release, it just comes with
> this disclaimer.  Since we've been modeling our sandbox on theirs, this
> is what we're aiming for.  I don't think we should add the sandbox to
> the first release, but after that, why not.
>


I did grab the lucene distribution and I do see you are right, there
is a contrib folder with the sandbox components.  (The quote you
posted, to me, doesn't imply that, but I see it's the case.)

However, does this always contain ALL sandbox compoments?  I see that
there are some folders in their sandbox SVN that are not in the
contrib directory of the Lucene 2.0.0 release (e.g., db, gdata-server,
javascript).

So perhaps there is after all a case-by-case decision made on each
sandbox component deciding when it is ready to be released?

-Adam

Re: Writing something about the Sandbox

Posted by Thilo Goetz <tw...@gmx.de>.
Here's what the Lucene folks say about their sandbox:

"Lucene project also contains a workspace, Lucene Sandbox, that is open 
to all Lucene committers, as well as a few other developers. The purpose 
of the Sandbox is to host various third party contributions, and to 
serve as a place to try out new ideas and prepare them for inclusion 
into the core Lucene distribution.
Users are free to experiment with the components developed in the 
Sandbox, but Sandbox components will not necessarily be maintained, 
particularly in their current state."

The Lucene sandbox is part of every Lucene release, it just comes with 
this disclaimer.  Since we've been modeling our sandbox on theirs, this 
is what we're aiming for.  I don't think we should add the sandbox to 
the first release, but after that, why not.

Thilo Goetz wrote:
> 
> 
> Marshall Schor wrote:
>> Other projects seem to treat the sandbox differently than as described 
>> below; I would prefer to keep the sandbox
>> aligned with usual Apache concepts for it, which seem to be - it's a 
>> subproject for potential new additions to the project or to 
>> subprojects of it, and things here are works in progress, with no 
>> guarantee that they will ever be promoted to
>> an official release of the project its subprojects.
>>
>> We should (in my opinion) establish other subprojects which can do 
>> releases, etc., beyond the sandbox, for things like
>> annotators, parsers, consumers, and tooling.   Things would graduate
>>> from the sandbox into one of these subprojects (or into the main Apache 
>> UIMA project) when we want to convey some higher level of support / 
>> testing / acceptance, and to have official "distributions/releases" for.
>> I think that the sandbox should not be a subproject which does 
>> "distributions/releases".  This allows more freedom
>> to tinker, which I think is a valuable thing to have as some part of 
>> the project.
>>
>> -Marshall
>>
>> Michael Baessler wrote:
>>> Marshall Schor wrote:
>>>> Michael - could you write something about the Sandbox on Apache?  
>>>> Purpose, what's in it.  Something short - to be included in the 
>>>> docbook docs.
>>>>
>>>> -Marshall
>>>>
>>>>
>>> So you want to include a short paragraph about the sandbox to the 
>>> docbook of the UIMA 2.1 release. I would only add something similar 
>>> as we have on the web:
>>>
>>>    The UIMA sandbox is a workspace that is open to all UIMA committers
>>>    and developers who would like to contribute code and join the UIMA
>>>    developer community. The sandbox is designed to host analysis
>>>    components like annotators, parser or consumers, as well as UIMA
>>>    tooling. All the components developed in the sandbox are free to use
>>>    and licensed under the Apache Software License
>>>    <http://incubator.apache.org/uima/license.html>.
>>>    A list of proposed analysis components and tooling for UIMA is
>>>    available at the UIMA wiki
>>>    <http://cwiki.apache.org/UIMA/uima-sandbox-components.html> and can
>>>    be discussed there.
>>>
>>>
>>> I would not tell the people what's currently in since we have no 
>>> release for the sandbox. My plan is to have also a release for the 
>>> sandbox as soon as we have released the core
>>> framework. For the next UIMA release we can add the components that 
>>> have already been released in the sandbox. Does this make sense?
>>>
>>> -- Michael
>>>
> 
> I'm confused.  I don't see the difference between what you and what 
> Michael are saying.
> 
> --Thilo

Re: Writing something about the Sandbox

Posted by Adam Lally <al...@alum.rpi.edu>.
On 2/1/07, Thilo Goetz <tw...@gmx.de> wrote:
> I'm confused.  I don't see the difference between what you and what
> Michael are saying.
>

I think the confusion is that Michael original said that we would
"have a release for the sandbox", which also took me by surprise.  But
in response to my question on the topic (not sure if Marshall sawa
that), Michael revised this to say that we might build downloadable
binaries for some of the sandbox components and make them available.

I don't have any particular objection to that, but wonder if how the
ASF views it.  Each of these would probably be a separate "release" as
far as they are concerned, and must require Incubator PMC approval?
If so that could be a lot of hassle for both us and the PMC.

-Adam

Re: Writing something about the Sandbox

Posted by Thilo Goetz <tw...@gmx.de>.
Marshall Schor wrote:
> Michael Baessler wrote:
>> <snip>
>> Maybe some of these project get also integrated to the core framework. 
>> But I'm not sure if, e.g. annotator components will be added to the
>> core. I think such analysis components will ever stay in the sandbox 
>> and can be downloaded there. Other opinions?
> 
> I prefer creating "subprojects" of Apache UIMA to hold these, for 
> reasons stated in previous notes.  For instance, how about a subproject 
> called "Apache UIMA Components", holding annotators?  (Another 
> subproject might be "corpii" - common test data, etc.)  We could do 
> distributions/releases of these.
> 
> -Marshall

The plural of corpus is corpora ;-)

I would hesitate to create that much structure when we have 2 annotators 
in the sandbox, hopefully one piece of tooling soon and nothing else so 
far (not a single corpus in sight, afaik).

We can hold certain pieces of software back from a release if they're 
too shaky even with a huge disclaimer (as Adam suggests in another 
mail).  Let's not make this more complicated than it needs to be.

I'm pointing at Lucene all the time because that's clearly a model that 
works.  They have all kinds of stuff in their sandbox.  Why don't we 
start out that way, and if it gets too much, we reorg.

--Thilo


Re: Writing something about the Sandbox

Posted by Michael Baessler <mb...@michael-baessler.de>.
Marshall Schor wrote:
> Michael Baessler wrote:
>> <snip>
>> Maybe some of these project get also integrated to the core 
>> framework. But I'm not sure if, e.g. annotator components will be 
>> added to the
>> core. I think such analysis components will ever stay in the sandbox 
>> and can be downloaded there. Other opinions?
>
> I prefer creating "subprojects" of Apache UIMA to hold these, for 
> reasons stated in previous notes.  For instance, how about a 
> subproject called "Apache UIMA Components", holding annotators?  
> (Another subproject might be "corpii" - common test data, etc.)  We 
> could do distributions/releases of these.
So you mean, when a sandbox analysis component is ready to use instead 
of adding it to the core framework we will add it to the "Apache UIMA 
components" project.
That's also fine with me. Though the sandbox in this case is only a 
temporary space and nothing that ever create any binary distributed 
component, right? In that case we also do not
need to add the sandbox to any release since if a sandbox component "is 
ready" we vote and add it to the core framework of to the components 
subproject. That is a kind of redefinition
of the current sandbox.

-- Michael

Re: Writing something about the Sandbox

Posted by Marshall Schor <ms...@schor.com>.
Michael Baessler wrote:
> <snip>
> Maybe some of these project get also integrated to the core framework. 
> But I'm not sure if, e.g. annotator components will be added to the
> core. I think such analysis components will ever stay in the sandbox 
> and can be downloaded there. Other opinions?

I prefer creating "subprojects" of Apache UIMA to hold these, for 
reasons stated in previous notes.  For instance, how about a subproject 
called "Apache UIMA Components", holding annotators?  (Another 
subproject might be "corpii" - common test data, etc.)  We could do 
distributions/releases of these.

-Marshall

Re: Writing something about the Sandbox

Posted by Michael Baessler <mb...@michael-baessler.de>.
Marshall Schor wrote:
> The difference may be one of emphasis.  Or, maybe I've misunderstood 
> what Michael said (sorry if true.)
> I'm trying to emphasize the purpose of the Sandbox is not in
> what it hosts (Annotators, Cas Consumers, Tools, etc.), but rather 
> that it is more free of the constraints
> we have for other projects / subprojects.  There's less need for 
> consensus here, more opportunity to
> try new things, some of which might be accepted eventually, others, not.
That was my intention. The sandbox is a place where new things can be 
developed... for example annotators, tools... and so on....
Maybe some of these project get also integrated to the core framework. 
But I'm not sure if, e.g. annotator components will be added to the
core. I think such analysis components will ever stay in the sandbox and 
can be downloaded there. Other opinions?

And I agree with Thilo, that we should add some of the sandbox 
components to the next release. So we can provide
binary versions of components that are ready to use.

-- Michael


Re: Writing something about the Sandbox

Posted by Marshall Schor <ms...@schor.com>.
Thilo Goetz wrote:
> <snip>
>
> I'm confused.  I don't see the difference between what you and what 
> Michael are saying.
>
>

The difference may be one of emphasis.  Or, maybe I've misunderstood 
what Michael said (sorry if true.) 

I'm trying to emphasize the purpose of the Sandbox is not in
what it hosts (Annotators, Cas Consumers, Tools, etc.), but rather that 
it is more free of the constraints
we have for other projects / subprojects.  There's less need for 
consensus here, more opportunity to
try new things, some of which might be accepted eventually, others, not.

-Marshall

Re: Writing something about the Sandbox

Posted by Thilo Goetz <tw...@gmx.de>.

Marshall Schor wrote:
> Other projects seem to treat the sandbox differently than as described 
> below; I would prefer to keep the sandbox
> aligned with usual Apache concepts for it, which seem to be - it's a 
> subproject for potential new additions to the project or to subprojects 
> of it, and things here are works in progress, with no guarantee that 
> they will ever be promoted to
> an official release of the project its subprojects.
> 
> We should (in my opinion) establish other subprojects which can do 
> releases, etc., beyond the sandbox, for things like
> annotators, parsers, consumers, and tooling.   Things would graduate
>> from the sandbox into one of these subprojects (or into the main Apache 
> UIMA project) when we want to convey some higher level of support / 
> testing / acceptance, and to have official "distributions/releases" for.
> I think that the sandbox should not be a subproject which does 
> "distributions/releases".  This allows more freedom
> to tinker, which I think is a valuable thing to have as some part of the 
> project.
> 
> -Marshall
> 
> Michael Baessler wrote:
>> Marshall Schor wrote:
>>> Michael - could you write something about the Sandbox on Apache?  
>>> Purpose, what's in it.  Something short - to be included in the 
>>> docbook docs.
>>>
>>> -Marshall
>>>
>>>
>> So you want to include a short paragraph about the sandbox to the 
>> docbook of the UIMA 2.1 release. I would only add something similar as 
>> we have on the web:
>>
>>    The UIMA sandbox is a workspace that is open to all UIMA committers
>>    and developers who would like to contribute code and join the UIMA
>>    developer community. The sandbox is designed to host analysis
>>    components like annotators, parser or consumers, as well as UIMA
>>    tooling. All the components developed in the sandbox are free to use
>>    and licensed under the Apache Software License
>>    <http://incubator.apache.org/uima/license.html>.
>>    A list of proposed analysis components and tooling for UIMA is
>>    available at the UIMA wiki
>>    <http://cwiki.apache.org/UIMA/uima-sandbox-components.html> and can
>>    be discussed there.
>>
>>
>> I would not tell the people what's currently in since we have no 
>> release for the sandbox. My plan is to have also a release for the 
>> sandbox as soon as we have released the core
>> framework. For the next UIMA release we can add the components that 
>> have already been released in the sandbox. Does this make sense?
>>
>> -- Michael
>>

I'm confused.  I don't see the difference between what you and what 
Michael are saying.

--Thilo

Re: Writing something about the Sandbox

Posted by Marshall Schor <ms...@schor.com>.
Other projects seem to treat the sandbox differently than as described 
below; I would prefer to keep the sandbox
aligned with usual Apache concepts for it, which seem to be - it's a 
subproject for potential new additions to the project or to subprojects 
of it, and things here are works in progress, with no guarantee that 
they will ever be promoted to
an official release of the project its subprojects.

We should (in my opinion) establish other subprojects which can do 
releases, etc., beyond the sandbox, for things like
annotators, parsers, consumers, and tooling.   Things would graduate 
from the sandbox into one of these subprojects (or into the main Apache 
UIMA project) when we want to convey some higher level of support / 
testing / acceptance, and to have official "distributions/releases" for. 

I think that the sandbox should not be a subproject which does 
"distributions/releases".  This allows more freedom
to tinker, which I think is a valuable thing to have as some part of the 
project.

-Marshall

Michael Baessler wrote:
> Marshall Schor wrote:
>> Michael - could you write something about the Sandbox on Apache?  
>> Purpose, what's in it.  Something short - to be included in the 
>> docbook docs.
>>
>> -Marshall
>>
>>
> So you want to include a short paragraph about the sandbox to the 
> docbook of the UIMA 2.1 release. I would only add something similar as 
> we have on the web:
>
>    The UIMA sandbox is a workspace that is open to all UIMA committers
>    and developers who would like to contribute code and join the UIMA
>    developer community. The sandbox is designed to host analysis
>    components like annotators, parser or consumers, as well as UIMA
>    tooling. All the components developed in the sandbox are free to use
>    and licensed under the Apache Software License
>    <http://incubator.apache.org/uima/license.html>.
>    A list of proposed analysis components and tooling for UIMA is
>    available at the UIMA wiki
>    <http://cwiki.apache.org/UIMA/uima-sandbox-components.html> and can
>    be discussed there.
>
>
> I would not tell the people what's currently in since we have no 
> release for the sandbox. My plan is to have also a release for the 
> sandbox as soon as we have released the core
> framework. For the next UIMA release we can add the components that 
> have already been released in the sandbox. Does this make sense?
>
> -- Michael
>
>
>
>


Re: Writing something about the Sandbox

Posted by Mirko Jahn <mi...@gmail.com>.
I think this is a good idea. If you have to build a project from the
source and get errors, you never know, if the project is under heavy
development and not proper working (like missing or invalid build
instructions) or you just made some mistakes (missing libraries for
instance). Having a binary is a good way to avoid such problems, I
think. Another point is, that with binary drops, it is possible to
express some sort of progress in development, even in the sandbox. The
binary drops can for instance only contain the name and date, so there
will be no real release associated with these binaries.

-- Mirko

On 1/23/07, Michael Baessler <mb...@michael-baessler.de> wrote:
> Adam Lally wrote:
> > On 1/23/07, Tong Fin <to...@gmail.com> wrote:
> >> I think Sandbox may have different meaning for other Apache project
> >> developers: It is a place that developers develop the code to
> >> test/try new
> >> ideas/concepts. If the developed code is mature enough, it will be
> >> moved to
> >> the main stream build.
> >
> > I think that's what we mean, too.
> Indeed, I thought the same but explained it more particularly...
> > I didn't think that the sandbox would have "releases".  I was
> > imagining that people who wanted to try out sandbox code would just
> > get it from SVN.  Eventually, if there's something in the sandbox
> > that's considered mature enough and makes sense to include the main
> > stream SDK build, we'll move it to the uimaj code branch.
> My thoughts about the sandbox release:
>  - when we think (or later also others) that own of the components in
> the sandbox is "ready to use" we build a binary version of it and make
> it available
>     at the download section.
> - Users can browse all released sandbox components and use them out of
> the box and must not build them self
>
> -- Michael
>

Re: Writing something about the Sandbox

Posted by Michael Baessler <mb...@michael-baessler.de>.
Adam Lally wrote:
> On 1/23/07, Tong Fin <to...@gmail.com> wrote:
>> I think Sandbox may have different meaning for other Apache project
>> developers: It is a place that developers develop the code to 
>> test/try new
>> ideas/concepts. If the developed code is mature enough, it will be 
>> moved to
>> the main stream build.
>
> I think that's what we mean, too.
Indeed, I thought the same but explained it more particularly...
> I didn't think that the sandbox would have "releases".  I was
> imagining that people who wanted to try out sandbox code would just
> get it from SVN.  Eventually, if there's something in the sandbox
> that's considered mature enough and makes sense to include the main
> stream SDK build, we'll move it to the uimaj code branch.
My thoughts about the sandbox release:
 - when we think (or later also others) that own of the components in 
the sandbox is "ready to use" we build a binary version of it and make 
it available
    at the download section.
- Users can browse all released sandbox components and use them out of 
the box and must not build them self

-- Michael

Re: Writing something about the Sandbox

Posted by Adam Lally <al...@alum.rpi.edu>.
On 1/23/07, Tong Fin <to...@gmail.com> wrote:
> I think Sandbox may have different meaning for other Apache project
> developers: It is a place that developers develop the code to test/try new
> ideas/concepts. If the developed code is mature enough, it will be moved to
> the main stream build.

I think that's what we mean, too.


> On 1/23/07, Michael Baessler <mb...@michael-baessler.de> wrote:
> > I would not tell the people what's currently in since we have no release
> > for the sandbox. My plan is to have also a release for the sandbox as
> > soon as we have released the core
> > framework. For the next UIMA release we can add the components that have
> > already been released in the sandbox. Does this make sense?
> >

I didn't think that the sandbox would have "releases".  I was
imagining that people who wanted to try out sandbox code would just
get it from SVN.  Eventually, if there's something in the sandbox
that's considered mature enough and makes sense to include the main
stream SDK build, we'll move it to the uimaj code branch.

I do agree, though, that our documentation shouldn't say specifically
what's in the sandbox, since this can change at any time.

-Adam

Re: Writing something about the Sandbox

Posted by Tong Fin <to...@gmail.com>.
I think Sandbox may have different meaning for other Apache project
developers: It is a place that developers develop the code to test/try new
ideas/concepts. If the developed code is mature enough, it will be moved to
the main stream build.

- Tong

On 1/23/07, Michael Baessler <mb...@michael-baessler.de> wrote:
>
> Marshall Schor wrote:
> > Michael - could you write something about the Sandbox on Apache?
> > Purpose, what's in it.  Something short - to be included in the
> > docbook docs.
> >
> > -Marshall
> >
> >
> So you want to include a short paragraph about the sandbox to the
> docbook of the UIMA 2.1 release. I would only add something similar as
> we have on the web:
>
>     The UIMA sandbox is a workspace that is open to all UIMA committers
>     and developers who would like to contribute code and join the UIMA
>     developer community. The sandbox is designed to host analysis
>     components like annotators, parser or consumers, as well as UIMA
>     tooling. All the components developed in the sandbox are free to use
>     and licensed under the Apache Software License
>     <http://incubator.apache.org/uima/license.html>.
>
>     A list of proposed analysis components and tooling for UIMA is
>     available at the UIMA wiki
>     <http://cwiki.apache.org/UIMA/uima-sandbox-components.html> and can
>     be discussed there.
>
>
> I would not tell the people what's currently in since we have no release
> for the sandbox. My plan is to have also a release for the sandbox as
> soon as we have released the core
> framework. For the next UIMA release we can add the components that have
> already been released in the sandbox. Does this make sense?
>
> -- Michael
>
>
>

Re: Writing something about the Sandbox

Posted by Michael Baessler <mb...@michael-baessler.de>.
Marshall Schor wrote:
> Michael - could you write something about the Sandbox on Apache?  
> Purpose, what's in it.  Something short - to be included in the 
> docbook docs.
>
> -Marshall
>
>
So you want to include a short paragraph about the sandbox to the 
docbook of the UIMA 2.1 release. I would only add something similar as 
we have on the web:

    The UIMA sandbox is a workspace that is open to all UIMA committers
    and developers who would like to contribute code and join the UIMA
    developer community. The sandbox is designed to host analysis
    components like annotators, parser or consumers, as well as UIMA
    tooling. All the components developed in the sandbox are free to use
    and licensed under the Apache Software License
    <http://incubator.apache.org/uima/license.html>. 

    A list of proposed analysis components and tooling for UIMA is
    available at the UIMA wiki
    <http://cwiki.apache.org/UIMA/uima-sandbox-components.html> and can
    be discussed there.


I would not tell the people what's currently in since we have no release 
for the sandbox. My plan is to have also a release for the sandbox as 
soon as we have released the core
framework. For the next UIMA release we can add the components that have 
already been released in the sandbox. Does this make sense?

-- Michael