Repository Merging

[Bob McWhirter]

It was discussed that perhaps we should simplify our repository  
layout, and make a mongo repo for -driver, -framework, and maybe - 
client-ruby.

I've done a candidate merge with git-filter-branch, preserving history  
across all of the repos into a single merged repo.

I've staged it upon my GitHub account:

http://github.com/bobmcwhirter/deltacloud-merge

You can view merged commit history here:

http://github.com/bobmcwhirter/deltacloud-merge/commits/master

If this looks roughly good, I'll finish tidying up (making a top-level  
COPYING and a README), adjust the -framework startup code to look for  
drivers in the right place.

Then we'll need to figure out where in FedoraHosted we want it to  
live.  Do we want to get a fresh repo (just plain "deltacloud" ?) and  
push there?  What's the process for getting a new repo?

After that, we'll want to destroy the old no-longer-relevant repos.

Thoughts, comments and feedback muchly appreciated.

Thanks,

-Bob

[Bob McWhirter]

I'd like to propose creating a new repository with a name similar or  
identical to

foundation.git

I don't think framework.git is appropriate any more.

And I think rest.git or api.git is also a misnomer, since portal.git  
also will have a RESTful API.

This repository now contains both client/server at the foundational  
layer, so foundation.git makes sense to me, personally.

Thoughts?  Objections?

-Bob

On Nov 30, 2009, at 10:57 AM, Bob McWhirter wrote:
> It was discussed that perhaps we should simplify our repository
> layout, and make a mongo repo for -driver, -framework, and maybe -
> client-ruby.
>
> I've done a candidate merge with git-filter-branch, preserving history
> across all of the repos into a single merged repo.
>
> I've staged it upon my GitHub account:
>
> http://github.com/bobmcwhirter/deltacloud-merge
>
> You can view merged commit history here:
>
> http://github.com/bobmcwhirter/deltacloud-merge/commits/master
>
> If this looks roughly good, I'll finish tidying up (making a top-level
> COPYING and a README), adjust the -framework startup code to look for
> drivers in the right place.
>
> Then we'll need to figure out where in FedoraHosted we want it to
> live.  Do we want to get a fresh repo (just plain "deltacloud" ?) and
> push there?  What's the process for getting a new repo?
>
> After that, we'll want to destroy the old no-longer-relevant repos.
>
> Thoughts, comments and feedback muchly appreciated.
>
> Thanks,
>
> -Bob
>
> deltacloud-devel mailing list
> [e-mail]
> https://fedorahosted.org/mailman/listinfo/deltacloud-devel

[Michael Neale]

I like it.

On Tue, Dec 1, 2009 at 2:57 AM, Bob McWhirter  wrote:
> It was discussed that perhaps we should simplify our repository
> layout, and make a mongo repo for -driver, -framework, and maybe -
> client-ruby.
>
> I've done a candidate merge with git-filter-branch, preserving history
> across all of the repos into a single merged repo.
>
> I've staged it upon my GitHub account:
>
> http://github.com/bobmcwhirter/deltacloud-merge
>
> You can view merged commit history here:
>
> http://github.com/bobmcwhirter/deltacloud-merge/commits/master
>
> If this looks roughly good, I'll finish tidying up (making a top-level
> COPYING and a README), adjust the -framework startup code to look for
> drivers in the right place.
>
> Then we'll need to figure out where in FedoraHosted we want it to
> live.  Do we want to get a fresh repo (just plain "deltacloud" ?) and
> push there?  What's the process for getting a new repo?
>
> After that, we'll want to destroy the old no-longer-relevant repos.
>
> Thoughts, comments and feedback muchly appreciated.
>
> Thanks,
>
> -Bob
>
> deltacloud-devel mailing list
> [e-mail]
> https://fedorahosted.org/mailman/listinfo/deltacloud-devel