I'm about one step away from going full go with status.net on my own shared hosting, which is bluehost; and I'm one step away from ditching it completely because of lack of documentation and support.
I would like to see status.net work because I can see the potential it can have and spreading like wordpress. And if I can get it to work effectively, like wordpress, then I can contribute to the open source.
I believe that in order for status.net to work and spread among communities the documentation needs to be translated into readable and functional steps for people like me- I can do html and css and create an active wordpress blog, but I'm not a programming engineer.
I put in a lot of time and effort to getting status.net installed and working on my own server with bluehost. And I thank bluehost for their support and guiding me through the process.
However, now that it's installed, where's the documentation? A lot of plugins are missing readme files and when I follow instructions to add plugins or remove plugins, they don't work. I even followed the optimization guide and mimicked the config.php file from this link: http://publications.jbfavre.org/statusnet/optimize-statusnet-nginx-php-fpm-apc-memcache.en
, but still couldn't get it functioning.
I guess what I'm getting at is...is there going to be support here? Or, am I on my own?
I don't intend to suck in information without giving back. But, I can't give back if I don't understand my own status.net instance and get that running first.
Status.net- what is your big picture here? What are your goals? Can you not see the potential of this program spreading like wordpress if it can be usable and understood for a person like me? There are millions of them out there. I would love to see you succeed.