|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (1)
View page history... |
| Atlassian (the developers of Confluence) encourages developers to write plugins and share them with the rest of the Confluence community. This is great for Atlassian, because they can focus on the core functionality, while many RFEs can be resolved via plugins, often developed outside of Atlassian. |
| This approach brings some problems (of course). Many plugins were developed by hobbyist developers running their small, often home or internal instances of Confluence. Functionality was the main goal for these developers, while security and scalability wasn't high on their list. Combine that with a powerful plugin framework and you get a recipe for disaster. There have actually has been incidents where large Confluence instances were taken down by a plugin that wasn't built with the scalability in mind ([recent problems|http://forums.atlassian.com/thread.jspa?forumID=96&threadID=19177] at confluence.atlassian.com are a good example of this). |
*The Plugins Policy* |
... |