Re: moving the site from SVN to git

[Jon Haddad]

Thanks for the help Michael and Nate.

It took a couple wacks with a hammer but I've gotten the website to
regenerate, pushing up the newest documentation and finally fixing the
community page to link to the Slack channel as a priority over IRC.

Jon

On Wed, Oct 30, 2019 at 1:52 PM Jon Haddad  wrote:

> Thanks Michael, that's exactly what I needed.
>
> On Wed, Oct 30, 2019 at 1:44 PM Michael Shuler 
> wrote:
>
>> Looks like the source markdown was added in the next commit.
>> http://svn.apache.org/viewvc?view=revision=1857226
>>
>> (which I see in git as commit 157df5cdfb83cb2edd0051002736316f5f470ad9)
>>
>> Michael
>>
>> On 10/30/19 3:29 PM, Nate McCall wrote:
>> > Unfortunately my svn foo is about as atrophied as yours. I followed the
>> > usual steps when publishing as I've done with the other posts, so no
>> idea
>> > what happened? I dont have anything uncommitted locally either.
>> >
>> > Whatever we can do to get it showing until we move off SVN (or just
>> move)
>> > is fine with me.
>> >
>> > On Thu, Oct 31, 2019 at 9:17 AM Jon Haddad  wrote:
>> >
>> >> I figured out what was wrong with the site generation, I've pushed up a
>> >> fix.
>> >>
>> >> I regenerated the site and noticed the blog post for streaming was
>> marked
>> >> as deleted, which was odd.  I dug back through the history and found
>> it an
>> >> HTML file committed at
>> >> http://svn.apache.org/viewvc?view=revision=1857225, but I'm
>> not
>> >> sure where the original content is.  (My SVN foo is terrible now)
>> >>
>> >> Looking at the Git history I see this:
>> >>
>> >> commit f00523b1eefc90b5e4515db0d8c3ab207656684b
>> >> Author: zznate 
>> >> Date:   Wed Apr 10 01:16:07 2019 +
>> >>
>> >>  CASSANDRA-14765 - Streaming performance post by Sumanth Pasupuleti
>> >>
>> >>  git-svn-id:
>> http://svn.apache.org/repos/asf/cassandra/site@1857225
>> >> 13f79535-47bb-0310-9956-ffa450edef68
>> >> <
>> http://svn.apache.org/repos/asf/cassandra/site@185722513f79535-47bb-0310-9956-ffa450edef68
>> >
>> >>
>> >> Was this just published directly as HTML?
>> >>
>> >> Nate, do you remember how this was handled?  Am I missing something
>> >> obvious?
>> >>
>> >> Jon
>> >>
>> >> On Tue, Oct 29, 2019 at 1:28 PM Jon Haddad  wrote:
>> >>
>> >>> I'll take a look at the website generation.  Thanks for fixing
>> manually
>> >>> for now.
>> >>>
>> >>> On Tue, Oct 29, 2019 at 1:16 PM Michael Shuler <
>> mich...@pbandjelly.org>
>> >>> wrote:
>> >>>
>>  I have updated the new releases in:
>>  src/_data/releases.yaml
>> 
>>  I ran through the docker build/run, yet the main index and download
>>  pages of the site were not modified with the new release versions and
>>  dates. I'm going to reset --hard and hand edit those pages. #justFYI
>> 
>>  Michael
>> 
>>  On 10/17/19 9:07 AM, Jon Haddad wrote:
>> > The migration is finished.
>> >
>> > I had to fix a few things along the way.  The docker containers
>> didn't
>> > build correctly (based on debian:latest rather than a fixed tag),
>> and
>>  the
>> > site had to be served out of the content directory rather than the
>>  publish
>> > one we were using.
>> >
>> > I'm going to address a couple things as follow ups.  We still point
>>  people
>> > to IRC, I'll update that to slack.  Longer term I'll migrate it to
>> >> Hugo,
>> > which will make the entire process a lot easier.
>> >
>> > Jon
>> >
>> >
>> >
>> > On Wed, Oct 9, 2019 at 10:26 PM Jon Haddad 
>> wrote:
>> >
>> >> OK, I checked with INFRA on some details and will finish the
>> >> migration
>> >> tomorrow.
>> >>
>> >> On Thu, Oct 3, 2019 at 11:32 AM Jon Haddad 
>> >> wrote:
>> >>
>> >>> Awesome, thanks Michael.
>> >>>
>> >>> We need to do a little bit of additional configuration to have it
>>  switch
>> >>> over.  Specifically, we need to set up the .asf.yaml config to
>> tell
>>  the
>> >>> servers how the site should be published.  I can take care of it
>> >>> tomorrow.
>> >>>
>> >>> Reference:
>> >>>
>> 
>> >>
>> https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories#id-.asf.yamlfeaturesforgitrepositories-Publishingabranchtoyourprojectwebsite
>> >>>
>> >>> On Thu, Oct 3, 2019 at 10:57 AM Michael Shuler <
>>  mich...@pbandjelly.org>
>> >>> wrote:
>> >>>
>>  committed! :)
>> 
>>  https://gitbox.apache.org/repos/asf?p=cassandra-website.git
>> 
>>  Michael
>> 
>>  On 10/3/19 12:22 PM, Jon Haddad wrote:
>> > I think we can safely ignore them.  Thanks for figuring this
>> out.
>> >
>> > On Thu, Oct 3, 2019 at 10:01 AM Michael Shuler <
>>  mich...@pbandjelly.org
>> >
>> > wrote:
>> >
>> >> I'm making progress through many periodic timeouts to svn.a.o
>> and
>> >> restarts, but it 

Re: moving the site from SVN to git

[Jon Haddad]

Thanks Michael, that's exactly what I needed.

On Wed, Oct 30, 2019 at 1:44 PM Michael Shuler 
wrote:

> Looks like the source markdown was added in the next commit.
> http://svn.apache.org/viewvc?view=revision=1857226
>
> (which I see in git as commit 157df5cdfb83cb2edd0051002736316f5f470ad9)
>
> Michael
>
> On 10/30/19 3:29 PM, Nate McCall wrote:
> > Unfortunately my svn foo is about as atrophied as yours. I followed the
> > usual steps when publishing as I've done with the other posts, so no idea
> > what happened? I dont have anything uncommitted locally either.
> >
> > Whatever we can do to get it showing until we move off SVN (or just move)
> > is fine with me.
> >
> > On Thu, Oct 31, 2019 at 9:17 AM Jon Haddad  wrote:
> >
> >> I figured out what was wrong with the site generation, I've pushed up a
> >> fix.
> >>
> >> I regenerated the site and noticed the blog post for streaming was
> marked
> >> as deleted, which was odd.  I dug back through the history and found it
> an
> >> HTML file committed at
> >> http://svn.apache.org/viewvc?view=revision=1857225, but I'm
> not
> >> sure where the original content is.  (My SVN foo is terrible now)
> >>
> >> Looking at the Git history I see this:
> >>
> >> commit f00523b1eefc90b5e4515db0d8c3ab207656684b
> >> Author: zznate 
> >> Date:   Wed Apr 10 01:16:07 2019 +
> >>
> >>  CASSANDRA-14765 - Streaming performance post by Sumanth Pasupuleti
> >>
> >>  git-svn-id: http://svn.apache.org/repos/asf/cassandra/site@1857225
> >> 13f79535-47bb-0310-9956-ffa450edef68
> >> <
> http://svn.apache.org/repos/asf/cassandra/site@185722513f79535-47bb-0310-9956-ffa450edef68
> >
> >>
> >> Was this just published directly as HTML?
> >>
> >> Nate, do you remember how this was handled?  Am I missing something
> >> obvious?
> >>
> >> Jon
> >>
> >> On Tue, Oct 29, 2019 at 1:28 PM Jon Haddad  wrote:
> >>
> >>> I'll take a look at the website generation.  Thanks for fixing manually
> >>> for now.
> >>>
> >>> On Tue, Oct 29, 2019 at 1:16 PM Michael Shuler  >
> >>> wrote:
> >>>
>  I have updated the new releases in:
>  src/_data/releases.yaml
> 
>  I ran through the docker build/run, yet the main index and download
>  pages of the site were not modified with the new release versions and
>  dates. I'm going to reset --hard and hand edit those pages. #justFYI
> 
>  Michael
> 
>  On 10/17/19 9:07 AM, Jon Haddad wrote:
> > The migration is finished.
> >
> > I had to fix a few things along the way.  The docker containers
> didn't
> > build correctly (based on debian:latest rather than a fixed tag), and
>  the
> > site had to be served out of the content directory rather than the
>  publish
> > one we were using.
> >
> > I'm going to address a couple things as follow ups.  We still point
>  people
> > to IRC, I'll update that to slack.  Longer term I'll migrate it to
> >> Hugo,
> > which will make the entire process a lot easier.
> >
> > Jon
> >
> >
> >
> > On Wed, Oct 9, 2019 at 10:26 PM Jon Haddad 
> wrote:
> >
> >> OK, I checked with INFRA on some details and will finish the
> >> migration
> >> tomorrow.
> >>
> >> On Thu, Oct 3, 2019 at 11:32 AM Jon Haddad 
> >> wrote:
> >>
> >>> Awesome, thanks Michael.
> >>>
> >>> We need to do a little bit of additional configuration to have it
>  switch
> >>> over.  Specifically, we need to set up the .asf.yaml config to tell
>  the
> >>> servers how the site should be published.  I can take care of it
> >>> tomorrow.
> >>>
> >>> Reference:
> >>>
> 
> >>
> https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories#id-.asf.yamlfeaturesforgitrepositories-Publishingabranchtoyourprojectwebsite
> >>>
> >>> On Thu, Oct 3, 2019 at 10:57 AM Michael Shuler <
>  mich...@pbandjelly.org>
> >>> wrote:
> >>>
>  committed! :)
> 
>  https://gitbox.apache.org/repos/asf?p=cassandra-website.git
> 
>  Michael
> 
>  On 10/3/19 12:22 PM, Jon Haddad wrote:
> > I think we can safely ignore them.  Thanks for figuring this out.
> >
> > On Thu, Oct 3, 2019 at 10:01 AM Michael Shuler <
>  mich...@pbandjelly.org
> >
> > wrote:
> >
> >> I'm making progress through many periodic timeouts to svn.a.o
> and
> >> restarts, but it appears that svn2git is smart enough to pick up
>  where
> >> it left off. The first commit captured at the svn path I'm
>  specifying
>  is
> >> when Cassandra was moved to a top level project at r922689
>  (2010-03-13).
> >> I don't know the old incubator path, and it's probably OK to
> >> ignore
>  the
> >> few older incubator commits? I imagine it would mean starting
> >> over
>  the
> >> entire import to pull 

Re: moving the site from SVN to git

[Michael Shuler]

Looks like the source markdown was added in the next commit.
http://svn.apache.org/viewvc?view=revision=1857226

(which I see in git as commit 157df5cdfb83cb2edd0051002736316f5f470ad9)

Michael

On 10/30/19 3:29 PM, Nate McCall wrote:

Unfortunately my svn foo is about as atrophied as yours. I followed the
usual steps when publishing as I've done with the other posts, so no idea
what happened? I dont have anything uncommitted locally either.

Whatever we can do to get it showing until we move off SVN (or just move)
is fine with me.

On Thu, Oct 31, 2019 at 9:17 AM Jon Haddad  wrote:


I figured out what was wrong with the site generation, I've pushed up a
fix.

I regenerated the site and noticed the blog post for streaming was marked
as deleted, which was odd.  I dug back through the history and found it an
HTML file committed at
http://svn.apache.org/viewvc?view=revision=1857225, but I'm not
sure where the original content is.  (My SVN foo is terrible now)

Looking at the Git history I see this:

commit f00523b1eefc90b5e4515db0d8c3ab207656684b
Author: zznate 
Date:   Wed Apr 10 01:16:07 2019 +

 CASSANDRA-14765 - Streaming performance post by Sumanth Pasupuleti

 git-svn-id: http://svn.apache.org/repos/asf/cassandra/site@1857225
13f79535-47bb-0310-9956-ffa450edef68


Was this just published directly as HTML?

Nate, do you remember how this was handled?  Am I missing something
obvious?

Jon

On Tue, Oct 29, 2019 at 1:28 PM Jon Haddad  wrote:


I'll take a look at the website generation.  Thanks for fixing manually
for now.

On Tue, Oct 29, 2019 at 1:16 PM Michael Shuler 
wrote:


I have updated the new releases in:
src/_data/releases.yaml

I ran through the docker build/run, yet the main index and download
pages of the site were not modified with the new release versions and
dates. I'm going to reset --hard and hand edit those pages. #justFYI

Michael

On 10/17/19 9:07 AM, Jon Haddad wrote:

The migration is finished.

I had to fix a few things along the way.  The docker containers didn't
build correctly (based on debian:latest rather than a fixed tag), and

the

site had to be served out of the content directory rather than the

publish

one we were using.

I'm going to address a couple things as follow ups.  We still point

people

to IRC, I'll update that to slack.  Longer term I'll migrate it to

Hugo,

which will make the entire process a lot easier.

Jon



On Wed, Oct 9, 2019 at 10:26 PM Jon Haddad  wrote:


OK, I checked with INFRA on some details and will finish the

migration

tomorrow.

On Thu, Oct 3, 2019 at 11:32 AM Jon Haddad 

wrote:



Awesome, thanks Michael.

We need to do a little bit of additional configuration to have it

switch

over.  Specifically, we need to set up the .asf.yaml config to tell

the

servers how the site should be published.  I can take care of it
tomorrow.

Reference:




https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories#id-.asf.yamlfeaturesforgitrepositories-Publishingabranchtoyourprojectwebsite


On Thu, Oct 3, 2019 at 10:57 AM Michael Shuler <

mich...@pbandjelly.org>

wrote:


committed! :)

https://gitbox.apache.org/repos/asf?p=cassandra-website.git

Michael

On 10/3/19 12:22 PM, Jon Haddad wrote:

I think we can safely ignore them.  Thanks for figuring this out.

On Thu, Oct 3, 2019 at 10:01 AM Michael Shuler <

mich...@pbandjelly.org


wrote:


I'm making progress through many periodic timeouts to svn.a.o and
restarts, but it appears that svn2git is smart enough to pick up

where

it left off. The first commit captured at the svn path I'm

specifying

is

when Cassandra was moved to a top level project at r922689

(2010-03-13).

I don't know the old incubator path, and it's probably OK to

ignore

the

few older incubator commits? I imagine it would mean starting

over

the

entire import to pull in those older incubator svn commits, then
changing the url and somehow importing the newer path on top?

I tried using a local path as the source to try to speed things

up,

after I got my first few timeouts, but that fails.

Curious if anyone really cares if we lose a few early commits -

if

so, I

can try to figure out the old path and start again.

Michael

On 10/3/19 11:14 AM, Jon Haddad wrote:

Thanks for taking a look, Michael.  Hopefully you have better

luck

than

me

:)

On Thu, Oct 3, 2019 at 6:42 AM Michael Shuler <

mich...@pbandjelly.org>

wrote:


I cloned the empty cassandra-website git repo, and I'm running:

svn2git http://svn.apache.org/repos/asf/cassandra/site

--rootistrunk

--no-minimize-url

..to see what I get. An svn checkout of the above url says it's

only

69M, so I suppose it's pulling all history of all time for all

projects?


I'll let this roll for a while I run an errand and report back!

Michael

On 10/2/19 9:30 PM, Jon Haddad wrote:

Daniel referred me to the GitBox self service 

Re: moving the site from SVN to git

[Jon Haddad]

I think I figured out what happened.. it's regenerating into a different
directory than originally was.  I'll dig into why.

The site's already moved and publishing via git, I'm just trying to figure
out the last couple wrinkles that I didn't spot in the process.

On Wed, Oct 30, 2019 at 1:30 PM Nate McCall  wrote:

> Unfortunately my svn foo is about as atrophied as yours. I followed the
> usual steps when publishing as I've done with the other posts, so no idea
> what happened? I dont have anything uncommitted locally either.
>
> Whatever we can do to get it showing until we move off SVN (or just move)
> is fine with me.
>
> On Thu, Oct 31, 2019 at 9:17 AM Jon Haddad  wrote:
>
> > I figured out what was wrong with the site generation, I've pushed up a
> > fix.
> >
> > I regenerated the site and noticed the blog post for streaming was marked
> > as deleted, which was odd.  I dug back through the history and found it
> an
> > HTML file committed at
> > http://svn.apache.org/viewvc?view=revision=1857225, but I'm not
> > sure where the original content is.  (My SVN foo is terrible now)
> >
> > Looking at the Git history I see this:
> >
> > commit f00523b1eefc90b5e4515db0d8c3ab207656684b
> > Author: zznate 
> > Date:   Wed Apr 10 01:16:07 2019 +
> >
> > CASSANDRA-14765 - Streaming performance post by Sumanth Pasupuleti
> >
> > git-svn-id: http://svn.apache.org/repos/asf/cassandra/site@1857225
> > 13f79535-47bb-0310-9956-ffa450edef68
> > <
> http://svn.apache.org/repos/asf/cassandra/site@185722513f79535-47bb-0310-9956-ffa450edef68
> >
> >
> > Was this just published directly as HTML?
> >
> > Nate, do you remember how this was handled?  Am I missing something
> > obvious?
> >
> > Jon
> >
> > On Tue, Oct 29, 2019 at 1:28 PM Jon Haddad  wrote:
> >
> > > I'll take a look at the website generation.  Thanks for fixing manually
> > > for now.
> > >
> > > On Tue, Oct 29, 2019 at 1:16 PM Michael Shuler  >
> > > wrote:
> > >
> > >> I have updated the new releases in:
> > >>src/_data/releases.yaml
> > >>
> > >> I ran through the docker build/run, yet the main index and download
> > >> pages of the site were not modified with the new release versions and
> > >> dates. I'm going to reset --hard and hand edit those pages. #justFYI
> > >>
> > >> Michael
> > >>
> > >> On 10/17/19 9:07 AM, Jon Haddad wrote:
> > >> > The migration is finished.
> > >> >
> > >> > I had to fix a few things along the way.  The docker containers
> didn't
> > >> > build correctly (based on debian:latest rather than a fixed tag),
> and
> > >> the
> > >> > site had to be served out of the content directory rather than the
> > >> publish
> > >> > one we were using.
> > >> >
> > >> > I'm going to address a couple things as follow ups.  We still point
> > >> people
> > >> > to IRC, I'll update that to slack.  Longer term I'll migrate it to
> > Hugo,
> > >> > which will make the entire process a lot easier.
> > >> >
> > >> > Jon
> > >> >
> > >> >
> > >> >
> > >> > On Wed, Oct 9, 2019 at 10:26 PM Jon Haddad 
> wrote:
> > >> >
> > >> >> OK, I checked with INFRA on some details and will finish the
> > migration
> > >> >> tomorrow.
> > >> >>
> > >> >> On Thu, Oct 3, 2019 at 11:32 AM Jon Haddad 
> > wrote:
> > >> >>
> > >> >>> Awesome, thanks Michael.
> > >> >>>
> > >> >>> We need to do a little bit of additional configuration to have it
> > >> switch
> > >> >>> over.  Specifically, we need to set up the .asf.yaml config to
> tell
> > >> the
> > >> >>> servers how the site should be published.  I can take care of it
> > >> >>> tomorrow.
> > >> >>>
> > >> >>> Reference:
> > >> >>>
> > >>
> >
> https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories#id-.asf.yamlfeaturesforgitrepositories-Publishingabranchtoyourprojectwebsite
> > >> >>>
> > >> >>> On Thu, Oct 3, 2019 at 10:57 AM Michael Shuler <
> > >> mich...@pbandjelly.org>
> > >> >>> wrote:
> > >> >>>
> > >>  committed! :)
> > >> 
> > >>  https://gitbox.apache.org/repos/asf?p=cassandra-website.git
> > >> 
> > >>  Michael
> > >> 
> > >>  On 10/3/19 12:22 PM, Jon Haddad wrote:
> > >> > I think we can safely ignore them.  Thanks for figuring this
> out.
> > >> >
> > >> > On Thu, Oct 3, 2019 at 10:01 AM Michael Shuler <
> > >> mich...@pbandjelly.org
> > >> >
> > >> > wrote:
> > >> >
> > >> >> I'm making progress through many periodic timeouts to svn.a.o
> and
> > >> >> restarts, but it appears that svn2git is smart enough to pick
> up
> > >> where
> > >> >> it left off. The first commit captured at the svn path I'm
> > >> specifying
> > >>  is
> > >> >> when Cassandra was moved to a top level project at r922689
> > >>  (2010-03-13).
> > >> >> I don't know the old incubator path, and it's probably OK to
> > ignore
> > >>  the
> > >> >> few older incubator commits? I imagine it would mean starting
> > over
> > >> the
> > >> >> entire import to pull in those older incubator svn 

Re: moving the site from SVN to git

[Nate McCall]

Unfortunately my svn foo is about as atrophied as yours. I followed the
usual steps when publishing as I've done with the other posts, so no idea
what happened? I dont have anything uncommitted locally either.

Whatever we can do to get it showing until we move off SVN (or just move)
is fine with me.

On Thu, Oct 31, 2019 at 9:17 AM Jon Haddad  wrote:

> I figured out what was wrong with the site generation, I've pushed up a
> fix.
>
> I regenerated the site and noticed the blog post for streaming was marked
> as deleted, which was odd.  I dug back through the history and found it an
> HTML file committed at
> http://svn.apache.org/viewvc?view=revision=1857225, but I'm not
> sure where the original content is.  (My SVN foo is terrible now)
>
> Looking at the Git history I see this:
>
> commit f00523b1eefc90b5e4515db0d8c3ab207656684b
> Author: zznate 
> Date:   Wed Apr 10 01:16:07 2019 +
>
> CASSANDRA-14765 - Streaming performance post by Sumanth Pasupuleti
>
> git-svn-id: http://svn.apache.org/repos/asf/cassandra/site@1857225
> 13f79535-47bb-0310-9956-ffa450edef68
> 
>
> Was this just published directly as HTML?
>
> Nate, do you remember how this was handled?  Am I missing something
> obvious?
>
> Jon
>
> On Tue, Oct 29, 2019 at 1:28 PM Jon Haddad  wrote:
>
> > I'll take a look at the website generation.  Thanks for fixing manually
> > for now.
> >
> > On Tue, Oct 29, 2019 at 1:16 PM Michael Shuler 
> > wrote:
> >
> >> I have updated the new releases in:
> >>src/_data/releases.yaml
> >>
> >> I ran through the docker build/run, yet the main index and download
> >> pages of the site were not modified with the new release versions and
> >> dates. I'm going to reset --hard and hand edit those pages. #justFYI
> >>
> >> Michael
> >>
> >> On 10/17/19 9:07 AM, Jon Haddad wrote:
> >> > The migration is finished.
> >> >
> >> > I had to fix a few things along the way.  The docker containers didn't
> >> > build correctly (based on debian:latest rather than a fixed tag), and
> >> the
> >> > site had to be served out of the content directory rather than the
> >> publish
> >> > one we were using.
> >> >
> >> > I'm going to address a couple things as follow ups.  We still point
> >> people
> >> > to IRC, I'll update that to slack.  Longer term I'll migrate it to
> Hugo,
> >> > which will make the entire process a lot easier.
> >> >
> >> > Jon
> >> >
> >> >
> >> >
> >> > On Wed, Oct 9, 2019 at 10:26 PM Jon Haddad  wrote:
> >> >
> >> >> OK, I checked with INFRA on some details and will finish the
> migration
> >> >> tomorrow.
> >> >>
> >> >> On Thu, Oct 3, 2019 at 11:32 AM Jon Haddad 
> wrote:
> >> >>
> >> >>> Awesome, thanks Michael.
> >> >>>
> >> >>> We need to do a little bit of additional configuration to have it
> >> switch
> >> >>> over.  Specifically, we need to set up the .asf.yaml config to tell
> >> the
> >> >>> servers how the site should be published.  I can take care of it
> >> >>> tomorrow.
> >> >>>
> >> >>> Reference:
> >> >>>
> >>
> https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories#id-.asf.yamlfeaturesforgitrepositories-Publishingabranchtoyourprojectwebsite
> >> >>>
> >> >>> On Thu, Oct 3, 2019 at 10:57 AM Michael Shuler <
> >> mich...@pbandjelly.org>
> >> >>> wrote:
> >> >>>
> >>  committed! :)
> >> 
> >>  https://gitbox.apache.org/repos/asf?p=cassandra-website.git
> >> 
> >>  Michael
> >> 
> >>  On 10/3/19 12:22 PM, Jon Haddad wrote:
> >> > I think we can safely ignore them.  Thanks for figuring this out.
> >> >
> >> > On Thu, Oct 3, 2019 at 10:01 AM Michael Shuler <
> >> mich...@pbandjelly.org
> >> >
> >> > wrote:
> >> >
> >> >> I'm making progress through many periodic timeouts to svn.a.o and
> >> >> restarts, but it appears that svn2git is smart enough to pick up
> >> where
> >> >> it left off. The first commit captured at the svn path I'm
> >> specifying
> >>  is
> >> >> when Cassandra was moved to a top level project at r922689
> >>  (2010-03-13).
> >> >> I don't know the old incubator path, and it's probably OK to
> ignore
> >>  the
> >> >> few older incubator commits? I imagine it would mean starting
> over
> >> the
> >> >> entire import to pull in those older incubator svn commits, then
> >> >> changing the url and somehow importing the newer path on top?
> >> >>
> >> >> I tried using a local path as the source to try to speed things
> up,
> >> >> after I got my first few timeouts, but that fails.
> >> >>
> >> >> Curious if anyone really cares if we lose a few early commits -
> if
> >>  so, I
> >> >> can try to figure out the old path and start again.
> >> >>
> >> >> Michael
> >> >>
> >> >> On 10/3/19 11:14 AM, Jon Haddad wrote:
> >> >>> Thanks for taking a look, Michael.  Hopefully you have better
> luck
> >> 

Re: moving the site from SVN to git

[Jon Haddad]

I figured out what was wrong with the site generation, I've pushed up a fix.

I regenerated the site and noticed the blog post for streaming was marked
as deleted, which was odd.  I dug back through the history and found it an
HTML file committed at
http://svn.apache.org/viewvc?view=revision=1857225, but I'm not
sure where the original content is.  (My SVN foo is terrible now)

Looking at the Git history I see this:

commit f00523b1eefc90b5e4515db0d8c3ab207656684b
Author: zznate 
Date:   Wed Apr 10 01:16:07 2019 +

CASSANDRA-14765 - Streaming performance post by Sumanth Pasupuleti

git-svn-id: http://svn.apache.org/repos/asf/cassandra/site@1857225
13f79535-47bb-0310-9956-ffa450edef68

Was this just published directly as HTML?

Nate, do you remember how this was handled?  Am I missing something obvious?

Jon

On Tue, Oct 29, 2019 at 1:28 PM Jon Haddad  wrote:

> I'll take a look at the website generation.  Thanks for fixing manually
> for now.
>
> On Tue, Oct 29, 2019 at 1:16 PM Michael Shuler 
> wrote:
>
>> I have updated the new releases in:
>>src/_data/releases.yaml
>>
>> I ran through the docker build/run, yet the main index and download
>> pages of the site were not modified with the new release versions and
>> dates. I'm going to reset --hard and hand edit those pages. #justFYI
>>
>> Michael
>>
>> On 10/17/19 9:07 AM, Jon Haddad wrote:
>> > The migration is finished.
>> >
>> > I had to fix a few things along the way.  The docker containers didn't
>> > build correctly (based on debian:latest rather than a fixed tag), and
>> the
>> > site had to be served out of the content directory rather than the
>> publish
>> > one we were using.
>> >
>> > I'm going to address a couple things as follow ups.  We still point
>> people
>> > to IRC, I'll update that to slack.  Longer term I'll migrate it to Hugo,
>> > which will make the entire process a lot easier.
>> >
>> > Jon
>> >
>> >
>> >
>> > On Wed, Oct 9, 2019 at 10:26 PM Jon Haddad  wrote:
>> >
>> >> OK, I checked with INFRA on some details and will finish the migration
>> >> tomorrow.
>> >>
>> >> On Thu, Oct 3, 2019 at 11:32 AM Jon Haddad  wrote:
>> >>
>> >>> Awesome, thanks Michael.
>> >>>
>> >>> We need to do a little bit of additional configuration to have it
>> switch
>> >>> over.  Specifically, we need to set up the .asf.yaml config to tell
>> the
>> >>> servers how the site should be published.  I can take care of it
>> >>> tomorrow.
>> >>>
>> >>> Reference:
>> >>>
>> https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories#id-.asf.yamlfeaturesforgitrepositories-Publishingabranchtoyourprojectwebsite
>> >>>
>> >>> On Thu, Oct 3, 2019 at 10:57 AM Michael Shuler <
>> mich...@pbandjelly.org>
>> >>> wrote:
>> >>>
>>  committed! :)
>> 
>>  https://gitbox.apache.org/repos/asf?p=cassandra-website.git
>> 
>>  Michael
>> 
>>  On 10/3/19 12:22 PM, Jon Haddad wrote:
>> > I think we can safely ignore them.  Thanks for figuring this out.
>> >
>> > On Thu, Oct 3, 2019 at 10:01 AM Michael Shuler <
>> mich...@pbandjelly.org
>> >
>> > wrote:
>> >
>> >> I'm making progress through many periodic timeouts to svn.a.o and
>> >> restarts, but it appears that svn2git is smart enough to pick up
>> where
>> >> it left off. The first commit captured at the svn path I'm
>> specifying
>>  is
>> >> when Cassandra was moved to a top level project at r922689
>>  (2010-03-13).
>> >> I don't know the old incubator path, and it's probably OK to ignore
>>  the
>> >> few older incubator commits? I imagine it would mean starting over
>> the
>> >> entire import to pull in those older incubator svn commits, then
>> >> changing the url and somehow importing the newer path on top?
>> >>
>> >> I tried using a local path as the source to try to speed things up,
>> >> after I got my first few timeouts, but that fails.
>> >>
>> >> Curious if anyone really cares if we lose a few early commits - if
>>  so, I
>> >> can try to figure out the old path and start again.
>> >>
>> >> Michael
>> >>
>> >> On 10/3/19 11:14 AM, Jon Haddad wrote:
>> >>> Thanks for taking a look, Michael.  Hopefully you have better luck
>>  than
>> >> me
>> >>> :)
>> >>>
>> >>> On Thu, Oct 3, 2019 at 6:42 AM Michael Shuler <
>>  mich...@pbandjelly.org>
>> >>> wrote:
>> >>>
>>  I cloned the empty cassandra-website git repo, and I'm running:
>> 
>>  svn2git http://svn.apache.org/repos/asf/cassandra/site
>>  --rootistrunk
>>  --no-minimize-url
>> 
>>  ..to see what I get. An svn checkout of the above url says it's
>> only
>>  69M, so I suppose it's pulling all history of all time for all
>>  projects?
>> 
>>  I'll let this roll for a while I run an errand and report back!
>> 
>>  Michael
>> 
>>  On 

Re: moving the site from SVN to git

[Jon Haddad]

I'll take a look at the website generation.  Thanks for fixing manually for
now.

On Tue, Oct 29, 2019 at 1:16 PM Michael Shuler 
wrote:

> I have updated the new releases in:
>src/_data/releases.yaml
>
> I ran through the docker build/run, yet the main index and download
> pages of the site were not modified with the new release versions and
> dates. I'm going to reset --hard and hand edit those pages. #justFYI
>
> Michael
>
> On 10/17/19 9:07 AM, Jon Haddad wrote:
> > The migration is finished.
> >
> > I had to fix a few things along the way.  The docker containers didn't
> > build correctly (based on debian:latest rather than a fixed tag), and the
> > site had to be served out of the content directory rather than the
> publish
> > one we were using.
> >
> > I'm going to address a couple things as follow ups.  We still point
> people
> > to IRC, I'll update that to slack.  Longer term I'll migrate it to Hugo,
> > which will make the entire process a lot easier.
> >
> > Jon
> >
> >
> >
> > On Wed, Oct 9, 2019 at 10:26 PM Jon Haddad  wrote:
> >
> >> OK, I checked with INFRA on some details and will finish the migration
> >> tomorrow.
> >>
> >> On Thu, Oct 3, 2019 at 11:32 AM Jon Haddad  wrote:
> >>
> >>> Awesome, thanks Michael.
> >>>
> >>> We need to do a little bit of additional configuration to have it
> switch
> >>> over.  Specifically, we need to set up the .asf.yaml config to tell the
> >>> servers how the site should be published.  I can take care of it
> >>> tomorrow.
> >>>
> >>> Reference:
> >>>
> https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories#id-.asf.yamlfeaturesforgitrepositories-Publishingabranchtoyourprojectwebsite
> >>>
> >>> On Thu, Oct 3, 2019 at 10:57 AM Michael Shuler  >
> >>> wrote:
> >>>
>  committed! :)
> 
>  https://gitbox.apache.org/repos/asf?p=cassandra-website.git
> 
>  Michael
> 
>  On 10/3/19 12:22 PM, Jon Haddad wrote:
> > I think we can safely ignore them.  Thanks for figuring this out.
> >
> > On Thu, Oct 3, 2019 at 10:01 AM Michael Shuler <
> mich...@pbandjelly.org
> >
> > wrote:
> >
> >> I'm making progress through many periodic timeouts to svn.a.o and
> >> restarts, but it appears that svn2git is smart enough to pick up
> where
> >> it left off. The first commit captured at the svn path I'm
> specifying
>  is
> >> when Cassandra was moved to a top level project at r922689
>  (2010-03-13).
> >> I don't know the old incubator path, and it's probably OK to ignore
>  the
> >> few older incubator commits? I imagine it would mean starting over
> the
> >> entire import to pull in those older incubator svn commits, then
> >> changing the url and somehow importing the newer path on top?
> >>
> >> I tried using a local path as the source to try to speed things up,
> >> after I got my first few timeouts, but that fails.
> >>
> >> Curious if anyone really cares if we lose a few early commits - if
>  so, I
> >> can try to figure out the old path and start again.
> >>
> >> Michael
> >>
> >> On 10/3/19 11:14 AM, Jon Haddad wrote:
> >>> Thanks for taking a look, Michael.  Hopefully you have better luck
>  than
> >> me
> >>> :)
> >>>
> >>> On Thu, Oct 3, 2019 at 6:42 AM Michael Shuler <
>  mich...@pbandjelly.org>
> >>> wrote:
> >>>
>  I cloned the empty cassandra-website git repo, and I'm running:
> 
>  svn2git http://svn.apache.org/repos/asf/cassandra/site
>  --rootistrunk
>  --no-minimize-url
> 
>  ..to see what I get. An svn checkout of the above url says it's
> only
>  69M, so I suppose it's pulling all history of all time for all
>  projects?
> 
>  I'll let this roll for a while I run an errand and report back!
> 
>  Michael
> 
>  On 10/2/19 9:30 PM, Jon Haddad wrote:
> > Daniel referred me to the GitBox self service system.
> >
> > I've attempted to port the site over using the tool Michael
>  suggested,
>  but
> > after a couple hours it died with this message:
> >
> > command failed: r922600
> > git checkout -f master
> >
> > If either of you (Mick or Michael) want to give svn2git a shot
>  maybe
>  you'll
> > get a different result.I think it may have been due to the
>  large
> >> size
> > of the repo and the small drive on the VM I was using.  I can try
>  it
>  again
> > tomorrow with more storage to see if I get a better result.  Mick
>  if
> >> you
> > want to give it a shot in the meantime that would be appreciated.
> >
> > Jon
> >
> > On Wed, Oct 2, 2019 at 3:18 PM Jon Haddad 
>  wrote:
> >
> >> I created an INFRA ticket here:
> 

Re: moving the site from SVN to git

[Michael Shuler]

I have updated the new releases in:
  src/_data/releases.yaml

I ran through the docker build/run, yet the main index and download 
pages of the site were not modified with the new release versions and 
dates. I'm going to reset --hard and hand edit those pages. #justFYI


Michael

On 10/17/19 9:07 AM, Jon Haddad wrote:

The migration is finished.

I had to fix a few things along the way.  The docker containers didn't
build correctly (based on debian:latest rather than a fixed tag), and the
site had to be served out of the content directory rather than the publish
one we were using.

I'm going to address a couple things as follow ups.  We still point people
to IRC, I'll update that to slack.  Longer term I'll migrate it to Hugo,
which will make the entire process a lot easier.

Jon



On Wed, Oct 9, 2019 at 10:26 PM Jon Haddad  wrote:


OK, I checked with INFRA on some details and will finish the migration
tomorrow.

On Thu, Oct 3, 2019 at 11:32 AM Jon Haddad  wrote:


Awesome, thanks Michael.

We need to do a little bit of additional configuration to have it switch
over.  Specifically, we need to set up the .asf.yaml config to tell the
servers how the site should be published.  I can take care of it
tomorrow.

Reference:
https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories#id-.asf.yamlfeaturesforgitrepositories-Publishingabranchtoyourprojectwebsite

On Thu, Oct 3, 2019 at 10:57 AM Michael Shuler 
wrote:


committed! :)

https://gitbox.apache.org/repos/asf?p=cassandra-website.git

Michael

On 10/3/19 12:22 PM, Jon Haddad wrote:

I think we can safely ignore them.  Thanks for figuring this out.

On Thu, Oct 3, 2019 at 10:01 AM Michael Shuler 
I'm making progress through many periodic timeouts to svn.a.o and
restarts, but it appears that svn2git is smart enough to pick up where
it left off. The first commit captured at the svn path I'm specifying

is

when Cassandra was moved to a top level project at r922689

(2010-03-13).

I don't know the old incubator path, and it's probably OK to ignore

the

few older incubator commits? I imagine it would mean starting over the
entire import to pull in those older incubator svn commits, then
changing the url and somehow importing the newer path on top?

I tried using a local path as the source to try to speed things up,
after I got my first few timeouts, but that fails.

Curious if anyone really cares if we lose a few early commits - if

so, I

can try to figure out the old path and start again.

Michael

On 10/3/19 11:14 AM, Jon Haddad wrote:

Thanks for taking a look, Michael.  Hopefully you have better luck

than

me

:)

On Thu, Oct 3, 2019 at 6:42 AM Michael Shuler <

mich...@pbandjelly.org>

wrote:


I cloned the empty cassandra-website git repo, and I'm running:

svn2git http://svn.apache.org/repos/asf/cassandra/site

--rootistrunk

--no-minimize-url

..to see what I get. An svn checkout of the above url says it's only
69M, so I suppose it's pulling all history of all time for all

projects?


I'll let this roll for a while I run an errand and report back!

Michael

On 10/2/19 9:30 PM, Jon Haddad wrote:

Daniel referred me to the GitBox self service system.

I've attempted to port the site over using the tool Michael

suggested,

but

after a couple hours it died with this message:

command failed: r922600
git checkout -f master

If either of you (Mick or Michael) want to give svn2git a shot

maybe

you'll

get a different result.I think it may have been due to the

large

size

of the repo and the small drive on the VM I was using.  I can try

it

again

tomorrow with more storage to see if I get a better result.  Mick

if

you

want to give it a shot in the meantime that would be appreciated.

Jon

On Wed, Oct 2, 2019 at 3:18 PM Jon Haddad 

wrote:



I created an INFRA ticket here:
https://issues.apache.org/jira/browse/INFRA-19218.

On Wed, Sep 25, 2019 at 6:04 AM Michael Shuler <

mich...@pbandjelly.org>

wrote:


I see no good reason to trash history. There are tools to make

moving

from svn to git (hopefully) painless. We used git-svn for the

main c*

source to retain history of both, which this tool uses to do

migrations

- https://github.com/nirvdrum/svn2git

Michael

On 9/25/19 12:57 AM, Mick Semb Wever wrote:



Personally, no, I don't.  What I need to know is if someone who

actually

works on the site needs the history in *git*.



Yes. I need the history in *git*.


And I believe that INFRA can do the migration for you.
(For example, INFRA-12055 and spark-website)



-

To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org





-

To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org

Re: moving the site from SVN to git

[Scott Andreas]

Thanks, Jon!


From: Jon Haddad 
Sent: Thursday, October 17, 2019 7:07 AM
To: dev@cassandra.apache.org
Subject: Re: moving the site from SVN to git

The migration is finished.

I had to fix a few things along the way.  The docker containers didn't
build correctly (based on debian:latest rather than a fixed tag), and the
site had to be served out of the content directory rather than the publish
one we were using.

I'm going to address a couple things as follow ups.  We still point people
to IRC, I'll update that to slack.  Longer term I'll migrate it to Hugo,
which will make the entire process a lot easier.

Jon



On Wed, Oct 9, 2019 at 10:26 PM Jon Haddad  wrote:

> OK, I checked with INFRA on some details and will finish the migration
> tomorrow.
>
> On Thu, Oct 3, 2019 at 11:32 AM Jon Haddad  wrote:
>
>> Awesome, thanks Michael.
>>
>> We need to do a little bit of additional configuration to have it switch
>> over.  Specifically, we need to set up the .asf.yaml config to tell the
>> servers how the site should be published.  I can take care of it
>> tomorrow.
>>
>> Reference:
>> https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories#id-.asf.yamlfeaturesforgitrepositories-Publishingabranchtoyourprojectwebsite
>>
>> On Thu, Oct 3, 2019 at 10:57 AM Michael Shuler 
>> wrote:
>>
>>> committed! :)
>>>
>>> https://gitbox.apache.org/repos/asf?p=cassandra-website.git
>>>
>>> Michael
>>>
>>> On 10/3/19 12:22 PM, Jon Haddad wrote:
>>> > I think we can safely ignore them.  Thanks for figuring this out.
>>> >
>>> > On Thu, Oct 3, 2019 at 10:01 AM Michael Shuler >> >
>>> > wrote:
>>> >
>>> >> I'm making progress through many periodic timeouts to svn.a.o and
>>> >> restarts, but it appears that svn2git is smart enough to pick up where
>>> >> it left off. The first commit captured at the svn path I'm specifying
>>> is
>>> >> when Cassandra was moved to a top level project at r922689
>>> (2010-03-13).
>>> >> I don't know the old incubator path, and it's probably OK to ignore
>>> the
>>> >> few older incubator commits? I imagine it would mean starting over the
>>> >> entire import to pull in those older incubator svn commits, then
>>> >> changing the url and somehow importing the newer path on top?
>>> >>
>>> >> I tried using a local path as the source to try to speed things up,
>>> >> after I got my first few timeouts, but that fails.
>>> >>
>>> >> Curious if anyone really cares if we lose a few early commits - if
>>> so, I
>>> >> can try to figure out the old path and start again.
>>> >>
>>> >> Michael
>>> >>
>>> >> On 10/3/19 11:14 AM, Jon Haddad wrote:
>>> >>> Thanks for taking a look, Michael.  Hopefully you have better luck
>>> than
>>> >> me
>>> >>> :)
>>> >>>
>>> >>> On Thu, Oct 3, 2019 at 6:42 AM Michael Shuler <
>>> mich...@pbandjelly.org>
>>> >>> wrote:
>>> >>>
>>> >>>> I cloned the empty cassandra-website git repo, and I'm running:
>>> >>>>
>>> >>>> svn2git http://svn.apache.org/repos/asf/cassandra/site
>>> --rootistrunk
>>> >>>> --no-minimize-url
>>> >>>>
>>> >>>> ..to see what I get. An svn checkout of the above url says it's only
>>> >>>> 69M, so I suppose it's pulling all history of all time for all
>>> projects?
>>> >>>>
>>> >>>> I'll let this roll for a while I run an errand and report back!
>>> >>>>
>>> >>>> Michael
>>> >>>>
>>> >>>> On 10/2/19 9:30 PM, Jon Haddad wrote:
>>> >>>>> Daniel referred me to the GitBox self service system.
>>> >>>>>
>>> >>>>> I've attempted to port the site over using the tool Michael
>>> suggested,
>>> >>>> but
>>> >>>>> after a couple hours it died with this message:
>>> >>>>>
>>> >>>>> command failed: r922600
>>> >>>>> git checkout -f master
>>> >>>>>
>>> >>>>> If either of you (Mick or Michael) want to g

Re: moving the site from SVN to git

[Jon Haddad]

The migration is finished.

I had to fix a few things along the way.  The docker containers didn't
build correctly (based on debian:latest rather than a fixed tag), and the
site had to be served out of the content directory rather than the publish
one we were using.

I'm going to address a couple things as follow ups.  We still point people
to IRC, I'll update that to slack.  Longer term I'll migrate it to Hugo,
which will make the entire process a lot easier.

Jon



On Wed, Oct 9, 2019 at 10:26 PM Jon Haddad  wrote:

> OK, I checked with INFRA on some details and will finish the migration
> tomorrow.
>
> On Thu, Oct 3, 2019 at 11:32 AM Jon Haddad  wrote:
>
>> Awesome, thanks Michael.
>>
>> We need to do a little bit of additional configuration to have it switch
>> over.  Specifically, we need to set up the .asf.yaml config to tell the
>> servers how the site should be published.  I can take care of it
>> tomorrow.
>>
>> Reference:
>> https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories#id-.asf.yamlfeaturesforgitrepositories-Publishingabranchtoyourprojectwebsite
>>
>> On Thu, Oct 3, 2019 at 10:57 AM Michael Shuler 
>> wrote:
>>
>>> committed! :)
>>>
>>> https://gitbox.apache.org/repos/asf?p=cassandra-website.git
>>>
>>> Michael
>>>
>>> On 10/3/19 12:22 PM, Jon Haddad wrote:
>>> > I think we can safely ignore them.  Thanks for figuring this out.
>>> >
>>> > On Thu, Oct 3, 2019 at 10:01 AM Michael Shuler >> >
>>> > wrote:
>>> >
>>> >> I'm making progress through many periodic timeouts to svn.a.o and
>>> >> restarts, but it appears that svn2git is smart enough to pick up where
>>> >> it left off. The first commit captured at the svn path I'm specifying
>>> is
>>> >> when Cassandra was moved to a top level project at r922689
>>> (2010-03-13).
>>> >> I don't know the old incubator path, and it's probably OK to ignore
>>> the
>>> >> few older incubator commits? I imagine it would mean starting over the
>>> >> entire import to pull in those older incubator svn commits, then
>>> >> changing the url and somehow importing the newer path on top?
>>> >>
>>> >> I tried using a local path as the source to try to speed things up,
>>> >> after I got my first few timeouts, but that fails.
>>> >>
>>> >> Curious if anyone really cares if we lose a few early commits - if
>>> so, I
>>> >> can try to figure out the old path and start again.
>>> >>
>>> >> Michael
>>> >>
>>> >> On 10/3/19 11:14 AM, Jon Haddad wrote:
>>> >>> Thanks for taking a look, Michael.  Hopefully you have better luck
>>> than
>>> >> me
>>> >>> :)
>>> >>>
>>> >>> On Thu, Oct 3, 2019 at 6:42 AM Michael Shuler <
>>> mich...@pbandjelly.org>
>>> >>> wrote:
>>> >>>
>>>  I cloned the empty cassandra-website git repo, and I'm running:
>>> 
>>>  svn2git http://svn.apache.org/repos/asf/cassandra/site
>>> --rootistrunk
>>>  --no-minimize-url
>>> 
>>>  ..to see what I get. An svn checkout of the above url says it's only
>>>  69M, so I suppose it's pulling all history of all time for all
>>> projects?
>>> 
>>>  I'll let this roll for a while I run an errand and report back!
>>> 
>>>  Michael
>>> 
>>>  On 10/2/19 9:30 PM, Jon Haddad wrote:
>>> > Daniel referred me to the GitBox self service system.
>>> >
>>> > I've attempted to port the site over using the tool Michael
>>> suggested,
>>>  but
>>> > after a couple hours it died with this message:
>>> >
>>> > command failed: r922600
>>> > git checkout -f master
>>> >
>>> > If either of you (Mick or Michael) want to give svn2git a shot
>>> maybe
>>>  you'll
>>> > get a different result.I think it may have been due to the
>>> large
>>> >> size
>>> > of the repo and the small drive on the VM I was using.  I can try
>>> it
>>>  again
>>> > tomorrow with more storage to see if I get a better result.  Mick
>>> if
>>> >> you
>>> > want to give it a shot in the meantime that would be appreciated.
>>> >
>>> > Jon
>>> >
>>> > On Wed, Oct 2, 2019 at 3:18 PM Jon Haddad 
>>> wrote:
>>> >
>>> >> I created an INFRA ticket here:
>>> >> https://issues.apache.org/jira/browse/INFRA-19218.
>>> >>
>>> >> On Wed, Sep 25, 2019 at 6:04 AM Michael Shuler <
>>> >> mich...@pbandjelly.org>
>>> >> wrote:
>>> >>
>>> >>> I see no good reason to trash history. There are tools to make
>>> moving
>>> >>> from svn to git (hopefully) painless. We used git-svn for the
>>> main c*
>>> >>> source to retain history of both, which this tool uses to do
>>> >> migrations
>>> >>> - https://github.com/nirvdrum/svn2git
>>> >>>
>>> >>> Michael
>>> >>>
>>> >>> On 9/25/19 12:57 AM, Mick Semb Wever wrote:
>>> 
>>> > Personally, no, I don't.  What I need to know is if someone who
>>> >>> actually
>>> > works on the site needs the history in *git*.
>>> 
>>> 
>>>  Yes. I need the history in 

Re: moving the site from SVN to git

[Jon Haddad]

OK, I checked with INFRA on some details and will finish the migration
tomorrow.

On Thu, Oct 3, 2019 at 11:32 AM Jon Haddad  wrote:

> Awesome, thanks Michael.
>
> We need to do a little bit of additional configuration to have it switch
> over.  Specifically, we need to set up the .asf.yaml config to tell the
> servers how the site should be published.  I can take care of it
> tomorrow.
>
> Reference:
> https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories#id-.asf.yamlfeaturesforgitrepositories-Publishingabranchtoyourprojectwebsite
>
> On Thu, Oct 3, 2019 at 10:57 AM Michael Shuler 
> wrote:
>
>> committed! :)
>>
>> https://gitbox.apache.org/repos/asf?p=cassandra-website.git
>>
>> Michael
>>
>> On 10/3/19 12:22 PM, Jon Haddad wrote:
>> > I think we can safely ignore them.  Thanks for figuring this out.
>> >
>> > On Thu, Oct 3, 2019 at 10:01 AM Michael Shuler 
>> > wrote:
>> >
>> >> I'm making progress through many periodic timeouts to svn.a.o and
>> >> restarts, but it appears that svn2git is smart enough to pick up where
>> >> it left off. The first commit captured at the svn path I'm specifying
>> is
>> >> when Cassandra was moved to a top level project at r922689
>> (2010-03-13).
>> >> I don't know the old incubator path, and it's probably OK to ignore the
>> >> few older incubator commits? I imagine it would mean starting over the
>> >> entire import to pull in those older incubator svn commits, then
>> >> changing the url and somehow importing the newer path on top?
>> >>
>> >> I tried using a local path as the source to try to speed things up,
>> >> after I got my first few timeouts, but that fails.
>> >>
>> >> Curious if anyone really cares if we lose a few early commits - if so,
>> I
>> >> can try to figure out the old path and start again.
>> >>
>> >> Michael
>> >>
>> >> On 10/3/19 11:14 AM, Jon Haddad wrote:
>> >>> Thanks for taking a look, Michael.  Hopefully you have better luck
>> than
>> >> me
>> >>> :)
>> >>>
>> >>> On Thu, Oct 3, 2019 at 6:42 AM Michael Shuler > >
>> >>> wrote:
>> >>>
>>  I cloned the empty cassandra-website git repo, and I'm running:
>> 
>>  svn2git http://svn.apache.org/repos/asf/cassandra/site --rootistrunk
>>  --no-minimize-url
>> 
>>  ..to see what I get. An svn checkout of the above url says it's only
>>  69M, so I suppose it's pulling all history of all time for all
>> projects?
>> 
>>  I'll let this roll for a while I run an errand and report back!
>> 
>>  Michael
>> 
>>  On 10/2/19 9:30 PM, Jon Haddad wrote:
>> > Daniel referred me to the GitBox self service system.
>> >
>> > I've attempted to port the site over using the tool Michael
>> suggested,
>>  but
>> > after a couple hours it died with this message:
>> >
>> > command failed: r922600
>> > git checkout -f master
>> >
>> > If either of you (Mick or Michael) want to give svn2git a shot maybe
>>  you'll
>> > get a different result.I think it may have been due to the large
>> >> size
>> > of the repo and the small drive on the VM I was using.  I can try it
>>  again
>> > tomorrow with more storage to see if I get a better result.  Mick if
>> >> you
>> > want to give it a shot in the meantime that would be appreciated.
>> >
>> > Jon
>> >
>> > On Wed, Oct 2, 2019 at 3:18 PM Jon Haddad 
>> wrote:
>> >
>> >> I created an INFRA ticket here:
>> >> https://issues.apache.org/jira/browse/INFRA-19218.
>> >>
>> >> On Wed, Sep 25, 2019 at 6:04 AM Michael Shuler <
>> >> mich...@pbandjelly.org>
>> >> wrote:
>> >>
>> >>> I see no good reason to trash history. There are tools to make
>> moving
>> >>> from svn to git (hopefully) painless. We used git-svn for the
>> main c*
>> >>> source to retain history of both, which this tool uses to do
>> >> migrations
>> >>> - https://github.com/nirvdrum/svn2git
>> >>>
>> >>> Michael
>> >>>
>> >>> On 9/25/19 12:57 AM, Mick Semb Wever wrote:
>> 
>> > Personally, no, I don't.  What I need to know is if someone who
>> >>> actually
>> > works on the site needs the history in *git*.
>> 
>> 
>>  Yes. I need the history in *git*.
>> 
>> 
>>  And I believe that INFRA can do the migration for you.
>>  (For example, INFRA-12055 and spark-website)
>> 
>> 
>> >> -
>>  To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
>>  For additional commands, e-mail: dev-h...@cassandra.apache.org
>> 
>> >>>
>> >>>
>> -
>> >>> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
>> >>> For additional commands, e-mail: dev-h...@cassandra.apache.org
>> >>>
>> >>>
>> >
>> 
>>  

Re: moving the site from SVN to git

[Jon Haddad]

Awesome, thanks Michael.

We need to do a little bit of additional configuration to have it switch
over.  Specifically, we need to set up the .asf.yaml config to tell the
servers how the site should be published.  I can take care of it tomorrow.

Reference:
https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories#id-.asf.yamlfeaturesforgitrepositories-Publishingabranchtoyourprojectwebsite

On Thu, Oct 3, 2019 at 10:57 AM Michael Shuler 
wrote:

> committed! :)
>
> https://gitbox.apache.org/repos/asf?p=cassandra-website.git
>
> Michael
>
> On 10/3/19 12:22 PM, Jon Haddad wrote:
> > I think we can safely ignore them.  Thanks for figuring this out.
> >
> > On Thu, Oct 3, 2019 at 10:01 AM Michael Shuler 
> > wrote:
> >
> >> I'm making progress through many periodic timeouts to svn.a.o and
> >> restarts, but it appears that svn2git is smart enough to pick up where
> >> it left off. The first commit captured at the svn path I'm specifying is
> >> when Cassandra was moved to a top level project at r922689 (2010-03-13).
> >> I don't know the old incubator path, and it's probably OK to ignore the
> >> few older incubator commits? I imagine it would mean starting over the
> >> entire import to pull in those older incubator svn commits, then
> >> changing the url and somehow importing the newer path on top?
> >>
> >> I tried using a local path as the source to try to speed things up,
> >> after I got my first few timeouts, but that fails.
> >>
> >> Curious if anyone really cares if we lose a few early commits - if so, I
> >> can try to figure out the old path and start again.
> >>
> >> Michael
> >>
> >> On 10/3/19 11:14 AM, Jon Haddad wrote:
> >>> Thanks for taking a look, Michael.  Hopefully you have better luck than
> >> me
> >>> :)
> >>>
> >>> On Thu, Oct 3, 2019 at 6:42 AM Michael Shuler 
> >>> wrote:
> >>>
>  I cloned the empty cassandra-website git repo, and I'm running:
> 
>  svn2git http://svn.apache.org/repos/asf/cassandra/site --rootistrunk
>  --no-minimize-url
> 
>  ..to see what I get. An svn checkout of the above url says it's only
>  69M, so I suppose it's pulling all history of all time for all
> projects?
> 
>  I'll let this roll for a while I run an errand and report back!
> 
>  Michael
> 
>  On 10/2/19 9:30 PM, Jon Haddad wrote:
> > Daniel referred me to the GitBox self service system.
> >
> > I've attempted to port the site over using the tool Michael
> suggested,
>  but
> > after a couple hours it died with this message:
> >
> > command failed: r922600
> > git checkout -f master
> >
> > If either of you (Mick or Michael) want to give svn2git a shot maybe
>  you'll
> > get a different result.I think it may have been due to the large
> >> size
> > of the repo and the small drive on the VM I was using.  I can try it
>  again
> > tomorrow with more storage to see if I get a better result.  Mick if
> >> you
> > want to give it a shot in the meantime that would be appreciated.
> >
> > Jon
> >
> > On Wed, Oct 2, 2019 at 3:18 PM Jon Haddad  wrote:
> >
> >> I created an INFRA ticket here:
> >> https://issues.apache.org/jira/browse/INFRA-19218.
> >>
> >> On Wed, Sep 25, 2019 at 6:04 AM Michael Shuler <
> >> mich...@pbandjelly.org>
> >> wrote:
> >>
> >>> I see no good reason to trash history. There are tools to make
> moving
> >>> from svn to git (hopefully) painless. We used git-svn for the main
> c*
> >>> source to retain history of both, which this tool uses to do
> >> migrations
> >>> - https://github.com/nirvdrum/svn2git
> >>>
> >>> Michael
> >>>
> >>> On 9/25/19 12:57 AM, Mick Semb Wever wrote:
> 
> > Personally, no, I don't.  What I need to know is if someone who
> >>> actually
> > works on the site needs the history in *git*.
> 
> 
>  Yes. I need the history in *git*.
> 
> 
>  And I believe that INFRA can do the migration for you.
>  (For example, INFRA-12055 and spark-website)
> 
> 
> >> -
>  To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
>  For additional commands, e-mail: dev-h...@cassandra.apache.org
> 
> >>>
> >>>
> -
> >>> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> >>> For additional commands, e-mail: dev-h...@cassandra.apache.org
> >>>
> >>>
> >
> 
>  -
>  To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
>  For additional commands, e-mail: dev-h...@cassandra.apache.org
> 
> 
> >>>
> >>
> >> 

Re: moving the site from SVN to git

[Michael Shuler]

committed! :)

https://gitbox.apache.org/repos/asf?p=cassandra-website.git

Michael

On 10/3/19 12:22 PM, Jon Haddad wrote:

I think we can safely ignore them.  Thanks for figuring this out.

On Thu, Oct 3, 2019 at 10:01 AM Michael Shuler 
wrote:


I'm making progress through many periodic timeouts to svn.a.o and
restarts, but it appears that svn2git is smart enough to pick up where
it left off. The first commit captured at the svn path I'm specifying is
when Cassandra was moved to a top level project at r922689 (2010-03-13).
I don't know the old incubator path, and it's probably OK to ignore the
few older incubator commits? I imagine it would mean starting over the
entire import to pull in those older incubator svn commits, then
changing the url and somehow importing the newer path on top?

I tried using a local path as the source to try to speed things up,
after I got my first few timeouts, but that fails.

Curious if anyone really cares if we lose a few early commits - if so, I
can try to figure out the old path and start again.

Michael

On 10/3/19 11:14 AM, Jon Haddad wrote:

Thanks for taking a look, Michael.  Hopefully you have better luck than

me

:)

On Thu, Oct 3, 2019 at 6:42 AM Michael Shuler 
wrote:


I cloned the empty cassandra-website git repo, and I'm running:

svn2git http://svn.apache.org/repos/asf/cassandra/site --rootistrunk
--no-minimize-url

..to see what I get. An svn checkout of the above url says it's only
69M, so I suppose it's pulling all history of all time for all projects?

I'll let this roll for a while I run an errand and report back!

Michael

On 10/2/19 9:30 PM, Jon Haddad wrote:

Daniel referred me to the GitBox self service system.

I've attempted to port the site over using the tool Michael suggested,

but

after a couple hours it died with this message:

command failed: r922600
git checkout -f master

If either of you (Mick or Michael) want to give svn2git a shot maybe

you'll

get a different result.I think it may have been due to the large

size

of the repo and the small drive on the VM I was using.  I can try it

again

tomorrow with more storage to see if I get a better result.  Mick if

you

want to give it a shot in the meantime that would be appreciated.

Jon

On Wed, Oct 2, 2019 at 3:18 PM Jon Haddad  wrote:


I created an INFRA ticket here:
https://issues.apache.org/jira/browse/INFRA-19218.

On Wed, Sep 25, 2019 at 6:04 AM Michael Shuler <

mich...@pbandjelly.org>

wrote:


I see no good reason to trash history. There are tools to make moving
from svn to git (hopefully) painless. We used git-svn for the main c*
source to retain history of both, which this tool uses to do

migrations

- https://github.com/nirvdrum/svn2git

Michael

On 9/25/19 12:57 AM, Mick Semb Wever wrote:



Personally, no, I don't.  What I need to know is if someone who

actually

works on the site needs the history in *git*.



Yes. I need the history in *git*.


And I believe that INFRA can do the migration for you.
(For example, INFRA-12055 and spark-website)



-

To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org






-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org






-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org






-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org

Re: moving the site from SVN to git

[Jon Haddad]

I think we can safely ignore them.  Thanks for figuring this out.

On Thu, Oct 3, 2019 at 10:01 AM Michael Shuler 
wrote:

> I'm making progress through many periodic timeouts to svn.a.o and
> restarts, but it appears that svn2git is smart enough to pick up where
> it left off. The first commit captured at the svn path I'm specifying is
> when Cassandra was moved to a top level project at r922689 (2010-03-13).
> I don't know the old incubator path, and it's probably OK to ignore the
> few older incubator commits? I imagine it would mean starting over the
> entire import to pull in those older incubator svn commits, then
> changing the url and somehow importing the newer path on top?
>
> I tried using a local path as the source to try to speed things up,
> after I got my first few timeouts, but that fails.
>
> Curious if anyone really cares if we lose a few early commits - if so, I
> can try to figure out the old path and start again.
>
> Michael
>
> On 10/3/19 11:14 AM, Jon Haddad wrote:
> > Thanks for taking a look, Michael.  Hopefully you have better luck than
> me
> > :)
> >
> > On Thu, Oct 3, 2019 at 6:42 AM Michael Shuler 
> > wrote:
> >
> >> I cloned the empty cassandra-website git repo, and I'm running:
> >>
> >> svn2git http://svn.apache.org/repos/asf/cassandra/site --rootistrunk
> >> --no-minimize-url
> >>
> >> ..to see what I get. An svn checkout of the above url says it's only
> >> 69M, so I suppose it's pulling all history of all time for all projects?
> >>
> >> I'll let this roll for a while I run an errand and report back!
> >>
> >> Michael
> >>
> >> On 10/2/19 9:30 PM, Jon Haddad wrote:
> >>> Daniel referred me to the GitBox self service system.
> >>>
> >>> I've attempted to port the site over using the tool Michael suggested,
> >> but
> >>> after a couple hours it died with this message:
> >>>
> >>> command failed: r922600
> >>> git checkout -f master
> >>>
> >>> If either of you (Mick or Michael) want to give svn2git a shot maybe
> >> you'll
> >>> get a different result.I think it may have been due to the large
> size
> >>> of the repo and the small drive on the VM I was using.  I can try it
> >> again
> >>> tomorrow with more storage to see if I get a better result.  Mick if
> you
> >>> want to give it a shot in the meantime that would be appreciated.
> >>>
> >>> Jon
> >>>
> >>> On Wed, Oct 2, 2019 at 3:18 PM Jon Haddad  wrote:
> >>>
>  I created an INFRA ticket here:
>  https://issues.apache.org/jira/browse/INFRA-19218.
> 
>  On Wed, Sep 25, 2019 at 6:04 AM Michael Shuler <
> mich...@pbandjelly.org>
>  wrote:
> 
> > I see no good reason to trash history. There are tools to make moving
> > from svn to git (hopefully) painless. We used git-svn for the main c*
> > source to retain history of both, which this tool uses to do
> migrations
> > - https://github.com/nirvdrum/svn2git
> >
> > Michael
> >
> > On 9/25/19 12:57 AM, Mick Semb Wever wrote:
> >>
> >>> Personally, no, I don't.  What I need to know is if someone who
> > actually
> >>> works on the site needs the history in *git*.
> >>
> >>
> >> Yes. I need the history in *git*.
> >>
> >>
> >> And I believe that INFRA can do the migration for you.
> >> (For example, INFRA-12055 and spark-website)
> >>
> >>
> -
> >> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> >> For additional commands, e-mail: dev-h...@cassandra.apache.org
> >>
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> > For additional commands, e-mail: dev-h...@cassandra.apache.org
> >
> >
> >>>
> >>
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> >> For additional commands, e-mail: dev-h...@cassandra.apache.org
> >>
> >>
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: dev-h...@cassandra.apache.org
>
>

Re: moving the site from SVN to git

[Michael Shuler]

I'm making progress through many periodic timeouts to svn.a.o and 
restarts, but it appears that svn2git is smart enough to pick up where 
it left off. The first commit captured at the svn path I'm specifying is 
when Cassandra was moved to a top level project at r922689 (2010-03-13). 
I don't know the old incubator path, and it's probably OK to ignore the 
few older incubator commits? I imagine it would mean starting over the 
entire import to pull in those older incubator svn commits, then 
changing the url and somehow importing the newer path on top?


I tried using a local path as the source to try to speed things up, 
after I got my first few timeouts, but that fails.


Curious if anyone really cares if we lose a few early commits - if so, I 
can try to figure out the old path and start again.


Michael

On 10/3/19 11:14 AM, Jon Haddad wrote:

Thanks for taking a look, Michael.  Hopefully you have better luck than me
:)

On Thu, Oct 3, 2019 at 6:42 AM Michael Shuler 
wrote:


I cloned the empty cassandra-website git repo, and I'm running:

svn2git http://svn.apache.org/repos/asf/cassandra/site --rootistrunk
--no-minimize-url

..to see what I get. An svn checkout of the above url says it's only
69M, so I suppose it's pulling all history of all time for all projects?

I'll let this roll for a while I run an errand and report back!

Michael

On 10/2/19 9:30 PM, Jon Haddad wrote:

Daniel referred me to the GitBox self service system.

I've attempted to port the site over using the tool Michael suggested,

but

after a couple hours it died with this message:

command failed: r922600
git checkout -f master

If either of you (Mick or Michael) want to give svn2git a shot maybe

you'll

get a different result.I think it may have been due to the large size
of the repo and the small drive on the VM I was using.  I can try it

again

tomorrow with more storage to see if I get a better result.  Mick if you
want to give it a shot in the meantime that would be appreciated.

Jon

On Wed, Oct 2, 2019 at 3:18 PM Jon Haddad  wrote:


I created an INFRA ticket here:
https://issues.apache.org/jira/browse/INFRA-19218.

On Wed, Sep 25, 2019 at 6:04 AM Michael Shuler 
wrote:


I see no good reason to trash history. There are tools to make moving
from svn to git (hopefully) painless. We used git-svn for the main c*
source to retain history of both, which this tool uses to do migrations
- https://github.com/nirvdrum/svn2git

Michael

On 9/25/19 12:57 AM, Mick Semb Wever wrote:



Personally, no, I don't.  What I need to know is if someone who

actually

works on the site needs the history in *git*.



Yes. I need the history in *git*.


And I believe that INFRA can do the migration for you.
(For example, INFRA-12055 and spark-website)

-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org






-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org






-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org

Re: moving the site from SVN to git

[Jon Haddad]

Thanks for taking a look, Michael.  Hopefully you have better luck than me
:)

On Thu, Oct 3, 2019 at 6:42 AM Michael Shuler 
wrote:

> I cloned the empty cassandra-website git repo, and I'm running:
>
> svn2git http://svn.apache.org/repos/asf/cassandra/site --rootistrunk
> --no-minimize-url
>
> ..to see what I get. An svn checkout of the above url says it's only
> 69M, so I suppose it's pulling all history of all time for all projects?
>
> I'll let this roll for a while I run an errand and report back!
>
> Michael
>
> On 10/2/19 9:30 PM, Jon Haddad wrote:
> > Daniel referred me to the GitBox self service system.
> >
> > I've attempted to port the site over using the tool Michael suggested,
> but
> > after a couple hours it died with this message:
> >
> > command failed: r922600
> > git checkout -f master
> >
> > If either of you (Mick or Michael) want to give svn2git a shot maybe
> you'll
> > get a different result.I think it may have been due to the large size
> > of the repo and the small drive on the VM I was using.  I can try it
> again
> > tomorrow with more storage to see if I get a better result.  Mick if you
> > want to give it a shot in the meantime that would be appreciated.
> >
> > Jon
> >
> > On Wed, Oct 2, 2019 at 3:18 PM Jon Haddad  wrote:
> >
> >> I created an INFRA ticket here:
> >> https://issues.apache.org/jira/browse/INFRA-19218.
> >>
> >> On Wed, Sep 25, 2019 at 6:04 AM Michael Shuler 
> >> wrote:
> >>
> >>> I see no good reason to trash history. There are tools to make moving
> >>> from svn to git (hopefully) painless. We used git-svn for the main c*
> >>> source to retain history of both, which this tool uses to do migrations
> >>> - https://github.com/nirvdrum/svn2git
> >>>
> >>> Michael
> >>>
> >>> On 9/25/19 12:57 AM, Mick Semb Wever wrote:
> 
> > Personally, no, I don't.  What I need to know is if someone who
> >>> actually
> > works on the site needs the history in *git*.
> 
> 
>  Yes. I need the history in *git*.
> 
> 
>  And I believe that INFRA can do the migration for you.
>  (For example, INFRA-12055 and spark-website)
> 
>  -
>  To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
>  For additional commands, e-mail: dev-h...@cassandra.apache.org
> 
> >>>
> >>> -
> >>> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> >>> For additional commands, e-mail: dev-h...@cassandra.apache.org
> >>>
> >>>
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: dev-h...@cassandra.apache.org
>
>

Re: moving the site from SVN to git

[Michael Shuler]

I cloned the empty cassandra-website git repo, and I'm running:

svn2git http://svn.apache.org/repos/asf/cassandra/site --rootistrunk 
--no-minimize-url


..to see what I get. An svn checkout of the above url says it's only 
69M, so I suppose it's pulling all history of all time for all projects?


I'll let this roll for a while I run an errand and report back!

Michael

On 10/2/19 9:30 PM, Jon Haddad wrote:

Daniel referred me to the GitBox self service system.

I've attempted to port the site over using the tool Michael suggested, but
after a couple hours it died with this message:

command failed: r922600
git checkout -f master

If either of you (Mick or Michael) want to give svn2git a shot maybe you'll
get a different result.I think it may have been due to the large size
of the repo and the small drive on the VM I was using.  I can try it again
tomorrow with more storage to see if I get a better result.  Mick if you
want to give it a shot in the meantime that would be appreciated.

Jon

On Wed, Oct 2, 2019 at 3:18 PM Jon Haddad  wrote:


I created an INFRA ticket here:
https://issues.apache.org/jira/browse/INFRA-19218.

On Wed, Sep 25, 2019 at 6:04 AM Michael Shuler 
wrote:


I see no good reason to trash history. There are tools to make moving
from svn to git (hopefully) painless. We used git-svn for the main c*
source to retain history of both, which this tool uses to do migrations
- https://github.com/nirvdrum/svn2git

Michael

On 9/25/19 12:57 AM, Mick Semb Wever wrote:



Personally, no, I don't.  What I need to know is if someone who

actually

works on the site needs the history in *git*.



Yes. I need the history in *git*.


And I believe that INFRA can do the migration for you.
(For example, INFRA-12055 and spark-website)

-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org






-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org

Re: moving the site from SVN to git

[Jon Haddad]

Daniel referred me to the GitBox self service system.

I've attempted to port the site over using the tool Michael suggested, but
after a couple hours it died with this message:

command failed: r922600
git checkout -f master

If either of you (Mick or Michael) want to give svn2git a shot maybe you'll
get a different result.I think it may have been due to the large size
of the repo and the small drive on the VM I was using.  I can try it again
tomorrow with more storage to see if I get a better result.  Mick if you
want to give it a shot in the meantime that would be appreciated.

Jon

On Wed, Oct 2, 2019 at 3:18 PM Jon Haddad  wrote:

> I created an INFRA ticket here:
> https://issues.apache.org/jira/browse/INFRA-19218.
>
> On Wed, Sep 25, 2019 at 6:04 AM Michael Shuler 
> wrote:
>
>> I see no good reason to trash history. There are tools to make moving
>> from svn to git (hopefully) painless. We used git-svn for the main c*
>> source to retain history of both, which this tool uses to do migrations
>> - https://github.com/nirvdrum/svn2git
>>
>> Michael
>>
>> On 9/25/19 12:57 AM, Mick Semb Wever wrote:
>> >
>> >> Personally, no, I don't.  What I need to know is if someone who
>> actually
>> >> works on the site needs the history in *git*.
>> >
>> >
>> > Yes. I need the history in *git*.
>> >
>> >
>> > And I believe that INFRA can do the migration for you.
>> > (For example, INFRA-12055 and spark-website)
>> >
>> > -
>> > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
>> > For additional commands, e-mail: dev-h...@cassandra.apache.org
>> >
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
>> For additional commands, e-mail: dev-h...@cassandra.apache.org
>>
>>

Re: moving the site from SVN to git

[Jon Haddad]

I created an INFRA ticket here:
https://issues.apache.org/jira/browse/INFRA-19218.

On Wed, Sep 25, 2019 at 6:04 AM Michael Shuler 
wrote:

> I see no good reason to trash history. There are tools to make moving
> from svn to git (hopefully) painless. We used git-svn for the main c*
> source to retain history of both, which this tool uses to do migrations
> - https://github.com/nirvdrum/svn2git
>
> Michael
>
> On 9/25/19 12:57 AM, Mick Semb Wever wrote:
> >
> >> Personally, no, I don't.  What I need to know is if someone who actually
> >> works on the site needs the history in *git*.
> >
> >
> > Yes. I need the history in *git*.
> >
> >
> > And I believe that INFRA can do the migration for you.
> > (For example, INFRA-12055 and spark-website)
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> > For additional commands, e-mail: dev-h...@cassandra.apache.org
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: dev-h...@cassandra.apache.org
>
>

Re: moving the site from SVN to git

[Mick Semb Wever]

> Personally, no, I don't.  What I need to know is if someone who actually
> works on the site needs the history in *git*. 


Yes. I need the history in *git*.


And I believe that INFRA can do the migration for you.
(For example, INFRA-12055 and spark-website)

-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org

Re: moving the site from SVN to git

[Anthony Grasso]

Hi Jon,

Thank you for actioning this!

The only trivial things that come to mind for me is to do with
documentation:

   - The README  file
   with the instructions to build the site points to SVN
   - The website Publication page
   
   and its source file
   

which
   point devs to the README file in SVN.

If we intend to keep SVN up for a while, I think it should be fine to move
the website over to the new Git repo. After the change over we could then
update the README file and website link. I am happy to make these changes
after we cut over to the Git repo.

Cheers,
Anthony

On Wed, 25 Sep 2019 at 06:44, Jon Haddad  wrote:

> While at apachecon I spoke with the folks at the INFRA desk to find out
> about moving the website from SVN to Git, and it's pretty straightforward.
> Here's the process:
>
> 1. Create a new Git repo fort the site
> 2. Copy the files over.  I don't think we care about history.  Unless
> someone speaks up, I'll just copy over what's current.
> 3. File a ticket and point them to the new repo
>
> Are there any dependencies currently pointing to the SVN repo that we'll
> need to update that would block me from taking care of this?
>
> Jon
>

Re: moving the site from SVN to git

[Jon Haddad]

Personally, no, I don't.  What I need to know is if someone who actually
works on the site needs the history in *git*.  It would still be archived
in SVN.

On Tue, Sep 24, 2019 at 2:12 PM Joshua Drake  wrote:

> On Tue, Sep 24, 2019 at 1:44 PM Jon Haddad  wrote:
>
> > While at apachecon I spoke with the folks at the INFRA desk to find out
> > about moving the website from SVN to Git, and it's pretty
> straightforward.
> > Here's the process:
> >
> > 1. Create a new Git repo fort the site
> > 2. Copy the files over.  I don't think we care about history.  Unless
> > someone speaks up, I'll just copy over what's current.
> >
>
> You care. Use a migration tool.
>
> JD
>

Re: moving the site from SVN to git

[Joshua Drake]

On Tue, Sep 24, 2019 at 1:44 PM Jon Haddad  wrote:

> While at apachecon I spoke with the folks at the INFRA desk to find out
> about moving the website from SVN to Git, and it's pretty straightforward.
> Here's the process:
>
> 1. Create a new Git repo fort the site
> 2. Copy the files over.  I don't think we care about history.  Unless
> someone speaks up, I'll just copy over what's current.
>

You care. Use a migration tool.

JD

moving the site from SVN to git

[Jon Haddad]

While at apachecon I spoke with the folks at the INFRA desk to find out
about moving the website from SVN to Git, and it's pretty straightforward.
Here's the process:

1. Create a new Git repo fort the site
2. Copy the files over.  I don't think we care about history.  Unless
someone speaks up, I'll just copy over what's current.
3. File a ticket and point them to the new repo

Are there any dependencies currently pointing to the SVN repo that we'll
need to update that would block me from taking care of this?

Jon