You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@infra.apache.org by "Semyon Vadishev (JIRA)" <ji...@apache.org> on 2012/11/23 17:54:59 UTC
[jira] [Comment Edited] (INFRA-4641) Update GitHub mirroring
[ https://issues.apache.org/jira/browse/INFRA-4641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13503247#comment-13503247 ]
Semyon Vadishev edited comment on INFRA-4641 at 11/23/12 4:53 PM:
------------------------------------------------------------------
Hi, I've just come across the discussion at the mailing list on ASF — GitHub mirroring. The thing is that I'm working on SubGit, http://subgit.com/ and I think ASF community would benefit a lot from using our tool.
We've just published SubGit 2.0 beta version that enables bi-directional synchronization of Git and SVN repositories located on different hosts (both repositories remain active). And we're going to improve SubGit, so it can be installed into any SVN repository and synchronize changes with GitHub (or any other Git hosting) automatically.
I doubt there're major technical issues with using SubGit at ASF servers. More questions come from licensing side of things. Here's what I'd like to mention:
1. SubGit is a commercial tool, but it's free for open-source projects.
2. Our partners get access to SubGit source code.
3. Currently we're considering the option to open-source the core SubGit library under the terms of GPL license. But so far we have no final decision in this regard.
Your questions and suggestions are welcome at support@subgit.com and here.
was (Author: vadishev):
Hi, I've just come across the discussion at the mailing list on ASF — GitHub mirroring. The thing is that I'm working on SubGit, http://subgit.com/ and I think ASF community would benefit a lot from using our tool.
We've just published SubGit 2.0 beta version that enables bi-directional synchronization of Git and SVN repositories located on different hosts (both repositories remain active). And we're going to improve SubGit, so it can be installed into any SVN repository and synchronize changes with GitHub (or any other Git hosting) automatically.
I doubt there're major technical issues with using SubGit at ASF servers. More questions come from licensing side of things. Here's what I'd like to mention:
1. SubGit is a commercial tool, but it's free for open-source projects.
2. Our partners get access to SubGit source code.
3. Currently we're considering the option to open-source the core SubGit library under the terms on GPL license. But so far we have no final decision in this regard.
Your questions and suggestions are welcome at support@subgit.com and here.
> Update GitHub mirroring
> -----------------------
>
> Key: INFRA-4641
> URL: https://issues.apache.org/jira/browse/INFRA-4641
> Project: Infrastructure
> Issue Type: Sub-task
> Security Level: public(Regular issues)
> Components: Git
> Reporter: Jukka Zitting
> Priority: Minor
>
> Currently GitHub uses a custom script to periodically parse http://git.apache.org/ and to automatically mirror all repositories found there.
> We should work with them to either adjust that script to work against http://git-wip-us.apache.org/ or (preferably) come up with a way for us to more actively create and manage mirrors on GitHub.
> We should also be able to automatically push changes to GitHub as soon as they occur on our svn or git repositories. We should make sure that such automatic pushing won't interfere with the mirroring scripts GitHub has in place.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira