On 3/31/09, DrunkenMonk <[email protected]> wrote: > > Hello everybody. I have a somewhat difficult decision to make > regarding one of my fields, and I thought I'd get input from the > Boltwire comunity too. > > I am using one wiki as the primary administration tool of my theatre > group. It's primary purpose (although it's damn useful across the > board) is to allow a large group of people to simulatnously write the > manuscript for our play. > > While the Boltwire wiki was an amazing improvement over our last > writing organisation (which was virtually nonexistant), it simply does > not have enough control over multiple users wanting to edit the same > page/section, and ... well, basically it isnt the subversion version > control system, and I need it to be. > > Now, I can fix this in two ways: > > a) I could move away from Boltwire and try ikiwiki, which is based on > subversion. > The positive sides are: > I don't have to write it myself > It works well once it's installed > It does not require that apache has write permissions, which could be > a small security bonus but it's unlikely to be relevant > > The negative sides are: > I'd have to teach people new wiki markup (although the changes are > slight) > The ikiwiki homepage is ugly, difficult to navigate, and I do not know > the community as well as Boltwires. > I *like* boltwire. > I probably have to recreate the whole site for the new iteration, > instead of just moving the current content-pages to old.content. > > b) I could write a subversion plugin for boltwire, completly changing > "edit" and "history" functionality, and generally recreating the > ikiwiki functionality on boltwire. > The positive sides are: > I basically know how, I wouldnt need to learn a new system > I wouldnt need to create my own site in ikiwiki markup, but could re- > use this site > > the negative sides are: > It would take me around 2 whole days of coding and weeks of debugging > and tuning. Time I do not have. > It is silly to recreate functionality that exists, unless you learn > from it, and I would learn very little. > > What do you guys think I should do?
Well, you know my encouragement would be to stick around. Especially if the alternative is something with a name like ikiwiki! :) And I'm glad you've found it useful. But more specifically, could you take a few minutes to describe exactly what you would like BoltWire to do, and what it's lacking. It's possible we might be able to either 1) do it already using some clever trick, or 2) make a minor change that would open up a lot of possibilities in general. To be honest, I've never used subversion, and only know the basics of what it is supposed to do. But not how it actually looks to the end user. If you could fill in some of the blanks for your specific need we might be able to come up with something. Also, should you decide to write your own solution, it would likely make a nice plugin for others! Another plus for the community here. I've even though of making a BoltWire plugin you could use like subversion to handle editing of the BoltWire code itself. Not sure how practical, but sounds kind of fun! Good luck with your decision. Cheers, Dan --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "BoltWire" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/boltwire?hl=en -~----------~----~----~----~------~----~------~--~---
