As a potential adopter, or at least someone trying to interest organisations in becoming potential adopters, I have to support this train of thought.

If it's not possible to show that there's a process in place to ensure that all the substantial changes and patches will be picked up and distributed, I can't even start talking sensibly to Health Board CIOs who are, by nature, conservative...

And with good reason. We're talking about a mission-critical application.

Cheers,
Stephen

Gary Monger wrote:
No doubt there will be branches to choose from, but adopters will want the
best from multiple branches.  A good example is the data standardization
effort underway in VA.  These releases will be must have.

The core enhancements that we're talking about will essentially define a new
distribution of VistA. Such a distribution is not viable without
incorporating many FOIA VistA patches.  Of course it won't matter until some
of these enhancements are built.  But if there isn't a plan for handling
name and number spaces, why should anyone put a lot of time into it?


-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Gregory
Woodhouse
Sent: Tuesday, January 17, 2006 10:54 PM
To: [email protected]
Subject: Re: [Hardhats-members] Attracting developers


On Jan 17, 2006, at 7:06 PM, Gary Monger wrote:

One thing that keeps coming up is the UI. A modern UI will require changes
to many packages, including Kernel, and Fileman.

I think you're right. In fact, that's one reason I've been wanting to redesign Fileman and Kernel. That sounds audacious, I know, but I don't think it's as bad as it sounds.

If these changes touch
components (routines, options, DDs, etc) that are later modified and
released by VA, then someone needs to merge the changes. Its possible that VA would incorporate some of the better releases, but not likely they would incorporate all of them. The code will diverge. Standing examples are IHS
and CHCS.  VOE will be another.

I do think it's reasonable to think that work developed by outside adopters will be incorporated into Standard VistA, but it's probably not realistic that they all will. (I could be wrong, of course.)
Essentially these are different products. They have a separate release mechanism within their own organization. They manage the name and number spaces for development against their product. If need be they merge in
releases from other organizations.  This community will need something
similar, maybe not today, but soon.

I think we need more sophisticated namespace (package) mechanism. The assumption that's going unquestioned here is the compatibility requires a non-branching version sequence, but is that really a valid assumption? I don't think so.

===
Gregory Woodhouse
[EMAIL PROTECTED]

"The universe is not required to be in
perfect harmony with human ambition."
--Carl Sagan




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Hardhats-members mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/hardhats-members



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Hardhats-members mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/hardhats-members


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Hardhats-members mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/hardhats-members

Reply via email to