3 ms·

I'm a backer, and am now very used to non-delivery after backing hundreds of projects as a gamer on Linux. The non-delivery of projects, either complete failure

I'm a backer, and am now very used to non-delivery after backing hundreds of projects as a gamer on Linux. The non-delivery of projects, either complete failure or just failure to deliver to Linux, is probably around 20% or so in about 100 projects backed. As a FOSS proponent I'm obviously biased in this, but I believe failed projects have a duty to release source to the backers in some way. In a perfect world, the community will help carry the project over the line, but worst case at least the backers receive something of value and can do with it what they will. It doesn't matter if the original developer has concerns about levels of quality or completion. Please see this both as a general comment to the community, but also a plea directly to the developer in this particular instance.

vertline3 8y ago
"I believe failed projects have a duty to release source to the backers in some way." He said in the link "I will prepare the source code for release" And he will be in touch after the source is released.
- benatkin 8y ago
  Commenters on the KS page were also asking about the source code despite the author mentioning that it will be released. Maybe they suspect that the source code release be failed to be released in a timely manner just like the product was. If it is indeed a duty, it might be prudent for a creator in a similar situation to delay the announcement until the source code has been prepared.
- Tempest1981 8y ago
  Sounds like the latest version may not compile, after incomplete refactoring. Would be good if he released the full git repo - a previous version might be a better starting point.