Tag Archive for 'subversion'

Unfuddle vs Assembla: Git Support

Assembla seems to be having problems with their git service, and that’s too bad; now, I’m going to go use Unfuddle instead. The forums suggest that this has been an issue that started maybe a couple weeks ago. Of course, had I known this, I wouldn’t have spent the better part of yesterday and a couple hours today, banging my head against the wall.

I did, however, become much more well versed in the distributed source management system known as git. By the way, GitCasts is like the best thing to learn git from, I just hope that one day we’ll see all the commands that were used during the screencasts for easier consumption. Even as this project is going to most likely stay a solo venture, the saner branching/merging I keep hearing about makes my heart flutter.

But less about git, and more about the services that are providing git hosting: I liked Assembla because of their integration with Trac, one of my favorite bug tracking tools. I wasn’t familiar with Unfuddle’s or Assembla’s own milestone/scrum/chat/ticket system, and so I wanted to just keep using Trac. After tonight’s mess, I think I’m going to go and stick with Unfuddle for the time being and just try to start using their refreshingly different UI for all things project management. After all, I can move the entire repository with a single clone anyway.

Assembla: “Backpack” for Software Engineering and FREE

I’ve found myself need a full toolkit for software development as I move forward with HanMeta. This list includes goodies like:

  • Wiki/Documentation
  • Bug Tracking
  • Source Code Management
  • Chat/Communication Tool
  • AND something to put all of this together.

Assembla has been working well. It’s kinda like basecamp for software developers. The application just screams Rails and lickability.

I have a couple of issues with using Assembla though. For one, I don’t like how I’m not in charge of my own data. Sure, with Subversion and Trac, I can just export the codebase back out using the standard interfaces they offer, but they have their own built in wiki and messaging system. I don’t see an easy way to export that data, because it would be nice to have a backup of the data… I don’t know how that would look like, since all of this data that exists on their servers is going to be in some proprietary format anywa.

The funny thing is for my job at NCSA, I had to do the same thing for the Blue Waters Project. I was in charge of looking into some project management, bug tracking, source control system. In the end, the suite of applications at Atlassian seemed to be the best bet. Since money wasn’t a problem, this was the valid choice.

Since all the funding for HanMeta is coming out of my pockets, it’s pretty important for me to keep my costs down. Using Assembla, I can effectively outsource all of the pain of maintaining and dealing with multiple tools. Plus, it was easy to get started.

I bet I won’t be saying the same when the Assembla servers go down… but that’s another story.

Why I HAVE to use Git from now on…

I love seeing these technology leaders speak, even though not in person. First it was Sergey Brin, now, through the advent of YouTube, Linus Torvalds himself.

Yes, there’s an upside to the Internet video madness. All that VC money at hard work.

And man, he’s so very “strongly opinionated”. Codeword for: a jerk. He’s like David Heinemeier Hansson in this regard. “Opinionated” is the euphemism I’d use, but then again, they themselves wouldn’t tolerate that bullcrap. But they have a reason to be so opinionated… they wrote the book(s) on it. Literally.

Now, Torvalds makes very valid points. Almost… too valid. After all, he is the father of the Linux kernel, and heads one of the largest distributed open source project out there. He knows what is needed in this arena, and so I’m happy to have seen this clip.

And so… time to look into this git business.

EDIT: Version Control and “the 80%”

Ch-check It Out

Check-ch-check-check-check-ch-check it out

What-wha-what-what-what’s it all about

Work-wa-work-work-work-wa-work it out

Let’s turn this turn this party out

Sidenote: Indeed, this is the clean version.

This ditty has been stuck in my head for the past week. And there is no sign of stopping.

I guess in one sense, this song could just mean subversion checkouts. But that’d be too nerdy, and so I’ll stop there.

Another stanza of goodness:

Now remain calm no alarm

Cause my farm ain’t fat

So what’s up with that

I’ve got friends and family that i respect

When i think i’m too good

They put me in check

So believe when i say i’m no better than you

Except when i rap

So i guess it ain’t true

Like that y’all and you just don’t stop

Guaranteed to make your body rock

Just replace “rap” with “code”. This song is sick.

Well, I’m going to sleep well tonight

I don’t know the exact number of hours spent on HanMeta today. I gotta keep better track of the hours spent. I mean, I read my feeds during my breaks, and do some other work related to finding a full time job. Regardless, It’s just been a very very hectic day.

I’ll try to be a little bit more detailed so that others that are trying to set up Rails, Subversion, and Capistrano won’t have to go through the craziness that ensued today. Just need to figure out Capistrano… followed by lots of tweaking.

Yes. I’m so happy the app is getting started. I set a goal for this Sunday night (a little leeway) to have all this process stuff out of the way. Which mean I need to:

  • People
    • Who’s in? Who do I want in at this early stage?
    • Who’s doing what?
    • Take inventory of the hours people have to put towards this project
  • Rails
    • FastCGI vs Proxing HTTP?
    • How do I even do the second (because I hear it’s the right thing to do) on DreamHost?
    • So many other questions just about deploying an app…
  • Subversion
    • Double check on user/passwords
    • Make documentation (very similar to what I did with UIUC’s College of Education) on how to connect to the servers
  • ActiveCollab
  • Capistrano

Oh, and as a bonus, I want to run through the tutorial in the Rails book again before the end of the week. That way, I’ll be completely prepared for the n00bage that’s going to start next week.

I really hope that this doesn’t turn out like the last time I set out to do this. Lesson from that failure: Do something. It’s so hard to get things rolling.