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

Jeremy D 2a7cea57b6 Fixed conflicts 11 éve
Packages dfe00a8a35 Fixed chmod that somehow got changed, which should resolve #105 12 éve
Smileys dfe00a8a35 Fixed chmod that somehow got changed, which should resolve #105 12 éve
Sources 2a7cea57b6 Fixed conflicts 11 éve
Themes 2a7cea57b6 Fixed conflicts 11 éve
attachments dfe00a8a35 Fixed chmod that somehow got changed, which should resolve #105 12 éve
avatars dfe00a8a35 Fixed chmod that somehow got changed, which should resolve #105 12 éve
cache dfe00a8a35 Fixed chmod that somehow got changed, which should resolve #105 12 éve
other 2a7cea57b6 Fixed conflicts 11 éve
.gitignore 2a7cea57b6 Fixed conflicts 11 éve
DCO.txt dfe00a8a35 Fixed chmod that somehow got changed, which should resolve #105 12 éve
README.md b13edea762 Revert "Update README.md" 11 éve
SSI.php 2a7cea57b6 Fixed conflicts 11 éve
agreement.txt dfe00a8a35 Fixed chmod that somehow got changed, which should resolve #105 12 éve
changelog.txt dfe00a8a35 Fixed chmod that somehow got changed, which should resolve #105 12 éve
favicon.ico dfe00a8a35 Fixed chmod that somehow got changed, which should resolve #105 12 éve
index.php 2a7cea57b6 Fixed conflicts 11 éve
ssi_examples.php 9c41d9c990 Revert Copyright Line 11 éve
ssi_examples.shtml dfe00a8a35 Fixed chmod that somehow got changed, which should resolve #105 12 éve
subscriptions.php 2a7cea57b6 Fixed conflicts 11 éve

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