|
I know that git support was deprecated in favor of SVN some time ago: Why did the OSQA source code move from git to svn? Nevertheless, I'm used to git, so having recently switched my project from Shapado to OSQA, I now host my fork on GitHub. What I do at the moment is to manually clone the official SVN trunk into a vendor branch and update ( I see that the official repo is really outdated. sghael's clone seems to be mostly keeping up with SVN. I pondered if reviving some kind of official repo wouldn't be a good move? As said, at the moment I'm keeping a git-svn mirror either way, but it's on my branch, not an official repo. Plus it's not updated automatically (doing it by hand). And maintaining a fork network on GitHub is good in the long run, compared to having individual separate repos mirroring the same code (which is what takes place right now). I thought that addressing this issue now, before I diverge too far with my fork, would enable me to keep it as it should be - a fork of the original pristine codebase. Additionally, it would provide some ground for other potential git oriented contributors, even if the core team remains with SVN for a long time to go. So, my question is - would you guys be interested in something like this? If you can't/don't want to, would it be OK, if I mirrored the svn trunk on GitHub by my own efforts into something more "official" than my personal branch (essentially recapturing the old git repo maintenance function)? If so, I would write some cron job on my server to keep up the git/svn repos in sync. |
|
I think it's a good idea to keep a git-svn sync yourself. It seems to me to be fairly straightforward to do that, and fully in keeping with the OSQA licence. I work in Mercurial, and have a SVN copy from trunk now, and a mercurial branch. It would be great to have something where we could cross-pollinate between trunk, your branch and ripper234's branch. And maybe even Askbot's too, though maybe it's forked off so far that we're left with porting features, rather than code, between branches. I see greater value to the OSQA community in maintaining portability of code between branches as much as possible. |
|
We’re using Git-SVN to mirror the official OSQA SVN repo on a branch of our GitHub repo. It’s not ideal, but it works. I offered last year to manage for the OSQA team a GitHub mirror of the official code, but after initially supporting the idea, they never came through with the necessary access to administer https://github.com/OSQA/osqa. That's what I'm doing too right now. But I thought that forking from a central place would be more elegant. That is why I tried to know if this would make sense.
(02 May '11, 19:59)
karoldvl
|
|
I've created a new repository mirroring the SVN codebase, so that I can keep the mirror separate from my personal repo. It's available at: https://github.com/OSQA-SVN/OSQA I will keep it pristine (read-only). For potential future developers - feel free to fork of it. You can throw some pull requests, but they will still have to go through JIRA/meta and into SVN to return back into the mirror. So it's only for presentation purposes (convenient patch generation) and additional graphic buzz. I would like to confirm with the core team that it's OK with you (esp. naming etc.)? If you want to organize it differently (eg. revive it under the official GitHub account), just drop me a line. I know git is not your tool of choice, and I don't want to change that, but I think it would be good to help those developers who are already using it either way. |
