We have 9 preferences to go with option 2 and 2 preferences to go with
option 1. I'll create the folder structure according to option 2 and create
Jira [1] for moving individual components from contribution to trunk. This
way,  non-committers can assign the issues to them and contribute to the
project.

Regards,
Shankar

[1] https://issues.apache.org/jira/browse/STONEHENGE


On Sat, Jan 31, 2009 at 8:04 AM, Sanjiva Weerawarana
<[email protected]>wrote:

> Do we have enough consensus to go ahead now? I think any of us can live
> with either one .. so please compute the consensus and execute :).
>
> We need to get the show on the road ..
>
> Sanjiva.
>
>
> Selvaratnam Uthaiyashankar wrote:
>
>> Hi,
>>
>> If we can decide on a folder structure for trunk, we can start move the
>> code
>> from "contrib" and start to do the improvements.
>>
>> We can organize the folder structure in two ways.
>>
>> (1) Organize based on components and then on framework
>> E.g: trunk/stocktrader/
>>        |
>>        +-business_service
>>        |    |
>>        |    +- dotnet
>>        |    |
>>        |    +- java
>>        |    |
>>        |    +- axis2
>>        |    |
>>        |    +- PHP
>>        |
>>        +-order_processor
>>            |
>>            +-dotnet
>>            |
>>            +-java
>>
>>
>> (2) Organize based on framework and then on component
>> E.g: trunk/stocktrader/
>>        |
>>        +-dotnet
>>        |    |
>>        |    +- business_service
>>        |    |
>>        |    +- order_processor
>>        |    |
>>        |    +- trader_client
>>        |
>>        +-Java
>>        |    |
>>        |    +-business_service
>>        |    |
>>        |    +-order_processor
>>        |
>>        +-axis2
>>            |
>>            +-business_service
>>            |
>>            +-order_processor
>>
>> Which one do you think is the better approach? IMHO, (2) is better because
>> when we have another application "AppXYZ", we still can have same folder
>> structure (first based on framework level and then on application specific
>> component level). Also, people are interested in how to implement using a
>> framework rather than how a component is implemented in different
>> frameworks. WDYT?
>>
>> Since we are going to have code from Axis2, CXF and Metro, and all of them
>> are written in Java, we can identify common code and keep it inside "java"
>> and move framework specific code inside respective frameworks. i.e we can
>> have "axis2", "cxf", "metro" folders and all of them can use jar from
>> "java"
>> folder.
>>
>> Thoughts?
>>
>> Regards,
>> Shankar
>>
>>
>>
>
> --
> Sanjiva Weerawarana, Ph.D.
> Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
> Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
> Member; Apache Software Foundation; http://www.apache.org/
> Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
>
> Blog: http://sanjiva.weerawarana.org/
>



-- 
S.Uthaiyashankar
Software Architect
WSO2 Inc.
http://wso2.com/ - "The Open Source SOA Company"

Reply via email to