> READ THIS FIRST!: We recently announced Taiga plans for the future and they greatly affect how we manage this repository and the current Taiga 6 release. Check it here.
The Taiga plugin for slack integration.
Define a variable with the latest repository release, for instance:
export TAIGA_CONTRIB_SLACK_TAG=6.0.2
Load the python virtualenv from your Taiga back directory:
source .venv/bin/activate
And install the package taiga-contrib-slack
with:
(taiga-back) pip install "git+https://github.com/taigaio/taiga-contrib-slack.git@${TAIGA_CONTRIB_SLACK_TAG}#egg=taiga-contrib-slack&subdirectory=back"
Modify in taiga-back
your settings/config.py
and include the line:
INSTALLED_APPS += ["taiga_contrib_slack"]
Then run the migrations to generate the required new table:
python manage.py migrate taiga_contrib_slack
Download in your dist/plugins/
directory of Taiga front the taiga-contrib-slack
compiled code (you need subversion in your system):
cd dist/
mkdir -p plugins
cd plugins
svn export "https://github.com/taigaio/taiga-contrib-slack/tags/${TAIGA_CONTRIB_SLACK_TAG}/front/dist" "slack"
Include in your dist/conf.json
in the contribPlugins
list the value "plugins/slack/slack.json"
:
...
"contribPlugins": [
(...)
"plugins/slack/slack.json"
]
...
This configuration should be used only if you're developing this library.
Clone the repo and
cd taiga-contrib-slack/back
workon taiga
pip install -e .
Modify in taiga-back
your settings/local.py
and include the line:
INSTALLED_APPS += ["taiga_contrib_slack"]
Then run the migrations to generate the new need table:
python manage.py migrate taiga_contrib_slack
After clone the repo link dist
in taiga-front
plugins directory:
cd taiga-front/dist
mkdir -p plugins
cd plugins
ln -s ../../../taiga-Contrib-slack/front/dist slack
Include in your dist/conf.json
in the contribPlugins
list the value "plugins/slack/slack.json"
:
...
"contribPlugins": [
(...)
"plugins/slack/slack.json"
]
...
In the plugin source dir taiga-contrib-slack/front
run
npm install
and use:
gulp
to regenerate the source and watch for changes.gulp build
to only regenerate the source.
Follow the instructions on our support page Taiga.io Support > Contrib Plugins > Slack integration
Currently, we have authored three main documentation hubs:
- API: Our API documentation and reference for developing from Taiga API.
- Documentation: If you need to install Taiga on your own server, this is the place to find some guides.
- Taiga Community: This page is intended to be the support reference page for the users.
If you find a bug in Taiga you can always report it:
- in Taiga issues. This is the preferred way
- in Github issues
- send us a mail to support@taiga.io if is a bug related to tree.taiga.io
- send us a mail to security@taiga.io if is a security bug
One of our fellow Taiga developers will search, find and hunt it as soon as possible.
Please, before reporting a bug, write down how can we reproduce it, your operating system, your browser and version, and if it's possible, a screenshot. Sometimes it takes less time to fix a bug if the developer knows how to find it.
If you need help to setup Taiga, want to talk about some cool enhancemnt or you have some questions, please go to Taiga community.
If you want to be up to date about announcements of releases, important changes and so on, you can subscribe to our newsletter (you will find it by scrolling down at https://taiga.io) and follow @taigaio on Twitter.
There are many different ways to contribute to Taiga's platform, from patches, to documentation and UI enhancements, just find the one that best fits with your skills. Check out our detailed contribution guide.
Help us keep the Taiga Community open and inclusive. Please read and follow our Code of Conduct.
Every code patch accepted in Taiga codebase is licensed under MPL 2.0. You must be careful to not include any code that can not be licensed under this license.
Please read carefully our license and ask us if you have any questions as well as the Contribution policy.