Hi Daniel,
We are a new podling trying to do our initial import and we are trying
to make a decision about git vs svn.
Right now we have a public GitHub repo
(https://github.com/hortonworks/knox). The consensus is that we would
like to stay with git but we have concerns.
1. We would like to retain the history from github if possible.
2. We will be using a maven generated site and need to workout a
"workflow" for bridging git & svn so that svnpubsub will work.
I've read the doc you linked before but it doesn't really seem to answer
these questions.
So the bottom line is that I think we would like a Git repo to play with
and see if we can make it work efficiently. In this case the git->git
information you describe would be required. I hope that will take care
of the history retention.
Do I need to file a Jira for that?
Project unix name: knox (This is the current svn repo)
https://svn.apache.org/repos/asf/incubator/knox)
Project layout: Maven style (Is that enough info?)
Writable tree: None. (I think)
Thanks.
Kevin.
On 3/7/13 9:18 AM, Daniel Shahaf wrote:
Actually give me 5 minutes to update the link to describe git->git
imports too, if that's what you meant.
Daniel Shahaf wrote on Thu, Mar 07, 2013 at 16:15:56 +0200:
http://www.apache.org/dev/infra-contact#what-we-need-to-know
Kevin Minder wrote on Thu, Mar 07, 2013 at 08:44:38 -0500:
Thanks David,
Sounds like dealing with different CM systems for code and site would be
a hassle.
Next question. Is there a magic way to have the GitHub repo imported?
This is where the code currently is:
https://github.com/hortonworks/knox
Kevin.
On 3/6/13 6:38 PM, David Nalley wrote:
On Wed, Mar 6, 2013 at 5:25 PM, Kevin Minder
<[email protected]> wrote:
Hi,
I'm a commiter on the new podling Knox. I'm gearing up to do the initial
code import. My question is should we switch to SVN or continue to use Git
on the https://git-wip-us.apache.org/repos/asf/... infrastructure? Our
current code base is on GitHub if that matters.
Kevin.
Sounds like a project decision to me.
Either should be fine.
Presumably you'll have SVN regardless for the website.
--David
