On open source and naming conventions…

Thursday, July 27, 2006 8:57 PM

**First on naming conventions…**Recently a series of posts caught my eye ( via Bil) on Coding in an Igloo that went on and on about code naming conventions. This guy looked at the various naming options and conventions most of us use and then gave his $.02 on what he used and why. he covered SQL Server objects, UI controls, classes, interfaces, properties, fields, local variables, methods, etc… quite a good read. I’ve never worked somewhere that had a set in stone coding style guide, but I’ve tried to create my own guide to follow. A while back I stumbled across IDesign’s C# Coding Standard and found my style fell in line pretty close to their recommendations, not to mention finding a few additional items that I picked up. So I guess if there’s anything I officially follow, it’s theirs.

Anyway, if you’re interested in reading the series on Coding in an Igloo, check out his “TOC” post with links to each post in the series:

» Code Naming Conventions, The Series

On open source… Earlier today I noticed a few posts on open source recently syndicated on Phil Haack’s blog. He first questioned if Community Server is really open source, as Dave recently stated. Before reading Phil’s post, I always considered a project who’s source code was available fell into the open source classification… but now I think there’s definately more to it. Phil makes the point, very well I add, that it’s not enough to give the source away to call something open source; your license must also allow for people to fork the code. He cites Karl Fogel’s point (from his book Producing Open Source Software - How to Run a Successful Free Software Project) that:

…the threat of a fork is what keeps the leader(s) of an open source project from being tyrannical. It is this threat of a fork that motivates and requires open source projects to be well run.

» Is Community Server Open Source?

Good point Phil!

Also, yesterday seems to be the official day NDoc died… at least that’s how just about everyone is stating it (via everyone). So the brains behind the outfit is quitting… ok… I understand that, and it’s his call. But it’s an open source project… so why is it dead? Can’t ~anyone~ else pick it up? Heck, the guy behind it, Kevin Downs, even offered up control of the SourceForge project to anyone who’s interested! Dead… seems a bit premature… and with a tool that’s so widely used and popular, I don’t think it’s dead,

comments powered by Disqus