On Mon, Jul 23, 2012 at 9:56 AM, cweiske cwei...@cweiske.de wrote:
Hi,
I'd like to be able to fork/clone a remote repository that is not hosted
on the gitorious instance I'm currently using.
Technically, the most easy implementation is to give the user a Remote
git URL text field which he can fill. Upon creating the local repository,
the data are cloned from the given remote url.
Very nifty would be if the user didn't have to know the Git URL at all,
but only the homepage of the project he wants to fork. The homepage (HTML)
would contain a link to the project's DOAP[1] description. The DOAP
description itself contains the link to the git repository, which would be
cloned.
Using the DOAP file would even allow gitorious to fill the name and
description fields.
Huh, that would be awesome! Did you put any thought into how this would
work from a user's/technical perspective? My initial thought is something
like this:
(- assuming the project exists)
- select add repository on the project page
- [server]: find the fork remote repository section on the page, enter
the upstream URL into a field. Redirect user to new repo page, which will
be displayed with a spinner creating...
- [server]: fetch the upstream project URL, extract git url
- [server]: initialize a Gitorious repository, create the bare .git
- [server]: do a git pull upstream URL from above
- the three steps above should probably be performed async, since it could
take some time
By supporting remote repository forking, gitorious would even more support
the federated internet.
Absolutely!
Feel like giving it a shot?
- M
--
To post to this group, send email to gitorious@googlegroups.com
To unsubscribe from this group, send email to
gitorious+unsubscr...@googlegroups.com
