geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alan D. Cabrera" <l...@toolazydogs.com>
Subject Re: [discuss] Eclipse as a Geronimo sub-project
Date Wed, 24 Aug 2005 02:22:29 GMT
NM, I changed my mind.  I guess this will be the same as when we get the 
CORBA donation.  It makes sense to me in that there is a reasonable 
expectation that this will be a vibrant sub-project and if it's not, we 
can just pull it in.


Regards,
Alan

Geir Magnusson Jr. wrote, On 8/23/2005 4:56 PM:

> Yes, it certainly can.   But one thing we're trying to do is build a  
> like-minded community of tools people.   We did something like this  
> very effectively (IMO) at Velocity, making it separate and letting  
> them setup things like web content, build structure, packaging,  
> releases, etc.
>
> What's the downside to starting to bucket functionality this way?   
> What bad things could happen if we made a subdirectory for tooling,  
> letting it be a separate build (and release cycle), and having a  
> subpage on the website behind a left-nav item?
>
> geir
>
>
> On Aug 23, 2005, at 7:50 PM, Alan D. Cabrera wrote:
>
>> It can go into a tools directory, just like we have a modules  
>> directory.
>>
>>
>> Regards,
>> Alan
>>
>> Geir Magnusson Jr. wrote, On 8/23/2005 4:34 PM:
>>
>>
>>> Tooling is one of our major initiatives to "knock the corners  
>>> off".   How do you integrate an eclipse plug in directly in  
>>> Geroniomo?  It's  for Eclipse, isn't it?
>>>
>>> I think it just makes sense to have a subproject on tooling, and   
>>> start producing releases independently...  I agree that Eclipse  is  
>>> too small by itself (as I noted in a previous email), but  general  
>>> tool isn't, and the eclipse plug in is an excellent  start....
>>>
>>> geir
>>>
>>> On Aug 23, 2005, at 4:28 PM, Alan D. Cabrera wrote:
>>>
>>>
>>>> Dain Sundstrom wrote, On 8/22/2005 9:14 PM:
>>>>
>>>>
>>>>
>>>>> On Aug 22, 2005, at 8:24 PM, Geir Magnusson Jr. wrote:
>>>>>
>>>>>
>>>>>
>>>>>> So we now have a subproject policy.
>>>>>>
>>>>>> Any thoughts on taking the IBM eclipse tooling contribution as  
>>>>>> a   subproject?  It's independent, has interested people that  
>>>>>> are   annoying us with patches :) adds value to the project and 

>>>>>> grows  the  community in a technically diverse way,  and has a  
>>>>>> plausible  roadmap.
>>>>>>
>>>>>> I would suggest that if we do so, we'd move the current code   
>>>>>> from  sandbox and add Sachin Patel as a committer for the   
>>>>>> subproject.
>>>>>>
>>>>>> This is a sensitive issue because of there's a person  involved,
 
>>>>>> so  if anyone has any issues that need to be  discussed  
>>>>>> confidentially,  please feel free to post to   
>>>>>> pmc@geronimo.apache.org, or mail to me  or another PMC member.
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> I think it is a bit premature to make this a full fledged    
>>>>> subproject.  I personally don't use eclipse so I don't know if  
>>>>> it   builds, or is what users want.  For now, I think the  sandbox 
>>>>> is   appropriate place to incubate the code and  community.   We 
>>>>> need to  be  careful when creating subprojects,  so we don't end 
>>>>> up with  lots of  abandoned codebases.  I  guessing this will 
>>>>> happen quickly  for the  eclipse plugin given  how many eclipse 
>>>>> users there are out  there and  we will be  better off for waiting 
>>>>> a bit.
>>>>>
>>>>>
>>>>
>>>>
>>>> I agree.  I think that this is a bit premature to make this a  
>>>> full  fledged subproject.  This should start in the sandbox with  
>>>> the idea  that it be integrated directly into Geronimo.
>>>>
>>>>
>>>> Regards,
>>>> Alan
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>>
>



Mime
View raw message