@TideSDK - I've been following this project for quite some time, hoping that it would succeed. With the updates from yesterday, however, I have to write it off as dead.
For months, the only communication from the team has consisted of vague hints at a major rewrite, big updates, fixes for the numerous problems that plague the current version. As time has passed, the excuses for the delays and lack of communication have piled up, while the status updates and team communication with the public have dwindled to almost nothing.
http://www.tidesdk.org/blog/2013/04/11/tidesdk-in-numbers/
it's more excuses. This time, it's money that's the problem, and the reason the project is not meeting it's promised releases is a lack of donations.
The post gathered a lot of attention, and sparked a number of pointed, yet insightful, comments raising legitimate concerns about the state of the project, the lack of communication, and the general attitudes of the development team. At first, a few responses were given, but they dodged the questions raised and only offered more dismissive excuses unrelated to the complaints.
Now, this morning, I see that the comments have been removed entirely.
(I've mirrored a screenshot of the removed comments above)
I hate to say it, but in it's current state I maintain little hope for this formerly promising project. Some big changes in how the project is run are needed to keep this project alive.
A few of the changes that I would need to see are:
Restore the comments. Sure, some of what they have to say is harsh, but they also raise legitimate concerns and deserve a real response. If nothing else, this would be a great way to show a commitment to change.
Develop in the open. There have been almost no updates in the public repository for months now, yet there are constant indications development is underway. Let us see the projects, review the commits, and see the progress being made.
Allow others to help. I've offered development time personally on IRC, and have been ignored. Others that have offered have been shot down. The only official response I have seen is insulting: "There is a gap between the skills needed for developing TideSDK and those required to use it." Implying your users are incapable of coding at your level.
Communicate. Let the public know what is being developed, be specific. No more excuses, vague promises, and empty updates. If there are delays, fine, that is expected in the development world, but let us know what the hurdles are, maybe someone can help.
Stop being assholes. Based on your communications so far, especially in twitter replies, you seem to have a strong distaste for your user base. Stop being so dismissive and hostile. There isn't exactly a flood of comments or posts directed at you, so take a few minutes to give thoughtful, helpful, and useful responses.
TideSDK, if you are listening, your post is inspiring such passionate and frustrated replies not because we hate your work, but because we want you to succeed. I want to see this project work, and have followed it closely since it was open-sourced. But unless you make some real changes to your development process, and treat your community with respect, I don't expect your post to generate the stampede of donations you are asking for, nor do I expect this project to survive at all.
jacobvanloon
areudirty
baratheonpilled
