elshara / ning2.0 Goto Github PK

Once we're sure that a change is in progress, we'll update this thread as an interactive change log of our commitment to the community at large available for next release. To submit your feedback for a core change. Be it a bug report, feature request or other type of feedback in the support forum. All of these changes shall be reflected here so that you know what's been done to core. changes we are planning shall show up as a feature request and will carry a milestone label of Community Feedback so that everyone can have a say, developers and administrators alike.

To submit a new feature request, reply here. Please note that the release of a major feature due to possible bug reports may be delayed, but not put off indefinitely. Maintenance releases and their time of application do not effect the build process of feature requests as we have different developers working on areas of core changes in an effort to keep things speedy and working as expected. We encourage new developers to contribute and fork their own code. If we like what you've built, we may ask to merge something you've contributed straight into core! That is just one change of many we plan to ensure keeps people connected safely and interactively so we shall have an online presence to remember for years to come. It's time to share your feedback with us.

If you see something, say something. Regardless of whether it's a server misconfiguration, a bug or an incompatible section of code. Your feedback is crucial to a fix.

This thread is for support. Anyone who is successfully running an instance of the Ning 2.0 project can reply here and get support from the developers and the community.