You see though pingme, I think we've addressed all of your concerns multiple times. And if you can't accept what Rickard and I and the rest of the developers say, then I don't know how much this is about the sale as it is about you not trusting us
Smarty concern is very simple. people have been happy the way Rick and team handled and supported users and development. With limited information of ownership change, people are bit worried about its future path. While there are assurances from the original team, the way acquisition was communicated is probably causing a panic.
I wouldn't say there's limited information, I'd say there's quite a bit. We're certainly not hiding anything from you guys.
additionally committing that Rick will pork out if necessary adds the uncertainty.
If I'm understanding you correctly, you're saying that Rickard making clear that he will fork the code if it's, for example, taken non-free is a BAD thing? You'll have to explain that one to me
If as a user, I am using punbb, today I don't know, if next versions will be available for free? will it become a paid software? will developers really continue with same dedication? (while assurances are there), and Qs like these are not answered.
Yes, they are. Unless, of course, you choose to not trust our word, which as I said is an issue entirely separate from the sale
But, to clarify for anyone reading:
- PunBB will remain free thanks to the GPL.
- In the words of Rickard, "If push comes to shove, I'll fork it myself!"
- We're still developing with even more dedication than before (excluding periods of real life peeking through, which I had for the past couple weeks).
May be some one from the new company coming to these forums and announcing their vision would have helped to clear many of these concerns. Keeping everything under wraps is what creating these ripples, confusion and slowly loosing confidence.
I don't know that they have fully decided what their ultimate, final plans are for PunBB. However, as we keep pointing out, it doesn't really matter what they decide. PunBB is still PunBB. It is released under the GPL. The code can not be retroactively closed. The code can be forked. Thus, if they make a decision like "abolish free PunBB," the code will be forked.
To give an excellent way of communicating sudden changes I suggest you go thro http://thevbgeek.com If Rick would have communicated in similar fashion taking the community in full confidence, people would have welcomed it with open mind.
If I'm reading what you linked properly, I have to disagree with you. I think we've been at least as open as that (and the outcome has been more positive)
At the site you linked, the person explained that he would be stopping development and support to focus on a family business in crisis.
The first post was August 5th and explained the very basics, saying rather unclearly "As such, I will be absent from the site for the unforeseeable future, leaving me unable to support and develop. This crisis could potentially be rectified by as soon as the end of next week, however it could also take substantially longer."
The next post was August 19th, two weeks later, and provided little information other than "there's still a problem, and I don't know how exactly you guys will be supported, but I'm thinking about it, and I'll refund some money to some people who I can't support"
The NEXT post is a month later and simply says "the problem is fixed but I can't support you guys anymore, I still haven't decided exactly how you will be supported"
I should note, I do think the issue was handled well on the site given the circumstances the person was working under, I just don't think it stands as a shining example of what to do. Ideally, he would have found someone else to support the code for him much quicker: in fact, he probably could have paid someone to do it. I also find it interesting that you compared the sale to a crisis when in reality it's just the opposite.