1
0
mirror of https://github.com/wbbaddons/Tims-Chat.git synced 2024-10-31 14:10:08 +00:00
Go to file
2012-01-22 15:40:25 +01:00
file Adding Color-Command 2012-01-22 15:40:25 +01:00
language Adding ChatCopyrightPage with overlay 2012-01-14 16:33:44 +01:00
template Merge branch 'master' into commands 2012-01-22 14:10:10 +01:00
.gitignore Updating gitignore 2011-12-26 21:01:16 +01:00
acloptions.xml Fixing namespace of XSD 2011-12-10 16:40:45 +01:00
build.php Ignore scss-files when taring the files.tar 2012-01-07 16:31:20 +01:00
eventListener.xml Added possibility of using Chat/Log and Chat/Send as routes 2011-12-10 21:36:33 +01:00
install.sql Adding some rooms for debugging 2012-01-14 12:09:07 +01:00
LICENSE Adding LICENSE file 2011-11-26 14:42:01 +01:00
objectType.xml Adding ACL-Options 2011-11-27 14:56:11 +01:00
option.xml Adding TimeIntervalOptionType 2011-12-10 16:15:49 +01:00
package.xml Fixed PIP names in package.xml 2012-01-07 00:27:45 +01:00
pagemenu.xml Fixing typo in XSD path 2012-01-13 17:04:46 +01:00
README.md Completed README.md 2012-01-06 18:01:17 +01:00
templatelistener.xml Code format and removing unneeded templatelistener 2012-01-21 17:45:53 +01:00

Tims Chat 3.0

Tims Chat is a chat-plugin for WoltLab Community Framework.

Version notes

The currently available source code represents an early alpha-version of Tims Chat, even though it may be installable, we cannot guarantee a working installation at any time. You MUST NOT install and/or use Tims Chat 3.0 in a production environment.

Contribution

Developers are always welcome to fork Tims Chat and provide features or bug fixes using pull requests. If you make changes or add classes it is mandatory to follow the requirements below:

  • Testing is key, you MUST try out your changes before submitting pull requests
  • You MUST save your files with Unix-style line endings (\n)
  • You MUST NOT include the closing tag of a PHP block at the end of file, provide an empty newline instead
  • You MUST use tabs for indentation
    • Tab size of 8 is required
    • Empty lines MUST be indented equal to previous line
  • All comments within source code MUST be written in English language
  • Use a sensible number of commits. In most cases one commit should be enough.
    • Split huge changes into several logical groups
    • Rebase small changes that consist of several commits into one commit

Follow the above conventions if you want your pull requests accepted.

License

For licensing information refer to the LICENSE file in this folder.