I am a little late in reporting this, but I hadn’t realized the problem until I had to maintain an older project that used Log4Net 1.2.8. I upgraded it to log4net 1.2.10 and noticed it stopped working. I then found this comment in the log4net mailing list archives.
There were a number of breaking changes in 1.2.9
In your config file “log4net.spi.LevelEvaluator” needs to be updated to “log4net.Core.LevelEvaluator”.
I hope changes that would break existing config files are far and few between.
This story from Boing Boing just cracks me up. Apparently monkeys have been harassing passengers of India’s Delhi Metro. This has become such a problem that they have had to hire some langurs (a fierce looking primate) along with a langur wrangler to scare away the monkeys. Here is a description of one such incident.
In that incident, a monkey boarded a train at the underground Chawri Bazaar station and reportedly scared passengers by scowling at them for three stops. It then disembarked at Civil Lines station. Passengers had to be moved to another car while staff chased the dexterous creature, causing delays.
Bad monkey! Bad monkey!
As the Simpsons showed us, the monkeys are trying to take over the world. The image above is from Family Guy.
If you read this blog outside of an aggregator, you might notice a few minor new tweaks. I am dogfooding Subtext 1.9 which runs on ASP.NET 2.0. We are very close to preparing a release, so I figured I would beta test this one on my own blog and see if everything works well.
A couple of new things you might notice is that there is now a simple search field on the left hand sidebar that displays its results in an overlaying div. Also, when you view an individual post, there are links to the next and previous post. I have also added gravatar support to the comments.
It took me a while to warm up to the idea, but I really like the gravatars. I have participated in many various message boards and sites (such as flickr) in which users choose an avatar to represent themselves. It is a small thing, but adds to the fun and identity for the visually focused. However in most cases, you have to set up a separate avatar for each site.
With gravatars, you register an avatar with their site and in any system that supports it, your avatar is displayed when you supply your email address to the software. Subtext takes your email address, creates a one-way MD5 hash of it, and then requests your gravatar from gravatar.com. If none is found, then a default placeholder is displayed. I will post a comment to this post as a demonstration.
Jeff “The CodingHorror” Atwood takes issue with the idea that software developers have any moral obligation to contribute to Open Source projects. And you know what? I agree. However I do take issue with his conclusion as well as some of the points that he makes in an attempt to bolster his argument.
The whole point of open source– the reason any open source project exists– is to save us time. To keep us from rewriting the same software over and over.
It’s exactly what open source is about: maximum benefit, minimum effort.
Well no. Not really. Back in the day, software was just an afterthought provided by hardware companies to complement and run their hardware. This software was widely shared freely, until companies began to impose restrictions with licensing agreements and started protecting their code by hiding the source.
Many developers grew frustrated as they lost control over their working environment and were unable to modify the programs to fit their needs. Hence Richard Stallman started the Free Software movement, hoping to give users the right to:
- run the program, for any purpose.
- modify the program to suit their needs. (To make this freedom effective in practice, they must have access to the source code, since making changes in a program without having the source code is exceedingly difficult.) They must have the freedom to redistribute copies, either gratis or for a fee.
- redistribute copies, either gratis or free.
- distribute modified versions of the program, so that the community can benefit from your improvements.
Thus originally, the whole point of open source was to provide users the freedom to regain control over software in order to get their jobs done.
Of course later, the movement split into the Free Software movement which was absolutist about the freedom issue, and the Open Source movement which sought to be more pragmatic and provide a business case for open source software. Open Source focuses on the intrinsic benefit of having communities of developers improving a software codebase.
Enough with the history lesson and please, I do know that I glossed over that with a big hand wave. That is called a rough history.
The highest compliment you can pay any piece of open source software is to simply use it, because it’s worth using. The more you use it, the more that open source project becomes a part of the fabric of your life, your organization, and ultimately the world.
Isn’t that the greatest contribution of all?
If I read a book you wrote because I found it worth reading, have I made a contribution? Hardly! Apart from the contribution I paid at Amazon.com for the pleasure of reading the book, I am merely using something worth using. That is not a contribution, it is just good sense.
Now if I post a positive review on my blog, that would be a contribution.
The way I see it, Jeff’s right, there is no moral obligation to contribute to an Open Source project. However I am not quite sure the puppy analogy he mentions suggests that. At the risk of yet another bad analogy, allow me to propose one that works for me. I think of Open Source software as being like a nice set of flowers in a common space such as a courtyard. Nobody that lives around the common space owns the flowers, yet they all enjoy the presense of the flowers.
Fortunately, one or two volunteers tend to the flowers and the flowers thrive. Some flowers seem to do fine with very little care, others require lots of care. But everybody benefits and there is no cost, nor moral obligation to others to contribute to the upkeep of the flowers.
However, should the caretakers decide to stop tending to the flowers, the others certainly have no right to complain to the caretakers. And while it is true that in some cases, others may take up the slack and tend to the flowers, or other flowers might grow as replacements, if nobody takes up the cause, or if the new flowers are simply weeds, then everybody loses out. Including those who had the time, means, and even desire to help with the flowers, but just never thought to because someone else was taking care of it.
So while I do not think contributing to Open Source software is a moral obligation, I do think it is a worthy practical consideration. No offense to my homie, but I think it is Jeff who misunderstands the economics of open source. Minimum effort does not equate to free in cost.
For example, should you begin to rely more and more on some piece of Open Source software, consider the effort to replace the software (which might tack on a monetary cost for a proprietary replacement) and learn a new toolkit if development of the software dies out. Hardly a minimal effort.
True, a contribution in this situation is no guarantee that a project will succeed. But doesn’t the same risk apply to purchasing proprietary software? It certainly applied to contributing to a political party (if you were a Democrat in the last couple of elections).
And while it may be infeasible for a large portion of the audience (Jeff pulls the figure 99% out of his rear, which is probably close to the truth) to contribute the extravagance of a bug fix, for the remainder for whom it is feasible, it is certainly worth considering. Every contribution not only helps in a small way to keep the project viable, but it improves the software for your own purposes. It is an entirely selfish benefit.
So again, please do not confuse exhortations to contribute to Open Source as a claim for moral obligation. I honestly believe that those who contribute will benefit from the contribution as much as the recipients of the contribution, which is why I am such a big proponent for contributing.
If you have the means, why not water the flowers for a bit? There are many forms of contributing to an open source project. I list several on the Subtext contribution web page.
One thing I love about my soccer league is that they have a kick butt website. The design isn’t much to look at, but the site is chock full of useful information both current and historical.
For example, you can see how my team (Westside Rovers) did last season. Tied for fourth isn’t such a bad showing for our first season in the league, but check out the GF and GA column.
Ouch! That is 24 goals we scored while there were 54 goals scored against us in fourteen games. That means we scored an average of 1.7 goals per game, while being scored on an average of 3.9 goals a game. When we got beat, we really got beat. Notice that LA Blues, the lead leaders scored 19 goals on us. We played them twice. Double ouch!
There’s no lesson here other than sometimes, you really are better off not knowing the detailed stats. At least we have an easy target to beat for the upcoming season.
The reason for the disparity becomes apparent when you read the following blurb on the front page.
FORMER PROFESSIONAL PLAYERS ARE PLAYING ON SOME OF OUR TEAMS: Some of the teams in our league have former professional players from the Major League Soccer (MLS) in the United States and from Professional Teams from around the world. One team even has a former World Cup Champion from France 1998 on its squad. Thus the level of play can be very high at times. Come, watch and enjoy the competitive level of play.
None of those players are on our team.
In really bad news, we had a pre-season friendly this past Saturday against another team in the league. They had a new player who was trying out for the team who made a vicious sliding tackle (no slide tackles allowed in our league due to the fields policies) on my teammate, breaking his tibia and fibia. The sound of the contact made a sickeningly loud crack! and bent his leg in an unsightly manner. It may take a while, but I hope he has a speedy recovery. Meanwhile, I am looking into better health insurance.
In a triumphant return after about three months of not blogging, Barry “idunno.org” Dorrans has published an HttpModule for modifying custom HTTP headers in response to a throw away comment by Scott Hanselman in his post on P3P requests.
The nice thing about Barry’s module is that it is much widely general and applicable than just for P3P headers.
This is a configurable HttpModule, allowing you to use web.config to specify what headers and values you wish added to requests.
So if you need tight control over your HTTP headers, this is the module for you.
UPDATE: I long ago stopped supporting Captain Hook. This is a dead project.
I recently introduced an internal tool for writing Subversion Hooks that we developed for internal use at VelocIT. We made the source code and binaries available to the general public and there was enough interest (hey, it only takes two or three and I’m sold!) that we decided to make an Open Source project out of it hosted on SourceForge. This is our company’s first Open Source project and we hope many will find it useful.
I thought about using CodePlex to try it out, but in this particular case I figured it would be less of a pain to host it in a Subversion repository since this is a tool for Subversion users after all.
At a Glance
- Mailing List
- captainhook-devs at lists dot sourceforge dot net Commits Mailing List
- captainhook-commits at lists dot sourceforge dot net Subversion Repository
- https://svn.sourceforge.net/svnroot/captainhook/trunk License
The mailing list might not be ready at the time you read this If you
would like to have Subversion commit access, please join the mailing
list and send an email to the list with your SourceForge username.
Please only request access if you are planning to work on it in the next
few months. I will probably cap it after some point just to keep the
process sane (not that I am expecting a flood of requests, but you never
And of course CaptainHook is licensed as BSD. Any code contributions should have their copyright for the contribution assigned to VelocIT, the maintainer of the project (an informal email ackowledgement is sufficient). As I mentioned before, assigning copyright when contributing is a standard operating procedure and nothing insidious. You do not lose your own rights to use the code elsewhere since the code is licensed as BSD.
Update Corrected my pop-culture iconography mix up.
Thomas Eyde brings up a great point in the comments section of Scott Hanselman’s post about SandCastle and the death of NDoc.
It’s sad to see good projects die, especially when programmer support is a main reason.
But on the other side, it’s not that easy to join these projects. How many of them advertise? How often do we see “Developers wanted on [your favorite project]”?
I think these projects must advertise what they need. Do they need C++ expertise? Java? C#? UI design? How do we know what to do? Where are the tasks listed? How do we assign to them?
Open Source project that are lacking in developer support probably need to tear off a page from the corporate playbook and be a bit more savvy about recruiting developers. I often hear developers wistfully day dreaming that if they just open source their pet project, legions of developers will take up the banner and join in.
Ha! Hardly! Recruitment is necessary and fundamental to an OS project. So much so that SourceForge has a tab dedicated to the topic in the admin section of a project.
Seeking skilled developers (and people who are interested in the goals of your project) is one of the most important activities performed by project administrators.
But by no means limit yourself to SourceForge. Consider putting a free ad in CraigsList or in the forums of other developer communities.
The second comment on Scott’s post by Martin Bennedik questions the donation model.
But I don’t understand the donation model. Who is supposed to donate the $5? Say I am an employee working for my company, and I am using NDoc. Should I donate the $5 personally? Or should I ask my company to pay the 5$?
When I wrote my original challenge to donate to Open Source projects, I wanted to avoid a
Suzanne Summers Sally Struthers For just five dollars you can feed
the kids of those poor Open Source Developers plea. As Scott points
out, monetary contributions are far down on the totem pole of
contributions. For the subtext project, I added a Contribution
that discusses several ways in which developers contribute should they
feel the desire.
I think it is the project leader’s job to make the barrier to contribution as low as possible.
UPDATE: Sorry, but this site appears to be down now. I’ll try to find the tools and upload them elsewhere.
One thing in common with these little tools and utilities is that we are hosting them on our new company tools site, http://tools.veloc-it.com/.
These tools are little scripts and apps that we use internally to increase our efficiency. Many of them relieve us from the drudgery of boring repetitive tasks. Quite likely, these are the tools that many of you would write yourself if you only had the time (some of them you probably already have written. I swear we did not plagiarize you). We hope you find them useful. There aren’t that many now, but over time we will add to the catalog.
You might be wondering, if these tools make us more efficient, potentially giving us a competitive advantage, why are we giving them away? Good question. I hadn’t thought of that. Jon! Take down the site!
Well the truth of the matter is that it is a way for us to show off how amazingly smart we are so we can get more clients, fame, and adulation.
Uhhh… Ok. Maybe not.
Let’s be realistic. Decision makers and CEOs are not dinking around the web looking for an Abstract Boilerplate HttpHandler.
Not only that, most of what we post here is not supremely innovative rocket science and going to make someone rich. If we had such a tool, you think I’d be blogging about software tools? No way man! I’d be regaling you with stories about the funny looking crab that walked up to the porch of my immense beach house in Hawaii. But I digress.
Part of the reason is certainly to increase exposure of our company, as I know we do some kick-butt work. Over time, we hope that our site will reflect the quality of the work we do for our clients. But our primary reason is the same reason we’ve been posting such tools even before there was a VelocIT. We enjoy helping other developers benefit from what we’ve learned. Likewise, we appreciate the tools and learning shared by other developers that have benefitted us. In the end, I think this sharing elevates the entire profession.
Recently we had a heat wave in California. My air conditioner broke because, I assume, it is not designed to operate in hot weather. That was the bad news. The good news is that I solved the problems in the Middle East. Allow me to explain.
Please, allow him.
UPDATE: CaptainHook is now an Open Source project on SourceForge.
One potent tool for team communications on a project, especially one with distributed developers, is the simple commit email. Setting up Subversion to send out an email when a developer commits changes to the repository is fairly easy. The Subversion distribution comes with a PERL script (commit-email.pl) that works quite well for this purpose.
At least it did for me until we changed mail servers to one that did not allow SMTP relay. Try as I might, I could not get the script to authenticate with our SMTP credentials. I downloaded various other PERL modules that were supposed to be able to authenticate with no luck. I read the RFC 2554 (seat of your pants reading) and authenticated manually via telnet and compared that to the SMTP logs for the components and realized that for some reasons, these scripts were doing the wrong thing.
That’s when it occurred to me that I could probably write a simple .NET app in a minute that could send out the commit email. As I got started though, I realized that it might be nice to write something that would allow others to easily handle other Subversion hooks. Hence CaptainHook was born.
Hooks in Subversion are scripts (or executables) that are triggered by an event in the subversion version control life cycle. The following are the five hooks supported by Subversion. For a short discussion on how to install the hooks, read this post by Pete Freitag.
Note that (except for
return value of the script controls whether or not the commit should
continue. If the script returns 0, the commit continues. If it returns
anything other than 0, the commit is stopped.
|Script Name||Triggered By||Arguments||Notes|
||Before the commit transaction starts||Repository Path and username||Can be used for repository access control.|
||After the commit transaction starts but before the transaction is commited||Repository Path and transaction name||Often used to validate a commit such as checking for a non-empty log message.|
||After the commit transaction completes||Repository Path and the revision number of the commit||Can be used to send emails or backup repository.|
||Before a revision property is changed||Repository Path, Revision, Username, name of the property||Revision Property’s new value is passed into standard input. Can be used to check permission.|
||After a revision property is changed||Repository Path, Revision, Username, name of the property||Can be used to email or backup these changes.|
My goal was to provide a nice strongly typed interface and a few useful service methods for accessing Subversion. Thus handling a Subversion hook is as easy as implementing an abstract base class and calling methods on a Subversion wrapper interface.
To setup CaptainHook, simply unzip the exe file and its related
assemblies into the
hooks folder on your Subversion server. The
distribution includes a
plugins directory with a single plugin already
there. The plugins directory is where CaptainHook looks for other hook
handlers. Be sure to update the config file with settings that match
The next step is to rename the .tmpl file for the hook events you wish
CaptainHook to handle. CaptainHook comes with some sample batch files
you can use instead, one for each hook. Just copy the ones you want to
use from the
SampleBatchFiles directory into the
Now when a commit occurs, Subversion will call the
file which in turn calls CaptainHook with the
post-commit flag. This
flag indicates to CaptainHook which plugins to load. CaptainHook then
looks in the
plugins directory for any assemblies with types that
PostCommitHook abstract class. It then instantiates
instances of these types and calls the
Initialize method and then the
Note that for the time being, CaptainHook is an executable so it has to incur the cost of searching the plugin assemblies every time which may seem like overkill (and it is). However my focus was on the model for CaptainHook. At some point it will evolve to use remoting as a Server Activated Singleton or it may become a Windows Service which fit the model better. Either way, there are ways in which we can incur this cost only once. But for now, this will do and performs well enough.
Assemblies and Classes
Captain hook contains serveral assemblies.
|CaptainHook||This is the main console exe and is the starting point for the application.|
|CaptainHook.Interfaces||Contains the interface definitions. This is the only assembly you need to reference when writing a plugin.|
|CaptainHook.SubversionWrapper||This is potentially useful as a stand-alone library. It includes the
Let me know if you find this useful. It is definitely a work in progress
as not every command is implemented in the
If it turns out that several people find this useful and want to
contribute to the code, I am willing to put the code on
The zip archive contains both the source code and the binaries. I also compiled an x64 version of the exe for you 64bit kids.
My company’s official 1 year birthday was yesterday, and we didn’t even notice. I guess it is a good thing that we are so busy that we fail to notice our own birthday passing us by.
We’ve had a rocky start which involves some interesting stories that I will tell someday when we are far enough removed from them. But things are starting to hum along much better now.
My goodness. Today is Open Source News Day for me.
I just read the sad news that Kevin Downs, the leader of the NDoc project, announced that NDoc 2 Is Officially Dead. NDoc is a wonderfully useful tool for generating nicely formatted CHM and HTML documentation from XML comments within your source code.
What is really troubling about the news is the attitude by some members of the community that was a contributing factor to Kevin calling it quits.
As some of you are aware, there are some in the community who believe that a .Net 2.0 compatible release was theirs by-right and that I should be moving faster – despite the fact that I am but one man working in his spare time…
This came to head in the last week; I have been subjected to an automated mail-bomb attack on both my public mail addresses and the ndoc2 mailing list address. These mails have been extremely offensive and resulted in my ISP temporarily suspending my account because of the traffic volume. This incident has been reported to the local authorities, although I am highly doubtful they will be able to do anything about it.
This has was the ‘last-straw’ and has convinced me that I should withdraw from the community; I’m not prepared to have myself and my family threatened by some lunatic!
I cannot understand the mentality of someone who demands for developers to hurry up and release a new version of a free software product. If you are in such dire need of the new version, why not hurry up and contribute?
Having said that, I feel particularly bad that I never contributed to NDoc, yet enjoyed so much use out of it. As the manager of an open source project myself, I understand the inherent difficulty in generating interest and contributions from the community at large.
In general, I try to contribute to Open Source projects when I can. I have contributed a tiny bit of money and some documentation and code to RSS Bandit, I bought a domain name for MbUnit, and of course I contribute to Subtext. But I realized today that I am quite haphazard in how I contribute to useful open source projects. I contribute to some when the mood strikes, but not others.
So I offer the following challenge. First, ask yourself these two questions:
- How much money do I save because of Open Source Software?
- Considering how many people spend three bucks for a useless ring tone, is a single dollar too much to contribute to a useful Open Source project?
So let’s ban together and declare today, July 26, 2006, Contribute To Open Source Day. Look at the open source software you use and consider making a tiny contribution to the project if you find it useful. The contribution could be a small monetary contribution such as a buck (or five). Even more valuable is contributing a single bug fix. If you want to contribute to Subtext, consider writing a Unit Test to cover a case that isn’t tested. What better way to learn about writing unit tests?
Gee, using GIMP alone saves me a few hundred that I would otherwise pay for Photoshop. My goal now is to at least contribute something everytime I download a new open source product, whether it be some useful bug reports or feedback, a bug fix, a buck…anything. Just as long as it is something.
I will check back with you next year on July 26 and remind you again to consider contributing. It is worth it.
It is a common notion that there is a lot of ambiguity and disagreement around the term Open Source. While that has been true in the past, I believe that there is much more consensus now because the term has been refined and the taxonomy of software has been improved. Certainly there are still arguments, but I believe for the most part, there is a detente.
Much of the past ambiguity surrounded the philosophical disagreements between those who felt software should be free as in liberty, not only free as in beer. This view essentially holds that derivative works of Free Software must themselves be open and Free. Richard Stallman (who does not want to be associated with the term Open Source) embodies this philosophy, as does the GPL license.
The opposition felt that we should not place such restrictions on software to consider it Open Source.
While this disagreement may have been heated at times, in many ways the core argument around the term Open Source has been resolved by differentiating between Free Software and Open Source. There are now sites dedicated to the Free Software Definition and the Open Source Definition to promote these terms.
While there are certainly disagreements between the two camps on how software should be licensed, in many ways the camps are compatible. When looking specifically at the licenses, it is helpful to think of Open Source as a superset of Free Software. Free Software is necessarily Open Source, but an Open Source is not necessarily Free Software because a Free Software license is in general as restrictive or more restrictive than an Open Source license.
Likewise a Source Available is not necessarily Open Source, but Open Source is necessarily Source Available.
In my hope to be a neologist, I will push the term Source Available (I like it better than my earlier term Code Available) and hope it catches on. If someone coined it before me, at least I hope the claim to fame of making it popular. ;)
I have written on the topic of Open Source software before if you are interested.
The Subtext team is currently furiously working to prepare the Subtext 1.9 Daedelus release for your blogging enjoyment. Subtext 1.9 will run on ASP.NET 2.0 in Medium trust and contain a few new goodies, though those goodies have been kept to a minimum as the goal was to create a straight port to ASP.NET 2.0. The release date has not been set since my day job and another minor side project has been keeping me busy. My hope is to release somewhere around the first or second week of August.
In the meanwhile, we found the need to respond to some minor bugs in the last release. Thus today we release Subtext 1.5.2 which still runs on ASP.NET 1.1. This is a very minor release, so probably not necessary unless you are affected by one of the bugs listed below.
Probably the most annoying bug was one that caused problems when attempting to create a post using the web-based admin tool. This was due to a misconfiguration on my part of our ReverseDOS configuration file.
Here are the release notes.
Version 1.5.2 - Bugfix Release - BUG:  Fixed a constraint on the subtext_Config.BlogGroup in the import script. - BUG:  The User Name Is Being Saved as the Title - BUG:  Change ReverseDOS.config - turn on isRegex="true" flag for Trusted Addresses. - BUG:  Fixed bug in which permissions were not applied to [Subtext_GetEntry_PreviousNext] stored procedure.
The number of code contributions to Subtext has been increasing lately which is wonderful! Thanks for sticking with us and we really appreciate the contributions. Keep it up!
Dave Burke makes the interesting claim that Community Server is an open source application. Whether this is true or not of course depends on your definition of the term Open Source. Here is Dave’s definition.
To talk about Community Server and Open Source we should start with a baseline definition of an Open Source application: All of the source code is available. For free.
But is that all there is to Open Source, access to the code? Is mere access to the code the fairy dust that has inspired such a passionate movement in the software community?
Certainly the term Open Source has had a history of ambiguity, so that definition might contain some validity. But I do not think that is the commonly agreed upon minimal criteria for something to be considered Open Source.
Open source isn’t just about whether the source code is available, it is all about the license to the source code.
The definition starts with the following introduction and then lists serveral criteria for open source software.
Open source doesn’t just mean access to the source code. The distribution terms of open-source software must comply with the following criteria:
The first criteria listed is Free Redistribution which states…
The license shall not restrict any party from selling or giving away the software as a component of an aggregate software distribution containing programs from several different sources. The license shall not require a royalty or other fee for such sale.
Contrast this to the Community Server license agreement 2.0 which states…
3g. Distribution. You may not distribute this product, or any portion thereof, or any derived work thereof, to anyone outside your organization. You are not allowed to combine or distribute the Software with other software that is licensed under terms that seek to require that the Software (or any intellectual propertyin it) be provided in source code form, licensed to others to allow the creation or distribution of derivative works, or distributed without charge.
For many people, the terms of the Community Server license might not be a problem. They are not terribly restrictive. If you plan to use Community Server under the community license your only requirement is to display the Powered By Community Server logo on every page of the site that uses Community Server.
However for many others, these terms are restrictive enough. For example, suppose you don’t like the way development is progressing on Community Server. You cannot fork the code base and start a new project based on the source code. Although a fork may seem like a bad thing, Karl Fogel points out in 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.
Not every open source license is created equal as I pointed out in my guide to Open Source Software Licensing. For example, under the BSD license in which Subtext is licensed, you and I are free to create a commercial derivative version of Subtext and keep your changes to the code closed source and proprietary. That’s right. If you wanted to (and had the ability to), you could package up the Subtext source code in its entirety and start selling it as a packaged product.
Note that you can’t turn around and claim that you have the copyright to the Subtext code. You would only have copyright to your changes to the code. Pretty much the only restriction is that the original license must be retained with with the code, but it does not have to be publicly visible in your site (such as in an about box).
In contrast, with a GPL Licensed project, you could start selling it, but you couldn’t keep your changes closed source without violating the terms of the license.
In the end, I think we need to agree on a term for unique products such as Community Server in which the source code is freely available, but does not fit the definition of an open source product. I suggest the term Source Available.
Please do not misconstrue this as an attack on Community Server or its licensing. I have met both Scott Watermasysk and Rob Howard and they are both very smart and capable leaders of a strong company. Community Server is a great product and deserves the recognition it gets. I am not a zealot and have no beef with closed source products. Certainly my livelihood depends on many such products.
At the same time, I am passionate about Open Source software and it is important to me to help keep the distinctions clear and educate others on what open source software is and the value it provides.
Anyone have recommendations for Content Management systems for ASP.NET (ideally 2.0) that can handle a lot of traffic and allow for extremely customized site design? I am curious about which products are out there other than DotNetNuke and Microsoft Content Management Server.
Ideally this is something that you have implemented successfully on a project.
Now is this really necessary? Don’t geeks have enough troubles with the ladies without these serious groaners to encourage them?
So naturally, I must respond with my own groaners. Warning, not safe for … well really anyone who enjoys humor that is actually humorous.
- You can handle my event any time
- What’s your sign? I’m unsigned and I do byte. Rowr.
- I’d like to get
Interlockedwith you and see what increments.
- Them hips must be newing up objects real fast because you are putting pressure on my heap.
- The moment I saw you I nearly overflowed my stack.
- Care to reference my private member?
- You Auto-Complete Me.
Creating .NET pickup lines are a bit like opening a strip bar in antartica. Who are you gonna use ’em on?
My response is that these are not for us geeks. It is for those who wish to land a geek.
My company has a small business account at Washington Mutual. I handle a lot of our banking via the online banking website. For several months now, their online banking website has been an absolute pain to use. After logging in I would be unable to access features that are kind of important such as…oh…I don’t know… the register and bill pay!
What was weird is that I would click on the link and would get some error message about calling technical support or an access denied message. But click on it again once (or 10 times) and it would finally work. Right now, the change password feature doesn?t appear to work.
Over time I would send messages to customer service and never get a satisfying response. Finally, Akumi offered to draft up a letter to the President of WAMU after one particularly frustrating bout with the site in which I was fuming.
Fast forward several days and I get a call from a representative who
actually knows something about what is going on with the site and
doesn’t blame me or my account. He is helpful and gives me his direct
line. As he is walking me through some steps, I notice that some of the
URLs end with
.aspx. Oh, that is a promising sign!
I mention this to the rep because I never noticed it before. Most of the site runs on classic legacy ASP. The rep informs me that this weekend they have a planned upgrade to ASP.NET. That is definitely a step in the right direction!