To make this the best possible environment, we ask that everyone follow a few simple guidelines. We'll do our part to ensure this remains a constructive and supportive place but we need your help here as well.
The Ning Developer Network is a place to share tips and tricks about the code that powers your social network; whether you're working on Ning Apps, Profile Apps or have this questions about the CSS on your social network, this is the place to chat about it. If you have questions about the standard features of the social network or have a bug to report please contact us via the Help Center.
Because we can most effectively answer general questions about features on Ning through the Help Center, any discussion thread not directly related to coding on Ning will be deleted.
Please don't spam. What is spam? Spam is posting the same message repeatedly across the network. Spam is writing the same post or comment over and over again. Spam is sending the same message to multiple members. You get the picture.
We take a hard line view on spam and, unfortunately, if you are reported or deemed by us to be a spammer, we'll have to ban you here on the Developer Network.
Respectfully disagreeing with someone - including us - in a constructive, well-reasoned manner is not only welcomed, but encouraged. We can't get better if we don't have thoughtful, constructive feedback from you about your social network on Ning. That's why we're here.
On the other hand, if you're here to find an outlet for your anger, frustration, or desire to call us IDIOTS IN ALL CAPS over and over again, this isn't the right place. Drop us a note in the Ning Help Center to get whatever it is off your chest. We do read every email that comes in and will get the message loud and clear when you are unhappy.
We take threatening, unconstructive, toxic, profane, or generally abusive people very seriously and will ban fast and furiously when we see them. Even if you have a right to be angry or frustrated, yelling at us or other members here isn't helpful and won't get you what you want. Just like in the real world.
Please read our Terms of Service and the Guidelines For Developing on the Ning Platform. Then please follow our Terms of Service. They are there for a reason. And we read it regularly to determine if a network, application developer, or individual is complying with it.
If something is not in compliance with our Terms of Service, we will unfortunately need to deactivate or take down the network, application, or individual account. Trust us, this brings us no joy and is the least favorite part of our job.
We'll certainly try our best to give you a few hours of notice to make changes, but because we are running a rapidly growing service we can't make any guarantees. We may need to shut your network, application or individual account down without notice.
The best plan is to follow our Terms of Service and try not to operate in too many gray areas. Namely, we might not shut you down today for not buying our premium services while running ads in your text box, but we will at some point and then you'll be bummed.
If you've been banned from Developer or had your network on Ning deactivated by us and you think it is in error, by all means let us know via the Ning Help Center. We'll always take another look at the specific case and respond at least once to your concerns.
Unfortunately, we aren't able to publicly handle appeals or articulate reasons for shutting down a network. These topics have a tendency to devolve into the realm of unconstructive shouting matches that take a lot of time and don't end well. As a result, we'll remove discussions and blog posts asking for public comment on banning or network deactivation.
We totally recognize that Ning won't be for everyone. If our Terms of Service or these few simple requests here aren't going to work for you, we totally understand. We hate having to ban people or deactivate networks, so if you don't think that this is going to work for you upfront, it's much better for all of us to know it now.
The Ning Team
Last updated by Devin Jul 14, 2009.