Changes between Version 15 and Version 16 of SeaChange

Timestamp:

Jan 18, 2016, 2:57:47 PM (8 years ago)

Author:

figaro

Comment:

Further cosmetic changes

SeaChange

@@ -1 @@
-=  A [http://en.wikipedia.org/wiki/Seachange Sea Change] for Trac =
+=  A [wikipedia:Seachange Sea Change] for Trac
 
 {{{#!div style="float: right; border: none; border-top: 1px solid grey; border-bottom: 1px solid grey; white-space: pre; font-size: 90%; margin-bottom: 4em;"
@@ -6 +6 @@
 Those are pearls that were his eyes,
 Nothing of him that doth fade,
-But doth suffer a [http://en.wikipedia.org/wiki/Seachange sea  change],
+But doth suffer a [wikipedia:Seachange sea change],
 into something rich and strange,
 Sea-nymphs hourly ring his knell,
@@ -17 +17 @@
 [[comment(should be: br(clear=both))]]
 
-The SeaChange/ pages are used for collecting information about problems with the Trac community, in order to fix them. By community we mean Trac administrators/plugin developers, end users and core developers. 
+These pages are used for collecting information about problems with the Trac community, in order to fix them. By community we mean Trac administrators, plugin developers, end users and core developers. 
 
  - [./WhatUsersWant] lists the most frequent requests for major features (you can vote there!)
@@ -25 +25 @@
  - [./DevelopmentProcess] contains some discussion about the development process itself.
 
-Also, it could be worth looking at other wikis, BugTrackingSystem and repository browsers, and see what the users can expect from other competitor systems. Note that since the success of Trac integration model (well, CvsTrac's model actually), some of the other bug tracking systems are evolving towards more integration as well, most notably by having an integrated wiki and/or source code browser.
+Also, it could be worth looking at other wikis, BugTrackingSystem and repository browsers, and see what the users can expect from competitor systems. Note that since the success of Trac integration model (well, CvsTrac's model actually), some of the other bug tracking systems are evolving towards more integration as well, most notably by having an integrated wiki and/or source code browser.
 
 == Other wild ideas
@@ -55 +55 @@
 Anyone fancy implementing a plug-in for [http://www.eclipse.org Eclipse]? There's currently an [http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-vcm-home/docs/online/bugs-plugin/index.html effort] going on to provide [https://www.bugzilla.org/ Bugzilla] integration, apparently extensible to other issue tracking systems. Such an effort would probably depend on us getting some kind of web-service layer working.
 
-'''Answer''': The [http://wiki.eclipse.org/Mylyn/SOC/2006/Trac_Connector Trac Connector] for Mylyn does exactly this.
+'''Answer''': The [http://wiki.eclipse.org/Mylyn/SOC/2006/Trac_Connector Trac Connector] for Mylyn does exactly this. See also th:MylynTracConnector.
 
 === Continuous Integration
@@ -61 +61 @@
 Provide integration with [http://docs.codehaus.org/display/DAMAGECONTROL/Continuous+Integration+Server+Feature+Matrix Continuous Integration tools].
 
-'''Answer''': A well tested CI tool is [http://trac.buildbot.net/ Buildbot] and described on [th:TracBuildbotIntegration]. Also see [PluginList#ContinuousIntegration other CI tool plugins]. Christopher Lenz's [http://bitten.cmlenz.net/ Bitten] plugin has been discontinued. 
+'''Answer''': A well tested CI tool is [http://trac.buildbot.net/ Buildbot] and integrated with Trac as [th:TracBuildbotIntegration] and [th:BuildbotPlugin]. Also see [PluginList#ContinuousIntegration other CI tool plugins]. Christopher Lenz's [http://bitten.cmlenz.net/ Bitten] plugin has been discontinued. 
 
 === RPC Interface
 
-Via SOAP or XML-RPC (recommended for utter simplicity!), export the user interface functions to allow integration with proprietary Intranets and so forth. This would also allow some crazy developers to write e.g. an [http://en.wikipedia.org/wiki/AJAX AJAX] interface to Trac.
+Via SOAP or XML-RPC (recommended for utter simplicity!), export the user interface functions to allow integration with proprietary Intranets and so forth. This would also allow some developers to write for example an [wikipedia:AJAX] interface to Trac.
 
 In particular, the ability to retrieve reports would make a lovely addition to my Intranet homepage. :) -- [http://botanicus.net/dw/ DavidWilson]
@@ -71 +71 @@
 Related Tickets: #217, #250.
 
-'''Answer''': The [https://trac-hacks.org/wiki/XmlRpcPlugin XML-RPC plugin] at trac-hacks does exactly this.
+'''Answer''': The [th:XmlRpcPlugin XML-RPC plugin] at trac-hacks does exactly this.
 
 === SVN Edition