Bastelstube/Tims-Chat
1
0
Fork 0
mirror of https://github.com/wbbaddons/Tims-Chat.git synced 2024-10-31 14:10:08 +00:00
Code Issues Releases Wiki Activity
802 Commits 3 Branches 25 Tags 4.7 MiB
PHP 52.8%
JavaScript 32.6%
Smarty 11.8%
SCSS 2.5%
Makefile 0.3%
32e979c7c5
Go to file
Tim Düsterhus 32e979c7c5 Add logo
2013-04-26 16:09:26 +02:00
acptemplate Make ACP WCF conform 2013-04-20 17:19:17 +02:00
contrib Convert CoffeeScript to Literate CoffeeScript 2013-04-20 18:43:56 +02:00
file Add logo 2013-04-26 16:09:26 +02:00
language Add logo 2013-04-26 16:09:26 +02:00
template Add logo 2013-04-26 16:09:26 +02:00
.gitignore Fixed ACP-icons 2012-05-31 18:17:23 +02:00
.travis.yml Check PHP syntax in travis 2013-03-03 19:12:53 +01:00
acloptions.xml Check permissions for log in template 2013-02-02 23:22:48 +01:00
acpMenu.xml Fixed installation process for now 2013-01-25 22:37:22 +01:00
cronjob.xml Port Chat to application (first parts) 2013-01-19 20:36:40 +01:00
dashboardBox.xml Add dashboard box with online-list 2013-01-31 16:02:14 +01:00
install.sql Drop enableBBCodes 2013-03-11 15:42:05 +01:00
LICENSE Improve LICENSE 2013-04-23 00:42:11 +02:00
objectType.xml Add global mute and global ban 2013-02-01 20:41:59 +01:00
option.xml Check for allowed BBCodes 2013-03-11 15:28:51 +01:00
package.xml Add logo 2013-04-26 16:09:26 +02:00
pagemenu.xml Port Chat to application (first parts) 2013-01-19 20:36:40 +01:00
README.md Completed README.md 2012-01-06 18:01:17 +01:00
templateListener.xml Add logo 2013-04-26 16:09:26 +02:00
userGroupOption.xml Check for allowed BBCodes 2013-03-11 15:28:51 +01:00

README.md

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.