1
0
mirror of https://github.com/wbbaddons/Tims-Chat.git synced 2024-10-31 14:10:08 +00:00
Go to file
2012-03-12 22:51:29 +01:00
acptemplate Fixed Template 2012-03-07 17:49:52 +01:00
file Prevent constructing of Util. 2012-03-12 22:51:29 +01:00
language Changing Package Identifier to be.bastelstu.wcf.chat 2012-03-12 17:19:01 +01:00
template Changing Package Identifier to be.bastelstu.wcf.chat 2012-03-12 17:19:01 +01:00
.gitignore Updating gitignore 2011-12-26 21:01:16 +01:00
acloptions.xml Changing Package Identifier to be.bastelstu.wcf.chat 2012-03-12 17:19:01 +01:00
acpMenu.xml Language items for ACP 2012-02-04 20:59:40 +01:00
build.php Changing Package Identifier to be.bastelstu.wcf.chat 2012-03-12 17:19:01 +01:00
eventListener.xml Changing Package Identifier to be.bastelstu.wcf.chat 2012-03-12 17:19:01 +01:00
install.sql Changing Package Identifier to be.bastelstu.wcf.chat 2012-03-12 17:19:01 +01:00
LICENSE Adding LICENSE file 2011-11-26 14:42:01 +01:00
objectType.xml Changing Package Identifier to be.bastelstu.wcf.chat 2012-03-12 17:19:01 +01:00
option.xml CHAT_LENGTH -> CHAT_MAX_LENGTH 2012-03-04 18:12:44 +01:00
package.xml Changing Package Identifier to be.bastelstu.wcf.chat 2012-03-12 17:19:01 +01:00
pagemenu.xml Changing Package Identifier to be.bastelstu.wcf.chat 2012-03-12 17:19:01 +01:00
README.md Completed README.md 2012-01-06 18:01:17 +01:00
userGroupOption.xml Adding ChatRoomListPage 2012-02-04 20:50:18 +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.