On 8/3/06, Greg Reddin <[EMAIL PROTECTED]> wrote:

What about just adding shale-petstore as part of shale-goodies?  Was
that just a thing of getting wires crossed or did you intend for it
to be a separate project?


It was definitely "great minds thinking alike at the same time"  ... :-)

I think we would want to set up a playground where multiple libraries or
examples could be hosted, rather than a separate one for each, so we can use
it for a little community building too.  Re: Google vs java.net, I confess
to the same curiousity Greg mentioned about the new features.  Yes, you can
use a Google Group for discussion.  No, they don't have an answer for binary
distros yet, but that's definitely something theiy are working on.

Greg


Craig

On Aug 3, 2006, at 2:26 PM, Sean Schofield wrote:

> And I just set up a shale-petstore ;-)
>
> Do you envision this being more then the petstore app?  Also, are we
> sure we want google as opposed to dev.java.net?  I don't know much
> about the google option.
>
> It seems like we can have discussion via a google group.  What about
> distribution of jar files?
>
> Sean
>
> On 8/3/06, Craig McClanahan <[EMAIL PROTECTED]> wrote:
>> On 8/3/06, Greg Reddin <[EMAIL PROTECTED]> wrote:
>> >
>> > +1.  I was wanting to figure out what all that google open source
>> > stuff was about anyway.  But I'm cool with either google or
>> java.net.
>>
>>
>> I just set up "shale-goodies" for us at Google[1].  Note that you
>> must have
>> a GMail account to log in with for SVN access, but that's already
>> true for a
>> bunch of us.  Send me your GMail username and I'll add you in as a
>> project
>> owner.
>>
>> Greg
>>
>>
>> Craig
>>
>> [1] http://code.google.com/p/shale-goodies/
>>
>>
>> On Aug 3, 2006, at 1:25 PM, Sean Schofield wrote:
>> >
>> > > I'm considering an option that Craig mentioned earlier -
>> moving this
>> > > to google's new open source area.  While I understand the
>> reasons for
>> > > the tight restrictions that ASF has, it makes it difficult to
>> host a
>> > > fully functional sample app using several different technologies.
>> > >
>> > > On google (and presumably dev.java.net), we can also distribute
>> > > binaries wither hibernate, etc.  That will allow more people
>> to use
>> > > the app.  No matter how easy you make it, some people are just
>> putoff
>> > > by compiling their own source.  I admit, sometimes I fall into
>> this
>> > > category (if my interest is only casual.)
>> > >
>> > > If we do move it, I'd still like some loose integration
>> between shale
>> > > and this project.  This would include links to the shale-
>> petstore from
>> > > the shale site and referring people on the user list to the
>> > > shale-petstore when it serves as an appropriate example.
>> > >
>> > > Thoughts?
>> > >
>> > > Sean
>> > >
>> > > On 8/3/06, Craig McClanahan <[EMAIL PROTECTED]> wrote:
>> > >> On 8/3/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:
>> > >> >
>> > >> > On 8/3/06, Sean Schofield <[EMAIL PROTECTED]> wrote:
>> > >> >
>> > >> > > Most of the images seem to be: GNU Free Documentation
>> License,
>> > >> Version
>> > >> > > 1.2.  What about the text?  Any ideas on that?
>> > >> >
>> > >> > Are you asking about the text on Wikipedia?  There's a
>> notice at
>> > >> the
>> > >> > bottom of every page: "All text is available under the
>> terms of the
>> > >> > GNU Free Documentation License."
>> > >> >
>> > >> > As for whether we can use the text or images, if GFDL is not
>> > >> listed on
>> > >> > Cliff's page [1] then I would ask on [EMAIL PROTECTED]
>> > >>
>> > >>
>> > >> I suspect the GNU license for docs will have issues, so
>> asking on
>> > >> legal-discuss would be a good idea.
>> > >>
>> > >> In the mean time, note that the original Blueprints PetStore
>> > >> application
>> > >> (including content and images) is BSD-licensed, so we can use
>> > >> stuff from
>> > >> there.  <https://blueprints.dev.java.net>)
>> > >>
>> > >> Craig
>> > >>
>> > >>
>> > >> [1] http://people.apache.org/~cliffs/3party.html
>> > >> >
>> > >> > --
>> > >> > Wendy
>> > >> >
>> > >>
>> > >>
>> > >
>> >
>> >
>>
>>
>


Reply via email to