Tuesday, February 22, 2011

More Mercurial Reading: Shared Repositories

I did some playing with Hg last night and found the basics to be easy enough. But, we're really gonna need a central repository with many projects running at once -- not something that Hg is really meant to support well. So below are some links to review.

First of course is the Hg guide itself
Man, this is deep stuff.

Here's some more also

"As an alternative, you can use hg-app http://hg.python-works.com it's hgwebdir replacement written entirely in pylons.

  • has it's own middleware to handle mercurial protocol request each request can be logged and authenticated + threaded performance unlikely to hgweb
  • full permissions per project read/write/admin access even on mercurial request
  • mako templates let's you cusmotize look and feel of application.
  • diffs annotations and source code all colored by pygments.
  • mercurial branch graph and yui-flot powered graphs
  • admin interface for performing user/permission managments as well as repository managment.
  • Additional settings for mercurial web, (hooks editable from admin panel !) also manage paths, archive, remote messages
  • backup scripts can do backup of whole app and send it over scp to desired location
  • setup project descriptions and info inside built in db for easy, non file-system operations
  • Full search text on repository codes
  • added cache with invalidation on push/repo managment for high performance and always upto date data.
  • rss / atom feeds, gravatar support
  • based on pylons 1.0 / sqlalchemy 0.6 "



Monday, February 21, 2011

A version of change

You know how you know you need to do something... you want to do that thing... you NEED to do that thing eventually... but the law or inertia just works against you? I know you've been there. Well, our IT development shop has been there for years. We've been rocking CVS as our version control system (VCS) for years (on the same server), and it's actually been OK. But some of us have seen the day of change coming for a long time now... or at least I have. The CVS is now past its prime and with new hardware we are poised to replace software as well.

Our shop often works on small projects and our developers have to work with just about every development technology known to man -- often in the same day. We grew up doing Java/Oracle mostly, but find ourselves living in .Net world these days. So Visual Studio integration would be a nice change for folks. Our guys and gals just want to focus on programming and do not want to deal with learning something ELSE new so a lower learning curve will initially seem more beneficial. In this vane, we currently don't  use a distributed VCS model nor we do likely need one (but, maybe there's some benefit here we're not thinking of).

Our projects range from small to medium-large in terms of code, though we often abuse CVS by sticking non-code in it. So, speed is not a HUGE issue, but I'm sure everyone would appreciate a speed up. Everyone knows we need to improve our tagging/branching/merging, so a VCS that helps us do this easily/safely and doesn't get in our way is desirable. Our company is pretty much Microsoft across the infrastructure board, but we rock the occasional Linux server. Our local backup is being augmented by the enterprise over-the-wire Microsoft solution that sends daily changes back to the HQ. So, we'll likely shift to a VCS that happily (natively?) runs on Windows.

So, tonight I've done more reading (been thinking about this for years) and determining the next CVS lilly pad is going to me more challenging than ever. It seems that all of the leading contenders have matured greatly.

Candidate 1 - SVN

Subversion seems to be adequate. We don't need distributed VCS and there are a lot of tools out there for it. Some of the disk and speed issues seem to have improved over the years, but likely are still issues. SVN likely offers the lowest learning curve for folks, but we also don't gain as much from it. Oh, and the migration from CVS seems to be mature. There do seem to be Windows native installations possible.

Candidate 2 - Hg
 Distributed VCS, decent documentation and rich tool sets. Learning curve will be steeper than SVN. Performance should be better than SVN, but not as fast as Git. Its python based and seems to be Windows native. I need to read more about CVS migration and how simple you can make using it (can you do central version management if you want to?). A little more reading from somewhat older links indicates that we will have a hard time following a centralized model with mercurial (though that may be a good thing).

The Rest - Git and Bzr
Git and Bazaar are both annoyingly compelling and mature. I'm going to ignore them for now however as I can't see anything that they do differently than what Hg does -reletive to our need.

Bzr seems like it is very flexible, but the toolset seems a little behind Git and Hg. Plus, it still seems to support Linux better than Windows given the competition developers seem to focus more on Hg and oddly Git for tool/integration outside of Linux.

Git is powerful and has some huge momentum. But the learning curve sounds like it's steepest here. That said, the existing toolset and mindshare to support them, particularly on Windows, seems to be present and not losing steam.

So, we don't have a decision yet, but I've provided some links below for more information.


Bazaar (bzr)

Subversion (svn)


Mercurial (hg)
Git (Git)

Comparisons

Instructions, Tutorials, Stories



Sunday, February 20, 2011

I've been waiting for..

James Fee called out two topics that I've been waiting for but failed to monitor. One is the maturation of an OpenLayers-eqsue, Flash-based mapping framework called OpenScales. We like building stuff in Flash and I remember being excited when I saw that OpenScales had started on the OpenLayers mailing list. I'm glad to see it achieve such maturity as an alternative to the ubiquitous OpenLayers (which also rocks).

The other topic relates to a running thought that I've had, "This SLD stuff sucks is too complex and time-consuming to produce for 90% of my needs. I wish there was a KML for styling - something that covers most of what I need but is simple to hack on." At the back of my mind I guess I was thinking about CSS for maps, or a something like a Mapserver Mapfile but for broader use.  Behold Carto. It's quite limited now as far as as the platforms its used in. But I hope similarly easy approaches (below) emerge as a wider alternative to SLD.

From the carto page, "We've been actively using and contributing to the Cascadenik project for several years, so it doesn't come as a surprise that Carto is heavily inspired by Mike's pioneering work in Cascadenik. We hope that our work on Carto will contribute to the emerging field of CSS-like map styling which includes projects like GSS and MapCSS and the GeoServers CSS Module"


Tuesday, June 23, 2009

Post-pre - Pre

I do not like wikis, SharePoint and a good many products from Microsoft. This includes Windows on phones - even the sexy new OS (tried it on the HTC Touch Pro and took it back immediately). My nerd-friends know this. These friends also know that we are a Sprint family for better or worse (we've had respectable service from the Sprint network and honestly we've always found them to provide excellent customer service and value as well. They also are willing to admit when they screw up and will cut you a deal. Verizon and AT&T do not want your business badly enough to incentivize you to stay). So, as a Sprint user, iPhone is out for now. Verizon's phones have never spoken to me, though Blackberry's would work fine if I could use them with my work email servers and not pay extra.

So, what I know is that I'm staying with Sprint for a while. This really should be OK because all I need is a phone with a modern browser, an OS that doesn't get in my way ( Windows), syncs with M$ Exchange, top-notch calendaring/contacts/texting, and is responsive. I also must have a vertical keyboard and will pay extra for a physical keyboard. So, I'm left with Crackberry and some device from our friends at Palm. As a historical Palm user (currently running a Centro after many years with a Treo 650), I will stay with Palm. Therefore, after all this I will eventually own a Pre.

I've been watching the reports about the Pre and all the comparisons to the iPhone. Firstly, if I wanted an iPhone badly enough I would switch to AT&T -- I don't have to have an iPhone. I just need a phone that provides many of the same benefits as an iPhone - and in my case I also want a physical keyboard. I do not consider the Pre as an iPhone-wanna-be, I see it as just another "modern" phone (with "modern" once again defined for us by Apple).

The reports I've also seen speak about the let-down some people have had with the Pre (poor quality, still missing SDK, anemic selection of apps). I'd be lying if I said these reports didn't sadden me a little. But, I'm willing to cut Palm some slack as they rapidly push out a huge new platform - there will be bugs/issues. That said, I really need Palm to get the Pre platform cleaned up and silky smooth within 6 months. It seems like they have a trajectory to do that. But they still have some major hurdles.

Thursday, April 9, 2009

Spatial DBs and Jumping Java

Some news clips from projects that I find fascinating: The anticipated 2.3.0 cleanup release of SpatialLite is now out. Building on the highly efficient, blazing fast, feature-rich and highly-embeddable SQLLite , this geodb data store and engine might be a good option to address the call in the Shapefile 2.0 manifesto. I agree with the thoughts in the manifesto (I'm sick of managing many little files) and I'm all about keeping things simple, focused and efficient. So I'm going to watch this project with interest especially since spatial support in MySQL is going no where fast.

Also, after a long wait, Open JUMP is out with a new version. We dabbled with this years ago but got sick of Java-based desktop apps. In fact, recently we are finally getting on the .Net bandwagon and are working with MapWindows. Though I guess we are using Java a little on the desktop through our CUPSS [1][2] [3] project (it uses Trolltech/Nokia Jambi that wraps Qt with Java). We generally have had to get away from supporting systems other than Windows for a variety of reasons :-( Hopefully we'll be able to get back into the platform-agnostic game soon.

Tuesday, April 7, 2009

Wednesday, April 1, 2009

Move to the cloud

For a group like mine that writes software for modeling and other computationally intensive code from scratch, moving code from early 2000-era single CPU approaches to SMP approaches (or even clustering) is a painful but probably required undertaking. We've discussed it, but the business cases (or the requests in the way of $$) have not materialized so we didn't fix what wasn't broken.

But, I wonder if we should just skip all of this and move the model to take advantage of the flexibility of cloud computing. Enterprise providers are convinced Cloud will scratch many itches and announcements like this ( [1] [2] [3]) Sun and IBM's investment in Cloud, and Cisco's leap of faith into building server fabrics because, "[cloud computing] is the future of the data center. It will evolve into clouds and change business models forever" make the question compelling.

For us in the niche world, we have to ask does the investment make sense? Where does Cloud stop being useful? When is it best used? When should you not use it?