distal-attribute
distal-attribute
distal-attribute
distal-attribute

moving to github/bitbucket ?

sandys posted 1 year ago in General
hi guys,
this is an awesome project, but I'm wondering if you can move to github or bitbucket to host this source code as well as use it as a bug tracker.
ansgar posted 1 year ago
SourceForge has a bugtracker as well. Yes, it looks outdated when you compare it to GitHub. But it's still a platform for a myriad of good projects, and as far as I know it was the first one at all.

HeidiSQL had it's code repository and bugtracker at Sourceforge in April 2006. Then, in May 2008, I switched to Google Code. I'm still a fan of Google Code due to its simplicity, but unfortunately Google will close it in January 2016, so I was foreced to move again. I played with the idea to move to GitHub, but as I'm more a fan of SubVersion than of Git, I moved back to good old Sourceforge.

Most issue reports come in here in the forum anyway. As a one-man-show spending a few spare hours on Heidi, a simple forum is a bit easier to maintain than a dedicated bugtracker.
sandys posted 1 year ago
hi ansgar,
thank you for replying. Yes I loved Google Code as well!!
But unfortunately it is closing. Do you not feel a bug tracker is more easier to manage ? I simply love Bitbucket for its bugtracker (it uses Atlassian bugtracker for free!).

I respect your decision, but it might be better for you as well. You can create a static website for yourself as well (https://pages.github.com/ and https://help.github.com/articles/setting-up-a-custom-domain-with-pages or https://confluence.atlassian.com/bitbucket/publishing-a-website-on-bitbucket-cloud-221449776.html ).And obviously you can do easy ticket management instead of forums.

I think if you ask, Bitbucket will also help migrate your existing data.

Great project !!
leus posted 1 year ago

I second the motion to move to a distributed versioning system, be it Git or Mercurial. Both Bitbucket and Github are good options. I use Bitbucket personally because it allows me to have several private projects for free, but I think Github has lot of more traction and better tools.

One of the great things about DCVS is merging - it looks just like magic, especially if you come from Subversion. I used to like subversion but it's just silly when compared with a modern DCVS. Branching and merging is an everyday thing when using Git; it's not a "special occasions" thing, but a normal operation that you do everytime you need to isolate something (be it a bug fix, a new feature, exploratory work, etc.) I have really painful memories when having to do complex merges with Subversion.

I really think this project would benefit from the extra exposure and less friction to new contributors if you move to Github.

ansgar posted 1 year ago

Exactly that feature - merging - didn't work like magic in Git for me. It always complained when pulling a modified file in which I had local modifications in other lines. This is what Subversion never has problems with - it just merges the file with my local modification, unless it's in the same line(s).

And, personally, I like the more simple approach of having one single head/trunk on the server.

Well, I'm probably also just used to Subversion due to so many years of using it.

Btw, CVS was never something I liked, as it did not even support renaming and moving files.

leus posted 1 year ago

Well, that's exactly the one killer feature of Subversion vs Git. Your experience is quite different from mine (and apparently from the rest of the world :D)

The flow you use (single head / trunk on the server) is fine. Remember, the server is just a normal repo.

When I say "DCVS" I mean "Distributed Concurrent Versioning System", not CVS. I've erased CVS from my mind. I used it a lot, and with great resistance moved to Subversion, and I was actually quite late to the game when moving to Mercurial, since Git looked like moontalk to me. I'm a recent Git convert, thought, but I'm really glad I did it.

Anyways, happy holidays, and many, many thanks for your extraordinary work.

sandys posted 1 year ago

@ansgar - while I appreciate the comments of @leus, my original post was around moving to github (and having bugs, wiki, source, everything there) rather than hosting your own. its much more easier to collaborate and work there.

incidentally, you can continue to use subversion on github.

https://help.github.com/articles/support-for-subversion-clients/ https://github.com/blog/1178-collaborating-on-github-with-subversion

github and subversion play very well together. and if you ever change your mind to get out of github (and move to a pure subversion host), it will be easy as well.

ansgar posted 9 months ago

I found the Subversion bridge on Github quite interesting, and played a bit with it recently. I found nearly nothing I need for HeidiSQL but could not be achieved with that.

I also played with an SVN importer on Github, and imported the current SVN state of HeidiSQL here: https://github.com/ansgarbecker/HeidiSQL

I am now searching for an easy way to migrate tickets, as there are quite some. Can anyone recommend some good issue migration tool for SourceForge to GitHub?

hazardland posted 9 months ago

Wow did not except Delphi still existed. Interesting can I compile source in Lazarus IDE with FreePascal? When I ll have time I want to try to give HeidiSQL Sublime Text Editor like UI if it will not be to complex task.

hazardland posted 9 months ago

Btw if you ll move to Lazarus you will be able to compile native binaries to linux and mac platforms

ansgar posted 9 months ago

Btw if you ll move to Lazarus you will be able to compile native binaries to linux and mac platforms

Yes, that's what I am keen on since several years. But unfortunately that seems to require a rewrite of large code blocks in HeidiSQL.

allanmc posted 9 months ago

Regarding ticket migration, it seems like this Perl script can get the job done: https://github.com/cmungall/gosf2github

thecotne posted 2 weeks ago

any updates about this?

it's not about svn vs git (but git is better :D )

it's just easier to contribute to open source projects on github then sending some files on email

also github has free static site hosting

bug tracker which can be used as forum as well

it has releases so you can host build files on github

you can use continuous integrations like travis ci to test code style automatically and run unit tests

and it will not get abandoned like google code did :D (btw google code did suggest moving to github)

Please login to leave a reply, or register at first.