Thinking of Using Git for our Version Control System
At work, we're redesigning the main website from the ground up and are currently developing protocols for how new content will be implemented and maintained. Since we are a large science museum, there is a hefty amount of always changing content (exhibits, 3-D shows, IMAX shows, live presentations, events, etc etc). In addition to frequently changing content, we also need to make sure that what goes online meets our branding and marketing guidelines, education standards and accessibility standards. This is all a long way of saying that there are many people working on any given portion of the site at any given moment, so we're in the process of researching the best version control system (VCS) to meet our needs.
I've pretty much come to the conclusion that Git is the way to go. In a Google tech talk, Linus Torvald, known for initiating the development on the Linux kernel, rips on CVS (Concurrent Versions System), harshly and only half-jokingly claiming that for 10 years of Linux kernel development, they used tarballs and patches and that was STILL better than CVS.
In 2002, Linux kernel development started using BitKeeper because, for a variety of reasons, Linus Torvald thought it was the best VCS tool available. Unfortunately, it was proprietary software owned by BitMover, which led to some passionate arguments since the Linux kernel development was a free project. Ultimately, Torvald and BitMover CEO Larry McVoy agreed that life would be easier for both parties if they parted ways.
So after the Linux & BitKeeper breakup, Torvald didn't want to do any more development until he had a workable replacement. He searched for alternatives, and said the vast majority he'd write off without even trying them out because there are just some criteria that weren't up for debate.
- It had to be distributed (Being distributed means you don't have one centralized location. Everyone works on their own branch and if it's good, instead of committing it to the "centralized branch", you just have your own good code that other people can clone and use. This eliminates the need for a few select gatekeepers and removes a lot of endless politicking.)
- It has to perform well and be reliable (Cited Monotone as an example, which he said had great ideas but the performance was terrible.)
- It needs to guarantee that whatever gets put into it comes out EXACTLY the same (i.e. In many CVS's, you may have memory or disk corruption and never know unless you see it in the file)
I think we're still researching our options, but I'd be surprised if we don't use Git. Now I'm seeing if I can get the book Pro Git by Scott Chacon ordered from our friendly local library.
Summary of First Full Week at MOS
I've completed a full week at the Museum of Science in Boston (MOS) and I'm looking forward to going back to work tomorrow. I had a nice introduction to the work culture before I even arrived for my first day when I was CC'd on an email that the director sent to our entire department introducing me in very kind words, letting everyone know when I'd be starting and suggested that people stop by during lunch to say hi. I also received some emails from a member of the department that included some kind words and helpful advice for my first day such as, "bring a sweater". These may seem like small gestures, but they are my first impression and as it's all I had to go on at the time, it made me feel optimistic about working with this team.
For my first day, the director gave me a tour of the museum campus and introduced to me quite a few people. The museum is huge; way larger than I had previously understood including a huge education wing that I had no idea existed. I come from Chicago, home of the Museum of Science and Industry and my understanding of MOS was that it was a great science museum, but that it's outreach and mission was on a much smaller scale than Chicago. While I'm still learning about MOS, I think it's safe to say that I underestimated its reach. My Chicago bias has been exposed. There is an entire department dedicated to working with other institutions. There is a library that provides science educational resources. It's quite involved in promoting education and scientific initiatives...it's great.
After getting the grand tour, I got to spend the rest of the day walking around the exhibits on my own. I tried to visit every exhibit, but I definitely spent more time in certain areas like technology and mathematics. I also got to take in a few shows and special exhibits: a special temporary exhibit A Day In Pompeii, an Omni film Greece: Secrets of the Past, a Planetarium show Undiscovered Worlds: The Search Beyond Our Sun, and the Lightening! Live Presentation in the Theater of Electricity.
For the rest of the week, I shadowed our Web Projects Manager to various meetings to meet members of other departments and get my footing on where we are in a massive web redesign project.
It's a great place doing wonderful work, a brilliant team, an interesting project (web redesign) and that only scratches the surface. I'd love to write more about everything I've learned this week; I'll hopefully manage to touch on the big topics. My general feeling right now is, "I can't believe I get to be here."
It's not all cupcakes and sprinkles though. The commute is about double what I anticipated and this last week has been hampered by purchasing a lemon of a vehicle that I thought would be a simple car to get me reliably to and from the T station. Unfortunately, there's a whole lot of problems with the car that are hopefully being fixed by the dealer (not likely...they've been awful and cheap) and I'm preparing myself to have to pursue a drawn out process for a refund. It's generally taking about an hour car drive to/from the T station and then another near hour on the T...four hours out of the day. It's a lot. I've been able to try out varying schedules and I'm liking the 8am-4pm time slot, and this'll do for a while. As much as I love and adore where I currently live, I suspect another move is in the not too distant future.