Changes between Version 21 and Version 22 of TracPluggableModules

Timestamp:

Aug 10, 2005, 7:31:56 PM (19 years ago)

Author:

ErikRose

Comment:

Removed spurious comma

TracPluggableModules

@@ -11 +11 @@
 If functionality is supposed to be made pluggable (and thus optional), we need to figure out what functionality sits at the core of the system. And at that point you will probably already get different opinions. Arguably, you should be able to use Trac without deploying the issue tracker. Quite certainly, the dependency on Subversion should be made optional. The Wiki functionality is central to the system, but do Wiki pages as such and their management also belong to the core system?
 
-In an ideal architecture, there is as little core functionality as absolutely required. Anything that '''can''' be separated from the core system,
-'''should''' be separated, for a variety of (mostly obvious) reasons:
+In an ideal architecture, there is as little core functionality as absolutely required. Anything that '''can''' be separated from the core system '''should''' be separated, for a variety of (mostly obvious) reasons:
 
  * Loose coupling between the core system and the individual components allows the addition or modification of functionality with minimum impact on the code-base, thus improving stability and customizability.