WIKI in Team Concert
we use a external WIKI to provide quick links for a project team and managers , e.g. for latest release notes, spec documents, how to documents, known issues, set up's or a list of review relevant documents , success stories of the product, fieldtest results etc.
The pages of plans are already kind of a WIKI, but a full WIKI inside Team concert would provide a easy drag an drop for links to documents contained in the source control or to work items.
With the external WIKI we need to define a workspace on a commonly accessable server and put all the links manuall - work items can not be adressed.
As you use WIKI style syntax for the pages in plans already, it mightnot be so hard to extent it to a full WIKI - specially as their are Eclipse plug ins available.
The WIKI might appear in the favourites of the tree view.
Roland
May someone else likes the ideas as well
Accepted answer
4 other answers
- Use a wiki page for knowledge sharing and on-demand access
- Use discussion forums for collaboration, idea sharing and brainstorming
- Use a community blog for news, announcements, and community-wide communication
And indeed, if we look at the Jazz development projects, they all use wiki pages, discussion forums and community blogs. If Jazz should support collaborative development, at least I would expect that wikis are out-of-the-box.
So, a big +1 from me on this!
Frank.
Jazz integrates with instant messaging tools too, but did not reinvent instant messaging...
It is sufficient if RTC would provide an existing wiki engine and preconfigure it to integrate with RTC. Of course, the wiki language of the wiki should be the same as the wiki language used in work items (and other fields that support wiki formatting).
Comments
Point, provided the Wiki tool can be redistributed.
On a second thought it would still add more complexity and test effort. The complexity of the system requirements would increase and a support statement would be hard to do anyway, even ifthe Wiki would be redistributable, if the Wiki is not developed by IBM. An install manager procedure would have to be set up too. It all sounds so easy but to mathc the requirements for being able to ship with our products would be a considerable effort.
1 vote
Hi Ralph, Frank of course, not re-invent - integration with Confluence WIKI would be great - not even redistribution is required. Most companies have thei "Intra Company WIKI", so a "second parallel" WIKI would not the first choice.
The user value would be to easily insert links links from WIKI to RTC and vice versa , to embedd WIKI pages in the notes tabs of plans e.g. for the releases notes of an iteration , which are any how published in the company WIKI), to push known defects lists for a release to the companies WIKI pages etc. Keep in mind, that RTC is used by the softeware engineers, but not thougout the company. Roland
Hi Roland,
my best suggestion to go ahead is to create a work item here: https://jazz.net/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.workitem.viewWelcome and describe the use cases you envision. Post the work item back to this thread so that people can subscribe and support it.
