svn structure

[Ross Gardler <rg...@apache.org>]

I'm playing with creating a widget to talk to the basecamp API (later
I will add code to work with my own projectAdmin app, but I may as
well do something with a wide user base first).

I've not set up a Wookie yet, instead I'm using the Opera browser to
test things. However, I'd like to get this code into svn, primarily so
that people who know widgets better than I do can keep an eye on what
I am doing. This raises a question, where should I put the code?

My intention is to create some ant scripts that will build and package
one or more of the widgets found in a widget source directory. We can
do it a number of ways, I'd suggest one of:

trunk -> wookie
trunk -> widgets -> ant.xml
trunk -> widgets -> widgetA -> ant.xml
trunk -> widgets -> widgetB -> ant.xml

or

wookie -> trunk
widgets -> trunk -> ant.xml
widgets -> trunk -> widgetA -> ant.xml
widgets -> trunk -> widgetB -> ant.xml

If the committers would like to indicate their preference then I will
provide a patch with my starter code (yes, I do have write access to
the repo, but I feel that mentors/champions should earn merit in the
project just like everyone else).

Ross

-- 
Ross Gardler

OSS Watch - supporting open source in education and research
http://www.oss-watch.ac.uk

Re: svn structure

[Paul Sharples <p....@bolton.ac.uk>]

Okay, go with the former.

Paul

Scott Wilson wrote:
> I'd opt for the former as it gives us the option of building Wookie 
> including additional Widgets, which may be useful.
>
> Paul, Kris - any preferences?
>
> On 5 Aug 2009, at 22:59, Ross Gardler wrote:
>
>> I'm playing with creating a widget to talk to the basecamp API (later
>> I will add code to work with my own projectAdmin app, but I may as
>> well do something with a wide user base first).
>>
>> I've not set up a Wookie yet, instead I'm using the Opera browser to
>> test things. However, I'd like to get this code into svn, primarily so
>> that people who know widgets better than I do can keep an eye on what
>> I am doing. This raises a question, where should I put the code?
>>
>> My intention is to create some ant scripts that will build and package
>> one or more of the widgets found in a widget source directory. We can
>> do it a number of ways, I'd suggest one of:
>>
>> trunk -> wookie
>> trunk -> widgets -> ant.xml
>> trunk -> widgets -> widgetA -> ant.xml
>> trunk -> widgets -> widgetB -> ant.xml
>>
>> or
>>
>> wookie -> trunk
>> widgets -> trunk -> ant.xml
>> widgets -> trunk -> widgetA -> ant.xml
>> widgets -> trunk -> widgetB -> ant.xml
>>
>> If the committers would like to indicate their preference then I will
>> provide a patch with my starter code (yes, I do have write access to
>> the repo, but I feel that mentors/champions should earn merit in the
>> project just like everyone else).
>>
>> Ross
>>
>> -- 
>> Ross Gardler
>>
>> OSS Watch - supporting open source in education and research
>> http://www.oss-watch.ac.uk
>

Re: svn structure

[Scott Wilson <sc...@gmail.com>]

I'd opt for the former as it gives us the option of building Wookie  
including additional Widgets, which may be useful.

Paul, Kris - any preferences?

On 5 Aug 2009, at 22:59, Ross Gardler wrote:

> I'm playing with creating a widget to talk to the basecamp API (later
> I will add code to work with my own projectAdmin app, but I may as
> well do something with a wide user base first).
>
> I've not set up a Wookie yet, instead I'm using the Opera browser to
> test things. However, I'd like to get this code into svn, primarily so
> that people who know widgets better than I do can keep an eye on what
> I am doing. This raises a question, where should I put the code?
>
> My intention is to create some ant scripts that will build and package
> one or more of the widgets found in a widget source directory. We can
> do it a number of ways, I'd suggest one of:
>
> trunk -> wookie
> trunk -> widgets -> ant.xml
> trunk -> widgets -> widgetA -> ant.xml
> trunk -> widgets -> widgetB -> ant.xml
>
> or
>
> wookie -> trunk
> widgets -> trunk -> ant.xml
> widgets -> trunk -> widgetA -> ant.xml
> widgets -> trunk -> widgetB -> ant.xml
>
> If the committers would like to indicate their preference then I will
> provide a patch with my starter code (yes, I do have write access to
> the repo, but I feel that mentors/champions should earn merit in the
> project just like everyone else).
>
> Ross
>
> -- 
> Ross Gardler
>
> OSS Watch - supporting open source in education and research
> http://www.oss-watch.ac.uk