There is currently discussion within the Ingres engineering group on the processes that should be employed to support community contributions. In parallel, there is a discussion on the tools that can best support the community effort. An issue and bug tracker produce by Atlassian called Jira is very promising but does not offer Ingres support out-of-the-box. I produced a set of configuration files for Jira that enables Ingres 2006 to be used as the repository and went to Atlassian community site to see how to contribute the patch. I found a ticket amongst their community issues JRA-6150 where one of their engineers had made configuration changes for Ingres 2.6.
I made a similar patch file and attached it to the ticket and received a response from the engineer added as a comment to the ticket. The gist of the response was that Atlassian already supports seven databases we don’t need an eighth, especially as some are in wider use than others. Resources would be better utilized focusing on Jira features rather than database support.
I can see some of the merits of this argument but with the wealth of innovation, support and features found in Ingres should this eighth entry into the field be dismissed?
Whilst Atlassian contemplate the error of their ways you can still download the patch and apply it to Jira for a 30 day evaluation.
For the significance of the number eight take a look at Numbers in Chinese Culture where the following quote
“It is no coincidence that the Summer Olympics in Beijing are scheduled to open on 08/08/08 at 8 p.m.” taken from an article from the Herald Tribune article Numbers Game in China by Jim Yardley is taken. ![]()
2 Comments
Blatant self-promotion but if you would like to look at a issue and bug- tracker that could potentially support Ingres and can be used publicly, I would encourage you to take a look at fixx at http://hedgehoglab.com/products/fixx
The dislaimer is that we have not tested it with Ingres, but since our core ORM is based in Hibernate, I am pretty confident it will run fine with Ingres. The current documentation does not talk about connecting to external databases, but this is being updated.
Open source licensing for fixx is on it’s way, so feel free to drop us an e-mail and we would be happy to look at helping you set this up for Ingres and/or an open source license (or fee waiver).
Sarat, fixx certainly looks interesting. I’ll definitely send you an email when I try it out. Thanks.
Post a Comment