From jleejj at gmail.com Thu Nov 1 01:56:12 2007 From: jleejj at gmail.com (Lee Johnson) Date: Wed, 31 Oct 2007 22:56:12 -0700 Subject: [Retrospectiva-general] Timeline and LDAP support? Message-ID: <149ff9930710312256l6befb303k6cc0459a8711ad29@mail.gmail.com> Hi there, Great work on Retrospectiva! I've been using Trac for about a year, but I have a preference for Ruby on Rails so I'll definitely be switching one of my company's sites over to this soon. To that end, I have a couple questions for you: 1. We've come to like Trac's "Timeline" feature to keep a pulse on how the project is going. I see that Retrospectiva has a dedicated link for the changeset history, but do you have any plans to merge changesets, tickets, wiki changes, blog entries, etc into a single stream like "Timeline"? 2. I've hacked all our sites to support Apache's REMOTE_USER and an LDAP query on first arrival to collect the person's name, e-mail, etc. This is a useful feature in corporate environments. If I create a patch for optional LDAP support in Retrospectiva, would you be interested in it? Thanks _Lee -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/retrospectiva-general/attachments/20071031/cdca94da/attachment.html From hugocf at gmail.com Fri Nov 2 13:42:05 2007 From: hugocf at gmail.com (Hugo Ferreira) Date: Fri, 2 Nov 2007 17:42:05 +0000 Subject: [Retrospectiva-general] Timeline and LDAP support? In-Reply-To: <149ff9930710312256l6befb303k6cc0459a8711ad29@mail.gmail.com> References: <149ff9930710312256l6befb303k6cc0459a8711ad29@mail.gmail.com> Message-ID: <05E4CE82-7B04-4ACD-B11A-5DDDFCF1BBB2@gmail.com> > 1. We've come to like Trac's "Timeline" feature to keep a pulse on > how the project is going. I see that Retrospectiva has a dedicated > link for the changeset history, but do you have any plans to merge > changesets, tickets, wiki changes, blog entries, etc into a single > stream like "Timeline"? I believe the "Timeline" extension gives you what you want. Changing to your installation directory, this should do the trick: RAILS_ENV=production ruby script/rxm install timeline --> instructions on extensions: http://retrospectiva.org/wiki/Extensions --> extensions for version 1.1: http://retrospectiva.org/browse/ extensions/1-1 -- Hugo -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/retrospectiva-general/attachments/20071102/84af704c/attachment.html From contact at dvisionfactory.com Fri Nov 2 17:32:52 2007 From: contact at dvisionfactory.com (Dimitrij Denissenko) Date: Fri, 02 Nov 2007 21:32:52 +0000 Subject: [Retrospectiva-general] Timeline and LDAP support? In-Reply-To: <149ff9930710312256l6befb303k6cc0459a8711ad29@mail.gmail.com> References: <149ff9930710312256l6befb303k6cc0459a8711ad29@mail.gmail.com> Message-ID: <472B9784.9080605@dvisionfactory.com> Hi Lee! I've already created a LDAP authentication plugin for Retrospectiva (uses the ruby-net-ldap GEM). I need to do a few more tests but I can hopefully release it by the end of next week). Dimitrij Lee Johnson wrote: > Hi there, > > Great work on Retrospectiva! I've been using Trac for about a year, > but I have a preference for Ruby on Rails so I'll definitely be > switching one of my company's sites over to this soon. To that end, I > have a couple questions for you: > > 1. We've come to like Trac's "Timeline" feature to keep a pulse on > how the project is going. I see that Retrospectiva has a dedicated > link for the changeset history, but do you have any plans to merge > changesets, tickets, wiki changes, blog entries, etc into a single > stream like "Timeline"? > > 2. I've hacked all our sites to support Apache's REMOTE_USER and an > LDAP query on first arrival to collect the person's name, e-mail, > etc. This is a useful feature in corporate environments. If I create > a patch for optional LDAP support in Retrospectiva, would you be > interested in it? > > Thanks > > _Lee > ------------------------------------------------------------------------ > > _______________________________________________ > Retrospectiva-general mailing list > Retrospectiva-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/retrospectiva-general > From shawn.badger at multiling.com Thu Nov 8 13:51:24 2007 From: shawn.badger at multiling.com (Shawn Badger) Date: Thu, 8 Nov 2007 11:51:24 -0700 Subject: [Retrospectiva-general] retro markup escape character Message-ID: <200711081152635.SM00860@MLShawn> Hi Dimitrij, Thanks for your good work on Retrospectiva. I really like it. I was just wondering what the escape character is for your retro markup. I didn't see it listed anywhere on the markup instruction page. Thanks, Shawn -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/retrospectiva-general/attachments/20071108/92c78499/attachment.html From nichols7 at googlemail.com Fri Nov 9 20:00:25 2007 From: nichols7 at googlemail.com (Thomas Nichols) Date: Sat, 10 Nov 2007 01:00:25 +0000 Subject: [Retrospectiva-general] Aloha and ideas Message-ID: <473502A9.7040608@googlemail.com> Hi, We have a new RoR project just starting up which will be XP/Agile driven, and Retrospectiva looks as though it may be pretty good for us - Trac does some things well, but we'd rather write mods in Ruby than in Python, and it feels like we're fighting it too much of the time, so we're looking at alternatives. I've read the Collaboa/R history, and the "extensions" architecture sounds like a good choice - so I'm just asking about future plans. Specifically -- we don't want to have to do stuff in a browser too much of the time, we'd rather be in vim/emacs hacking text - and rspecs are great for this. So what we're really after is a smooth way of hooking up R (which looks good enough to show to clients, can be used by a PM) with BDD development built around RSpecs, where a "story" (as in, an XP story) is basically defined by one or more rspecs. We want as much as possible to be driven from an editor / the commandline, with the web UI used mainly for browsing. Oh yeah -- and we want to use Markdown for wiki pages ;-) So -- would R make a good place for us to start from, and discuss how these could be implemented? And does anyone else want something similar? Or have other people tried this and would warn against it? At the moment we're seriously considering a TODO.txt under SVN control as our main ticket repo, I'm trying to come up with something better than that... so any feedback would be welcome. -- Thomas.