Thoughts, Ideas and bits of code for SMF (2.1)
PHP JavaScript CSS PLpgSQL
Clone or download
Permalink
Failed to load latest commit information.
Packages Lower all header Feb 24, 2018
Smileys Use smiley set name for folder Jun 23, 2018
Sources Merge pull request #4914 from Yoshi2889/4913 Aug 15, 2018
Themes Merge pull request #4914 from Yoshi2889/4913 Aug 15, 2018
attachments Lower all header Feb 24, 2018
avatars Lower all header Feb 24, 2018
cache Lower all header Feb 24, 2018
custom_avatar Lower all header Feb 24, 2018
other Merge pull request #4903 from sbulen/smiley_fixer Aug 13, 2018
.gitattributes More PHP 5.5 fixes found while working on 2.0 PHP 5.5 Combat Oct 6, 2013
.gitignore Load on upgrade everytime the english language file Mar 17, 2018
.gitmodules Seems travis doesn’t like ssh Feb 17, 2017
.scrutinizer.yml Add .scrutinizer.yml Aug 25, 2017
.travis.yml PHP 7.2 is out now, so we should test with that too Jan 23, 2018
DCO.txt Revert "Added integration hooks for knownInts and knownFloats" Jul 23, 2012
LICENSE Create LICENSE Jul 12, 2015
README.md Fix mark-up of README.md (#4089) Jun 5, 2017
SSI.php Put their precious BBCs back. Aug 11, 2018
agreement.txt * Typo in agreement.txt (fixes #2066) Jul 19, 2014
contributors.txt Updates year to 2018. Adds $software_year substitution to installer a… Jan 19, 2018
cron.php Tidies whitespace Mar 26, 2018
favicon.ico Update the favicon (#4394) Dec 6, 2017
index.php Protects against misconfigured cron jobs Apr 5, 2018
proxy.php Tidies whitespace Mar 26, 2018
ssi_examples.php Bye bye windowbg2 Jul 8, 2018
ssi_examples.shtml Updates year to 2018. Adds $software_year substitution to installer a… Jan 19, 2018
subscriptions.php Lower all header Feb 24, 2018

README.md

SMF

Build Status

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.
  • It is enough to include in your commit comment "Signed-off by: " followed by your name and email address (for example: Signed-off-by: Angelina Belle <angelinabelle1@hotmail.com>)
  • 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

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

Security matters:

Lastly, if you have a security issue you would like to notify us about regarding SMF - not just for 2.1, but for any version - please file a security report on our website: https://www.simplemachines.org/about/smf/security.php

This will enable the team to review it and prepare patches as appropriate before exploits are widely known, which helps keep everyone safe.