Last post Oct 07, 2005 12:10 AM by MikeSchinkel
Sep 19, 2005 08:45 PM|worldspawn|LINK
Oct 07, 2005 12:10 AM|MikeSchinkel|LINK
What are your plans for this? Are you going to make it an open-source project on SourceForge.net?
Rather than just giving it away via a post on a forum, why not try and create an actual open-source project on SourceForge or similar, and encourage a few other people to join you in maintaining it? I love to see developers creating reusable software
for others to use, but it's only good for most of the developers who might use it if they can depend on it to have bugs fixed and enhancements made as most don't have the time and many don't have the skill to do so.
Another issue is licensing. Since you don't include a license with your ZIP file, many potential users would be banned by their companies from using it. I'd suggest you include a license with it, such as the
BSD License. Of course, including a BSD license will by definition make it open-source. (If you use the
GPL License many people will be unable to use it too, because of GPL's viral aspects.)
Otherwise it's better for developers to avoid free software like this, and to seek out existing and supported commercial or open-source components. IMO, it's better to have fewer components doing the same thing in the world than to have more of them since
each one requires maintenance, but more importantly, each component needs to be learned by a group of developers.
Think about how much effort has gone into learn ASP.NET DataGrid, for example! It's a lot like spoken languages; if the nations of the world each spoke a different language and only one language, it would be practically impossible to interact meaningfully
between Nations! Ignoring the lost culture aspects, having everyone on the web learn English really helps foster broader communication, and greatly reduces the cost of said communication (imagine running a business in Canada and being force by law to publish
everything in English and French! Sorry for French speakers, but it significantly increases costs.)
Same is true globally of the proliferation of components all doing the same thing, but you don't really have the loss of culture issues with software components. So fewer components doing the same thing = better. If you are going to give away your components,
it should be incumbant upon you to make sure a significant percentage of .NET developers actually use it. :)
BTW, as I was writing this, I realize I am coming across rather harsh, but I don't mean to be. I have been thinking about these issues for several years now and plan at least one really big
blog post on the subject in the future. If the paragraphs above sounds harsh its because it's hard to get the point across in a few paragraphs.
So please understand I'm only making some suggestions based on issues that have become clear to me over the past several years, I don't mean to jump on you for your generousity.