Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Thoughts, Ideas and bits of code for SMF (2.1)
PHP JavaScript PLpgSQL CSS Other
Branch: master
Pull request Compare This branch is 17 commits ahead, 5847 commits behind release-2.1.

Merge pull request #105 from jdarwood007/no-closing-php

Removed closing PHP line endings
latest commit 404fd53479
@Oldiesmann Oldiesmann authored
Failed to load latest commit information.
Packages Fixed chmod that somehow got changed, which should resolve #105
Smileys Fixed chmod that somehow got changed, which should resolve #105
Sources Fixed conflicts
Themes Fixed conflicts
attachments Fixed chmod that somehow got changed, which should resolve #105
avatars Fixed chmod that somehow got changed, which should resolve #105
cache Fixed chmod that somehow got changed, which should resolve #105
other Fixed conflicts
.gitignore Fixed conflicts
DCO.txt Fixed chmod that somehow got changed, which should resolve #105
README.md Revert "Update README.md"
SSI.php Fixed conflicts
agreement.txt Fixed chmod that somehow got changed, which should resolve #105
changelog.txt Fixed chmod that somehow got changed, which should resolve #105
favicon.ico
index.php Fixed conflicts
ssi_examples.php Revert Copyright Line
ssi_examples.shtml Fixed chmod that somehow got changed, which should resolve #105
subscriptions.php Fixed conflicts

README.md

SMF, www.simplemachines.org

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. ;)

Something went wrong with that request. Please try again.