Assuring Users When Closed Software Becomes Open?

Posted by Cliff on Tuesday November 12, 2002 @06:37PM from the keeping-them-happy dept.

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?"

1 of 22 comments (clear)

Min score:

Reason:

Sort:

Depending on your licence.. by arcadum · 2002-11-12 18:50 · Score: 0, Redundant

It means you have released your soucre and they (or anyone) can do with it as they please [BSD], or they must keep the source open to their customers while doing with it what they please [GPL].