Hi, Peter, We are now starting to take a serious look at Greenhopper for the Image Gallery project, having installed it on UCB's local instance of JIRA. Up until now, we've used a combination of the Sakai and Fluid JIRAs. I'd prefer that we not spread things out further. It sounds like the drawbacks you cite below are not dealbreakers, especially for a contrib project. Any chance you'd be willing to install Greenhopper within the next week or so, if we decide to adopt it for the project?
Oliver Knoop, Peter wrote: > > While GreenHopper offers some cool functionality, that functionality > is dependent on certain practices in Jira that Sakai has not followed > or deviated from with custom fields, so there would have to be a bit > of education and redesign as part of this. For instance, almost no one > uses the “In Progress” step in the workflow; issues generally go from > Open to Resolved. Also, because we have the extra, non-standard > “Target Version” field, (rather than Jira’s built-in expectation of > relying on the combination of the Status and Fixed Version to > determine if an issue is planned for a release or in a release), the > drag-and-drop setting of versions in GreenHopper probably won’t work > quite right. > > So, if there are features here that you want to use in your own > project we can get it for free. However, if you’re expecting everyone > in the Sakai project to use it, then we should run this by the general > audience first to see if the community is willing to adapt its practices. > > -peter > > *From:* Allison Bloodworth [mailto:[EMAIL PROTECTED] > *Sent:* Tuesday, December 18, 2007 2:32 PM > *To:* Daphne Ogle > *Cc:* Marc Brierley; Knoop, Peter; [email protected] > *Subject:* Re: GreenHopper? > > Wow, this app does indeed seem incredibly cool from watching the > demo--thanks for the link, Marc! It sounds like we can use it for > free, too, since we are an open-source project. Perhaps we can talk > during our Thursday design team meeting about whether this is > something that team would like to try. The only question I have is > whether creating all design-related cards as separate JIRA issues > would clutter up JIRA too much...but perhaps we can have a separate > space in JIRA for design planning. > > Allison > > On Dec 17, 2007, at 5:42 PM, Daphne Ogle wrote: > > > > I don't think this was on our radar -- at least I didn't know about > it. This looks great based on the video and would save a ton of time > synching jira with our cards. And even allows us to do some reporting! > > I wonder if plug-ons fall into the free to open source projects > category? Peter, including you here in case you know. > > Thanks for pointing this our Marc! > > -Daphne > > On Dec 17, 2007, at 4:59 PM, Marc Brierley wrote: > > > > When you guys were thinking about a virtual story card system, did you > > look at GreenHopper? > > http://www.greenpeppersoftware.com/en/products/GreenHopper > > -mARC > > _______________________________________________ > > fluid-work mailing list > > [email protected] <mailto:[email protected]> > > http://fluidproject.org/mailman/listinfo/fluid-work > > Daphne Ogle > > Senior Interaction Designer > > University of California, Berkeley > > Educational Technology Services > > [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > > cell (510)847-0308 > > > > _______________________________________________ > > fluid-work mailing list > > [email protected] <mailto:[email protected]> > > http://fluidproject.org/mailman/listinfo/fluid-work > > Allison Bloodworth > > Senior User Interaction Designer > > Educational Technology Services > > University of California, Berkeley > > (415) 377-8243 > > [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > > > > ------------------------------------------------------------------------ > > _______________________________________________ > fluid-work mailing list > [email protected] > http://fluidproject.org/mailman/listinfo/fluid-work > _______________________________________________ fluid-work mailing list [email protected] http://fluidproject.org/mailman/listinfo/fluid-work
