Replacing JIRA with an Open Source Application

I appreciate that JIRA may be considered the best of breed and that it is free of charge to this organization, but I feel that we need to be able to take any work that OSEHRA has done and "run it in somebody's basement" if OSEHRA does not succeed. Using open source codes guarantees that that transition would be possible and relatively easy to do if it becomes necessary. I also feel that we should be supporting other open source projects by using their applications and helping them improve them. Having an open source application replace JIRA would almost certainly give that open source project a high profile shot in the arm. Like it or not, OSEHRA is a new and innovative approach to working with VistA that might not survive for many reasons. I do not want to see the good work that has been done go to waste if OSEHRA goes out of existence. If the switch to something besides JIRA is made, and I hope it will be, now is the time to make the switch before there is any more data stored in it. Thank you all for your consideration and hard work. In no way am I trying to belittle the work that has been done so far. It has been excellent. -- Nancy Anthracite
like0

Comments

Replacing JIRA with an Open Source Application

Lawrence Landis's picture

On Thu, Jan 19, 2012 at 8:37 PM, Nancy Anthracite
<nanthracite@earthlink.net> wrote:
> I appreciate that JIRA may be considered the best of breed and that it is free
> of charge to this organization, but I feel that we need to be able to take any
> work that OSEHRA has done and "run it in somebody's basement" if OSEHRA does
> not succeed.  Using open source codes guarantees that that transition would be
> possible and relatively easy to do if it becomes necessary.
>
> I also feel that we should be supporting other open source projects by using
> their applications and helping them improve them.  Having an open source
> application replace JIRA would almost certainly give that open source project
> a high profile shot in the arm.
>
> Like it or not, OSEHRA is a new and innovative approach to working with VistA
> that might not survive for many reasons.  I do not want to see the good work
> that has been done go to waste if OSEHRA goes out of existence.
>
> If the switch to something besides JIRA is made, and I hope it will be, now is
> the time to make the switch before there is any more data stored in it.
>
> Thank you all for your consideration and hard work.  In no way am I trying to
> belittle the work that has been done so far.  It has been excellent.
>
> --
> Nancy Anthracite
>

Hi,

I concur with Nancy's points and would like to add...

I am not very knowledgeable in this, but have been around many
"camp fires" hearing tails of the VISTA NOIS package, and things
of the mighty VA FORUM. Wouldn't it make sense for the VISTA
world to invest in improving its own "dog food" by setting up and
growing a FORUM on the outside (e.g. via OSEHRA)?

Fancy user interfaces using EWD should be within the reach of
VISTA folks, and can continue the usefulness of widely heralded
VISTA packages which are likely far more functional and "deep".

Cheers,
--ldl

--
---
NOTE: If it is important CALL ME - I may miss email,
which I do NOT normally check on weekends nor on
a regular basis during any other day.
---
LD Landis - N0YRQ - de la tierra del encanto
3960 Schooner Loop, Las Cruces, NM 88012
651-340-4007  N32 21'48.28" W106 46'5.80"

like0

I Agree -- Though Could Go Either Way

Van Curtis's picture

We should be supporting Open Source projects as much as possible. I'm certainly a big proponent of eating one's own dog food as well, but I'd caution against being too clever getting in the way of being productive.

The good thing about reusing and extending VistA is that in theory we should have a lot of expertise in this community in how to extend it, etc...   ;-)

It has been my experience in the VA that the NOIS/FORUM tools have not translated well to the non-VistA programmers. I think if the OSEHRA community were to extend this with mechanisms such as EWD, we'd also want to do things like link our VistA-based development tools with which you're discussing replacing JIRA with the source control repository. There are already plenty of Open Source tools that do that like Trac or Red Mine to name a few.

The other thing is how OSEHRA grows up the application stack over time. Right now, we are VistA-centric, but as we start looking at layers above that and use IDEs for Java and C# (for instance), do we get into writing hooks that can be accessed programmatically by Eclipse and Visual Studio so that we can interact with our project tracking in VistA? Or do we ask programmers to manually complete various tracking steps?

So I'm not against the VistA proposal, I just wanted to point out that there additional tasks that we'd have to be willing to undertake in my opinion.

- van.

like0