Etusivu Tutki Apua
Rekisteröidy Kirjaudu sisään
Omnimaga
/
SMF2.1
peilaus alkaen [email protected]:Omnimaga/SMF2.1.git
2
0
Fork 0
Tiedostot Ongelmat 0 Wiki

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

Puu: cdd86791de
Haarat Tagit
SMF2.1
ZIP TAR.GZ
Peter Spicer cdd86791de ! I have no idea why drafts are disabled by default, that seems insane. But even if you do want them disabled, it shouldn't require going to the Core Features page to do it, should really be from the Drafts page. And, so it is. 11 vuotta sitten
Packages c8e62fe029 ! Fix many of the phpdocumentor errors with our docblock's 12 vuotta sitten
Smileys c8e62fe029 ! Fix many of the phpdocumentor errors with our docblock's 12 vuotta sitten
Sources cdd86791de ! I have no idea why drafts are disabled by default, that seems insane. But even if you do want them disabled, it shouldn't require going to the Core Features page to do it, should really be from the Drafts page. And, so it is. 11 vuotta sitten
Themes cdd86791de ! I have no idea why drafts are disabled by default, that seems insane. But even if you do want them disabled, it shouldn't require going to the Core Features page to do it, should really be from the Drafts page. And, so it is. 11 vuotta sitten
attachments c8e62fe029 ! Fix many of the phpdocumentor errors with our docblock's 12 vuotta sitten
avatars ab4aa21af9 ! Removed wolf icon due to the fact that it's someone else's logo as per #558. 11 vuotta sitten
cache a18e888838 10610 12 vuotta sitten
other cdd86791de ! I have no idea why drafts are disabled by default, that seems insane. But even if you do want them disabled, it shouldn't require going to the Core Features page to do it, should really be from the Drafts page. And, so it is. 11 vuotta sitten
.gitattributes 3e46fa2644 More PHP 5.5 fixes found while working on 2.0 PHP 5.5 Combat 11 vuotta sitten
.gitignore 7cc1428fdc Fixed login on upgrade not working on first try. 11 vuotta sitten
DCO.txt b486a1e52a Adding a Developer's Certifcate of Origin to be used when submitting contributions. 12 vuotta sitten
README.md 10f8066483 Update README.md with instructions on how to contribute (sorry for the direct commit...) 12 vuotta sitten
SSI.php aec98628cb ! Oops, that shouldn't have been Wedge style code. 11 vuotta sitten
agreement.txt a18e888838 10610 12 vuotta sitten
contributors.txt 8afad0752c Corrected missing comma. 11 vuotta sitten
favicon.ico a18e888838 10610 12 vuotta sitten
index.php 5d594b0d9e Disregard -> Unwatch 11 vuotta sitten
ssi_examples.php 2c50939f27 Copyright update per BoD 11 vuotta sitten
ssi_examples.shtml b17452c904 ! update ssi_examples shtml ... we are not longer rc4 or llc :P 12 vuotta sitten
subscriptions.php 2c50939f27 Copyright update per BoD 11 vuotta sitten

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