On Tue, Feb 9, 2010 at 2:47 AM, Stephen Bannasch <[email protected]> wrote: > github does a great job with hosting git repos and making forking and sharing > easy (but you already know this)
Yes, we like github, but right after we decided we would move directly to github they were down for most of a day. That made the decision for us...we set up our own repository server on jruby.org. Of course we will continue to mirror everything to github. > While there are things I don't like about jira on codehaus I think the > collected set of jruby issues and comments are a great resource and having > used a bunch of other systems for issues I think Jira is the best. > > I don't have a good sense of what the benefit might be of using github's > issue tracking instead of Jira. The searchability of Jira is great (as > opposed to the UI for performing searches) and I like the ability for > creation of rich comment threadson an issue in Jira. > > On the wiki page about using webstart with JRuby I was easily able to add a > url link which would show all Jira issues tagged aswebstart -- that's nice. JIRA is definitely here to stay, and despite its warts (noise UI, cumbersome search interface) it's by far the best bug tracking software I've ever used. Plus we have a large collection of issues we don't want to lose or migrate to another tracking system. There's a strong likelihood that we will set up our own JIRA server at jruby.org for the remaining kenai projects, and then at some point in the future we'll migrate JRuby's JIRA issues as well. However JRuby's JIRA is still hosted on Codehaus (for which we are very thankful!) and there's less pressure to move it right now. > I don't like trying to find things in the wiki on Kenai at all -- here > doesn't seem to be a way to search easily for a pagein the JRuby wiki itself. > I recently wrote a response to a thread on the jruby-user mailing list about > using a debugger. I had edited this pagein the past and wanted to reference > it in the email but this page was a pain to find: > http://kenai.com/projects/jruby/pages/UsingTheJRubyDebugger -- I'd like this > to be easier. > > Brainstorming about the wiki I'd like it to be easier for people to > contribute, to review contributions, to mark pages or sections as out-of-date > and to highlight when a page hasn't been edited for a long time to help folks > know when something might be out-of-date. Yes, the lack of a search is obviously a problem. We are considering moving back to a hosted Mediawiki instance on jruby.org, since we'll have all the features of Mediawiki then. But it's not set in stone...if there's a better solution (like a Ruby-based wiki, maybe with Mediawiki markup support), we're all ears. > If the wiki was easier to use I might have taken some of what I wrote in the > email to the user list about debugging and added it to the wiki page on the > debugger. How do you feel about Mediawiki wikis? > A great deal of useful info is shared in IRC -- in the past when there was an > exchange I found particularly helpful I'd addit to a wiki page. It should be > as easy as possible to get to the wiki and either find the topic already > covered, find a place to add the tip/suggestion or to know when to create, > what to name, and where to put a new page. > > A new page or section of page just written should be able to be tagged by a > writer if they'd like it reviewed for accuracy.Another reader could see this > tag and know that the writer has asked for this review and whether any > reviews/edits had taken place. Folks with more experience should be able to > easily find and review pages which have been tagged as "please check out what > I wrote". I believe Mediawiki has support for these kinds of tags and plugins. Obviously they do it on Wikipedia all the time... > It would be great to be able to get a hirearchical/searchable pdf export of > the wiki. Yeah, no export on Kenai is a bit of a pain too. Mediawiki does have an XML export, and probably has PDF export plugins too. - Charlie --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
