Then perhaps it's inappropriate to claim that "Otto can deploy to many different infrastructure providers" until "Otto can deploy to many different infrastructure providers".
Right or wrong, it's pretty standard practice to sell the vision of the product as opposed to the actuality of the product.
"Otto will some day hopefully be able to deploy to many different infrastructure providers" isn't a particularly attractive statement. You could try something like "Otto currently only supports deploying to AWS, but will eventually support many more" but while perhaps technically correct it'll probably shy more people away than get them involved. Those same people might just contribute additional deploy targets if only they got nudged enough to get involved in the first place.
You're not wrong, but getting people on board with the vision is much more important for a "hive mind" project such as Otto, than being technically correct as to the current state of things.
I'm not saying it isn't; I'm just saying that people do this all the time. Many times just to fake it till you make it, other times to be willfully be deceptive. I doubt it's the latter in this case.
"Otto will some day hopefully be able to deploy to many different infrastructure providers" isn't a particularly attractive statement. You could try something like "Otto currently only supports deploying to AWS, but will eventually support many more" but while perhaps technically correct it'll probably shy more people away than get them involved. Those same people might just contribute additional deploy targets if only they got nudged enough to get involved in the first place.
You're not wrong, but getting people on board with the vision is much more important for a "hive mind" project such as Otto, than being technically correct as to the current state of things.