shale-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Schofield" <sean.schofi...@gmail.com>
Subject Re: Should we move shale-petstore somewhere else? Was --> Re: Wikipedia: More Licensing Questions
Date Fri, 04 Aug 2006 01:00:35 GMT
Well the email list is not public atm.  That's probably the problem.
We could create a shell gmail account for the svn emails and have that
same account subscribed to the group.  Then set up forwarding.  That
should work.

Which brings us to the issue of the list permissions.  One option is
to require the moderator approval to join the list (I believe that's
what its set to now.)  We could rubber stamp people who want to join
but also remove them if they're acting like assholes.  Or just let the
floodgates open.  The problem with the open flood gate approach is
that it would be hard to switch back to the other model if we changed
our mind.

I'm not sure where I stand on this.  What does the rest of the group think?

Sean

On 8/3/06, Craig McClanahan <craigmcc@apache.org> wrote:
> On 8/3/06, Sean Schofield <sean.schofield@gmail.com> wrote:
> >
> > Lets think on the package names a bit.
>
>
> OK.
>
>   I set up a google group for
> > us.  I tried adding the svn commit messages to the group but I'm not
> > sure that's possible.  Maybe we just add each "commiter" manually as
> > we go?
>
>
> Hmm ... looks like you have it set up right ... maybe commit mail isn't
> working yet.
>
> It also looks like we can only have one destination address for the commits.
>
> Sean
>
>
> Craig
>
>
> On 8/3/06, Craig McClanahan <craigmcc@apache.org> wrote:
> > > On 8/3/06, Sean Schofield <sean.schofield@gmail.com> wrote:
> > > >
> > > > Any reason why we can't use org.apache.shale for the package names
> > > > still?  I can't really think of a better package name off hand.
> > >
> > >
> > > Using org.apache.shale.xxxxx would seem to create a false perception
> > that
> > > the goodies were actually a formal part of the Shale project, and would
> > > contradict the project description claim in that regard.  We should use
> > > "goodies" or "shalegoodies" or something like that.
> > >
> > > Sean
> > >
> > >
> > > Craig
> > >
> > > On 8/3/06, Craig McClanahan <craigmcc@apache.org> wrote:
> > > > > On 8/3/06, Sean Schofield <sean.schofield@gmail.com> wrote:
> > > > > >
> > > > > > I'm ok with shale-goodies as long as we can release artifacts
as
> > > > > > different versions, etc.  I'm assuming that's the case.  I think
> > we're
> > > > > > all curious about the google option so lets go ahead with it.
 We
> > can
> > > > > > always move it in a few months if it doesn't pan out.  Right
now
> > > > > > there;s just shale-petstore and it wouldn't be the end of the
> > world to
> > > > > > lose the svn history if we had to move it.
> > > > >
> > > > >
> > > > > I set up a "maven/trunk/master-pom" analogous to what we have in
the
> > > > Apache
> > > > > repository ... you could set up shale-petstore/trunk to make it
> > > > > independently branchable and so on.  We could even set up a
> > "current"
> > > > > externals later.
> > > > >
> > > > > We'll have to think about the package names (and Maven artifact ids)
> > > > here
> > > > > ... I used "shale-goodies:shale-goodies:1-SNAPSHOT" for the initial
> > > > master
> > > > > pom, but haven't checked in any code yet.
> > > > >
> > > > > my gmail is sean.schofield
> > > > >
> > > > >
> > > > > Added.
> > > > >
> > > > > Sean
> > > > > >
> > > > > > ps. Google is also doing something cool which is allowing you
to
> > host
> > > > > > your domain email through them.  There is a beta test going
on and
> > > > > > they accepted my application.  Something to consider for folks
who
> > > > > > have their own domain for business purposes.
> > > > >
> > > > >
> > > > > That is pretty cool.
> > > > >
> > > > > Craig
> > > > >
> > > > >
> > > >
> > >
> > >
> >
>
>

Mime
View raw message