Jay Levitt wrote:
> Branko Čibej wrote:
>> Jay Levitt wrote:
>> We'd still want the wiki page sources stored in Subversion. So Trac
>> is a non-starter, and AFAIK subwiki is the only wiki implementation
>> that stores pages in SVN.
> Ah, ok. Is that for dogfood reasons (svn docs should be in svn, ipso
> facto), or for workflow (when you check out SVN, you get the docs, and
> when you check it in, you can update it)?
Workflow reasons, of course. We want to keep a history of the docs
changes in our repository.
> What state is subwiki in? I got the impression from Greg's last post
> on the topic that it's technically active but hasn't gone anywhere.
> Subwiki's own wiki is apparently down or dead.
I guess it's in a very... pre-alpha stage. Trying kwiki might be a good
> If it's more about workflow than dogfood, I suspect the easiest
> solution would be some type of cross-merge - edit the wiki and it
> checks it into svn, and vice-versa.
>> since that could pave the way for eventual migration from bugzilla to
>> Trac for issue-tracking, if such a thing is ever desired. (In fact,
>> I'd be willing to do the work for that, too; the tight integration
>> between design docs, issue tracking and source code is a wonder to
>> As long as Subversion is hosted on tigris.org, we'll use whatever
>> issue tracking tigris provides.
> No problem; I didn't realize that subversion was limited in its choice
> of tools.
It's not exactly limited, but I think we'd need a lot of incentive to
change the issue tracker.
> I had read that "the issue tracker is becoming a victim of
> Subversion's success", and seen all the (apparently) manual work done
> here for voting, nominating, approving, etc., and thought that Trac
> might be a better workflow fit in the medium- to long-term. If
> bugzilla it is, then bugzilla it shall be; that certainly makes Trac
> less desirable as a pure wiki engine.
> darix wrote:
>and i think it should be rather easy to teach trac svn storage too.
> I know they've talked about it on the trac lists, but not sure if
> that's easy or hard. I imagine teaching it to "cross-file" with svn
> would be easy, due to its plugin architecture, and teaching it to rely
> on svn as its sole repository would be harder (and certainly beyond my
> abilities right now as a Python novice).
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Wed Oct 19 18:59:13 2005