[Remember Mailing List] Moving repository to GitHub?

1 view
Skip to first unread message

ken manheimer

unread,
Feb 1, 2012, 6:30:13 PM2/1/12
to Remember Plone Product
Hey, all.  There's an increasing trend to migrate Plone products from the Plone subversion repository to GitHub, which will only be accelerated by the recent shutdown of the plone.org SVN browser service.  I would like to make the Products.remember migration happen, soon, and have scoped it out so it should be easy to do.

I believe the result of the migration would be that the trunk in the plone.org svn repo would be replaced by a note, indicating the new location on GitHub, so ongoing development and new releases would be done via GitHub.  The current branches and tags would still be accessible in the svn repo, however, so production checkouts wouldn't break.

See the http://collective.github.com web page for info about the Plone collective on GitHub.  (From the bit I've done with GitHub, it seems to be an outstanding source code management platform, with a somewhat more elaborate but substantially improved workflow compared to the svn service.)

Any objections to the migration?  I need to do the migration soon, before I get swamped in other work.

Ken



--
Archive: http://www.coactivate.org/[…]/1328139029680
To unsubscribe send an email with subject "unsubscribe" to reme...@lists.coactivate.org. Please contact remember...@lists.coactivate.org for questions.

Maurits van Rees

unread,
Feb 4, 2012, 9:17:17 AM2/4/12
to reme...@lists.coactivate.org
Op 02-02-12 00:30, ken manheimer schreef:
Hey, all.  There's an increasing trend to migrate Plone products from the Plone subversion repository to GitHub, which will only be accelerated by the recent shutdown of the plone.org SVN browser service.  I would like to make the Products.remember migration happen, soon, and have scoped it out so it should be easy to do.

I believe the result of the migration would be that the trunk in the plone.org svn repo would be replaced by a note, indicating the new location on GitHub, so ongoing development and new releases would be done via GitHub.  The current branches and tags would still be accessible in the svn repo, however, so production checkouts wouldn't break.

See the http://collective.github.com web page for info about the Plone collective on GitHub.  (From the bit I've done with GitHub, it seems to be an outstanding source code management platform, with a somewhat more elaborate but substantially improved workflow compared to the svn service.)

Any objections to the migration?  I need to do the migration soon, before I get swamped in other work.

+1

-- 
Maurits van Rees   http://maurits.vanrees.org/
Web App Programmer at Zest Software: http://zestsoftware.nl
"Logical thinking shows conclusively that logical thinking
is inconclusive." - My summary of Gödel, Escher, Bach

Tom Kapanka

unread,
Feb 7, 2012, 12:41:06 PM2/7/12
to reme...@lists.coactivate.org
go go go!

--

~Spanky

--
Archive: http://www.coactivate.org/projects/remember/lists/remember/archive/2012/02/1328636471547

ken manheimer

unread,
Feb 7, 2012, 5:32:40 PM2/7/12
to reme...@lists.coactivate.org
On Tue, Feb 7, 2012 at 12:41 PM, Tom Kapanka <spa...@kapanka.com> wrote:
go go go!

:-)

I actually did the migration last friday, Feb 3 - should have posted a followup here:
I have a few questions for those with git savvy out there, due to my own, limited git familiarity:
  • How would you tag the new repository with 1.9b2?  I'm able to tag a local clone, but that apparently doesn't incur changes that can be pushed back to the origin.

  • Does anyone know if there is an easy way to create a git tag corresponding to a particular tag that existed in the copied SVN repository?  If I remember right, Products.remember v 1.3 is the last one compatible with Plone 3.x (and membrane versions before v2).  We can direct people to the version in the svn repo, but it would be nice to be free of any dependencies on it.

  • In general, please examine a clone/checkout from the git repo, to confirm that all is as it should be.
Ken

Wichert Akkerman

unread,
Feb 8, 2012, 2:04:19 AM2/8/12
to reme...@lists.coactivate.org
On 2012-2-7 23:32, ken manheimer wrote:
> On Tue, Feb 7, 2012 at 12:41 PM, Tom Kapanka <spa...@kapanka.com
> <mailto:spa...@kapanka.com>> wrote:
>
> go go go!
>
>
> :-)
>
> I actually did the migration last friday, Feb 3 - should have posted a
> followup here:
>
> * https://github.com/collective/Products.remember
>
> * I renamed the svn trunk directory:
> .../trunk-MOVED-TO-GITHUB-COLLECTIVE/
> <https://svn.plone.org/svn/collective/Products.remember/trunk-MOVED-TO-GITHUB-COLLECTIVE/>
>
> * and left some notes directing to the git repo:
>
> o README.github
> <https://svn.plone.org/svn/collective/Products.remember/trunk-MOVED-TO-GITHUB-COLLECTIVE/README.github> in
> the trunk directory, and
> o a note at the top of the README.txt
> <https://svn.plone.org/svn/collective/Products.remember/trunk-MOVED-TO-GITHUB-COLLECTIVE/README.txt>

> in the same directory
>
> I have a few questions for those with git savvy out there, due to my
> own, limited git familiarity:
>
> * How would you tag the new repository with 1.9b2? I'm able to tag a

> local clone, but that apparently doesn't incur changes that can be
> pushed back to the origin.

git is stupid that way: you have to push tags separately. Use this:

git push --tags

> * Does anyone know if there is an easy way to create a git tag


> corresponding to a particular tag that existed in the copied SVN
> repository? If I remember right, Products.remember v 1.3 is the
> last one compatible with Plone 3.x (and membrane versions before
> v2). We can direct people to the version in the svn repo, but it
> would be nice to be free of any dependencies on it.

svn2git does that automatically. Please don't use another tool to do a
svn->git conversions (in particular do not rely on git svn).

Wichert.

--
Wichert Akkerman <wic...@wiggy.net> It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.


--
Archive: http://www.coactivate.org/projects/remember/lists/remember/archive/2012/02/1328684662527

ken manheimer

unread,
Feb 8, 2012, 3:29:49 PM2/8/12
to reme...@lists.coactivate.org
On Wed, Feb 8, 2012 at 2:04 AM, Wichert Akkerman <wic...@wiggy.net> wrote:
On 2012-2-7 23:32, ken manheimer wrote:
I actually did the migration last friday, Feb 3 - should have posted a
followup here:

 * https://github.com/collective/Products.remember
[...]

I have a few questions for those with git savvy out there, due to my
own, limited git familiarity:

 * How would you tag the new repository with 1.9b2?  I'm able to tag a
   local clone, but that apparently doesn't incur changes that can be
   pushed back to the origin.

git is stupid that way: you have to push tags separately. Use this:

   git push --tags

Thanks!  Will have to try it on my scratch repo.
 
 * Does anyone know if there is an easy way to create a git tag
   corresponding to a particular tag that existed in the copied SVN
   repository?  If I remember right, Products.remember v 1.3 is the
   last one compatible with Plone 3.x (and membrane versions before
   v2).  We can direct people to the version in the svn repo, but it
   would be nice to be free of any dependencies on it.

svn2git does that automatically. Please don't use another tool to do a svn->git conversions (in particular do not rely on git svn).

Before doing the migration I corresponded with Alex Clark, and got instructions from him and from the collective.github.com main page to use the link on the new repository to do the migration.  I assume it uses the collective's svn-migrate, and I haven't determined what it does underneath, but figure it was the right thing to do.  However, when I visit the new git repo's web view and follow the branches link, it reports that there are no unmerged branches.  Similarly, the Tags link reports zero tags.  ?

Ken
 
Wichert.
--
Wichert Akkerman <wic...@wiggy.net>   It is simple to make things.
http://www.wiggy.net/                  It is hard to make things simple.
--
Archive: http://www.coactivate.org/projects/remember/lists/remember/archive/2012/02/1328684662527

To unsubscribe send an email with subject "unsubscribe" to reme...@lists.coactivate.org.  Please contact remember-manager@lists.coactivate.org for questions.

Maurits van Rees

unread,
Mar 22, 2012, 7:31:09 AM3/22/12
to reme...@lists.coactivate.org
Hi,

Op 8 feb 2012, om 21:29 heeft ken manheimer het volgende geschreven:

Before doing the migration I corresponded with Alex Clark, and got instructions from him and from the collective.github.com main page to use the link on the new repository to do the migration.  

Which link is that? I think the link you see on a fresh repository is a link that has no chance of working for any collective project. Maybe I am just repeating rumours, but that link will need to read in the full Plone svn collective and will quit after an hour, which is not enough. Or did I miss something?

But you did import trunk, so something at least worked. :-)

https://github.com/plone/svn-migrate advocates to clone this svn-migrate project, run its buildout, sync the collective repository (which may take a few days this first time) and write a config file with instructions on which directories to take from svn to create the new project.

I assume it uses the collective's svn-migrate, and I haven't determined what it does underneath, but figure it was the right thing to do.  However, when I visit the new git repo's web view and follow the branches link, it reports that there are no unmerged branches.  Similarly, the Tags link reports zero tags.  ?

I finally took a look at this, using svn-migrate. I have created a repository in my own github account, which has all the tags and branches:

I guess the best thing would now be to remove the collective/Products.remember repository, create a new one and pull from my project. Not sure if that may break some things in github. But at least no changes have been made to this repo on github since it was imported.

Oh, I may need an authors.cfg file that has more collective authors and try the export again. I will ask Rok Garbas if he has one.
Compare this commit by you (Ken) in the collective repo which shows your github account:
versus the same one in my repo:

Cheers,

Maurits van Rees
Zest Software

Maurits van Rees

unread,
Apr 2, 2012, 11:58:36 AM4/2/12
to reme...@lists.coactivate.org
Op 22-03-12 12:31, Maurits van Rees schreef:

> I finally took a look at this, using svn-migrate. I have created a
> repository in my own github account, which has all the tags and branches:
> https://github.com/mauritsvanrees/Products.remember
>
> I guess the best thing would now be to remove the
> collective/Products.remember repository, create a new one and pull
> from my project. Not sure if that may break some things in github. But
> at least no changes have been made to this repo on github since it was
> imported.

As far as I saw, no actions had been taken on the github repo (no issues
filed, no new commits, no pull requests), so today I indeed removed
https://github.com/collective/Products.remember. It got recreated again
by the automatic scripts that read permission.cfg as indicated in
http://collective.github.com. But I have no admin access anymore. I am
asking Rok Garbas for help. For a bit more detail see
https://github.com/collective/collective.github.com/pull/229

Ken and Ross, you are in the same github team:
https://github.com/organizations/collective/teams/138790
Do you somehow still have admin access?

Meanwhile, https://github.com/mauritsvanrees/Products.remember has the
same repo, in case anyone is desperately in need of that. If anyone
gets admin access, a pull from this repo (with all branches and tags)
should work fine too. I will likely delete my own repo after a while
once everything is fine.

Hang in there! :-)

--
Maurits van Rees: http://maurits.vanrees.org/

Zest Software: http://zestsoftware.nl

--
Archive: http://www.coactivate.org/projects/remember/lists/remember/archive/2012/04/1333382318643

Ken Manheimer

unread,
Apr 2, 2012, 12:47:11 PM4/2/12
to reme...@lists.coactivate.org
Hi, Marits. Sorry I've been unresponsive about this - my available time is very low at the moment.

The repository migration I did was actually based on something Alex Clark was doing - he was migrating some other repositories, and offered help to others who were doing the same thing. Therefore, I'm not entirely sure what the process was - I added myself to the permissions.cfg in the collective.github.com github repository, he processed that and enabled an "Import from subversion" link, on the Products.remember github repository that I created, which I used. I gather that wasn't the right thing - perhaps a generic github script? - and I should have instead used the https://github.com/plone/svn-migrate script.

It sounds like, in order to use svn-migrate, you needed to be added to the [repo:Products.remember] collective team, but it looks like you're now included.

Ken

To unsubscribe send an email with subject "unsubscribe" to reme...@lists.coactivate.org.  Please contact remember-manager@lists.coactivate.org for questions.


Reply all
Reply to author
Forward
0 new messages