If they're not official parts of deltaspike but a proving ground and we can pull things in, or get iCLAs for people when we pull in their stuff, is that a problem? Or what if we ask them for an iCLA once they do a pull request?

I'm worried we're losing some momentum (if it's not already gone) from the community about contributing. We also have a bunch of Seam devs (Cody, Marius, George, etc.) asking about when they can put their bits into DeltaSpike because it's not on the roadmap, or it's very far out on the roadmap. 

On Wed, Jun 27, 2012 at 1:33 PM, Mark Struberg <struberg@yahoo.de> wrote:
basically +1

BUT we really have to be careful that we don't do too much at github!

All commits done on github must either be done by a deltaspike committer or someone who has at least an iCLA on file.

Commits from other people need to get added via an attachment in a Jira ticket.
I know this sounds not really git-like, but it's the only way we can ensure IP clearance.


----- Original Message -----
> From: Mehdi Heidarzadeh <heidarzadeh2@gmail.com>
> To: deltaspike-dev@incubator.apache.org
> Cc:
> Sent: Wednesday, June 27, 2012 7:28 PM
> Subject: Re: Sandbox for DeltaSpike
> +1
> Great idea.
> On Wed, Jun 27, 2012 at 4:52 AM, Shane Bryzak <sbryzak@redhat.com> wrote:
>>  Fantastic idea, +1.
>>  On 27/06/12 05:39, Jason Porter wrote:
>>>  Hey everyone!
>>>  I wanted to bring up the idea of having a sandbox to add bits and other
>>>  non-core extensions. We have a great bunch of people from the Seam
>>>  development group looking to add their extensions, but they're
> either not
>>>  on the roadmap for DS, or are very far down. I suggest we setup a
> sandbox
>>>  on github people can write to, or at least do pull requests to so we
> can
>>>  get some of these modules and other ideas in and pull them into core as
> we
>>>  get there. We can also use this as a vetting ground for new ideas and
> other
>>>  things which may not exactly fit into core, like the forge extension.
>>>  To do this we need to
>>>  1. Setup the repo somewhere
>>>  2. Seed it with a basic structure (pom.xml, contribution instructions,
>>>  etc)
>>>  3. Get some CI setup somewhere (we could leverage OpenShift for this if
>>>  needed)
>>>  What does everyone else think? I've cc'd the Seam Development
> list here
>>>  hoping to get some feedback from them as well and hopefully rekindle
> some
>>>  of the fire we had there.
>>>  --
>>>  Jason Porter
>>>  http://lightguard-jp.blogspot.**com
> <http://lightguard-jp.blogspot.com>
>>>  http://twitter.com/**lightguardjp
> <http://twitter.com/lightguardjp>
>>>  Software Engineer
>>>  Open Source Advocate
>>>  Author of Seam Catch - Next Generation Java Exception Handling
>>>  PGP key id: 926CCFF5
>>>  PGP key available at: keyserver.net <http://keyserver.net>,
> pgp.mit.edu <
>>>  http://pgp.mit.edu>
>>>  ______________________________**_________________
>>>  seam-dev mailing list
>>>  seam-dev@lists.jboss.org
> https://lists.jboss.org/**mailman/listinfo/seam-dev<https://lists.jboss.org/mailman/listinfo/seam-dev>
> --
> Mehdi Heidarzadeh Ardalani
> Independent JEE Consultant, Architect and Developer.
> http://www.TheBigJavaBlog.com

Jason Porter

Software Engineer
Open Source Advocate
Author of Seam Catch - Next Generation Java Exception Handling

PGP key id: 926CCFF5
PGP key available at: keyserver.net, pgp.mit.edu