Edgewall Software
Modify

Opened 16 years ago

Closed 16 years ago

Last modified 11 years ago

#2890 closed enhancement (wontfix)

Migrate to MoinMoin

Reported by: ttingey@… Owned by: Jonas Borgström
Priority: highest Milestone:
Component: wiki system Version: 0.9.4
Severity: normal Keywords: wiki moinmoin
Cc: ttingey@… Branch:
Release Notes:
API Changes:
Internal Changes:

Description

Several tickets already exist regarding better editing. MoinMoin is a better wiki and enables more options for editing. It currently comes with a much more rich editing environment. MoinMoin is also written in Python and should make for much easier migration. I would love to help if we can get this ticket higher on the priority list.

Attachments (2)

a.doc (84.5 KB ) - added by anonymous 14 years ago.
ms word to wiki test.doc (23.5 KB ) - added by anonymous 14 years ago.

Download all attachments as: .zip

Change History (11)

comment:1 by anonymous, 16 years ago

I wanted to add a note as to why this is so important.

The user story goes like this. We want to replace our current bug-tracking system with trac. Trac offers us wiki pages and especially the ability to link between tickets, changes sets, etc. This is huge for having an understanding of how code relates to tickets and how tickets relate to tickets. All of that is great, but, what we really want to be able to do is put our user stories and use cases directly into trac. Then we can drop our documents and maintain those documents directly on the wiki. This requires that trac has a better editing system. We need real WYSIWYG capability in order to get non-programmers to use the system. We would need mostly non-technical writers to feel comfortable leaving behind Microsoft Word to maintain our documentation and to use our trac wiki to document instead. Can we do this? Please?

comment:2 by Jonas Borgström, 16 years ago

Resolution: wontfix
Status: newclosed

This can and will not be done for various reasons. One showstopper is the MoinMoin license, we're simply not allowed to do that according to their GPL license.

comment:3 by Christian Boos, 16 years ago

Milestone: 0.10

Well, a possible alternative would be to disable the trac.wiki.* components in Trac, create a TracMoinMoinWiki plugin that simply parses WikiPageNames and produces links pointing to an external MoinMoin wiki…

comment:4 by anonymous, 16 years ago

is it their license or your license? why you dont offer trac with gpl license then?

comment:5 by Emmanuel Blot, 16 years ago

Trac used to be licensed under the GPL a while ago (until 0.9) and the development team has decided to change the license for a BSD-like license.

GPL would have been an issue for people (companies) that want to integrate Trac in other products, or to write proprietary Trac plugins.

Ref: http://svn.haxx.se/dev/archive-2005-07/1355.shtml

by anonymous, 14 years ago

Attachment: a.doc added

by anonymous, 14 years ago

Attachment: ms word to wiki test.doc added

comment:6 by martinshaw, 13 years ago

Looks like the licensing issues are going to prevent an integration.

But I like the idea of a TracMoinMoinWiki plugin to link to an external Moin wiki. Our company have an established MoinMoin wiki farm and have more recently adopted trac for tickets.

It would be great to disable the trac wiki and instead link to our moin wiki. The other side of this coin would be to equip MoinMoin with the full abbreviated traclinks markup, so the moin wiki pages could link back to tickets and the source browser etc.

If anybody is working on this or would be interested in starting I'm happy to collaborate.

comment:7 by anonymous, 13 years ago

How about http://moinmo.in/MacroMarket/IncludeUrlContentWiki + Interwiki? (since Trac shares markup with MoinMoin)

Would this allow integrating Trac into MoinMoin? Any licensing issues on integrating Trac on MoinMoin through plugins?

in reply to:  7 comment:8 by lin, 11 years ago

Replying to anonymous:

Any licensing issues on integrating Trac on MoinMoin through plugins?

MoinMoin is GPL lincenced, Trac is BSD licenced.

A citation about plugins integration (gnu.org):

If a program released under the GPL uses plug-ins, what are the requirements for the licenses of a plug-in?

It depends on how the program invokes its plug-ins. If the program uses fork and exec to invoke plug-ins, then the plug-ins are separate programs, so the license for the main program makes no requirements for them.

If the program dynamically links plug-ins, and they make function calls to each other and share data structures, we believe they form a single program, which must be treated as an extension of both the main program and the plug-ins. This means the plug-ins must be released under the GPL or a GPL-compatible free software license, and that the terms of the GPL must be followed when those plug-ins are distributed.

If the program dynamically links plug-ins, but the communication between them is limited to invoking the ‘main’ function of the plug-in with some options and waiting for it to return, that is a borderline case.

So, as far as I understand, the integration of Trac into MoinMoin is not possible as a single program.

But, indeed, using a sort of plugin like IncludeUrlContentWiki seems to be a good alternative: two separate programs communicationg via hyperlinks.

I'm disapointed. This Trac / MoinMoin cooperation would just be perfect. Does someone knows the right way of doing it ?

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain Jonas Borgström.
The resolution will be deleted. Next status will be 'reopened'.
to The owner will be changed from Jonas Borgström to the specified user.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.