Dev - specialized and website folders in SVN tree

[Jacopo Cappellato]

What do you think about moving the specialized and website folders
outside of the svn "trunk" folder?

I think it would be nice to change the svn tree from this (the current
structure):

branches/
tags/
trunk/base
trunk/applications
trunk/framework
trunk/specialized
trunk/website

to this:

branches/
tags/
specialized/
website/
trunk/base
trunk/applications
trunk/framework

Advantages:

1) quicker downloads for the ones that are not interested in playing
with the OFBiz's website and with the specialized folders

2) cleaner separation between the *software* itself and other (official)
resources such as documentation, vertical applications etc...

One last question: will we move the specialized and the website
components to the ASF svn server?

Jacopo

 
_______________________________________________
Dev mailing list
[hidden email]
http://lists.ofbiz.org/mailman/listinfo/dev

[Andrew Zeneski]

The suggested structure for SVN is

branches/
tags/
trunk/

Keeping the latest in trunk having a standard way of getting to tags  
and branches. If this change was to happen, I would prefer it to be  
something like:

trunk/ofbiz
trunk/website
trunk/specialized

However, with the move to apache SVN this doesn't seem worth it. I  
don't think these two will go with us, but if they did we can re-
organize it at that time.

Andy

On May 17, 2006, at 12:24 PM, Jacopo Cappellato wrote:

> What do you think about moving the specialized and website folders
> outside of the svn "trunk" folder?
>
> I think it would be nice to change the svn tree from this (the current
> structure):
>
> branches/
> tags/
> trunk/base
> trunk/applications
> trunk/framework
> trunk/specialized
> trunk/website
>
> to this:
>
> branches/
> tags/
> specialized/
> website/
> trunk/base
> trunk/applications
> trunk/framework
>
> Advantages:
>
> 1) quicker downloads for the ones that are not interested in playing
> with the OFBiz's website and with the specialized folders
>
> 2) cleaner separation between the *software* itself and other  
> (official)
> resources such as documentation, vertical applications etc...
>
> One last question: will we move the specialized and the website
> components to the ASF svn server?
>
> Jacopo
>
>
> _______________________________________________
> Dev mailing list
> [hidden email]
> http://lists.ofbiz.org/mailman/listinfo/dev

 
_______________________________________________
Dev mailing list
[hidden email]
http://lists.ofbiz.org/mailman/listinfo/dev

[Jacques Le Roux]

> The suggested structure for SVN is
>
> branches/
> tags/
> trunk/
>
> Keeping the latest in trunk having a standard way of getting to tags  
> and branches. If this change was to happen, I would prefer it to be  
> something like:
>
> trunk/ofbiz
> trunk/website
> trunk/specialized
>
> However, with the move to apache SVN this doesn't seem worth it. I  
> don't think these two will go with us, but if they did we can re-
> organize it at that time.
>
> Andy

So waiting for Apache ?

Jacques

 

> On May 17, 2006, at 12:24 PM, Jacopo Cappellato wrote:
>
> > What do you think about moving the specialized and website folders
> > outside of the svn "trunk" folder?
> >
> > I think it would be nice to change the svn tree from this (the current
> > structure):
> >
> > branches/
> > tags/
> > trunk/base
> > trunk/applications
> > trunk/framework
> > trunk/specialized
> > trunk/website
> >
> > to this:
> >
> > branches/
> > tags/
> > specialized/
> > website/
> > trunk/base
> > trunk/applications
> > trunk/framework
> >
> > Advantages:
> >
> > 1) quicker downloads for the ones that are not interested in playing
> > with the OFBiz's website and with the specialized folders
> >
> > 2) cleaner separation between the *software* itself and other  
> > (official)
> > resources such as documentation, vertical applications etc...
> >
> > One last question: will we move the specialized and the website
> > components to the ASF svn server?
> >
> > Jacopo
> >
> >
> > _______________________________________________
> > Dev mailing list
> > [hidden email]
> > http://lists.ofbiz.org/mailman/listinfo/dev
>
>  
> _______________________________________________
> Dev mailing list
> [hidden email]
> http://lists.ofbiz.org/mailman/listinfo/dev

 
_______________________________________________
Dev mailing list
[hidden email]
http://lists.ofbiz.org/mailman/listinfo/dev

[Vinay Agarwal]

I like this structure. Do we really have to wait for Apache move?
> trunk/ofbiz
> trunk/website
> trunk/specialized


-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On
Behalf Of Jacques Le Roux
Sent: Wednesday, May 17, 2006 10:45 AM
To: OFBiz Project Development Discussion
Subject: Re: [OFBiz] Dev - specialized and website folders in SVN tree

> The suggested structure for SVN is
>
> branches/
> tags/
> trunk/
>
> Keeping the latest in trunk having a standard way of getting to tags  
> and branches. If this change was to happen, I would prefer it to be  
> something like:
>
> trunk/ofbiz
> trunk/website
> trunk/specialized
>
> However, with the move to apache SVN this doesn't seem worth it. I  
> don't think these two will go with us, but if they did we can re-
> organize it at that time.
>
> Andy

So waiting for Apache ?

Jacques

 

> On May 17, 2006, at 12:24 PM, Jacopo Cappellato wrote:
>
> > What do you think about moving the specialized and website folders
> > outside of the svn "trunk" folder?
> >
> > I think it would be nice to change the svn tree from this (the current
> > structure):
> >
> > branches/
> > tags/
> > trunk/base
> > trunk/applications
> > trunk/framework
> > trunk/specialized
> > trunk/website
> >
> > to this:
> >
> > branches/
> > tags/
> > specialized/
> > website/
> > trunk/base
> > trunk/applications
> > trunk/framework
> >
> > Advantages:
> >
> > 1) quicker downloads for the ones that are not interested in playing
> > with the OFBiz's website and with the specialized folders
> >
> > 2) cleaner separation between the *software* itself and other  
> > (official)
> > resources such as documentation, vertical applications etc...
> >
> > One last question: will we move the specialized and the website
> > components to the ASF svn server?
> >
> > Jacopo
> >
> >
> > _______________________________________________
> > Dev mailing list
> > [hidden email]
> > http://lists.ofbiz.org/mailman/listinfo/dev
>
>  
> _______________________________________________
> Dev mailing list
> [hidden email]
> http://lists.ofbiz.org/mailman/listinfo/dev

 
_______________________________________________
Dev mailing list
[hidden email]
http://lists.ofbiz.org/mailman/listinfo/dev
 
_______________________________________________
Dev mailing list
[hidden email]
http://lists.ofbiz.org/mailman/listinfo/dev

[David E. Jones]

I agree, no real reason to do this until we do the Apache SVN move (which will hopefully be soon...). When we do that we'll have to reorganize things anyway, and the current SVN repository will be very different...

-David


A. Zeneski wrote:

> The suggested structure for SVN is
>
> branches/
> tags/
> trunk/
>
> Keeping the latest in trunk having a standard way of getting to tags  
> and branches. If this change was to happen, I would prefer it to be  
> something like:
>
> trunk/ofbiz
> trunk/website
> trunk/specialized
>
> However, with the move to apache SVN this doesn't seem worth it. I  
> don't think these two will go with us, but if they did we can re-
> organize it at that time.
>
> Andy
>
> On May 17, 2006, at 12:24 PM, Jacopo Cappellato wrote:
>
>> What do you think about moving the specialized and website folders
>> outside of the svn "trunk" folder?
>>
>> I think it would be nice to change the svn tree from this (the current
>> structure):
>>
>> branches/
>> tags/
>> trunk/base
>> trunk/applications
>> trunk/framework
>> trunk/specialized
>> trunk/website
>>
>> to this:
>>
>> branches/
>> tags/
>> specialized/
>> website/
>> trunk/base
>> trunk/applications
>> trunk/framework
>>
>> Advantages:
>>
>> 1) quicker downloads for the ones that are not interested in playing
>> with the OFBiz's website and with the specialized folders
>>
>> 2) cleaner separation between the *software* itself and other  
>> (official)
>> resources such as documentation, vertical applications etc...
>>
>> One last question: will we move the specialized and the website
>> components to the ASF svn server?
>>
>> Jacopo
>>
>>
>> _______________________________________________
>> Dev mailing list
>> [hidden email]
>> http://lists.ofbiz.org/mailman/listinfo/dev
>
>  
> _______________________________________________
> Dev mailing list
> [hidden email]
> http://lists.ofbiz.org/mailman/listinfo/dev

 
_______________________________________________
Dev mailing list
[hidden email]
http://lists.ofbiz.org/mailman/listinfo/dev

[Leon Torres-2]

Is Apache still doing the one SVN repository for all projects, where the
revision number can jump a lot between commits? Or are they doing one repository
per project?

- Leon



David E Jones wrote:
> I agree, no real reason to do this until we do the Apache SVN move (which will hopefully be soon...). When we do that we'll have to reorganize things anyway, and the current SVN repository will be very different...
>
> -David
>
 
_______________________________________________
Dev mailing list
[hidden email]
http://lists.ofbiz.org/mailman/listinfo/dev

[Christian Geisert]

Leon Torres schrieb:
> Is Apache still doing the one SVN repository for all projects, where the
> revision number can jump a lot between commits? Or are they doing one repository
> per project?

It's one repository for all projects

Christian

 
_______________________________________________
Dev mailing list
[hidden email]
http://lists.ofbiz.org/mailman/listinfo/dev

[David E. Jones]

Hmmm... kind of a pain. Hopefully we can arrange an alternative, but if not I guess that's the way it will be. I hope they have a good reason for it... if it's just a matter of resources to setup a new repository I say we raise whatever funds are needed to get it done...

-David


Christian Geisert wrote:

> Leon Torres schrieb:
>> Is Apache still doing the one SVN repository for all projects, where the
>> revision number can jump a lot between commits? Or are they doing one repository
>> per project?
>
> It's one repository for all projects
>
> Christian
>
>  
> _______________________________________________
> Dev mailing list
> [hidden email]
> http://lists.ofbiz.org/mailman/listinfo/dev

 
_______________________________________________
Dev mailing list
[hidden email]
http://lists.ofbiz.org/mailman/listinfo/dev

[Jacopo Cappellato]

+1

:-)

David E Jones wrote:

> Hmmm... kind of a pain. Hopefully we can arrange an alternative, but if not I guess that's the way it will be. I hope they have a good reason for it... if it's just a matter of resources to setup a new repository I say we raise whatever funds are needed to get it done...
>
> -David
>
>
> Christian Geisert wrote:
>> Leon Torres schrieb:
>>> Is Apache still doing the one SVN repository for all projects, where the
>>> revision number can jump a lot between commits? Or are they doing one repository
>>> per project?
>> It's one repository for all projects
>>
>> Christian
>>
>>  
>> _______________________________________________
>> Dev mailing list
>> [hidden email]
>> http://lists.ofbiz.org/mailman/listinfo/dev
>  
> _______________________________________________
> Dev mailing list
> [hidden email]
> http://lists.ofbiz.org/mailman/listinfo/dev
>

 
_______________________________________________
Dev mailing list
[hidden email]
http://lists.ofbiz.org/mailman/listinfo/dev

[Jacques Le Roux]

+1

Jacques

----- Original Message -----
From: "Jacopo Cappellato" <[hidden email]>
To: "OFBiz Project Development Discussion" <[hidden email]>
Sent: Thursday, May 18, 2006 6:06 AM
Subject: Re: [OFBiz] Dev - specialized and website folders in SVN tree


> +1
>
> :-)
>
> David E Jones wrote:
> > Hmmm... kind of a pain. Hopefully we can arrange an alternative, but if not
I guess that's the way it will be. I hope they have a good reason for it... if
it's just a matter of resources to setup a new repository I say we raise
whatever funds are needed to get it done...
> >
> > -David
> >
> >
> > Christian Geisert wrote:
> >> Leon Torres schrieb:
> >>> Is Apache still doing the one SVN repository for all projects, where the
> >>> revision number can jump a lot between commits? Or are they doing one
repository

> >>> per project?
> >> It's one repository for all projects
> >>
> >> Christian
> >>
> >>
> >> _______________________________________________
> >> Dev mailing list
> >> [hidden email]
> >> http://lists.ofbiz.org/mailman/listinfo/dev
> >
> > _______________________________________________
> > Dev mailing list
> > [hidden email]
> > http://lists.ofbiz.org/mailman/listinfo/dev
> >
>
>
> _______________________________________________
> Dev mailing list
> [hidden email]
> http://lists.ofbiz.org/mailman/listinfo/dev

 
_______________________________________________
Dev mailing list
[hidden email]
http://lists.ofbiz.org/mailman/listinfo/dev

[davidnwelton]

> Hmmm... kind of a pain. Hopefully we can arrange an alternative, but if not I guess that's the way it will be. I hope they have a good reason for it... if it's just a matter of resources to setup a new [SVN - davidw] repository I say we raise whatever funds are needed to get it done...

I think it's more likely a problem of ongoing, maintainance resources
- i.e. having someone take care of managing the repository, backing it
up, and so on.

--
David N. Welton
 - http://www.dedasys.com/davidw/

Linux, Open Source Consulting
 - http://www.dedasys.com/
 
_______________________________________________
Dev mailing list
[hidden email]
http://lists.ofbiz.org/mailman/listinfo/dev

[Christian Geisert]

David Welton schrieb:
>>Hmmm... kind of a pain. Hopefully we can arrange an alternative, but if not I guess that's the way it will be. I hope they have a good reason for it... if it's just a matter of resources to setup a new [SVN - davidw] repository I say we raise whatever funds are needed to get it done...
>
> I think it's more likely a problem of ongoing, maintainance resources
> - i.e. having someone take care of managing the repository, backing it
> up, and so on.

Yes, managing access control, hooks, moving between projects etc. is a
lot simpler with one repository instead of dozens (some of the
infrastructure people are also subversion developers so they should know
what they are doing ;-)

We could ask on infrastructure@ but I guess they won't be very
enthusiastic about the idea ...

Why is a continous revesion number that important?

--
Christian
 
_______________________________________________
Dev mailing list
[hidden email]
http://lists.ofbiz.org/mailman/listinfo/dev