Questions about openhab repository

[IgorZ]

Hi community,

I'm using openhab in test mode. Recently I found couple of issues and want to propose a fix for one of them.

I have local clone of openhab where I can make a changes, test them and so on. But I cannot understand how to propose change to be added into main repository.
Page https://code.google.com/p/openhab/wiki/HowToContribute says that I need to create server side clone using this link http://code.google.com/p/openhab/source/createClone. But looks like this link is wrong...

How can I create server side clone?
Or maybe there is another way to contribute/propose a patch...

And second question. Do project owners consider to have a clone of repository at (or even move to) GitHub? :-)

Thank you,
Igor

[Kai Kreuzer]

Hi Igor,

> I have local clone of openhab where I can make a changes, test them and so on. But I cannot understand how to propose change to be added into main repository.

> Page https://code.google.com/p/openhab/wiki/HowToContribute says that I need to create server side clone using this link http://code.google.com/p/openhab/source/createClone. But looks like this link is wrong…

4 days ago, this link was still working, but then Google seems to having removed this functionality - very weird! Especially as I cannot find any trace on the web why this was done (or that it was announced).

> How can I create server side clone?

No idea, best follow up on https://code.google.com/p/support/issues/detail?id=30989

> And second question. Do project owners consider to have a clone of repository at (or even move to) GitHub? :-)

Especially now: YES!
After our release next weekend, we will actually start creating the Eclipse Smart Home project and thus moving the openHAB code away from Google Code - so expect to see it becoming available on GitHub during the coming weeks (but please allow us some time as September will be busy for JavaOne already…)

Stay tuned!
Kai

[Jan-Willem Spuij]

Regarding google code: I've actually noticed it too. The list with clones is not accessible from the menu, new clones cannot be created anymore and the last updated dates of the list of clones are not updated anymore. I posted a comment on the google code discussion group, but the post was deleted.

To me, cloning is essential functionality for a cloud repository service and it should be really easy to use. The sooner the move to Github, the better.

[Kai]

Good news!

We have just moved our sources to GitHub! See https://github.com/openhab/openhab.

This is now the place to create forks of the repo, create pull requests etc - I hope this will ease the collaboration on our code base again!

I have updated the wiki pages accordingly, if I missed anything, please let me know.

Please note that we so far have only moved the sources to GitHub - Issue tracker, wiki etc. still remains at Google Code, although we will look into moving this as well at some point. But there isn't any time pressure on this.

Best regards,
Kai

[Jan-Willem Spuij]

Great news Kai!

I was wondering which tool/method you've used to convert the repository. I'd like to convert my clone with history as well. Probably have the best chance using the same method I guess.

Thanks in advance,

JwS

[Pali]

I'm wondering exactly the same. I have some bindings and changes (multiple branches) on my clone, which are not yet merged to main repo. So what is the best way to move on github? If we convert our personal repos to github, they then new projects on github not forks? So is it even possible then easily pull changes to main repo? It's easy to make new fork, but how import changes from google clone?

Pali

[davy vanherbergen]

Hi Kai,

Attached you can find an attempt for a .gitignore file to replace the old .hgignore.

Kind regards,

Davy

[Kai Kreuzer]

Thanks a lot, Davy! I have just pushed it.

Regards,
Kai

[Kai Kreuzer]

Hi,

We have used fast-export as described in http://stackoverflow.com/questions/16037787/convert-mercurial-project-to-git

Problem is that this only works if the git repo is completely empty - so it won't work if you create a fork of the existing openHAB git repo. Not sure if you can create pull requests for a repo that is not a fork? If this is possible, that would be your way to go: Create a completely empty repo on Github, check it out and run fast-export to get all your code from the hg repo.

If one of you can try this out or finds another solution, please post it here for the others :-)

Cheers,

Kai

--
You received this message because you are subscribed to the Google Groups "openhab" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openhab+u...@googlegroups.com.
To post to this group, send email to ope...@googlegroups.com.
Visit this group at http://groups.google.com/group/openhab.
For more options, visit https://groups.google.com/groups/opt_out.

[Till Klocke]

I currently try to use hg-git. I already managed to checkout my github fork into a new local hg-repo and push from my old hg-clone to the new local hg-repo. There were some warnings, but it seems to look okay. Next I have to try to push to my github fork and verify everyhting went okay. But at least yesterday evening pushing wan't working. I don't know why yet.

[Jan-Willem Spuij]

Ok, I managed to convert my clone into a github fork. Ultrashort version:

1. create a github account.
2. while logged in, go to: https://github.com/openhab/openhab and hit the fork button.
3. clone your forked repo into a folder on your local drive. This is the final git repo that you will be using from now on.
4. create a temporary repo (lets call this temp-repo) on your local drive using git init to have a destination to convert the mercurial repo into.
5. use https://github.com/frej/fast-export to export your mercurial repo into temp-repo according to instructions.
6. add temp-repo as remote to the git repo in step 3, by changing to the final git repo dir and using git remote add <remotename> file:///<path to temp repo>
7. use this remote to check-out the branches that you want to convert into the final repo. Do not use the --track option!
   
8. push your branches to your github fork.

Hope it helps.

Jan-Willem

[Jan-Willem Spuij]

And for those more visually oriented ;-)

http://imagebin.org/271824

Op dinsdag 24 september 2013 20:34:04 UTC+2 schreef Jan-Willem Spuij:

[Thomas Eichstädt-Engelen]

Hi Jan,

thanks for great writeup!

Would you mind if i add it to the openHAB Wiki?

Best,

Thomas E.-E.

[Jan-Willem Spuij]

NP, please do.

JwS

Op woensdag 25 september 2013 00:45:13 UTC+2 schreef Thomas E.-E.: