Well, I will offer that if I see a specific requirements document, I will consider doing something, and that something would be done using php/pear/postgresql and that the work product would be released under a BSD license.
I've gotten paid to do that kind of work since '95. Of course ymmv given this would be pro bono. >From my perspective, the most important thing is a sound database architecture. The point here is that you might or might not like the look and feel of an implementation but what matters is the data--that's where all the retained value is. Nor for that matter does it need to be monolithic, again a good database schema + appropriate business logic in the database means that different parts could easily be partitioned + done and redone as needed without someone being saddled with the requirement of doing it all again. I assure you of course that you can specify a set of requirements that will make me have absolutely no interest in this project, nor would handing me the jira feature list likely induce me to act. -Jon >From Jeroen Ruigrok/asmodai <[EMAIL PROTECTED]>, Thu, Sep 15, 2005 at >09:10:23AM +0200: > -On [20050915 04:57], Chris Pressey ([EMAIL PROTECTED]) wrote: > >This doesn't change the fact that JIRA is closed-source. > > > >Does anyone (besides me) have objections to this on principle (rather > >than on a pragmatic basis)? > > I do have objections on that basis as well yes. > > -- > Jeroen Ruigrok van der Werven <asmodai(at)wxs.nl> / asmodai / kita no mono > Free Tibet! http://www.savetibet.org/ | http://www.andf.info/ > http://www.tendra.org/ | http://www.in-nomine.org/ > But Time, keeps flowing like a river (on and on)... >
