SMF2.1

SMF, www.simplemachines.org

Simple Machines Forum — SMF in short — is a free, professional grade software package that allows you to set up your own online community within minutes.

Its powerful custom made template engine puts you in full control of the layout of your message board and with our unique SSI - or Server Side Includes - function you can let your forum and your website interact with each other.

SMF is written in the popular language PHP and uses a MySQL database. It is designed to provide you with all the features you need from a bulletin board while having an absolute minimal impact on the resources of the server. SMF is the next generation of forum software - and best of all it is and will always remain completely free!

This is a SMF 2.1 development repository. The software is licensed under BSD 3-clause license.

Contributions to documentation are licensed under CC-by-SA 3. Third party libraries or sets of images, are under their own licenses.

######Notes:

Feel free to fork this repository and make your desired changes.

Please see the Developer's Certificate of Origin in the repository: by signing off your contributions, you acknowledge that you can and do license your submissions under the license of the project.

######Branches organization:

• master - is the main branch, only used to merge in a "final release"
• development - is the branch where the development of the "next" version/s happens
• release-2.1 - is the branch where bug fixes for the version 2.1 are applied

######How to contribute:

• fork the repository. If you are not used to Github, please check out fork a repository.
• branch your repository, to commit the desired changes.
• sign-off your commits, to acknowledge your submission under the license of the project.
  • an easy way to do so, is to define an alias for the git commit command, which includes -s switch (reference: How to create Git aliases)
• send a pull request to us.

######How to submit a pull request:

• If you want to send a bug fix for the version 2.1, send it to the branch release-2.1
• If you want to send a new feature, use the branch development
• You should never send any pull request against the master branch For more informations, the ideal branching we would like to follow is the one described in this article

Finally, feel free to play around. That's what we're doing. ;)