Assuring Users When Closed Software Becomes Open?
joeldg asks: "I just recently decided to go open source with a project I have been doing for some time. After initially going open source I have had an avalanche of questions from users about what 'Open Source' means and how it will affect them. Many are scared of the implications and the broad new sweeping changes others could make in the project. My question is how do you alleviate the fears of over 5,000 dedicated users and get them to accept the idea of the project going open source and also keep some track of the project so that you can direct the current userbase to new sites running the code?"
I think that it probably important to let them know that even though the source is now available, not just anybody will be allowed to access the "official" version. You are still the gatekeeper, and what gets done to the code goes through first.
When I want your opinion I will beat it out of you.
Due to overwhelming requests and inquiries about specialized customization and personal control over the boards, we've decided to go one step further with our goal to do more than everyone else out there: Open Source
Maybe, if that's what you are planning to do, you should explain clearly that you or - qboard.org - will always be the source for downloading "your version" and that qboard being open source only makes your possibilities for providing new and consistent features with potentially less effort. Explain, that you will still keep control of this one release althought there might be others as well - which might be suitable for some. You are just opening new possibilities, this should not be anything to fear of - if everything looks and is under control.
if you have a lot of questions, start a FAQ and refer folks to it.. it's been suggested b4 and it's a good suggestion.
:) also you will expect comment from your particular community on howto improve your code.
my subject line asks a decent question tho'.. and I'm guessing that's what most of your questions get back to.
From a customer's point of view, open source means several things:
It is a quality assurance. You're obviously confident enough to show the world how good your code is
It is additional coding resource to get jobs done quicker.
It is control for your customer in that they can use your code as a toolkit to build features that they would otherwise not be available.
It doesn't remove you as the project controller and you still maintain the same control over the released code as before.
Note that I am assuming that although the qboard project is winding down, you or your team will still be 'controlling' qboard's path?