hisham hm

🔗 Migrating my projects from SourceForge+Subversion to Github+Git

It’s been a while that I’ve been using Git comfortably — even though I still get stumped now and then, the workflow is much better than Subversion. I do finer grained commits with ease and I’m no longer afraid of making branches. Still, some projects of mine are still hosted in svn servers, mostly due to inertia and because they’re mostly single-person projects with the occasional patch and bug report but not much collaboration. For a more “social” project such as LuaRocks, git and Github have proven to be very useful tools.

Farewell to SourceForge

This, however, was the push I needed to move my projects away from SourceForge. From gimp.org:

In the past few months, we have received some complaints about the site where the GIMP installers for the Microsoft Windows platforms are hosted.

SourceForge, once a useful and trustworthy place to develop and host FLOSS applications, has faced a problem with the ads they allow on their sites - the green “Download here” buttons that appear on many, many adds leading to all kinds of unwanted utilities have been spotted there as well.

The tipping point was the introduction of their own SourceForge Installer software, which bundles third-party offers with Free Software packages. We do not want to support this kind of behavior, and have thus decided to abandon SourceForge.

From now on, Jernej Simončič, who provides the installer packages, uploads them to our FTP directly, and from there they will be distributed automatically to our mirrors. Please check Downloads page for updated information. http://gimp-win.sourceforge.net will remain active for the time being and direct users to the new download locations.

This saddens me a lot. I’ve been a SourceForge user for over 13 years. Having my first project there with a “.sourceforge.net” URL was a moment of pride; I felt I was becoming a free software developer “for real”, seeing my code there along with all those other projects I relied on daily, such as GIMP.

htop, in particular, has lived a beautiful life in SourceForge:

It blows my mind to think that these are direct downloads of the source code only. I assume the vast majority of users install htop running the distro package manager (apt-get, yum, etc.) but I have absolutely no way to estimate how many times this program has been installed. And that’s not only okay, it’s beautiful: it’s the nature of free software, the actual freedom, at work. There is no tight grip on users from a central authority, the code is roaming free in what is essentially a network of solidarity. I’ve certainly benefited from this network much more than I’ve contributed to it, but I’m happy to give a small part.

Another achievement I’m very proud of: a perfect 5-star rating score for htop. Surely not that many reviews when compared to really big projects, but it’s noteworthy to me at least, and I’m thankful to everyone who rated.

So, thanks for everything SourceForge, but it looks like it’s time to move on.

Say hello to Github, htop

I’ve already got a bunch of projects in Github so this change should not be traumatic.

I’m converting the repositories to Github and moving the website to my own domain. I’ve started with dit, which is a low-profile project, and everything went smoothly. So it’s time to do the same with htop.

The process is straightforward:

  1. Here are the Instructions for importing from Subversion from Github
  2. They recommend using svn2git. It took me a few tries to get the conversion perfect. I recommend taking a look at the generated repository with gitk and creating a file called ~/.svn2git/authors containing aliases matching your svn usernames with Github equivalents.

    My authors file looks like this:

    loderunner = Hisham Muhammad <hisham@gobolinux.org>
    hisham = Hisham Muhammad <hisham@gobolinux.org>
    

    And the command-line for svn2git:

    svn2git svn://svn.code.sf.net/p/htop/code/
    
  3. The next step was to create a new Github repository. I did that through their web interface.
  4. And then, to push the code from the locally generated git repo to Github:
    git remote add origin https://github.com/hishamhm/htop.git
    git push -u origin master
    
  5. Next, I wanted to download the htop website from SourceForge. I usually edited things straight through their shell account, but this got me to an SFTP session in which I could fetch the files:
    sftp loderunner,htop@frs.sf.net

    (By the way, I actually use yafc, which I highly recommend, instead of sftp. Also, as I looked for its URL to post on this paragraph, I just learned that the original yafc 1.1.1 from 2001, which I still use and was hosted in SourceForge and sat there for years without updates, has been taken by a new group of developers who resurrected the project and develop it in Github.)

    The site for htop is really simple so moving it to a new location was a relatively quick process; just needed to grep all references to sf.net and svn, and get my own direct Paypal donation button (to replicate the one I had in SourceForge I used this and this).

  6. Getting the archive of releases was a bit trickier. It’s also in frs.sf.net, but you need to know the correct directory. It doesn’t show up when you log in and ls. You have to cd to it:
    yafc ftp://loderunner@frs.sf.net
    # then, in the sftp session:
    cd /home/frs/project/htop
    get -p -r htop
    

    Now I have an archive of all releases, with their (mostly accurate) historical timestamps!

  7. The final steps are shutting down the sf.net services, such as the bug tracker and the code repository. This can be done easily through their admin interface. I’ve never had any plans to migrate the bug tracker history; this simplifies things (and I don’t even know if it’s possible). I’m not shutting everything down immediately, though: until I make a proper new release and distro maintainers catch up with the new URLs, I’ll keep the download links active there.

    The original website, however, is now gone and replaced with the following:

    <html>
    <head>
    <meta http-equiv="refresh" content="0; url=http://hisham.hm/htop">
    </head>
    </html>
    

    (I did try an .htaccess file, but the sf.net servers kept redirecting to a default page even when I tried to do it via html… thanks to Lynx I realized it was redirecting with a 403 Forbidden error, so I removed the .htaccess file and things worked as expected.)

  8. Still TODO: migrate the htop-general mailing list.

One criticism I’ve had of Github in the past was that it did not promote a culture of making proper releases like SourceForge always did, but that has improved in recent years. Github now has a “releases” feature which, while not perfect, does the job in many cases. I’m not sure if I’ll use it, since I prefer to make the tarballs for htop using the make dist feature from GNU Autotools. I hope to cause as little disruption as possible to the distro maintainers and I want to keep my packages looking the same.

The big test for the new setup will be the next release, which I hope to make in time for htop’s tenth anniversary(!), in the coming months. It is quite fitting that htop presents its new home in such a special occasion!

🔗 Free music: Color Bleed is finally online

I recorded an album with a group of extremely talented friends who I had collaborated with in previous projects. I wrote music and lyrics for all the songs; Roberto Coutinho from Ampli Studio was in charge of the mixing board (and also played in a number of tracks).

We are all very happy with the results, so check it out:

colorbleed.com.br

You can listen online and also download the mp3 files for free. It’s licensed CC BY-NC-SA 3.0.

All feedback is welcome and much appreciated!

🔗 GoDaddy updates its terms of service

Today I received a message that domain/hosting provider GoDaddy has updated its terms of service. Here is the relevant part of the message:


We recently made changes to the Universal Terms of Service Agreement affecting your Go Daddy® products and services. We are sending this email to all Go Daddy customers to make you aware of the following changes:

Section 1 (Overview)

We added language to provide that changes or modifications to the Universal Terms of Service Agreement will be effective upon posting to the Go Daddy website. You will be able to tell when the Agreement has been updated by looking at the “Last Revised” date at the top of the Agreement.

Section 8 (Additional Reservation of Rights)

We added language to assist with our fraud and abuse detection and prevention efforts.

Section 15 (Fees and Payments)

We added language to explain the differences between multi-currency product pricing and multi-currency transaction processing for products and services displayed on our website.

We updated the service fees associated with the “Pay By Check” payment option should your electronic check be returned unpaid.

Section 16 (Unclaimed Property; Dormancy Charges)

We added a new section to address the Revised Arizona Unclaimed Property Act.

This email shall serve as our official notification to you the above-referenced changes, all of which shall be effective immediately. Please take a moment to review the latest version of the Universal Terms of Service Agreement, which may be found here. Your continued use of Go Daddy products and services shall constitute your acceptance of the Agreement as last revised.

Section 8 (my emphasis) caught my eye. I searched around to see if anyone had pinpointed what was this change and I found an excellent project from the Electronic Frontier Foundation called TOSBack, a site dedicated to backtracking changes in Terms of Service pages. The page had some hiccups to sift through the various revisions of the file and pointing out the exact changes between the previous and the latest (as of Jan 2011) versions, but here’s what changed in Section 8:

8. ADDITIONAL RESERVATION OF RIGHTS

Go Daddy expressly reserves the right to deny, cancel, terminate, suspend, lock, or modify access to (or control of) any Account or Services (including the right to cancel or transfer any domain name registration) that it deems necessary, in its sole and absolute discretion, for any reason (as determined by Go Daddy in its sole and absolute discretion), including but not limited to the following:

  • to correct mistakes made by Go Daddy in offering or delivering any Services (including any domain name registration),
  • to protect the integrity and stability of, and correct mistakes made by, any domain name registry,
  • to assist with our fraud and abuse detection and prevention efforts,
  • to comply with applicable local, state, national and international laws, rules and regulations,
  • to comply with requests of law enforcement, including subpoena requests,
  • to comply with any dispute resolution process,
  • to defend any legal action or threatened legal action without consideration for whether such legal action or threatened legal action is eventually determined to be with or without merit, or
  • to avoid any civil or criminal liability on the part of Go Daddy, its officers, directors, employees and agents, as well as Go Daddy’s affiliates.

Go Daddy expressly reserves the right to review every Account for excessive space and bandwidth utilization, and to terminate or apply additional fees to those Accounts that exceed allowed levels.

(Note: I changed the numbered items to bullets in order to avoid adding noise to the diff by having to renumber them.)

So, basically GoDaddy says it “added language to assist with our fraud and abuse detection and prevention efforts”, while silently adding language that says they can cancel your account for any reason and that the causes include but are not limited to the list presented (thus rendering the list meaningless).

So, the new wording of the Terms of Service allows GoDaddy to terminate service without providing any reason whatsoever to their customers. I wonder if this has anything to do with the recent crackdowns on domain names and demands for companies to comply with the government in secrecy.


Latest posts


Search


Admin area


Feeds