I guess the question needs to be -- will this inclusion actually drive more users to Harrow than the damage to goodwill&#x2F;annoyance of including it. Personally, I&#x27;m less inclined to try Harrow now, but I admit that&#x27;s just personal bias. I don&#x27;t think there&#x27;s anything wrong with trying to build platforms to sustain work on great FOSS products - of which cap is definitely one (that I use every day! thanks!) -- in an ideal world this dependency doesn&#x27;t exist AND harrow gets enough users to support further work on capistrano. But since this isn&#x27;t an ideal world, I&#x27;m not going to second guess the choice too much, other than to say, I don&#x27;t think it will make people choose to use Harrow that wouldn&#x27;t otherwise, and maybe it is better to find other ways of reaching potential users than with a message during cap install.