Discussion:
[seam-dev] Sandbox for DeltaSpike
Jason Porter
2012-06-26 19:39:26 UTC
Permalink
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://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, pgp.mit.edu
Lincoln Baxter, III
2012-06-26 20:15:16 UTC
Permalink
+1

I think this is a great idea! We certainly want to make sure that we are
supporting innovation of community members, and this would help a great
deal.

~Lincoln
Post by Jason Porter
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://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, pgp.mit.edu
_______________________________________________
seam-dev mailing list
https://lists.jboss.org/mailman/listinfo/seam-dev
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
Shane Bryzak
2012-06-27 00:22:10 UTC
Permalink
Fantastic idea, +1.
Post by Jason Porter
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://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
https://lists.jboss.org/mailman/listinfo/seam-dev
Jason Porter
2012-06-27 17:50:16 UTC
Permalink
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.
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.
LieGrue,
strub
----- Original Message -----
Sent: Wednesday, June 27, 2012 7:28 PM
Subject: Re: Sandbox for DeltaSpike
+1
Great idea.
Post by Shane Bryzak
Fantastic idea, +1.
Post by Jason Porter
Hey everyone!
I wanted to bring up the idea of having a sandbox to add bits and
other
Post by Shane Bryzak
Post by Jason Porter
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
Post by Shane Bryzak
Post by Jason Porter
on the roadmap for DS, or are very far down. I suggest we setup a
sandbox
Post by Shane Bryzak
Post by Jason Porter
on github people can write to, or at least do pull requests to so we
can
Post by Shane Bryzak
Post by Jason Porter
get some of these modules and other ideas in and pull them into core
as
we
Post by Shane Bryzak
Post by Jason Porter
get there. We can also use this as a vetting ground for new ideas and
other
Post by Shane Bryzak
Post by Jason Porter
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
Post by Shane Bryzak
Post by Jason Porter
needed)
What does everyone else think? I've cc'd the Seam Development
list here
Post by Shane Bryzak
Post by Jason Porter
hoping to get some feedback from them as well and hopefully rekindle
some
Post by Shane Bryzak
Post by Jason Porter
of the fire we had there.
--
Jason Porter
http://lightguard-jp.blogspot.**com
<http://lightguard-jp.blogspot.com>
Post by Shane Bryzak
Post by Jason Porter
http://twitter.com/**lightguardjp
<http://twitter.com/lightguardjp>
Post by Shane Bryzak
Post by 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 <http://keyserver.net>,
pgp.mit.edu <
Post by Shane Bryzak
Post by Jason Porter
http://pgp.mit.edu>
______________________________**_________________
seam-dev mailing list
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
http://lightguard-jp.blogspot.com
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, pgp.mit.edu
Mark Struberg
2012-06-28 05:54:21 UTC
Permalink
We also have a bunch of Seam devs (Cody, Marius, George, etc.) asking about when they can put their bits into DeltaSpike
That's perfect, but doing stuff off-list is not increasing the visibility of this work.


Cody, Marius, George are all already DeltaSpike committer!

PLEASE, just put your ideas on the deltaspike-dev mailing list and start a quick introduction about what you like to add!


The momentum is used best if you commit that stuff.
Of course there is a difference in the way the seam3 project and Apache projects are developed. In Apache projects there is no code ownership. Every line gets reviewed and improved 5 times from 10 pairs of eyes. Please be one of those 10++ pairs of eyes and also start reviewing code or add new functionality!

LieGrue,
strub
________________________________
Sent: Wednesday, June 27, 2012 7:50 PM
Subject: Re: Sandbox for DeltaSpike
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. 
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.
LieGrue,
strub
----- Original Message -----
Sent: Wednesday, June 27, 2012 7:28 PM
Subject: Re: Sandbox for DeltaSpike
+1
Great idea.
 Fantastic idea, +1.
 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
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
http://lightguard-jp.blogspot.com
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, pgp.mit.edu
Jason Porter
2012-06-27 18:32:50 UTC
Permalink
Why wouldn't this be in the public? The idea is to get people to contribute. If we need a separate Apache repo for a sandbox, okay fine but then we're back to the icla issue aren't we?

Sent from my iPhone
Btw, another thingy.
It is not the best community building approach to develop something 'in the dark' and then drop all that on all other community members.
Don't get me wrong, it's perfectly fine to experiment around if ideas are good at all. But doing this 'in public' is much more appreciated. You can get lots or precious feedback that way.
LieGrue,
strub
----- Original Message -----
Sent: Wednesday, June 27, 2012 7:33 PM
Subject: Re: Sandbox for DeltaSpike
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.
LieGrue,
strub
----- Original Message -----
Sent: Wednesday, June 27, 2012 7:28 PM
Subject: Re: Sandbox for DeltaSpike
+1
Great idea.
Post by Shane Bryzak
Fantastic idea, +1.
Post by Jason Porter
Hey everyone!
I wanted to bring up the idea of having a sandbox to add bits and
other
Post by Shane Bryzak
Post by Jason Porter
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
Post by Shane Bryzak
Post by Jason Porter
on the roadmap for DS, or are very far down. I suggest we setup a
sandbox
Post by Shane Bryzak
Post by Jason Porter
on github people can write to, or at least do pull requests to so
we
can
Post by Shane Bryzak
Post by Jason Porter
get some of these modules and other ideas in and pull them into
core as
we
Post by Shane Bryzak
Post by Jason Porter
get there. We can also use this as a vetting ground for new ideas
and
other
Post by Shane Bryzak
Post by Jason Porter
things which may not exactly fit into core, like the forge
extension.
Post by Shane Bryzak
Post by Jason Porter
To do this we need to
1. Setup the repo somewhere
2. Seed it with a basic structure (pom.xml, contribution
instructions,
Post by Shane Bryzak
Post by Jason Porter
etc)
3. Get some CI setup somewhere (we could leverage OpenShift for
this if
Post by Shane Bryzak
Post by Jason Porter
needed)
What does everyone else think? I've cc'd the Seam
Development
list here
Post by Shane Bryzak
Post by Jason Porter
hoping to get some feedback from them as well and hopefully
rekindle
some
Post by Shane Bryzak
Post by Jason Porter
of the fire we had there.
--
Jason Porter
http://lightguard-jp.blogspot.**com
<http://lightguard-jp.blogspot.com>
Post by Shane Bryzak
Post by Jason Porter
http://twitter.com/**lightguardjp
<http://twitter.com/lightguardjp>
Post by Shane Bryzak
Post by 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 <http://keyserver.net>,
pgp.mit.edu <
Post by Shane Bryzak
Post by Jason Porter
http://pgp.mit.edu>
______________________________**_________________
seam-dev mailing list
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
Mark Struberg
2012-06-28 06:12:14 UTC
Permalink
With 'public' I meant that the main communication tool is the mailing list. There is a saying "if it's not on the list, it didn't happen".

IRC is fine as backing channel, but there are different time zones etc. It's also not logged (because freenode has a policy about not logging chats), thus other uses cannot simply search some archive to find any old information.


It's perfect if you drop a few lines of mail explaining what problem/idea/feature you are working on and add a pointer to some github repo.
But be aware that you must work alone on that gibhut repo or at least must _not_ accept patches/pull-requests from non-committers. Otherwise you would not be IP clean. And since goog vs orcl (Harmony,...) we _really_ care about that!

github is also a great tool, but it doesn't really strengthen the team collaboration spirit. It's more fore the lone fighter who works on his own...

Maybe I should explain it another way what could happen:


Imagine you get a cool new feature which has a decent complexity. Say 45 classes and 25000 lines of code. And all that in one big merge-commit!
Compare that with work that evolves over a few weeks with 5 people working on it and adding ideas. There would be much more understanding of the topic in the community and the quality would also be much better at the end. There will also be much less overlapping with other features in the project quite naturally...

LieGrue,
strub


----- Original Message -----
Sent: Wednesday, June 27, 2012 8:32 PM
Subject: Re: Sandbox for DeltaSpike
Why wouldn't this be in the public? The idea is to get people to contribute.
If we need a separate Apache repo for a sandbox, okay fine but then we're
back to the icla issue aren't we?
Sent from my iPhone
Btw, another thingy.
It is not the best community building approach to develop something 'in
the dark' and then drop all that on all other community members.
Don't get me wrong, it's perfectly fine to experiment around if
ideas are good at all. But doing this 'in public' is much more
appreciated. You can get lots or precious feedback that way.
LieGrue,
strub
----- Original Message -----
Sent: Wednesday, June 27, 2012 7:33 PM
Subject: Re: Sandbox for DeltaSpike
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.
LieGrue,
strub
----- Original Message -----
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
  Fantastic idea, +1.
  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
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
2012-06-28 16:54:00 UTC
Permalink
Maybe we should do a new thread for the security stuff so we don't derail
this one.

Having talked to some of the Seam Contributors here at JBoss World / Red
Hat Summit it seems like a lot of them aren't quite sure how to get the
discussions started for their previous Seam modules, especially since many
of them target EE apis (I'm ccing the Seam dev list so hopefully those who
may not be following DeltaSpike dev will see this). That is a large part of
where this sandbox idea came from. If we want to create a new Apache repo,
or another sub directory in our current repo, or perhaps even different
branches for this work I'm fine. However, I do agree that getting too many
topics going all at once is bad. That happened in Seam and we were
overloaded. Perhaps we should create some sort policy for getting these
ideas in if they're not on the current roadmap. I'm not sure if any of
really know when we'll be tackling some of the EE stuff. Next release,
release after that one? I really don't want to lose these people and see
DeltaSpike stagnate with only a few developers doing it in their spare time.
Oh yea, that was my fault. I was on a conference earlier that week and
overlooked his mail. Found it now.
Shane, what is the direction you working on? What are the basic ideas and
what shortcomings did you identify while doing the review?
I'm not sure if it wouldn't be better we would make that work directly in
the deltaspike main repo. There are lots of other people looking at the
repo and we got many questions regarding security already. And not being
able to point people to a canonical repo which contains the latest stuff...
Btw, welcome Bolek! We've talked on IRC already a few times. Would be
great if you could introduce yourself with a few words and also if we move
the technical discussions from IRC more to email. This is much easier to
follow for people in different timezones. And it will also raise visibility
and make people aware that there is a new face working on DeltaSpike :)
There is a general ASF rule "If it isn't on the list, it didn't happen".
Using IRC or even skype calls is fine for _additional_ ad hoc
communication, but it must not lead to 'silently' doing things without
having conversation on the list. IRC is just not a mail archive which can
get scanned easily.
txs and LieGrue,
strub
----- Original Message -----
Sent: Thursday, June 28, 2012 6:20 PM
Subject: Re: Sandbox for DeltaSpike
But if we don't talk about that stuff at all, then there will be no
visibility and no progress neither.
There is really no problem with spreading out parallel topics, IF there
are people interested in contributing.
What I do _not_ like to have is starting with 15 different topics and
not
finishing anything!
Btw, what is the state of deltaspike-security?
I have no clue about it nor did I do any review. I've also not seen any
commit lately.
Who is working on that? Or is noone working on it at all?
https://github.com/sbryzak/DeltaSpike/tree/security
I believe Shane has been working on it apparently, but there hasn't been
much discussion.
LieGrue,
strub
--
Jason Porter
http://lightguard-jp.blogspot.com
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, pgp.mit.edu
Marius Bogoevici
2012-06-29 18:02:42 UTC
Permalink
I think it is a good idea. Discussions can and should take place, but
IMO an opend sandbox would be a good place to stage code for new
features without endangering the stability of the whole project.
Post by Jason Porter
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.
Lincoln Baxter, III
2012-06-29 19:21:31 UTC
Permalink
I see nothing wrong with a sandbox, particularly since I think sometimes
seeing code is a better way to make spark discussion than trying to discuss
everything up front. In order to facilitate contribution and individual
communication styles, and to promote more contributions in general, I think
this is a good step.

On Fri, Jun 29, 2012 at 2:02 PM, Marius Bogoevici <
Post by Marius Bogoevici
I think it is a good idea. Discussions can and should take place, but
IMO an opend sandbox would be a good place to stage code for new
features without endangering the stability of the whole project.
Post by Jason Porter
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
Post by Jason Porter
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
Post by Jason Porter
as we get there. We can also use this as a vetting ground for new ideas
and
Post by Jason Porter
other things which may not exactly fit into core, like the forge
extension.
Post by Jason Porter
To do this we need to
1. Setup the repo somewhere
2. Seed it with a basic structure (pom.xml, contribution instructions,
etc)
Post by Jason Porter
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.
_______________________________________________
seam-dev mailing list
https://lists.jboss.org/mailman/listinfo/seam-dev
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
Marius Bogoevici
2012-06-29 23:09:11 UTC
Permalink
+1

We have taught ourselves to write self-explanatory code, and that is starting to show ;)

Sent from my iPhone
I see nothing wrong with a sandbox, particularly since I think sometimes seeing code is a better way to make spark discussion than trying to discuss everything up front. In order to facilitate contribution and individual communication styles, and to promote more contributions in general, I think this is a good step.
I think it is a good idea. Discussions can and should take place, but
IMO an opend sandbox would be a good place to stage code for new
features without endangering the stability of the whole project.
Post by Jason Porter
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.
_______________________________________________
seam-dev mailing list
https://lists.jboss.org/mailman/listinfo/seam-dev
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
_______________________________________________
seam-dev mailing list
https://lists.jboss.org/mailman/listinfo/seam-dev
Loading...