You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by David Bosschaert <da...@gmail.com> on 2009/09/28 15:24:34 UTC
Re: [aries] Moved geronimo blueprint implementation into aries
podling
Great - let me see if I can make it part of a larger Aries build with a
shared parent pom, a pom in the root dir etc...
I'd also like to rename some things from Geronimo to Aries...
Finally, should we asking INFRA for a Hudson build? Or is this normally not
done for podlings?
Cheers,
David
2009/9/28 Guillaume Nodet <gn...@gmail.com>
> The Geronimo PMC has voted to donate the blueprint implementation to
> aries, so I've gone ahead and moved the code to:
> https://svn.apache.org/repos/asf/incubator/aries/blueprint/
>
> I guess we need to discuss how we want to organized the svn tree /
> build, and until the mailing lists are set up, we can start discussing
> that here.
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
> ------------------------
> Open Source SOA
> http://fusesource.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
Re: [aries] Moved geronimo blueprint implementation into aries podling
Posted by Kevan Miller <ke...@gmail.com>.
On Sep 29, 2009, at 5:17 AM, Guillaume Nodet wrote:
> Please note that the aries-private mailing list is subscription
> moderated and currently restricted to mentors or ASF *members* until
> the community is bootstrapped. So please do not subscribe unless you
> fall into one of those two categories.
Update -- Initial Committers should now be able to subscribe to the
aries-private list, also.
(hopefully all aries community communication will now be on aries
specific mailing lists...)
--kevan
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [aries] Moved geronimo blueprint implementation into aries
podling
Posted by Guillaume Nodet <gn...@gmail.com>.
Please note that the aries-private mailing list is subscription
moderated and currently restricted to mentors or ASF *members* until
the community is bootstrapped. So please do not subscribe unless you
fall into one of those two categories.
On Tue, Sep 29, 2009 at 05:22, Kevan Miller <ke...@gmail.com> wrote:
>
> On Sep 28, 2009, at 3:23 PM, Guillaume Nodet wrote:
>
>> Ok, let's put everything in standby until those lists are created.
>
> OK, the mailing lists have been created. Thanks Brett Porter!
>
> aries-dev-subscribe@incubator.apache.org
> aries-user-subscribe@incubator.apache.org
> aries-commits-subscribe@incubator.apache.org
> aries-private-subscribe@incubator.apache.org
>
> --kevan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [aries] Moved geronimo blueprint implementation into aries podling
Posted by Kevan Miller <ke...@gmail.com>.
On Sep 28, 2009, at 3:23 PM, Guillaume Nodet wrote:
> Ok, let's put everything in standby until those lists are created.
OK, the mailing lists have been created. Thanks Brett Porter!
aries-dev-subscribe@incubator.apache.org
aries-user-subscribe@incubator.apache.org
aries-commits-subscribe@incubator.apache.org
aries-private-subscribe@incubator.apache.org
--kevan
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [aries] Moved geronimo blueprint implementation into aries
podling
Posted by Guillaume Nodet <gn...@gmail.com>.
Ok, let's put everything in standby until those lists are created.
On Mon, Sep 28, 2009 at 21:19, Stuart McCulloch <mc...@gmail.com> wrote:
> 2009/9/29 Alan D. Cabrera <li...@toolazydogs.com>
>
>>
>> On Sep 28, 2009, at 12:01 PM, Guillaume Nodet wrote:
>>
>> 2009/9/28 Alan D. Cabrera <li...@toolazydogs.com>:
>>>
>>>>
>>>> On Sep 28, 2009, at 7:12 AM, Kevan Miller wrote:
>>>>
>>>>
>>>>> On Sep 28, 2009, at 9:32 AM, Guillaume Nodet wrote:
>>>>>
>>>>> On Mon, Sep 28, 2009 at 15:24, David Bosschaert
>>>>>> <da...@gmail.com> wrote:
>>>>>>
>>>>>>>
>>>>>>> Great - let me see if I can make it part of a larger Aries build with
>>>>>>> a
>>>>>>> shared parent pom, a pom in the root dir etc...
>>>>>>> I'd also like to rename some things from Geronimo to Aries...
>>>>>>>
>>>>>>
>>>>>> Sure.
>>>>>> I guess the first thing though is to decide on the svn layout.
>>>>>> I think we should aim for a single trunk/tags/branches for now.
>>>>>> This does no preclude having blueprint released separatly if needed,
>>>>>> but this is another problem we can address later.
>>>>>>
>>>>>
>>>>> Personally, I'd much prefer to see some community setup, prior to these
>>>>> types of discussions and code changes -- mailing lists, committer account
>>>>> setup, etc. The fact that we're forced to discuss this on general@ is,
>>>>> IMO, not very good.
>>>>>
>>>>
>>>> Agreed. Plus a quick 30 minute email discussion does not constitute
>>>> community consensus. While this does not require that everything move lock
>>>> step through community discussions, do not get upset if a discussion moves
>>>> in a different direction after you have made impromptu changes.
>>>>
>>>
>>> That's the whole purpose of RTC, isn't it ?
>>>
>>
>> Yep. I think I pointed that out, albeit obliquely, above. But, since you
>> point this out I'll add a finer point to RTC. The gist of RTC is that as
>> people's work gets more narrowly focused, running every minute detail by the
>> community makes the work impossible. Hence RTC.
>>
>> We are no where near there at this point. We're at the point where
>> newcomers can grok what's going on in the project. It's a perfect time to
>> collect opinions and to build community.
>
>
> +1 I'd really like to see the mailing lists appear asap... it would be
> annoying to have to monitor the general list for Aries discussions
>
>
>> Regards,
>> Alan
>>
>
> --
> Cheers, Stuart
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [aries] Moved geronimo blueprint implementation into aries
podling
Posted by Stuart McCulloch <mc...@gmail.com>.
2009/9/29 Alan D. Cabrera <li...@toolazydogs.com>
>
> On Sep 28, 2009, at 12:01 PM, Guillaume Nodet wrote:
>
> 2009/9/28 Alan D. Cabrera <li...@toolazydogs.com>:
>>
>>>
>>> On Sep 28, 2009, at 7:12 AM, Kevan Miller wrote:
>>>
>>>
>>>> On Sep 28, 2009, at 9:32 AM, Guillaume Nodet wrote:
>>>>
>>>> On Mon, Sep 28, 2009 at 15:24, David Bosschaert
>>>>> <da...@gmail.com> wrote:
>>>>>
>>>>>>
>>>>>> Great - let me see if I can make it part of a larger Aries build with
>>>>>> a
>>>>>> shared parent pom, a pom in the root dir etc...
>>>>>> I'd also like to rename some things from Geronimo to Aries...
>>>>>>
>>>>>
>>>>> Sure.
>>>>> I guess the first thing though is to decide on the svn layout.
>>>>> I think we should aim for a single trunk/tags/branches for now.
>>>>> This does no preclude having blueprint released separatly if needed,
>>>>> but this is another problem we can address later.
>>>>>
>>>>
>>>> Personally, I'd much prefer to see some community setup, prior to these
>>>> types of discussions and code changes -- mailing lists, committer account
>>>> setup, etc. The fact that we're forced to discuss this on general@ is,
>>>> IMO, not very good.
>>>>
>>>
>>> Agreed. Plus a quick 30 minute email discussion does not constitute
>>> community consensus. While this does not require that everything move lock
>>> step through community discussions, do not get upset if a discussion moves
>>> in a different direction after you have made impromptu changes.
>>>
>>
>> That's the whole purpose of RTC, isn't it ?
>>
>
> Yep. I think I pointed that out, albeit obliquely, above. But, since you
> point this out I'll add a finer point to RTC. The gist of RTC is that as
> people's work gets more narrowly focused, running every minute detail by the
> community makes the work impossible. Hence RTC.
>
> We are no where near there at this point. We're at the point where
> newcomers can grok what's going on in the project. It's a perfect time to
> collect opinions and to build community.
+1 I'd really like to see the mailing lists appear asap... it would be
annoying to have to monitor the general list for Aries discussions
> Regards,
> Alan
>
--
Cheers, Stuart
Re: [aries] Moved geronimo blueprint implementation into aries podling
Posted by "Alan D. Cabrera" <li...@toolazydogs.com>.
On Sep 28, 2009, at 12:01 PM, Guillaume Nodet wrote:
> 2009/9/28 Alan D. Cabrera <li...@toolazydogs.com>:
>>
>> On Sep 28, 2009, at 7:12 AM, Kevan Miller wrote:
>>
>>>
>>> On Sep 28, 2009, at 9:32 AM, Guillaume Nodet wrote:
>>>
>>>> On Mon, Sep 28, 2009 at 15:24, David Bosschaert
>>>> <da...@gmail.com> wrote:
>>>>>
>>>>> Great - let me see if I can make it part of a larger Aries build
>>>>> with a
>>>>> shared parent pom, a pom in the root dir etc...
>>>>> I'd also like to rename some things from Geronimo to Aries...
>>>>
>>>> Sure.
>>>> I guess the first thing though is to decide on the svn layout.
>>>> I think we should aim for a single trunk/tags/branches for now.
>>>> This does no preclude having blueprint released separatly if
>>>> needed,
>>>> but this is another problem we can address later.
>>>
>>> Personally, I'd much prefer to see some community setup, prior to
>>> these types of discussions and code changes -- mailing lists,
>>> committer account setup, etc. The fact that we're forced to
>>> discuss this on general@ is, IMO, not very good.
>>
>> Agreed. Plus a quick 30 minute email discussion does not
>> constitute community consensus. While this does not require that
>> everything move lock step through community discussions, do not get
>> upset if a discussion moves in a different direction after you have
>> made impromptu changes.
>
> That's the whole purpose of RTC, isn't it ?
Yep. I think I pointed that out, albeit obliquely, above. But, since
you point this out I'll add a finer point to RTC. The gist of RTC is
that as people's work gets more narrowly focused, running every minute
detail by the community makes the work impossible. Hence RTC.
We are no where near there at this point. We're at the point where
newcomers can grok what's going on in the project. It's a perfect
time to collect opinions and to build community.
Regards,
Alan
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [aries] Moved geronimo blueprint implementation into aries
podling
Posted by Guillaume Nodet <gn...@gmail.com>.
2009/9/28 Alan D. Cabrera <li...@toolazydogs.com>:
>
> On Sep 28, 2009, at 7:12 AM, Kevan Miller wrote:
>
>>
>> On Sep 28, 2009, at 9:32 AM, Guillaume Nodet wrote:
>>
>>> On Mon, Sep 28, 2009 at 15:24, David Bosschaert
>>> <da...@gmail.com> wrote:
>>>>
>>>> Great - let me see if I can make it part of a larger Aries build with a
>>>> shared parent pom, a pom in the root dir etc...
>>>> I'd also like to rename some things from Geronimo to Aries...
>>>
>>> Sure.
>>> I guess the first thing though is to decide on the svn layout.
>>> I think we should aim for a single trunk/tags/branches for now.
>>> This does no preclude having blueprint released separatly if needed,
>>> but this is another problem we can address later.
>>
>> Personally, I'd much prefer to see some community setup, prior to these types of discussions and code changes -- mailing lists, committer account setup, etc. The fact that we're forced to discuss this on general@ is, IMO, not very good.
>
> Agreed. Plus a quick 30 minute email discussion does not constitute community consensus. While this does not require that everything move lock step through community discussions, do not get upset if a discussion moves in a different direction after you have made impromptu changes.
That's the whole purpose of RTC, isn't it ?
> Regards,
> Alan
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [aries] Moved geronimo blueprint implementation into aries podling
Posted by "Alan D. Cabrera" <li...@toolazydogs.com>.
On Sep 28, 2009, at 7:12 AM, Kevan Miller wrote:
>
> On Sep 28, 2009, at 9:32 AM, Guillaume Nodet wrote:
>
>> On Mon, Sep 28, 2009 at 15:24, David Bosschaert
>> <da...@gmail.com> wrote:
>>> Great - let me see if I can make it part of a larger Aries build
>>> with a
>>> shared parent pom, a pom in the root dir etc...
>>> I'd also like to rename some things from Geronimo to Aries...
>>
>> Sure.
>> I guess the first thing though is to decide on the svn layout.
>> I think we should aim for a single trunk/tags/branches for now.
>> This does no preclude having blueprint released separatly if needed,
>> but this is another problem we can address later.
>
> Personally, I'd much prefer to see some community setup, prior to
> these types of discussions and code changes -- mailing lists,
> committer account setup, etc. The fact that we're forced to discuss
> this on general@ is, IMO, not very good.
Agreed. Plus a quick 30 minute email discussion does not constitute
community consensus. While this does not require that everything move
lock step through community discussions, do not get upset if a
discussion moves in a different direction after you have made
impromptu changes.
Regards,
Alan
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [aries] Moved geronimo blueprint implementation into aries podling
Posted by Kevan Miller <ke...@gmail.com>.
On Sep 28, 2009, at 9:32 AM, Guillaume Nodet wrote:
> On Mon, Sep 28, 2009 at 15:24, David Bosschaert
> <da...@gmail.com> wrote:
>> Great - let me see if I can make it part of a larger Aries build
>> with a
>> shared parent pom, a pom in the root dir etc...
>> I'd also like to rename some things from Geronimo to Aries...
>
> Sure.
> I guess the first thing though is to decide on the svn layout.
> I think we should aim for a single trunk/tags/branches for now.
> This does no preclude having blueprint released separatly if needed,
> but this is another problem we can address later.
Personally, I'd much prefer to see some community setup, prior to
these types of discussions and code changes -- mailing lists,
committer account setup, etc. The fact that we're forced to discuss
this on general@ is, IMO, not very good.
--kevan
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [aries] Moved geronimo blueprint implementation into aries podling
Posted by Daniel Kulp <dk...@apache.org>.
On Mon September 28 2009 9:32:05 am Guillaume Nodet wrote:
> On Mon, Sep 28, 2009 at 15:24, David Bosschaert
> > Finally, should we asking INFRA for a Hudson build? Or is this normally
> > not done for podlings?
>
> I guess Hudson should be ok.
There are several people on the aries list that can already setup things in
Hudson (myself for example). Once the lists and stuff are setup, we can
start working on that.
> I don't think podlings can use Nexus for the release, but that needs
> to be double checked.
Yes they can, if they would like to.
Dan
>
> > Cheers,
> >
> > David
> >
> > 2009/9/28 Guillaume Nodet <gn...@gmail.com>
> >
> >> The Geronimo PMC has voted to donate the blueprint implementation to
> >> aries, so I've gone ahead and moved the code to:
> >> https://svn.apache.org/repos/asf/incubator/aries/blueprint/
> >>
> >> I guess we need to discuss how we want to organized the svn tree /
> >> build, and until the mailing lists are set up, we can start discussing
> >> that here.
> >>
> >> --
> >> Cheers,
> >> Guillaume Nodet
> >> ------------------------
> >> Blog: http://gnodet.blogspot.com/
> >> ------------------------
> >> Open Source SOA
> >> http://fusesource.com
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> >> For additional commands, e-mail: general-help@incubator.apache.org
>
--
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [aries] Moved geronimo blueprint implementation into aries
podling
Posted by Guillaume Nodet <gn...@gmail.com>.
I have only set up svn write access to the four mentors. I was
planning on checking with the other ones the right wau to go forward.
On Mon, Sep 28, 2009 at 16:05, David Bosschaert
<da...@gmail.com> wrote:
> 2009/9/28 Guillaume Nodet <gn...@gmail.com>
>
>>
>> Sounds good to me. We need to set up the trunk/tags/branches first I
>> think.
>>
>
> I don't seem to have the permissions to create these. Could someone create
> them or give me enough permissions so I could?
>
> Cheers,
>
> David
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [aries] Moved geronimo blueprint implementation into aries
podling
Posted by David Bosschaert <da...@gmail.com>.
2009/9/28 Guillaume Nodet <gn...@gmail.com>
>
> Sounds good to me. We need to set up the trunk/tags/branches first I
> think.
>
I don't seem to have the permissions to create these. Could someone create
them or give me enough permissions so I could?
Cheers,
David
Re: [aries] Moved geronimo blueprint implementation into aries
podling
Posted by Guillaume Nodet <gn...@gmail.com>.
On Mon, Sep 28, 2009 at 15:46, David Bosschaert
<da...@gmail.com> wrote:
> 2009/9/28 Guillaume Nodet <gn...@gmail.com>
>
>> On Mon, Sep 28, 2009 at 15:24, David Bosschaert
>> <da...@gmail.com> wrote:
>> > Great - let me see if I can make it part of a larger Aries build with a
>> > shared parent pom, a pom in the root dir etc...
>> > I'd also like to rename some things from Geronimo to Aries...
>>
>> Sure.
>> I guess the first thing though is to decide on the svn layout.
>> I think we should aim for a single trunk/tags/branches for now.
>> This does no preclude having blueprint released separatly if needed,
>> but this is another problem we can address later.
>>
>
> Yes, I was thinking a single build system for now. The layout would be:
> /pom.xml (references all the submodules), can be used to kick off a build
> for everything in Aries
> /parent/... (parent poms, I was thinking of taking the ones from Geronimo
> Genesis as the starting point
> /blueprint (blueprint submodule)
> /xyz (other submodule)
Sounds good to me. We need to set up the trunk/tags/branches first I think.
>
>>
>> > Finally, should we asking INFRA for a Hudson build? Or is this normally
>> not
>> > done for podlings?
>>
>> I guess Hudson should be ok.
>> I don't think podlings can use Nexus for the release, but that needs
>> to be double checked.
>>
>>
> I will get back when the root pom.xml is there. Dan or someone else with
> Hudson credentials can then enable.
>
> Cheers,
>
> David
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [aries] Moved geronimo blueprint implementation into aries
podling
Posted by David Bosschaert <da...@gmail.com>.
2009/9/28 Guillaume Nodet <gn...@gmail.com>
> On Mon, Sep 28, 2009 at 15:24, David Bosschaert
> <da...@gmail.com> wrote:
> > Great - let me see if I can make it part of a larger Aries build with a
> > shared parent pom, a pom in the root dir etc...
> > I'd also like to rename some things from Geronimo to Aries...
>
> Sure.
> I guess the first thing though is to decide on the svn layout.
> I think we should aim for a single trunk/tags/branches for now.
> This does no preclude having blueprint released separatly if needed,
> but this is another problem we can address later.
>
Yes, I was thinking a single build system for now. The layout would be:
/pom.xml (references all the submodules), can be used to kick off a build
for everything in Aries
/parent/... (parent poms, I was thinking of taking the ones from Geronimo
Genesis as the starting point
/blueprint (blueprint submodule)
/xyz (other submodule)
>
> > Finally, should we asking INFRA for a Hudson build? Or is this normally
> not
> > done for podlings?
>
> I guess Hudson should be ok.
> I don't think podlings can use Nexus for the release, but that needs
> to be double checked.
>
>
I will get back when the root pom.xml is there. Dan or someone else with
Hudson credentials can then enable.
Cheers,
David
Re: [aries] Moved geronimo blueprint implementation into aries
podling
Posted by Guillaume Nodet <gn...@gmail.com>.
On Mon, Sep 28, 2009 at 15:24, David Bosschaert
<da...@gmail.com> wrote:
> Great - let me see if I can make it part of a larger Aries build with a
> shared parent pom, a pom in the root dir etc...
> I'd also like to rename some things from Geronimo to Aries...
Sure.
I guess the first thing though is to decide on the svn layout.
I think we should aim for a single trunk/tags/branches for now.
This does no preclude having blueprint released separatly if needed,
but this is another problem we can address later.
> Finally, should we asking INFRA for a Hudson build? Or is this normally not
> done for podlings?
I guess Hudson should be ok.
I don't think podlings can use Nexus for the release, but that needs
to be double checked.
> Cheers,
>
> David
>
> 2009/9/28 Guillaume Nodet <gn...@gmail.com>
>
>> The Geronimo PMC has voted to donate the blueprint implementation to
>> aries, so I've gone ahead and moved the code to:
>> https://svn.apache.org/repos/asf/incubator/aries/blueprint/
>>
>> I guess we need to discuss how we want to organized the svn tree /
>> build, and until the mailing lists are set up, we can start discussing
>> that here.
>>
>> --
>> Cheers,
>> Guillaume Nodet
>> ------------------------
>> Blog: http://gnodet.blogspot.com/
>> ------------------------
>> Open Source SOA
>> http://fusesource.com
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org