Move to GitHub this weekend.

[Gunnar Aastrand Grimnes]

Just to make this visible to those who do not follow the rdfextras
release thread!

We decided to move rdflib/rdfextras to github - for increased
visibility, increased contributions, and simply increased geek-cred.

All infrastructure will be moved, i.e. wiki-pages, issues and source code.

Graham has kindly volunteered to do the nitty gritty details of moving
this weekend, so please stop making changes to the google code stuff
now! :)

A few details:

* I think we should leave the google code projects (i.e. do not delete
them), but just have a front-page that links to github

* We have a good history of leaving out-dated docs around, I propose
deleting all the google code wiki-pages NOW :)

* I do not know what to do about the hg repository - there is no way
to mark it read only - I guess I can take away everyone's commit
rights :) OR I can delete it completely once we are sure we have
moved. There appears to be a way to get pip to install development
snapshots directly from hg - this relies on the hg url being in pypi -
I could never get it to work.

* @Graham: What about rdfextras - it seems the git-repos was cloned
from hg on 25th of January, any changes I made after that are only in
hg. I can probably roll it into one patch, and apply it to git and
it's all good?

- Gunnar

--
http://gromgull.net

[Graham Higgins]

On Saturday, 18 February 2012 07:33:31 UTC, Gunnar Aastrand Grimnes wrote:

All infrastructure will be moved, i.e. wiki-pages, issues and source code.

* I think we should leave the google code projects (i.e. do not delete

them), but just have a front-page that links to github

+1

* We have a good history of leaving out-dated docs around, I propose
deleting all the google code wiki-pages NOW :)

Makes very good sense. They have been transcribed to the RDFLib GitHub wiki.

* I do not know what to do about the hg repository - there is no way
to mark it read only - I guess I can take away everyone's commit
rights :) OR I can delete it completely once we are sure we have
moved.

Both, I guess.

There appears to be a way to get pip to install development
snapshots directly from hg - this relies on the hg url being in pypi -
I could never get it to work.

Not quite sure of the context here but anyway ,,,

I've used the standard "pip install from repos" approach with success.

pip install git+https://github.com/RDFLib/rdflib.git

or, to download into ./src and setup+install from there:

pip install -e git+https://github.com/RDFLib/rdflib.git#egg=rdflib

There's also the "pip install from tarzipball" approach:

pip install https://github.com/downloads/RDFLib/rdflib/rdflib-3.2.0.tar.gz

 

* @Graham: What about rdfextras - it seems the git-repos was cloned
from hg on 25th of January, any changes I made after that are only in
hg. I can probably roll it into one patch, and apply it to git and
it's all good?

All done.

I went the long way round, converting the latest rdfextras-hg to git and merging that with the github master. This approach has the advantage of preserving the individual commits and their messages.

I've tried a few techniques for converting repos from hg to git. The one that has proved reliable in terms of including branches and tags is hg-fast-export and is detailed in a comment to a blog post on the subject [1]. It's quite terse, so I'll repeat it here for convenience (it references Bitbucket but GitHub is a straight replacement).

"""

Instead use hggit you may use hg-fast-export.

1. Create new git repo at Bitbucket.

2. git clone git://repo.or.cz/fast-export.git

3. mkdir new_git_repo

4. cd new_git_repo

5. git init

6. /path/to/hg-fast-export.sh -r /path/to/hg_repo

7. git checkout HEAD

8. git remote add origin g...@bitbucket.org:shaharevron/myproject.git

9. git push origin master

"""

I've added SkipTest to a few more rdfextras tests in order to get a (somewhat spurious) set of "blue balls" across the board for rdfextras on the shiningpanda CI build space [2]. I will add issue tickets as appropriate (I was hoping to have transferred the issue lists by now but I have been delayed).

Thanks for everyone's co-operation with this exercise and apologies for the inconvenience - I feel that we're in a more commanding position.

[1] http://arr.gr/blog/2011/10/bitbucket-converting-hg-repositories-to-git/

[2] https://jenkins.shiningpanda.com/rdflib/

Cheers

Graham

[Gunnar Aastrand Grimnes]

>> * We have a good history of leaving out-dated docs around, I propose
>> deleting all the google code wiki-pages NOW :)
>
> Makes very good sense. They have been transcribed to the RDFLib GitHub wiki.

They are gone.

>
>> * I do not know what to do about the hg repository - there is no way
>> to mark it read only - I guess I can take away everyone's commit
>> rights :) OR I can delete it completely once we are sure we have
>> moved.
>
> Both, I guess.

Call me paranoid - but I'll hang for just a few days before nuking
them - I'll do it by next weekend :)

>
> I went the long way round, converting the latest rdfextras-hg to git and
> merging that with the github master. This approach has the advantage of
> preserving the individual commits and their messages.

Good work - thanks a lot!

I've split out the -web parts and made rdfextras-web (I realised later
all the other projects are called rdflib-* - oh well.

[Graham Higgins]

On Monday, 20 February 2012 17:50:52 UTC, Gunnar Aastrand Grimnes wrote:

Call me paranoid - but I'll hang for just a few days before nuking
them - I'll do it by next weekend :)

There are still quite a few scattered references around to specific LOCs in specific hg revs. I don't see any harm in nuking commit privs and then simply leaving the repos on Gcode with a message in the setup.py to the effect that the repos is now frozen. Naturally, we'd encourage folks to move over to github eventually but it's not like Google are charging rent.

I've split out the -web parts and made rdfextras-web (I realised later
all the other projects are called rdflib-* - oh well.

With GitHub, it's really easy to junk a repos and set up another. Unlike Google, GitHub actually deletes the repos.

And anyway, I was merely ensuring there was space for re-integrating a much-shrunken rdfextras back into RDFLib at some point in the future if that proved to be desirable. 

Cheers,

Graham

[Gunnar Aastrand Grimnes]

I've removed most members from the google code projects - there is no
other way to mark the hg-repos as read-only or to remove just
commit-rights.

Another admin issue is creating pypi entries for each of the new projects.

This is fairly easy with setuptools, I did it for rdfextras-web, and just ran:

python setup.py register

and then editted setup.cfg to have

[egg_info]
tag_build=.dev
tag_date=1

then do:

python setup.py bdist_egg upload

And you get dev snapshots uploaded.

If we actually make a release of something, you edit setup.py to
remove the dev tag and do the branching etc.

Apparently there is a better way with git:
http://dcreager.net/2010/02/10/setuptools-git-version-numbers/

I'm too lazy to look into it now.

- Gunnar

> --
> You received this message because you are subscribed to the Google Groups
> "rdflib-dev" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/rdflib-dev/-/JHxATk0XdYUJ.
>
> To post to this group, send email to rdfli...@googlegroups.com.
> To unsubscribe from this group, send email to
> rdflib-dev+...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/rdflib-dev?hl=en.

--
http://gromgull.net