Thoughts, Ideas and bits of code for SMF (2.1)

Suki c660e998a8 I uploaded the avatars I needed to test things out, theres no need for this anymore 12 år sedan
Packages c8e62fe029 ! Fix many of the phpdocumentor errors with our docblock's 12 år sedan
Smileys c8e62fe029 ! Fix many of the phpdocumentor errors with our docblock's 12 år sedan
Sources c660e998a8 I uploaded the avatars I needed to test things out, theres no need for this anymore 12 år sedan
Themes b8bfccb997 Add a missing text string 12 år sedan
attachments c8e62fe029 ! Fix many of the phpdocumentor errors with our docblock's 12 år sedan
avatars 75a0617d30 Merge pull request #226 from emanuele45/new_avatars 12 år sedan
cache a18e888838 10610 12 år sedan
other 2ce9fefa7d install.php CSS Bugfix 12 år sedan
.gitignore b8bfccb997 Add a missing text string 12 år sedan
DCO.txt b486a1e52a Adding a Developer's Certifcate of Origin to be used when submitting contributions. 12 år sedan
README.md 10f8066483 Update README.md with instructions on how to contribute (sorry for the direct commit...) 12 år sedan
SSI.php 6ac2d0d926 Fixed undefined variable in SSI [Bug 4992] 12 år sedan
agreement.txt a18e888838 10610 12 år sedan
changelog.txt a18e888838 10610 12 år sedan
favicon.ico a18e888838 10610 12 år sedan
index.php ea6aa67f3b Merge pull request #210 from emanuele45/disregard 12 år sedan
ssi_examples.php 5efaf7a21a Revert "Copyright correction." 12 år sedan
ssi_examples.shtml b17452c904 ! update ssi_examples shtml ... we are not longer rc4 or llc :P 12 år sedan
subscriptions.php 5efaf7a21a Revert "Copyright correction." 12 år sedan

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